> KB 1714

Patch 1 Release Notes for Veeam Backup & Replication 6.5

KB ID: 1714
Products: Veeam Backup & Replication
Version: 6.5.0.109
Published:
Created: 2012-12-24
Last Modified: 2013-01-02

Challenge:

These are the issues resolved by the Patch 1 for Veeam Backup version 6.5.0.109All patches are cumulative so each below fix is contained in this patch.

Cause:

Please confirm you are running version 6.5.0.106 or 6.5.0.109 prior to applying this patch.  You can check this under Help | About in Veeam Backup & Replication console.  After upgrading, your build will be version 6.5.0.128.

Solution:

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 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
• Autoimport 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 following error: "Object reference not set"
• 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.

More Information:

To obtain the patch please download it from: 
Download
How helpful is this article:
Rating: 4 / 5 (6 votes cast)
‹‹ Back to knowledge base search

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!