backward compatibility is 100%
check ARCserve home directory\log\tape.log at this time 16/10/2009 1:50:18 PM
It will have something like this
2009/10/16 14:51:56 [1038] =>ABSL:3050 [REQUEST SENSE ] 03 00 00 00 40 00 00 00 00 00
2009/10/16 14:51:56 [1038] <TEST UNIT READY >, Sense Data as Follows:
2009/10/16 14:51:56 [1038] SENSE ABSL:3050 70 00 06 00 00 00 00 10 00 00 00 00 28
2009/10/16 14:51:56 [1038] EX SENSE ABSL:3050 00 00 00 94 09 00 00 00 00 00 00 00 00 00 00 00
2009/10/16 14:51:56 [1038] SENSE ABSL:3050 Unit Attention [06]
2009/10/16 14:51:56 [1038] EX SENSE ABSL:3050 Not Ready to Ready Transition(Medium May Have Changed) [28, 00]
details in your case will be completely different, but the important part is Request Sense is the SCSI command sent by the ARCserve Tape Engine to the tape device requesting the devices sense codes which have details on the command that failed. Following lines are those sense codes from the drive.
That said chances are that based off message in the activity log the command that failed was a READ command and the reason is the drive, even after many retries could not read tape.
As a test of the drive try a restore from a brand new brand new backup, if you are lucky it will fail and you have a bad drive. Lucky??? yeah I'
Main Topics
Browse All Topics





by: prashant9885Posted on 2009-10-16 at 09:53:30ID: 25591176
Are you able to restore data from tape which were used by r12 sp2 ?
How is the tape library connected to the backup server SCSI or FIbre ?
If connected to SCSI, disable the drivers for TL and TD and let ARCserve use it's SCSI commands to communicate with Library and tape drives.
Do you get any errors in windows event log ?
Please enable debug on tape engine and then run a scan of these tapes, it shoud give details information on whats happening in the backgroud.