backup failing with scsi errors

[jimmies]

Good morning
I am using Legato v7.0 on solaris 9
The problem is that when i launch my backup it fails immediately with these messages, can you please help me to solve this problem :
06/29/07 17:55:52 nsrd: amapmcp1:/osp/BACKUP/osp_bkp saving to pool 'Daily Backups' (DailyBackup.001)
06/29/07 17:55:52 nsrd: amapmcp1:/osp/BACKUP/in_bkp saving to pool 'Daily Backups' (DailyBackup.001)
06/29/07 17:59:34 nsrd: savegroup info: Daily Backups running on amapmcp1
06/29/07 18:04:34 nsrd: savegroup info: Daily Backups running on amapmcp1
06/29/07 18:09:34 nsrd: savegroup info: Daily Backups running on amapmcp1
06/29/07 18:14:34 nsrd: savegroup info: Daily Backups running on amapmcp1
06/29/07 18:18:03 nsrd: media critical: TapeAlert flag "TapeAlert Unsupported" has been posted for /dev/rmt/0cbn
06/29/07 18:18:03 nsrd: media warning: /dev/rmt/0cbn writing: Bad file number, at file 34 record 23557
06/29/07 18:18:03 nsrd: media notice: LTO Ultrium-2 tape DailyBackup.001 on /dev/rmt/0cbn is full
06/29/07 18:18:03 nsrd: media notice: LTO Ultrium-2 tape DailyBackup.001 used 68 GB of 200 GB capacity
06/29/07 18:18:04 nsrd: media warning: verification of volume "DailyBackup.001", volid 8698624 failed, read open error: drive status is Drive
reports no error - but state is unknown
06/29/07 18:18:04 nsrd: media notice: verification of volume "DailyBackup.001", volid 8698624 failed, volume is being marked as full.
06/29/07 18:18:04 nsrd: media notice: Save set (4270111496) amapmcp1:/osp/BACKUP/in_bkp volume DailyBackup.001 on /dev/rmt/0cbn is being term
inated because: Media verification failed
06/29/07 18:18:04 nsrd: amapmcp1:/osp/BACKUP/in_bkp done saving to pool 'Daily Backups' (DailyBackup.001) 34 GB
06/29/07 18:18:04 nsrd: media notice: Save set (4286888712) amapmcp1:/osp/BACKUP/osp_bkp volume DailyBackup.001 on /dev/rmt/0cbn is being ter
minated because: Media verification failed
06/29/07 18:18:04 nsrd: amapmcp1:/osp/BACKUP/osp_bkp done saving to pool 'Daily Backups' (DailyBackup.001) 33 GB
06/29/07 18:18:04 nsrd: write completion notice: Writing to volume DailyBackup.001 complete
06/29/07 18:18:04 nsrd: savegroup info: Daily Backups running on amapmcp1
06/29/07 18:18:05 nsrd: media info: suggest relabeling DailyBackup.002 (000011) on amapmcp1 for writing to pool 'Daily Backups'
06/29/07 18:18:05 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool 'Daily Backups' tape(s) on amapmcp1
06/29/07 18:18:05 nsrd: nsrjb notice: nsrjb -j Storedge-L8 -O13 -l -R -M DailyBackup.002
06/29/07 18:19:40 nsrd: /dev/rmt/0cbn Eject operation in progress
06/29/07 18:20:28 nsrd: media info: loading volume DailyBackup.002 into /dev/rmt/0cbn
06/29/07 18:21:02 nsrd: /dev/rmt/0cbn Verify label operation in progress
06/29/07 18:21:04 nsrd: media warning: /dev/rmt/0cbn reading: read open error: drive status is Drive reports no error - but state is unknown
06/29/07 18:21:05 nsrd: /dev/rmt/0cbn Eject operation in progress
06/29/07 18:21:47 nsrd: Jukebox 'Storedge-L8' failed: expected volume 'DailyBackup.002' got 'NULL'.
06/29/07 18:22:19 nsrd: media info: suggest labeling volume from slot 3 in jukebox Storedge-L8 on amapmcp1 for writing Daily Backups


Thanks for your support

 

[Rif123]

Hi,

Has this ever worked or is it a completely new installation?

I would start by trying to disable CDI on the device(s). There were a couple of problems with that earlier. you can find the setting under the device configuration in NetWorker. I'm not familiar with the library you are using, but it looks like it is a more of an autoloader without a barcode reader? Aree the tapes new or have they been used before? Have you seen any block size issues?

 

[605]

Also keep in mind that NW sets a media to full (prematurely) if it cannot recover from a write error.

 

[jimmies]

Thanks for your answers
It was working for one month and it stopped suddenly
I have a bar coder but i don't use it
Cheers

 

[bombcan]

This type of problem is usually due to the drive order in Networker. Make sure that drive 1 is defined to the right device (cbn).

 

[605]

The drive configuration most obviously is not the problem here. Otherwise NW will show read I/O errors.

 

[Martin999]

Yep, if the drive order is wrong, networker ends up trying to access a device with no media and you get a read open error i/o error.

Martin