Veem job Failed to prepare guest for freeze, wait timeout 900 sec
Backup
Technology: Veeam
Sometimes Veeam backup jobs failed on VM with
below error message continuously.
Failed to prepare guest for host backup. Error:
VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Error: VSSControl: Failed to prepare guest for
freeze, wait timeout 900 sec
We need to follow the below steps to resolve
the issue.
Cause:
This issue typically involves a very active
transactional application running in the virtual machine, and it is taking
longer than expected per the default timeout to freeze the I/O for this
application/VM
Solution
You can change this timeout by
modifying the value in the registry of the server where Veeam Backup
& Replication is installed as follows:
1. Go to Veeam registry path HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam
Backup and Replication.
2. Add a DWORD (32-bit) value named
VssPreparationTimeout. The value is in milliseconds (decimal), the default
timeout is 900000, which equals to 15 min.
Set the value to 1200000. This will change the timeout to 20 minutes.
Set the value to 1200000. This will change the timeout to 20 minutes.
3. Restart the Veeam services.
You may need to increase the timeout up to 30 minutes (1800000) in certain cases.
For versions prior to v7:
On x64 platforms, the registry key should be additionally created under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Veeam\Veeam Backup and Replication
If the VM is a vCenter machine with a local database (local instance of SQL), or a SQL machine which hosts a vCenter database, the job needs to be reconfigured: the VM should be added to the job via a standalone host (not via vCenter). For more information, refer to the following KB article:
http://www.veeam.com/kb_articles.html/KB1051
This also could be due to failing VSS writers. You should run vssadmin list writers and verify they are all in a stable / no-error state first.
ReplyDeleteMost think the Microsoft VSS writers are a Veeam issue for some reason instead of Microsoft.
So you can perform a manual shadow copy and then check to see if the writers are failing afterwards. Otherwise, you can perform a Windows Server backup (with all VSS options enabled) as both of these do the same exact thing as when Veeam is in the picture and sends out API calls to leverage VSS.
More than likely, your event viewer logs are best to point you towards other issues.