This is a new installation and configuring the backup for the first time. We have two local volumes C and E and a Hyper-V guest located on E. We are trying to backup everything every night and by default windows offers to backup it all including system state,
hyperv, and the volumes.
After configuring the backup completes on System state and C: just fine and then moves to E:. Before it even displays a total drive size it calls an error and fails the backup with 'The mounted backup volume is inaccessible." The error in event log
is 0x807800C5 which in all my searches of forums seems to be related to others doing backups to network drives. I'm using the dedicated local drive option and have added the drives as valid backup destinations.
Upon further looking if I examine C:\Windows\Logs\WindowsServerBackup\Backup_error-xxxxx.log I find the following:
Backup of volume E: has failed. The mounted backup volume is inaccessible. Please retry the operation.
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: 5C9E0993-9FC4-494E-B6E7-28C7A2C22597
Caption : Backup Using Child Partition Snapshot\SERVERF-APPS-HV
Logical Path:
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Component: Host Component
Caption : Host Component
Logical Path:
*-----------------------------*
E: has roughly 5.4TB free space and is using approximately 0.5TB total. My backup drives are empty 3TB drives.
I had Shadow Copy enabled for drive E so I tried changing the size limits to No Limit and when that didn't help I disabled Shadow Copy entirely on E:.
I'm at a loss of where to go next. It's difficult for me to make many changes because I have 6 backup destinations setup for the server and the infurating problem with needing to have all the destinations plugged in before you can successfully make changes
to the backup settings is making it real difficult to try many things. I am remote to this server and had to make some serious changes to get the 6 drives all connected to begin with. (Yes, I read and tried all the command line suggestions which used to work
on 2008 R2 just fine and now don't in 2012.)
Jeremy Regehr