Veeam vient de publier le 13 février 2014 un nouveau patch pour sa version 7.0 R2.
Le patch est téléchargeable à partir du lien : Télécharger
Cette publication apporte plusieurs améliorations, et en particulier en terme de performance.
En plus de nombreuses corrections, de fix et bugs corrigés, ce patch 3 apporte des nouvelles fonctionnalités:
Les fonctionnalités ci-dessous sont issues de la KB 1864.
- Significantly reduced load on SQL Server hosting the configuration database, and improved performance of various job activities and user interface operations.
- Improved vCenter Server hierarchy enumeration logic to speed up vCenter Server registration process in a few times.
- Intelligent load balancing can now be configured to give preference to backup proxy located on the same host using the EnableSameHostHotaddMode(DWORD) registry value.
- Replication jobs should now fail immediately upon encountering fatal error, rather than wasting time performing additional operations that are no longer relevant.
- Added timeouts on all snapshot operations, including snapshot creation, deletion, import to off-host proxy, and reading snapshot data to prevent conditions with stuck snapshots due to environmental issues.
- Maximum volume snapshot life time is now customizable using the hvSnapshotLifeTimeHour (DWORD) registry value. Default value is 72 hours, but customization may be necessary to allow full backup of very large VMs on slow backup hardware.
- Added ability to configure SCVMM communication timeouts using the SCVMMConnectionTimeoutMinutes (DWORD)
- Support for downloading files larger than 4GB.
Built-in WAN acceleration
- Data processing performance has been further improved by up to 25% comparing to R2 update.
Multi-OS File level recovery
- Added support for file names with Unicode characters.
- Support for backing up files with file names longer than 260 characters, and directory names longer than 248 characters.
- Support for devices that do not implement sending error in response to attempt of writing to write protected tape.
- Support for devices that do not implement sending the end of media event, such as certain IBM tape drives. Capacity for such drives is now controlled by the job.
- Support for devices that do not implement drive enumeration in the drivers correctly. Such tape devices are now additionally queried for drives with SCSI commands.
- Column sizes and sorting rules will now persist for each user in all grids and views.
- Disabling GFS retention in Backup Copy job now offers to remove the existing full backup along.
- Backup file repair process is now reported with the dedicated job status.
This update adds full support for rotated media with all job types and backup modes removes the need of using additional scripting. The new functionality is controlled by the following registry values:
- ForceCreateMissingVBK (DWORD)
Enables support for rotated drives. With this functionality enabled, if any backup file from the latest full backup chain is missing (such as when the existing hard drive is replaced by another one), jobs will start the new backup chain and create the new full backup (instead of failing out).
Set to 1 to enable support for rotated drives.
- ForceDeleteBackupFiles (DWORD)
Enables automatic cleanup of the backup repository from ALL existing files if any backup file from the latest full backup chain is missing (such as when the existing hard drive is replaced by the hard drive brought back from offsite location, and containing some older backup files).Set to 3 to make the job delete the entire contents of the backup job’s folder only.Set to 5 to make the job delete the entire contents of the root backup repository folder, thus potentially deleting any files belonging to other jobs along. Note that if backup repository points at the volume’s root folder, the entire volume’s contents is erased.