Corrupt file caused snapshot of shared folder to stop...
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