Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Corrupt file caused snapshot of shared folder to stop...

Created: 20 Feb 2011 • Updated: 21 Feb 2011 | 4 comments
This issue has been solved. See solution.

During a snapshot of a shared folder backup exec has discovered a corrupt file.  This has caused the snapshot to stop and as a consiquence 55GB worth of home folders on one of our fileservers has been missed from the snapshot and not backed up.

Is this normal behaviour when encountering a corrupt file and if so is there anyway to tell backup exec to continue to backup files/folders after the corrupt file?  I've had a look through the jobs options and can't see anything that suggest you can do this..

We are using MS VSS as the AFO option. The fileserver is W2K3 R2 SP2, Backup Exec version is 2010 R2

 

Cheers

 

Adam.

Comments 4 CommentsJump to latest comment

AmolB's picture

In the AOFO tab along with MS VSS select "System - MS snapshot provider"

Engineer 007's picture

Hello Adam, 

This issue can be fixed and Backup exec can continue backing up files even though if it encounters any corrupt files.

There's a registry key called "Fail jobs on corrupt files" and its value is set as 1 (True) changing it to 0 will set it to false and the backups will continue to work even if there's any corrupt file.

Please check the below KB article to resolve the issue.

http://www.symantec.com/business/support/index?page=content&id=TECH5633&actp=search&viewlocale=en_US&searchid=1298226086819

Please see the fig. in step no.4 where you'll see the registry and the path for that registry Hive.

Please Don't forget to Mark this as a solution if that resolves your issue.

 

Thanks!

SOLUTION
Dev T's picture

 Hello,

We faced the same issue. We also changed the registry key, however the error did not go. We than installed the VSS rollup patch http://support.microsoft.com/kb/940349 (REBOOT REQUIRED) on the problem server and the issue was resolved.

hope this helps...

Its a best practice to have a "Support Contract" with Symantec...