You may notice SureBackup job performance degaradation and higher space utilization after upgrading to Veeam Backup & Replication 9.5 U4.
Upgrade to Veeam Backup & Replication 9.5 U4 has changed the default location for redo logs for verified VMs impacting original Virtual Lab configuration in VMware environment. Originally redo logs (auxiliary files used to keep changes that take place when VMs run in the virtual lab) were stored on a datastore in the virtual environment specified in the Virtual Lab wizard, but in Veeam Backup & Replication 9.5 U4 redo logs are stored on the vPower NFS server by default.
The hotfix provided here is intended for customers with Virtual Labs existing prior to the update. The hotfix will revert the changes made in U4 and forces SureBackup VM's redo logs to be written to the datastore which was chosen in the Virtual Lab settings. As an alternative you may choose to create new Virtual Lab(s) and reconfigure existing SureBackup jobs to use the newly configured Virtual Lab and remove the old Virtual Lab.
- Ensure that all jobs are in a stopped state.
- Stop all services on the Veeam Backup server that begin with Veeam. (PowerShell: gsv Veeam* | spsv )
- Navigate to the Veeam installation folder on the Veeam Backup Server (by default it is C:\Program Files\Veeam\Backup and Replication\Backup)
- Rename the Veeam.Backup.Model.dll file to Veeam.Backup.Model.dll_backup
- Replace the files listed in the previous step with those found in the hotfix package
- Start Veeam services on Veeam Backup server. (PowerShell: gsv Veeam* | sasv )
MD5 for Veeam.Backup.Model.dll: 8fe3a782a42094b248a3321af1f9d54f
SHA256 for Veeam.Backup.Model.dll: deaaaff1d42d30e41fc19d9f9dba6efebc0e2c0277aa0c7992076760868f7fbf
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.