Problems initially presented as a Backup Exec job completing with exceptions with the following message in the Job Log
Backup- PTISVR2
– AOFO: Initialization failure on: “D:”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11226 – VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider selected returned: “Unexpected provider error”. Ensure that all provider services are enabled and can be started. Check the Windows Event Viewer for details.
Backup- \\PTISVR3.domain.local\System?State
VSS Snapshot warning. File c:\windows\system32\nhsrvice.exe is not present on the snapshot.
VSS Snapshot warning. File c:\windows\microsoft.net\framework\v2.0.50727\aspnet_state.exe is not present on the snapshot.
Backup- \\PTISVR1.domain.local\System?State
VSS Snapshot warning. File %BeBootDrive%\bootmgr is not present on the snapshot.
Checked Event log and found several entries in the application Log with a source of VSS, one of which said…
VssAdmin: Unable to create a shadow copy: The shadow copy provider had an unexpected error while trying to process the specified command.
Command-line: ‘C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\\?\Volume{9ccebbf8-08ab-11e2-93de-3440b5884b71}\’.
I tried to execute the command C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\\?\Volume{9ccebbf8-08ab-11e2-93de-3440b5884b71}\ at the command line and received the same error.
Executed vssadmin list shadowstorage and discovered {9ccebbf8-08ab-11e2-93de-3440b5884b71} was D: drive.
Navigated to my computer and right clicked D: drive. Click on Shadow Copies tab. The list of available shadow copies was 18months out of date! Deleted the shadow copies, recreated the settings (can’t remember how it came about but the settings seemed to disappear?! Recreated with a storage area of C:\ and 4096 use limit.). Re-executed C:\Windows\system32\vssadmin.exe Create Shadow /AutoRetry=15 /For=\\?\Volume{9ccebbf8-08ab-11e2-93de-3440b5884b71}\ and it completed successfully.
Waiting to see if it solve the Backup Exec problem.