Job Failing - Corrupt Data Encountered on Quantum SNAP Server

[Kevin_Barnett]

We keep getting failed jobs because corrupt data is encountered on our snap server. We can restore data from the job, but need the job to complete successfully. Any suggestions?

[Joshua_Small]

More information is needed.
Can you provide an example filename which is being considered corrupt? Post the relevant section of a log.

[Kevin_Barnett]

There are hundreds of files being corrupt. Different types include *.xls, *.pab, *.pst, *.doc, *.txt, *.bmp, *.pdf..... They are usually in usrhome directories, but the users do not have these files open. Some are *.cab's etc. Short file names, long file names, 4 directories deep, some more, some less.

(example)

Database or database element is corrupt
WARNING: "\\SERVER1\C$\Data\Usrhome\TSmith\RFox\My Documents\Bodycote Pkg List Spec.doc" is a corrupt file.
This file cannot verify.

[priya_khire]

Hello,

Although you have mentioned that users do not have these files open, do verify again if the files are in use during the backup? If yes, are you using the Advanced Open file option during the backup? If not, ensure that the files are closed during the backup.
In case you are running an anti virus during the backup, try stopping that before the back as it might be accessing the same files during backup.
For more information, refer to the follwing technote:

Title: What causes Backup Exec to report a file as a corrupt file?
http://support.veritas.com/docs/233646

Hope this information helps. In case the problem persists, you can write back to the forum with details. Howeve rif we do not hear from you within two business days, this post would be marked ‘assumed answered’ and would be moved to ‘answered questions’ pool.

Regards.

[Kevin_Barnett]

We are running AOFO (automatic mode). Shouldn't that take care of the files if they are "in use?" Also, shouldn't the job log say "skipped" instead of corrupt data encountered?

[Joshua_Small]

It would take care of them, but if you are running a verify, they will be considered changed since the backup ran, and therefore fail a verify.

Are you running a verify? I would suggest simply turning it off, and doing manual test restores regularly to ensure your backups are good.

[Kevin_Barnett]

We are not running a verify

[Joshua_Small]

Is there potentially a virus scanner blocking access to those files?

[Renuka_-]

Hello,


1. Please note that :



In order for Backup Exec to backup Snap Servers effectively the Snap Servers must have the following combinations:


For Microsoft Windows NT 3.51 should be a minimum of Service Pack 5
For Microsoft Windows NT 4.0 should be a minimum Service Pack 6
For Microsoft Windows 98 Service Pack 1 (Windows 98 second edition is preferred).
For Microsoft Windows 95 Service Pack 1 (should be a minimum version 4.00.950a)


2. Currently, Quantum Snap! Servers running Snap OS version 2.3 or 2.4 or later can be backed up successfully with VERITAS Backup Exec (tm). Snap OS upgrades are available from the following Quantum Web site: http://www.snapserver.com/ .


To identify the currently installed software version, click on the Snap, Quantum, or Meridian data logo on the server's Web Administration page


A window will appear, displaying the version information


PLease get back with the confirmation on compatibilty of the SNAP server you are using.


3. To avoid your backups failing due to corrupt files you might wish to do the following:



How to prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding Microsoft Exchange files)
http://support.veritas.com/docs/193940


NOTE : If we do not receive your reply within two business days, this post would be marked assumed answeredand would be moved toanswered questions pool.

[Sheetal_Risbood]

As per our previous reply, marking the case as assumed answered and moving it to answered questions pool.