Corrupt file

[nyrfaninva]

I have BE 8.6 Rev 3808.

I am having problems with corrupt files. If I hit a corrupt file, it stops processing (File cannot verify). I followed the advice of changing the registry settings, but to no avail. I would like to continue with the next file.

We are getting BE 9.0 soon. Does that resolve the corrupt file problem?

Thanks for reading my post!

 

[SQLBill]

You are not using the latest build (version) for BE8.6. It should be build 3878. You might want to load that upgrade and see if it solves the issue.

-SQLBill

 

[nyrfaninva]

My typing is bad, SQLBill. It is version 3878.

By the way, I seen your responses. You should be an instructor. You really know your BE!!!

 

[SQLBill]

Thanks for the compliment! There's still a lot I don't know, I just have the luck of working in a computer lab so part of my job is to browse tech sites and learn what I can. I've never had the 'corrupt file' issue, so I can't help with it. We are getting ready to have a new cluster built and BE 9.0 was supplied to us, so I get to learn something new.

Again, thanks for the compliment...and if I find a solution to your issue I'll let you know.

-SQLBill

 

[Rols]

Hi nyrfaninva,

Corrupt files should not stop the backups from completing - the backup should just move on to the next file and report the file as corrupt in the backup log.

Could you please post your backup log?

Cheers

 

[nyrfaninva]

Hi ROLS

Thanks for offering to help.
=====================================================
OFO: Started for device: "\\CSFFILE3\D$"

Performing Remote Agent backup

Media Name: "Server Files:Full 5/9/03"
Backup of "\\CSFFILE3\D$ "
Backup set #8 on storage media #3
Backup set description: "Files Backup Full "
Backup Type: FULL - Back Up Files - Reset Archive Bit
Backup started on 5/10/03 at 7:30:27 AM.

Drive and media information from media mount:
Robotic Library Name: OVERLAND 1
Drive Name: Quantum 1
Slot: 9
Media GUID: {4F37E96A-6601-11D7-A432-006008F5E10A}
Media Label: HBG012
Overwrite Protection Time Left: 3 Weeks
Append Time Left: Infinite
Targeted Media Set Name: Rotation - Full
Backup set #8 on storage media #5

Drive and media information from media mount:
Robotic Library Name: OVERLAND 1
Drive Name: Quantum 1
Slot: 10
Media GUID: {4F37E976-6601-11D7-A432-006008F5E10A}
Media Label: HBG013
Overwrite Protection Time Left: 3 Weeks
Append Time Left: Infinite
Targeted Media Set Name: Rotation - Full
Backup set #8 on storage media #6
WARNING: "\userdir\VargasT\BACKUP\X0\D\BACKUP\Leave Slips\Sick Leave\CY 2001\S-L & A-L 7-18-2001.doc" is a corrupt file.
This file cannot verify.
^ ^ ^ ^ ^
Unknown OFO error: 0xe0001002.
OFO: Error during backup. Set has been canceled.

Backup completed on 5/10/03 at 8:05:42 PM.
Backed up 217863 files in 19387 directories.
1 corrupt file was backed up
Processed 68,462,101,466 bytes in 12 hours, 25 minutes, and 57 seconds.
Throughput rate: 87.5 MB/min
========================================================

 

[Rols]

Ok its the OFO error that is killing the backup - try turning it off and see if the backup completes. Also try re-installing the OFO option.

Cheers

Rols

 

[jlvandusen]

We too are having the same issue with our large file servers that contain the users home directories:

The backup gets like down to the S's or T's of the usernames and it returns the following:

Unknown OFO error: 0xe0001002

There is no way to turn off OFO per say, as well as I have the setting (as suggested by Vertias) set to manual and I created a folder named OFO on the most free drive. I then set the size limits to the maximum as I could.

Looking for further suggestions...

Jlvandusen@cazenovia.edu