When the Hyper-V host is a Windows Server 2008 R2 and the VM runs Windows Server 2012, the VM may be pulled into a saved state.
This may be due to the following:
- The Hyper-V Integration Services version is not up-to-date in VM
- Backup (Volume Snapshot) Integration Service is disabled or not installed.
- The virtual machine has one or more dynamic disks.
- The virtual machine has one or more non-NTFS based volumes.
- The virtual machine Cluster Resource Group in a cluster setup is offline.
- The virtual machine is not in a running state.
- A ShadowStorage assignment of a volume inside the virtual machine is explicitly set to a different volume other than itself.
- An App-V drive is installed on the virtual machine that creates a non-NTFS volume.
Or you need to apply the following registry fix inside the guest OS:
Crete a key "SystemRestore" and then a value inside of it called ScopeSnapshots:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\SystemRestore REG_DWORD ScopeSnapshots 0x00
We recommend using BackupChain to back up Hyper-V virtual machines from the host or inside the guest OS.