Difference Encountered in File Data BackupExec 8.6

[benewm]

Client using BE 8.6 Build 3878. Job randomly fails during verify stage due to the following errors, "Difference encountered in file data" and "An inconsistency was encountered on the storage media in SEAGATE 2." The files are different each time, but they are always in Exchange Information stores (ie, Sent Items, Deleted Items, etc.). I have tried inserting a cleaning tape. I have tried to use different drivers but it hasn't helped. I started with the Seagate drivers, then I used Microsoft drivers, and finally I downloaded the updated Veritas drivers but job still failing. I have seen other posts with similar problems, but I can't find a solution. PLEASE HELP!!

 

[neilcorbett]

Hi,

I am having the same problem as this. Did you find a solution to the problem?

Many Thanks

 

[TheDonMiguel]

What does happen when you do a Backup 2 Disk? Do you know the little tool, SGMON? Have a look at it, you will get much more information about the problem as the BE GUI can provide you:

http://seer.support.veritas.com/docs/190979.htm

Good luck

 

[benewm]

After a lot of work with Veritas, I was not able to get the issue resolved. I replaced the SCSI card, with no luck. The only thing I didn't do was replace the drive (again- it had been replaced recently). To work around the issue, I turned off Verify. This allowed the job to run successfully. I tested Restoring, and it worked so this was suitable temporarily. I also knew a new server was arriving in the near future. Once the drive was implemented in the new server, there were no problems. Good luck.

 

[neilcorbett]

Hi, Thanks for the prompt replies ;-)

I have enabled the SGMON tool, very nice util. I can not run a one off backup today however the scheduled backup will run over night so ill post the results tomorrow.

Have not tried backup to disk, will try if the results of SGMON are no help.

Thanks

Neil

 

[neilcorbett]

Would you beleive it, since I enabled the SGMON util the last 2 backups have worked perfect!! won't fail when your monitoring it!!

I will leave the SGMON running and see if it fails in the next few days, as soon as it does I will update the forum.

Thanks for your help

Neil

 

[neilcorbett]

The backup has now failed with 1 file different, I have compared the logs and their is a difference see below;

Here is a section of the log from around the time of failure. If you want the entire log email me (each one is 80 pages long)

SUCCESS
2228: Len Req = 65536 Len Got = 0
2228: 840 7/9/2004 6:37:12:
2228: TF xfer time = 338 seconds.
2228: 840 7/9/2004 6:37:12:
2228: TF_CloseSet
2228: 840 7/9/2004 6:37:12: [no resource for 3832]
2228: 840 7/9/2004 6:37:12:
2228: TF_OpenSet( )
2228: 840 7/9/2004 6:37:12:
2228: Requested Set: ID = 30e8b00d Seq = 1 Set = 24
2228: 840 7/9/2004 6:37:12:
2228: Current VCB: ID = 30e8b00d Seq = 1 Set = 23
2228: 840 7/9/2004 6:37:12:
2228: End of TF_OpenSet: Ret_val = 0 Buffs = 10 HiWater = 0
2228: 840 7/9/2004 6:37:12:
2228: GotoBlock: VCB_PBA = 2012011, VCB_LBA = 0, LBA = 0,
2228: 840 7/9/2004 6:37:12:
2228: PBA = 2012011, offset = 0
2228: 840 7/9/2004 6:39:42:
2228: Device Error = 1101
2228: 840 7/9/2004 6:39:42:

Fail
2228: Len Req = 65536 Len Got = 0
2228: a0 7/10/2004 6:41:35:
2228: TF xfer time = 254 seconds.
2228: a0 7/10/2004 6:41:35:
2228: TF_CloseSet
2228: a0 7/10/2004 6:41:35: [no resource for 3832]
2228: a0 7/10/2004 6:41:35:
2228: TF_OpenSet( )
2228: a0 7/10/2004 6:41:35:
2228: Requested Set: ID = 30e9b00d Seq = 1 Set = 27
2228: a0 7/10/2004 6:41:35:
2228: Current VCB: ID = 30e9b00d Seq = 1 Set = 26
2228: a0 7/10/2004 6:41:35:
2228: End of TF_OpenSet: Ret_val = 0 Buffs = 10 HiWater = 0
2228: a0 7/10/2004 6:41:35:
2228: GotoBlock: VCB_PBA = 2234028, VCB_LBA = 0, LBA = 0,
2228: a0 7/10/2004 6:41:35:
2228: PBA = 2234028, offset = 0
2228: a0 7/10/2004 6:41:42:
2228: Device Error = 1101
2228: a0 7/10/2004 6:41:42:

The main thing I see different is on the fail its showing Device Error A0 whereas on success its 840.

No idea what they mean :-(

Can anyone help?

Thanks a lot.

Neil