I have been struggling to get backups to succeed using Windows Server Backup on Windows Server 2008 R2.
The machine is running HyperV with about 8 running VM’s.
The machine would hang for about 10 minutes before failing to backup. I have included all the symptoms at the bottom of this blog post. I solved my issue by enabling the auto mounter on the host machine.
Perhaps the HyperV VSS writer uses the auto mounter to connect to the shadow copies on the guest VM’s?
Solution
The solution for this is to enable disk auto mounting. Open a command window with elevated privileges and run:
diskpart
Check the status of auto mount by typing automount into the DISKPART window.
Automatic mounting of new volumes disabled.
Enable auto mount by typing automount enable
Type exit
Related Articles
http://blogs.technet.com/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
http://social.technet.microsoft.com/Forums/en-US/winserverfiles/thread/9cf42e8a-2a33-47c5-a797-269330e9ba1a
http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/313b46c6-5581-496f-9937-36e9dc33948d
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/2c9bbe55-3931-4a54-a4dc-5e15debc4a47
Symptoms
Windows Server Backup fails with the following error message:
Status: Failed Creation of shared protection point timed out.
The following is recorded in the Windows Application log
The backup operation that started at ‘2010-04-09T00:40:45.524000000Z’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code ’2155348129′. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
The command vssadmin list writers displays the following error:
Writer name: ‘Microsoft Hyper-V VSS Writer’
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {fe2b0556-d9e8-47e5-9e0f-e6ba44216f3d}
State: [5] Waiting for completion
Last error: Unexpected error
The following warning is recorded in the application log 10 or so minutes after the backup fails.
Volume Shadow Copy Service error: The shadow copy writer could not communicate with the Shadow Copy publisher. The shadow copy publisher (for example the backup application) might have terminated during the shadow copy process. hr = 0x800706ba, The RPC server is unavailable.
.
Operation:
Gathering Writer Data
Context:
Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Name: Microsoft Hyper-V VSS Writer
Writer Instance ID: {fe2b0556-d9e8-47e5-9e0f-e6ba44216f3d}
Volume Shadow Copy Service error: The shadow copy writer could not communicate with the Shadow Copy publisher. The shadow copy publisher (for example the backup application) might have terminated during the shadow copy process. hr = 0x800706ba, The RPC server is unavailable..
Operation: Gathering Writer Data
Context: Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Name: Microsoft Hyper-V VSS Writer Writer Instance ID: {fe2b0556-d9e8-47e5-9e0f-e6ba44216f3d}
For each virtual machine an entry is recorded under logs \Microsoft\Windows\HyperV-VMMS
No snapshots to revert were found for virtual machine ‘xxx’. (Virtual machine ID xxxxx )