Ignite-UX backup

[Brian Lee_4]

Whenever I run ignite-ux backup, I am getting the following message.

/opt/ignite/bin/make_recovery -AvCi -d /dev/rmt/0m
Option -A specified. Entire Core Volume Group/disk will be backed up.
make_recovery(284): Writing to the tape failed. Please check the existence of the tape, or the tape
is write protected, or the tape is bad.
make_recovery(210): Encountered a fatal error.
make_recovery(212): Please fix errors and re-try.
Cleanup

I clean up the drive and insert a brand new DDS4 tape.

Please help me out.

[Rick Garland]

Is this a DDS4 tape drive?

Also look into the ioscan output to see if this device is present. Can do "ioscan -fnCtape" to just get a listing of tape devices. Is the device present? Is it claimed?

Using the right device name? Try doing a tar to the tape with the device name you believe. Did it write?

[Tom Danzig]

Either the tape IS write protected or you are not using the correct device file for the tape drive.

Are you sure the tape drive is dev/rmt/0m? If not, use "-a /dev/rmt/?m"

[Eric Antunes]

Maybe the tape is write protected?

[Brian Lee_4]

There has been no problem since last January 2003. This problem just happened today.
I am using the correct device(/dev/rmt/0m) and the DDS4 drive is present(Claimed) when I run "ioscan -funCtape".
I tried with three different tapes.
I tried ignite-ux backup with those tapes in another server and they all worked fine.

[Rick Garland]

A call to HP hardware might be in order to replace the tape drive.

[Michael Tully]

Before calling HP, let's try a couple of other things.

Have you tried the make_tape_recovery using the no-rewind device?

Second, have you tried to write to the tape using other methods, like tar, cpio or fbackup.

If none of these work, clean the drive, try one more time and then call hardware.

[Jan de Haas_1]

Check with IO scan to see if the identity string shows this is an actual HP DDS4 drive and not a third party drive.
If the drive is third party, there is a possibility that the Ignite util checks for the identity string to make sure the drive is supported (I know fbackup does that, unsure if Ignite does the same).

Make sure you have the latest patch installed for support of DDS4 drives.
Search for 'stape' in the patch list for your HP-UX version.

It doesn't appear that Ignite gets that far, but Ignite also uses tar, so make sure tar works fine with this drive.

[Shaikh Imran]

Hi,

Pls refer this thread the similar problem
is discussed here earlier.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=61262

Regards,

[Shaikh Imran]

hi,

Also this thread :

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=18018

Regards,