topic Re: Errors and Command Options for make_tape_recovery in Operating System - HP-UX

Errors and Command Options for make_tape_recovery

Andrew Kaplan — Tue, 30 Jan 2007 14:41:38 GMT

Hi there --

I am running Ignite 6.7.79 on an HP-UX 11.11 v.1 system. I currently run make_tape_recovery without any options, and while it does complete it does so with errors. I've included the recovery.log file in this posting. Are these errors show-stoppers, or do I have an effective recovery tape for the system?

What I would like to do is be able to back up the entire core operating system so that if the unthinkable does happen, I can insert the recovery tape and have a full system restore completed. What command options should I include to accomplish this? Thanks.

Re: Errors and Command Options for make_tape_recovery

James R. Ferguson — Tue, 30 Jan 2007 14:45:45 GMT

Hi Andrew:

I prefer this:

# make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn

Regards!

...JRF...

Re: Errors and Command Options for make_tape_recovery

Andrew Kaplan — Tue, 30 Jan 2007 16:14:03 GMT

Hi there --

I ran make_tape_recovery with the options you suggested, and it completed with errors. I checked the recovery.log file, and I included it with this posting.

I noticed the following series of messages in the file:

vgcfgbackup: Warning: couldn't query physical volume
The specified path does not correspond to physical volume attached to this volume group

I also saw several instances of the following:

vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "/dev/vg102".

The latter refers to volume groups that are not mounted, so I am not too worried about that. The vgcfgbackup lines have me more concerned. Is there something that am missing or are those messages mostly informational?

Re: Errors and Command Options for make_tape_recovery

Bill Hassell — Tue, 30 Jan 2007 21:06:50 GMT

Ignite always validates all the disk configurations to make the recovery as accurate as possible. The vgdisplay command probably fails too, possibly other LVM commands -- due to the bad volume group. If the volume group is bogus or no longer used, remove it properly with a vgexport command. You want vgdisplay and lvlnboot -v to report normal lines of output with no error messages. Then Ignite should work OK.