Ignite

[James Rohrich]

I am using Ignite (11 to 11) to create a bootable tape. The software is on an HP9000 N class machine running version HPUX11.This server is actually a backup server and connects to a 9740 silo with 10 9840 tape drives and 1 DLT7000. There is a locally attached dat tape (DD3). After running the make_recovery it appears to have runn successfully, but now I am questioning whether it went to the local DAT tape or to one of my 9840's. I cannot find a setting to point it to the local DAT. In the silo one of my backup tapes when loaded by Legato (my backup software), it claims the tape is a tapeexercise tape.

[James Rohrich]

When I tried to create the tape, I had only run make_recovery without any options. I thought this would have directed it to the local dat tape. With no options does it just select any tape. Also is there a command to check to see what is on the tape.

[David Manson]

Are you using make_recovery? If so you can use the -d option to specify the destination of the local DAT tape device file. A no-rewind device file is required. I think the default is /dev/rmt/0mn.

For example:-

make_recovery -Avi -d /dev/rmt/0mn

Good luck!

[James R. Ferguson]

James:

You can verify an Ignite make_recovery tape by doing the following:

# mt -t /dev/rmt/0mn rew
# mt -t /dev/rmt/0mn fsf 1
# tar -tf /dev/rmt/0m | awk '{print $1}' > /tmp/tarcontents
# diff /tmp/diff /var/opt/ignite/logs/makrec.log2


The tar to extract the contents of the tape should NOT be (v)erbose. The 'awk' is necessary to eliminate the symbolic link information (where applicable) from the /tmp/diff. With these changes you can get a quick OK/NOT_OK comparison of the files actually on the tape to that which make_recovery logged.

...JRF...

[James R. Ferguson · Accepted solution]

James:

(Corrected typographical error)

You can verify an Ignite make_recovery tape by doing the following:

# mt -t /dev/rmt/0mn rew
# mt -t /dev/rmt/0mn fsf 1
# tar -tf /dev/rmt/0m | awk '{print $1}' > /tmp/diff
# diff /tmp/diff /var/opt/ignite/logs/makrec.log2


The tar to extract the contents of the tape should NOT be (v)erbose. The 'awk' is necessary to eliminate the symbolic link information (where applicable) from the /tmp/diff. With these changes you can get a quick OK/NOT_OK comparison of the files actually on the tape to that which make_recovery logged.

...JRF...

[James Rohrich]

David and James your information is extremely helpful. One last question is how can I determine where the data was written? I believe it went to a 9840 tape by accident, but I need t verify it. I thought that the tape used would have been in the log1 or 2 which are the two log files that ignite generates, but it is not there.