Configuration:
Windows Server 2012 R2
Running as a domain controller
Backing up to 2 external hard drives attached via eSATA
External hard drives are encrypted using BitLocker
Windows Server Backup is configured to backup to both drives as volumes.
Error:
Both drives must be attached to the server on boot. If they aren't, errors ensue.
When opening the Windows Server Backup GUI the following message is displayed:
A fatal error occurred during a Windows Server Backup snap-in (Wbadmin.msc) operation.
Error details: The Windows Server Backup service has stopped..
Close Wbadmin.msc and then restart it.
In the Event Viewer, there is an Application error with Event ID 1000:
Faulting application name: wbengine.exe, version: 6.3.9600.17415, time stamp: 0x54504543
Faulting module name: wbengine.exe, version: 6.3.9600.17415, time stamp: 0x54504543
Exception code: 0xc0000005
Fault offset: 0x000000000011e4d7
Faulting process id: 0x1308
Faulting application start time: 0x01d08451e1f1960b
Faulting application path: C:\Windows\system32\wbengine.exe
Faulting module path: C:\Windows\system32\wbengine.exe
Report Id: 257ca2e7-f045-11e4-80d2-001e67c53a63
Faulting package full name:
Faulting package-relative application ID
Attaching both drives does not fix the problem, but rebooting after both drives are attached does fix it. If both drives are attached on boot, one can be removed and Windows Server Backup will function correctly until the next boot. This leads me to believe that Windows Server Backup is looking for both drive on boot and failing in some way if they are not available. The desire is to rotate one drive offsite for disaster recovery, so having both attached on every boot is undesirable. Windows Server Backup works with this configuration without problem on Windows Server 2008 R2 and Windows Server 2012.
Deleting the catalog using "wbadmin delete catalog" and then recreating the backup schedule did not help. Is there anything obvious that I'm missing?
