Device files

[Phillip Popp]

Hi All,
Using HP10.2, Just added a tape drive to the hardware. I need to make a boot tape with ignite. My question concerns the tape drive. I never used one before. Which Device file do I use. Here are the specifics.
The driver of the tape is stape. The description is C1533A 4 GB DDS Compression Tape Drive (DAT)

My device files range from /dev/rmt/0m, /0mb, /0mn, /0mnb, /c1t3d0BEST, plus several others. Descriptions for these device files are at&t best density available or Berkely options, some with no rewind. Also some that say DDS1 DAT tape cartridge, again at&t or Berkely, with no rewind options.

Can anyone help to decide which device file to use.
I am going to be making a boot tape of / I need to reconfigure my vg00. Veritas version is too old.

Older postings I have read indicate using no rewind for my application.

Help!!!

Thanks,

Phil

[James R. Ferguson]

Hi Phil:

For Ignite tapes you need a no-rewind device. Hence, use:

/dev/rmt/0mn

To better understand tape device files, see the manpages for 'mt(7)'.

Regards!

...JRF...

[Greg Traud_2]

You could let ignite choose its own tape drive by performing:

/opt/ignite/bin/make_tape/recovery -i -I

for an interactive session. This works for both text screens and Xwindows.

It brings up a SAM looking interface.

[Phillip Popp]

Hi again,
Thanks for the help, but I seem to be having a permission issue with running ignite. I just do a /opt/ignite/bin/make_recovery and I get not found. How do I set this in my path? I put it in the .profile, but still no luck.

Thanks,

Phil

[A. Clay Stephenson · Accepted solution]

You need to do something like this:

export PATH=${PATH}:/opt/ignite/bin

You can do this directly on the command line or add it to your .profile BUT this will not help when you execute using an absolute path.

The fundamental problem is that you are using the wrong command. It should be /opt/ignite/bin/make_tape_recovery.

An my preference is for the mnb device for all norewind devices because frankly, the at&t style convention is insane (and I say this coming from a non-Berkeley UNIX background).