[KNOWN ISSUES] 6.5 : Known Issues, Patches and Hot fixes

Availability for the Always-On Enterprise

[KNOWN ISSUES] 6.5 : Known Issues, Patches and Hot fixes

Veeam Logoby Gostev » Sun Dec 23, 2012 5:05 pm

Topic for tracking known issues, patches and hot fixes for Veeam Backup & Replication 6.5
Gostev
Veeam Software
 
Posts: 21648
Liked: 2433 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Patch #1 (build 6.5.0.128) [December 24, 2012]

Veeam Logoby Gostev » Sun Dec 23, 2012 5:10 pm

Resolved Issues

General
• Application-aware processing takes significantly longer on some virtual machines than it used to with the previous product versions.
• Disk space check may be failing on certain CIFS-based backup repositories with the following warning: "Could not perform threshold check for backup location [backup repository name] due to space info retrievement fail!"

VMware
• Under certain circumstances, the job will not attempt to remove the VM snapshot left behind by the previous job run.
• Quick migration does not support virtual hardware version 9 VMs.
• SureBackup virtual lab cannot be created on ESX host with SSH connection credentials supplied.
• After upgrading ESX to ESXi, Veeam jobs fail with the following error: "The object has already been deleted or has not been completely created"
• Attempting to backup a VM from free ESXi host results in unclear error logged.

Hyper-V
• Rebooting Hyper-V host may occasionally result in resetting changed block tracking data.
• Under certain circumstances, jobs are unable to leverage changed block tracking data with the following error: "Failed to flush change tracking data for VM"
• Changed block tracking driver reliability enhancements for tracking virtual disk files larger than 2TB.
• Upgrading to this and following patches and releases should no longer require Hyper-V host reboot to finalize driver installation.

Veeam Explorer for Microsoft Exchange
• Auto import of Microsoft Exchange mailbox databases fails with the "Failed to open exchange store" error for configurations with both mailbox databases and transaction logs located at the same path on different volumes.
• Items restored back to original mailbox are incorrectly marked and acting as Drafts.
• Restoring the complete mailbox to the original location fails with the "Object reference not set" error.
• Veeam Explorer for Microsoft Exchange will not start on certain localized operating system versions.

Veeam Explorer for SAN Snapshots
• Increased default timeouts for communication with storage to prevent "Failed to execute CLIQ command" errors in large infrastructures.

Veeam ONE integration
• Backup repository status queries do not close network connections properly, and are adding up. Eventually, this may result in backup repository hanging.

B&R 6.5 Patch 1 is superseded by Patch 3 (see below)
Gostev
Veeam Software
 
Posts: 21648
Liked: 2433 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Patch #2 (build 6.5.0.133) [February 11, 2013]

Veeam Logoby Gostev » Sun Apr 28, 2013 6:30 pm

Required for Veeam Backup & Replication Cloud Edition.
Brings no additional fixes or enhancements.

Distributed as a part of the Cloud Edition ISO.

B&R 6.5 Patch 2 is superseded by Patch 3 (see below)
Gostev
Veeam Software
 
Posts: 21648
Liked: 2433 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Patch #3 (build 6.5.0.144) [April 22, 2013]

Veeam Logoby Gostev » Sun Apr 28, 2013 6:32 pm

Resolved Issues

General
• Application-aware image processing may cause Windows Server 2012 Domain Controller to stop booting if VM is configured to use EFI.
• File level recovery process hangs on dynamic disks with partitions size being multiple of 4GB.
• Re-IP fails for replicas if host where replica VM was originally created is deleted from the cluster.
• Disabled ability to move folders in the Files tree with Shift + drag and drop operation because this functionality is not fully implemented and may result in data loss if the move process is cancelled.

VMware
• Adding virtual disks that were originally excluded back to the job results in wrong change ID used during the first incremental backup.
• Upgrading vCenter or ESX(i) hosts may result in duplicate hosts appearing under Managed Servers, causing jobs to fail with object not found errors.
• VM Copy job always logs the following warning when the target is another VMFS datastore: "Could not perform threshold check for backup location."
• Deleting temporary VM snapshot manually instead of letting the job delete it results in vCenter connections duplication. As the result, vCenter Server may stop responding due to too many connections already opened with the following error: 503 Service Unavailable
• Under certain circumstances, additional registry processing required for SureBackup jobs and re-IP addressing may cause registry corruption with VM failing to boot with the following error: "System hive error" or "Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
• If vCenter Server is registered with Backup Infrastructure twice (as vCenter Server, and as a Windows server), replica seeding and backup mapping fails with the following error: "Cannot find VM in the backup file specified for seeding."
• Improved performance of enumerating infrastructure objects in large vSphere deployments.

Hyper-V
• Changed block tracking (CBT) driver does not monitor newly appearing virtual disks on volumes that were in redirected access mode at the time when CBT driver started. This results in full scan incremental runs for the affected virtual disks with the following warning: "Failed to flush change tracking data before snapshot."
• Adding virtual disk files located on volumes mounted into the folder under changed block tracking fails with the following error: "The device object parameter is either not a valid device object or is not attached to the volume specified by the file name."
• Instant VM Recovery fails if virtual disk files are located on a mount point.
• Copying very large files from Windows Server 2012 CSV volume may consume lots of host memory.
• Under rare circumstances, backup file update may fail with the following error: "Failed to store all blob data at the metastore."

Veeam Explorer for Exchange
• Exporting a very large amount of individual items may use up all available system memory.
• Opening certain mailbox databases may fail with the "Jet error -1206" error when Veeam Backup & Replication is installed on Windows 8 or Windows Server 2012.
• Restoring emails that were sent using Outlook Web Access (OWA) fails with the following error: "Error code: ErrorItemSavePropertyError".

PowerShell
• Start-VBRInstantVMRecovery cmdlet fails with the following error: "Cannot complete login due to an incorrect user name or password."

B&R 6.5 Patch 3 is available for download starting April 22, 2013 (KB1751)
Gostev
Veeam Software
 
Posts: 21648
Liked: 2433 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: baber, Google [Bot], tdewin and 1 guest