Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Problem Description;

I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :)
Full Error Description;

Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 secError: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec





Explanation;

 This can happen with overloaded servers. When the server you're trying to backup is a busy or handles a lot of services at the same time, the Veeam backup server times out to take a snapshot. 

 The solution involves increasing the timeout value for the VSS on the Veeam server. The default value is 15min and usually you can get around this issue by increasing this value to 30min.
Solution;
  1. Logon to your Veeam server and start "Regedit"
  2. Find the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication" and add a new DWORD (32-bit) key with the VALUE "180000" (30 minutes) Decimal.
  3. Go to "Services.msc" and restart the "Veeam Backup Service" service and try again to run your backup job!


Location: Montreal, QC, Canada

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more