[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Backup Exec 11d question

Posted on 2009-03-30
5
Medium Priority
?
463 Views
Last Modified: 2013-12-01
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
0
Comment
Question by:parklandindustries
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 23

Accepted Solution

by:
Iamthecreator OM earned 1500 total points
ID: 24037719
Even if you select the option for MS VSS or set the cache size the problem might persists
Whenever the backup fails with the VSS error check the status of the writer on the concerned server (hosting the resources to be backed up) by running the following command
VSSADMIN LIST WRITERS at the prompt
it will list all the writers and the current state
if any writer comes up as WAITING FOR COMPLETION or  FAILED the  you have an issue with  the VSS
ensure that you have the latest service pack installed if its W2k3 or W2K8 server
MS has released quite a few hotfixes over a period of  time to resolve VSS related issue and all of them are included in the latest SP
W2K did not have VSS so if you are receiving the error on a W2K box then the issue lies with the VSP
 
Also ensure that u are not trying to use the AOFO option on a resource  that cannot be snapped for instance a network drive
0
 
LVL 23

Expert Comment

by:Iamthecreator OM
ID: 24037728
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
0
 
LVL 23

Expert Comment

by:Iamthecreator OM
ID: 24037738
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
0
 

Author Comment

by:parklandindustries
ID: 24040968
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?
0
 
LVL 23

Expert Comment

by:Iamthecreator OM
ID: 24078299
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
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is an update and follow-up of my previous article:   Storage 101: common concepts in the IT enterprise storage This time, I expand on more frequently used storage concepts.
A Bare Metal Image backup allows for the restore of an entire system to a similar or dissimilar hardware. They are highly useful for migrations and disaster recovery. Bare Metal Image backups support Full and Incremental backups. Differential backup…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through setting the global and backup job media overwrite and protection periods in Backup Exec 2012. Log onto the Backup Exec Central Administration Server. Examine the services. If all or most of them are stop…

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question