Link to home
Start Free TrialLog in
Avatar of parklandindustries
parklandindustriesFlag for Canada

asked on

Backup Exec 11d question

I am running Symantec Backup Exec 11d and have been running into a few errors. I have a few different servers rolled into one job (backing up all files, no databases). Sometimes, not all the time, I will get a notification saying the job failed. When I check the log, it tells me a particular section cannot be backed up and the specific error report says:

Snapshot provider error (0x2): The system cannot find the file specified.
Check the Windows Event Viewer for details.
V-79-57344-37907 - Snapshot error during backup. Set has been canceled.

The selection is not always the same either. So I'm not sure if the problem resides with the selection(s) or within Backup Exec. After researching a bit on Syamntec's website, I found two possible options. Either change the snapshot provider to Microsoft VSS from VSP, or increase the file cache size on the Advanced Open File Wizard.

Can anyone help out and provide me with some direction? I can provide more info as well.

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Iamthecreator
Iamthecreator
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Also, it is recommended to avoid mixing database backups with file system backups especially if it is not required to backup databases using VSS. It is recommended a separate backup job should be created for each type of backup. Some systems lack the available resources to snap all the selections in one backup job and hence splitting of the backup jobs is beneficial
If you are backing up server which does not have enough space to accomodate the snapshot then runing the AOF wizard on the backup exec server to specify the size of the cache file would be recommended
Avatar of parklandindustries

ASKER

Thanks for the input.

After running this command on 2 servers that have failed in the past with error, all the writers came back as Stable with no errors. Does the status on the writer reset after so long? Should I run the command as soon as possible after the job fails?

When you say not to mix file system selections with database selections, where do shadow copy components and system state fall? Currently we have both running in the same job as file systems.

Also, how am I to tell the size of the snapshot to make sure there is enough space on the drive/server? By default where are the snapshots created and how long do they stay there?
The VSS writers are re-initialized upon a server restart and can also be stabilized by a function call from some other application after the failed backup in BEWS.The backups will fail with that error only if BEWS try to backup resources when the concerned writers are unstable or not running
Apply the latest SP for the OS
By default the VSS snapshot are stored in the SYS VOL and deleted upon completion of the backup
The SYSTEM STATE and Shadow Copy Components also require the VSS writers
By not mixing the FILE Folder backups with DATABASE backup it was intended  to separate any DB backup from the AOFO (snapshot ) backup
The SYSTEM STATE or SHADOW COPY COMPONENT backup will use the VSS irrespecitive of the AOFO option selected