topic Re: Reg:checking data in DAT-72 tape in Operating System - HP-UX

Reg:checking data in DAT-72 tape

praneepteja — Sat, 12 Mar 2011 04:49:28 GMT

Hi,

I am using tar -tvf /dev/rmt/0m command to check data in DAT-72 tape.but it is showing

Tar: tape blocksize error.....

Can you suggest me how to get out of this error and check data in DAT-72 tape..

Re: Reg:checking data in DAT-72 tape

Dennis Handly — Sat, 12 Mar 2011 04:55:20 GMT

This error message indicates that you don't have a tar file on the tape. What did you use to write to the tape?
Since you are using 0m, the tape should have been rewound.

Re: Reg:checking data in DAT-72 tape

Dennis Handly — Sat, 12 Mar 2011 04:56:51 GMT

If this is an ignite tape, depending on your architecture, you must use a norewind device and use mt(1) to fsf 1 (PA) or 22 (Integrity) before you try to read the tape.

Re: Reg:checking data in DAT-72 tape

praneepteja — Sat, 12 Mar 2011 06:26:17 GMT

This is an ignite tape and it is integrity machine.

I used make_tape_recovery for ignite backup into DAT 72 tape.

Can u give me commands to check data in this tape?

Re: Reg:checking data in DAT-72 tape

praneepteja — Sat, 12 Mar 2011 09:30:48 GMT

i used make_tape_recovery command for ignitebackup into DAT 72 tape.

And this is an integrity server.

Can u suggest me commands for checking data on DAT 72 tape?

Re: Reg:checking data in DAT-72 tape

Dennis Handly — Thu, 04 Aug 2011 18:01:00 GMT

>Can you suggest commands for checking data on DAT 72 tape?

This was provided on your previous thread by Manix:
http://h30499.www3.hp.com/t5/Ignite-UX/Reg-ignite-back-up/m-p/4758520#M18080

# mt -f /dev/rmt/0mn rew
# mt -f /dev/rmt/0mn fsf 22
# tar -tvf /dev/rmt/0m

A similar thread:
http://h30499.www3.hp.com/t5/Ignite-UX/Listing-file-system-from-IGNITE-Backup-Tape/m-p/4744505#M17991

Re: Reg:checking data in DAT-72 tape

VK2COT — Sun, 13 Mar 2011 01:57:57 GMT

Hello,

You already got good advice from other ITRC
members.

Two more:

a) Put the tape into the drive on the original
server and use check_tape_recovery(1M) command.

b) Put the tape into the drive on any
server and use ansitape(1M). This command
saved my customer recently when they had
serious Ignite recovery problem:

# /opt/ignite/lbin/ansitape tv mt=/dev/rmt/#mn

It is especially useful if your Ignite image
format was not tar(1M).

Where "#mn" is a DFS for tape drive...

Cheers,

VK2COT