replaced DDS3 drive, now output has changed, why?

[Cindy Wolford]

Hi Everyone,

This is the first time this has happened so I'm a bit confused. We use our DDS3 tape drive as our nightly backup drive. It has always been /dev/rmt/0mb. We have had this tape drive replaced several times now....but each time the new drive was still /dev/rmt/0mb. I don't know how/why, but we just had the tape drive replaced and this time, the drive was found at /dev/rmt/2mb? I noticed that our nightly backups were not working, because of this drive change. Can anyone tell me how/why this drive is now 2mb? Can I change it to 0mb or do I need to edit my backup scripts to identify 2mb instead of 0mb?
TIA.

[Pete Randall · Accepted solution]

Cindy,

It could change if it was plugged into a different slot and came up with a different instance number.

Anyway, it's no big deal, you can just rename the device file or you can re-create to be anything you want. I'm attaching directions to do so.


Pete

[Rajesh SB]

Hi,

Device file will be created based on controller and instances. This can be verified by cmd
# lssf /dev/rmt/2mb

Ex:
# lssf /dev/rmt/0mnb
stape card instance 0 SCSI target 3 SCSI LUN 0 berkeley no rewind best density available at address 0/0/1/0.3.0 /dev/rmt/0mnb

Cheers,
RAjesh

[Torsten.]

Hi Cindy,

one reason could be that you are using a different scsi id. But it's also possible your new drive is a different model. But follow the posted advisory to change the dev file back.

[Cindy Wolford]

Thanks everyone. Notes attached were great. I'm running a test backup and all looks fine.

Thanks everyone!

[RAC_1]

You can also manage without creating device files. Just create soft links poiting to right devices.