FRECOVER(1001) file trailer errors

[Adegoke Apalara]

Hi everyone
Just two days ago our database crashed and we had to move to the backup server for our live production(which was O.K). What shocked me was that the backup tape from the Backup Server was giving a error while restoring. the error message is:
frecover(1001): file trailer does not match file header for
frecover(1002): file bnk.data/&HOLD&/121456342300
frecover(1045): error in trailer recovery

Both Servers are of the same spec but what caught my eye was that using SAM my filesystem on the backup has the option of upgrading to veriosn 4 while the live server does not. This i believe may have been due to the fact that a DEMO version of VERITAS NETBACKUP 4.5 was installed last week on the backup server.
This put me in a hitch cos i can't restore my data back to the live server.
The file system type on both servers fron fstyp is 3

Heeeeeelp!!!!

[Helen French]

Normally, "file trailer does not match file header" error comes when there is a SCSI overload exists while communicating with backup device. Check the SCSI controller in which the backup drive is connected and see if it's overloaded. Remove any additional devices that shares the same SCSI bus and try again.

Just a thought ...

[Adegoke Apalara]

Please, How do i check if the SCSI device is overloaded?

[Helen French]

1) Check how many physical devices are connected to the same controller?

2) Check the SCSI controller type (SE, Wide, Ultra) and see if the SCSI bus you are pulling from the same controller exceeds it's maximum limit (or at bottleneck)?

3) Check disks and peripheral performance (which are connected to the same SCSI bus) using sar, Glance etc.

4) While you do the frecover, check system performance, disk read/writes, data transfer rate, data wait time etc. using Glance

# gpm (or glance)
# sar
# top
# vmstat

[Helen French]

To add:

One best way to check if this is a SCSI problem, connect your backup device directly to a controller and see if it works!