11-07-2011 08:40 PM
Hi Symantec community,
I have recently installed Backup Exec 2010 R3 SBS edition on my SBS2K11 server.
Previously using Acronis Backup and Recovery, however the backups are now failing with errors and I am unable to identify the issue to allow for a successful backup. I have searched the backup exec knowledge base, checked the configuration made amendments according to their knowledge base with no result.
I suspect it is a VSS issue but VSS has no issues running at all and the vssadmin tool reports no error. I really need to get a Full backup running successfully. Please review the errors found below.
The backup is running to a B2D folder on an external drive which is accessible with appropriate rights.
Backup Exec errors:
“Error: e00084af - The directory or file was not found, or could not be accessed.”
"Storage device "Backup2Disk Folder" reported an error on a request to write data to media.
Error Reported:
The process cannot access the file because it is being used by another process.
V-7957344-34036 - An unknown error has occured."
Event Log
Event ID: 13
“Volume Shadow Copy Service information: The COM Server with CLSID {79079d5c-ef20-4952-b9fc-cfd443b38641} and name SW_PROV cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Operation:
Obtain a callable interface for this provider
List interfaces for all providers supporting this context
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {f782463b-33bb-4043-ad8d-60b728d26a6c}
Class ID: {79079d5c-ef20-4952-b9fc-cfd443b38641}
Snapshot Context: 0
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {00000000-0000-0000-0000-000000000000}
Volume Name: \\?\Volume{02b248c4-a9e8-11e0-a987-1c6f65d6c17f}\
Execution Context: Coordinator”
Event ID 12292
“Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {79079d5c-ef20-4952-b9fc-cfd443b38641} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Operation:
Obtain a callable interface for this provider
List interfaces for all providers supporting this context
Check If Volume Is Supported by Provider
Add a Volume to a Shadow Copy Set
Context:
Provider ID: {f782463b-33bb-4043-ad8d-60b728d26a6c}
Class ID: {79079d5c-ef20-4952-b9fc-cfd443b38641}
Snapshot Context: 0
Snapshot Context: 0
Execution Context: Coordinator
Provider ID: {00000000-0000-0000-0000-000000000000}
Volume Name: \\?\Volume{02b248c4-a9e8-11e0-a987-1c6f65d6c17f}\
Execution Context: Coordinator”
Look forward to reading your comments.
Solved! Go to Solution.
11-07-2011 08:46 PM
Have you looked at www.symantec.com/docs/TECH65148
11-07-2011 08:46 PM
Have you looked at www.symantec.com/docs/TECH65148
11-08-2011 07:50 PM
Hi VJware,
After reading your comment I decided to do some digging. Found my previous backup software has left its VSS behind. I went into the backup exec settings and have selected to use windows VSS to produce a snapshot.
Is it best to use windows or Symantec VSS?
Thanks for your response.
11-08-2011 07:59 PM
Win 2k3 & later will use microsoft VSS...So choosing snapshot provider - System - Use Microsoft Software Shadow Copy Provider is a good choice
11-10-2011 04:29 PM
Thanks for your assistance