Saved State: Why some Hyper-V Virtual Machines are Paused when a Backup is Started
What is the Hyper-V Saved State?
Some Hyper-V virtual machines briefly go offline into a "Saved State" at the initial phase of a backup. While the backup is running, they usually come back online after a couple of seconds.
The decision to pull Hyper-V virtual machines offline into a Saved State is done solely within Hyper-V Management Services. Backup utilities have no way to force a live backup when Hyper-V determines it can't and shouldn't be done.
New:Use our VssDiag tool to find out why your VMs are being pulled into Saved State
There are many factors that are considered by Hyper-V when it decides whether to take a VM offline or not:
Hyper-V Live Backup Requirements
To achieve zero downtime live backups of virtual machines, you need the following conditions met:
1. The VM guest needs to have Integration Services installed, enabled, and running (COM System Application Service, Distributed Transaction Coordinator Service, and Volume Shadow Copy Service). Also review the VM settings in Hyper-V, the 'backup' option needs to be checked.
2. All disks involved need to be formatted with NTFS, including the disks within the VM.
3. The Volume Shadow Copy Service and related VSS services need to be enabled and running.
4. The shadow copy storage space for each drive must be available to Hyper-V VSS Writer and be located at the same volume. For instance, the storage space for drive C: needs to be on drive C: itself, and so on. Use the VSSADMIN command from the command line to check the settings. (Use: vssadmin list shadowstorage / vssadmin resize shadowstorage)
5. Ensure the VMs are partitioned using 'basic disk' formatting. At the moment Hyper-V does not support live backup for VMs formatted using dynamic disk partitioning or GPT.
6. Ensure you have at least about 20% free space on each drive involved, such as the drive on the host and the VM's main system drive.
7. Ensure plenty of un-fragmented RAM is available on the host. If a machine is pulled into Saved State, Hyper-V may not be able to bring the VM back online if it can't allocate a continuous block of RAM. Note that there may be sufficient total RAM available but not enough to place a single block. You should therefore aim to keep at least 512 MB to 1 GB of RAM free when all VMs are powered up.
8. Microsoft has released new integration services for Linux (3.5) here: http://www.microsoft.com/en-us/download/details.aspx?id=41554&WT.mc_id=rss_alldownloads_all
What to Do Next
If the problem persists check all Hyper-V logs in the Event Viewer. Hyper-V may be logging the reason in the Hyper-V logs found in the Windows Event Viewer.
If you haven't installed BackupChain backup software, give it a try today! The trial is fully functional!
Contact support ( 1-844-717-5612 or call your Priority Support number) if the problem persists.