We run Hyper-v on Server 2012 and have an issue with the vss writer not using online backup.
When we were running 2008R2, we had the same problem, but only with a couple of VM's, now we have gone to 2012 Hosts we have about 12 VM's that wont backup in online state.
When I list writers, it shows "Backup Using Saved State" for the VM's under Microsoft Hyper-v VSS Writer, so it would be a Hyper-v problem and not with DPM.
I have checked the Microsoft list of reasons when you cannot perform an online backup, but none of those apply.
How can I diagnose what is preventing the Hyper-v VSS Writer perform online backup?
Was verifying that you have the Integration Components inside the VMs up to date one of those MSFT things to check?
All the ICs in the VMs must be at the level of the hypervisor the VMs are running on. So if they were not updated, begin there.
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will.
Please confirm your child vm follows up the following conditions. By default, DPM 2010 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.
• VM has one or more dynamic disks.
• VM has one or more non-NTFS based volumes.
• The VM Cluster Resource Group in a cluster setup is offline.
• VM is not in a running state.
• A ShadowStorage assignment of a volume inside the VM is explicitly set to a different volume other than itself.
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>
Conditions When DPM Fails to Back up Hyper-V Virtual Machines in an Online State
Hope this helps.
I have check those conditions and they are not applicable.
I have noticed that Hyper-v manager shows the Heartbeat as "no contact" and when I look at the services on the guest, the Hyper-v intergration services are not running. When trying to start the Hyper-v VSC Requestor, I get Error 1083: The executable program that this service is configured to run in does not implement the service In Event viewer it shows as Event 7000.
I have installed the latest Intergration Services. I tried to find out how to uninstall Intergration Services in order to install a fresh copy, to no avail. Before I moved these machines to Server 2012 Hosts they were working correctly on 2008R2 Hosts. Should I have somehow removed Hyper-v Intergration Services first?