Veeam Backup & Replication 4.1.1
Released: February 18, 2010
Build version: 4.1.1.105
To download the latest version, please follow this link:
http://www.veeam.com/vmware-esx-backup/download.html
For complete list of enhacements and resolved issues, please refer to the Release Notes document:
http://www.veeam.com/veeam_backup_4_1_1 ... tes_rn.pdf
Please consider upgrading if you can be affected by some of the resolved issues.
-
- Chief Product Officer
- Posts: 31754
- Liked: 7259 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
-
- Chief Product Officer
- Posts: 31754
- Liked: 7259 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [4.1.1 INFO and UPDATES] Last updated: May 19, 2010
Cumulative update for version 4.1.1
Released: May 19, 2010
Resolved issues
• Workaround for ESX4 changed block tracking issue with snapshot reversal. For more information, please refer to VMware KB, and this topic.
• Under rare circumstances, Veeam Backup job may fail to correctly initiate Retry cycle.
• vCenter events logged by Veeam Backup contain incorrect job status information, always showing jobs as failed.
• On certain Windows 2008 configurations, network connection used for Veeam VSS processing may remain open after backup completes.
• Occasionally, running job can be incorrectly marked as Failed with the Job has failed unexpectedly error logged in the sessions' history while the job is still running. This does not affect job execution, the job finishes correctly with backup file properly created.
Please consider upgrading if you can be affected by some of the resolved issues.
To obtain the update, please contact Veeam Technical Support.
Released: May 19, 2010
Resolved issues
• Workaround for ESX4 changed block tracking issue with snapshot reversal. For more information, please refer to VMware KB, and this topic.
• Under rare circumstances, Veeam Backup job may fail to correctly initiate Retry cycle.
• vCenter events logged by Veeam Backup contain incorrect job status information, always showing jobs as failed.
• On certain Windows 2008 configurations, network connection used for Veeam VSS processing may remain open after backup completes.
• Occasionally, running job can be incorrectly marked as Failed with the Job has failed unexpectedly error logged in the sessions' history while the job is still running. This does not affect job execution, the job finishes correctly with backup file properly created.
Please consider upgrading if you can be affected by some of the resolved issues.
To obtain the update, please contact Veeam Technical Support.
Who is online
Users browsing this forum: chris.childerhose and 60 guests