Hi,
First, SCS DPM 2012 does not support being installed on a Windows server 2012 or protecting Server 2012 until after SCS 2012 Sp1 ships later this year.
System Center DPM 2012 is not supported running on Windows Server 2012 until we release System Center SP1 later this year. We have had reports of DPM 2012 console crashes when navigating to the recovery tab if DPM 2012 is installed on Windows server
2012. This issue is fixed in SP1.
If you are already in this condition, I recommend you backup the DPMDB, rebuild the DPM server using Windows 2008 R2 install DPM 2012, then restore your current database. The process is explained in the below technet article.
Recovering DPM servers
http://technet.microsoft.com/en-us/library/jj244606.aspx
We also do not support protecting Windows Server 2012 using SCS DPM 2012 until after SC SP1 is released. Please do not expect any support for DPM 2012 running on Windows Server 2012, or issues while protecting data sources in Windows Server
2012.
However, with that said here are the general conditions that make a VM go into a saved state during backup.
Protecting Hyper-V machines
http://technet.microsoft.com/en-us/library/hh757866.aspx
Conditions when DPM fails to back up Hyper-V virtual machines in an online state
By default, System Center 2012 Data Protection Manager (DPM) performs a backup of a Hyper-V Virtual Machine (VM) in an online state. However, DPM cannot back up a Hyper-V VM in an online state, if one or more of the following
conditions are true:
- 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.
These conditions are set by the Hyper-V writer. In such a case, the VM is put in a saved state before a snapshot of host volumes are taken (except when the VM is turned off) for a backup. The Hyper-V writer adds the VM in the following format:
- For offline backups: Backup Using Saved State\<VMName>
- For online backups: Backup Using Child Partition Snapshot\<VMName>
Additional reason if we have less than 300MB free space on a volume in the