Documentation

Special cases and solutions

Causes and solutions outside the regular checklist for Hyper-V backup problems.

1. In very rare cases, the VSS provider service of the virtual machine "Hyper-V Volume Shadow Copy Requester" has to be restarted 5 minutes before the Hyper-V host starts the backup each time. This may be required for a specific virtual machine that meets all other Microsoft requirements. The virtual machine only backs up in the offline or in the saved state. You can create and trigger a Windows Task Scheduler job to automatically restart this "Hyper-V Volume Shadow Copy Requester" service 5 minutes before each backup process. This would be a possible workaround. However, we recommend contacting Microsoft Support for assistance.

2. In other cases, you might encounter a Hyper-V VMMS failure while creating a Hyper-V checkpoint for certain virtual machines. You may see the following Windows event log errors - Source: Hyper-V VMMS with Event IDs 10150, 18012, 3280, and 16010. If you are having this type of problem, the following steps are a possible solution:

   1. Open the Hyper-V manager console and in the Hyper-V guest settings at the “Integration Services” tab, you need to disable the option “Backup (volume snapshot)”.
   2. Run a Hyper-V host based backup, since this option is now disabled for this virtual guest machine. This kind of backup does not use VSS method and is only to fix this kind of Hyper-V-VMSS checkpoint creating issue. Note: Do not run this backup task at regular working hours to avoid glitches during the productive virtual guest is running.
      
   3. After this one time backup without this option enabled is done,  go back to the “Integration Services” tab and re-enable the option “Backup (volume snapshot)”.
      
   4. Start a new Hyper-V host based backup and the Hyper-V-VMMS checkpoint creation errors should be gone.
      

If you still have issues we recommend to contact Microsoft Support for assistance.