make_recovery succeeds but non vg00 not mounted

[Edward Alfert_2]

Hi,

I have the following in a D390:

* 4 x 2GB drives in vg00 (2 PV each containing 2 drives and mirroring between PV)

* 14 x 2GB drives in vg01 (2 PV each containing 7 drives and mirroring between PV)

I want to replace the 2GB drives that make up vg00 with 9GB drives.

I issued the following command to create a bootable recovery tape.

#make_recover -A -C -v

The tape was created successfully.

I shut down the server and replaces the boot disks (2GB) with 9GB disks.

I then rebooted the server off the recovery tape and it successfully loaded the vg00 data onto the new set of 9GB drives.

BUT.... vg01 is not mounted.

/etc/fstab shows the correct entries for vg01.

In SAM, if I list the drives it shows the drives for vg01 as "UNUSED".

I then shutdown the system and put the old 2GB drives in the server. Rebooted, and the server is back to the way it was.

I want to try again replacing the 2GB drives in vg00 with 9GB drives and would like any pointers, hints, or solutions on what I am doing wrong.

Thank you in advance for the help.

[Pete Randall · Accepted solution]

First, download the latest version of Ignite from here:

http://www.docs.hp.com/en/IUX/

Then, to make sure you get everything backed up use this syntax:

make_tape_recovery -I -v -x inc_entire=vg00

Finally, after you restore you will need to vgimport your vg01. Run a vgexport in preview mode before you make your backup. Store a map file (from vgexports -m option) in /tmp and it will get restored along with vg00.


Pete

[Patrick Wallek]

Before you replace the drives do the following:

# vgexport -m /var/tmp/vg01.map -p -v -s /dev/vg01

Now take the /var/tmp/vg01.map file and copy it to your PC or another server.

Put your 9GB drives in.

When the server comes up with the new drives do the following:

Copy the map file to this machine from your PC or where ever you put it.
# mkdir /dev/vg01

# mknod /dev/vg01/group c 64 0x010000

# vgimport -m /var/tmp/vg01.map -v -s /dev/vg01

# vgchange -a y /dev/vg01

# mount -a

Your VG01 should now be back.

[Edward Alfert_2]

Thank you Pete and Patrick,

Since you both mentioned vgexport -m and you both have nice green leaf crowns I'm sure that is the step I missed. :)

I will attempt the swap again tonight (after everyone is off the system and I have done a full system backup) and assign points to your replies tomorrow if ("when") everything works.

Since I'm going to be recovering the boot disk anyways, I should probably take the opportunity to increase the size of certain partitions like /, /var, /usr, /tmp, /stand, and /opt

I believe all I have to do is interrupt the boot process of the make_recovery tape and a CHUI (similar to SAM) will come up which will give me the options to resize the partitions. Is this correct? An "gotchas" I should be aware of?

Pete,

Do you "highly recommend" (or just "recommend") I upgrade to make_tape_recovery instead of using make_recovery?

I want to introduce the least amount of changes to the system during this entire process and I have several make_recovery tapes from different dates that I can fall back on in case something goes wrong.

[Patrick Wallek]

I would *highly* recommend the latest version of Ignite/UX.

make_tape_recovery offers many more options that make_recovery.

Here is the make_tape_recovery command line we regularly use on our systems:

/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -m tar -t "$(uname -n) system recover tape created on $(date)" -v -x inc_entire=vg00

Where the ?mn is your appropriate tape drive. Once you have the new version installed see the make_tape_recovery man page for what all those options do.

By the way, when upgrading versions of Ignite, I ALWAYS swremove the old version before swinstall'ing the new version.

[Pete Randall]

The "make_recovery" versions of Ignite are quite old and there have been MANY improvements and fixes since then, so I highly recommend upgrading.

The key here, by the way, is not so much the vgexport but the vgimport - the export is done simply to get the map file. It's not even necessary if your logical volumes follow standard naming conventions (lvol01, lvol02, etc). It's also nice to run the -s option on the export so that you don't have to specify the individual disks to the import (which also uses the -s option to discover the disks), but, once again, it's not necessary if you know which disks were part of vg01.

As Patrick points out, you can just use the 9GB disks you previously recovered to, not bothering with re-running the make_recovery or make_tape_recovery - just running the vgimport. I would prefer, however, to re-run the newer version with the syntax I gave you. It will take you a little longer but you'll be sure you've gotten everything!

Good luck.


Pete

[Steven E. Protter]

make_recovery is obsolete.

its not being worked on and everyone uses make_tape_recovery

If you want long term support for DR you must use make_tape_recovery

The other commands posted are excellent and I'm personally bookmarking this post as a reference.

SEP

[Hoang Chi Cong_1]

I recommend to use make_tape_recovery command instead of make_recove...
This is full command to backup whole vg00:
make_tape_recovery -v -A -I -x inc_entire=vg00 -a /tape_device

Regard,
Hoang Chi Cong

[Edward Alfert_2]

Thanks all for the valuable information. It worked this time. I have assigned points as promised.

I have 1 issue that has appeared after the restore but I will start a new thread since it is a completely new topic.

[Steven Chen_1]

I am interested:

Last time I replaced a bad 4G root disk with a 9G new one using make_tape_recovery, I am told I could downsize it to use 4G again only.

Then I did, and reduced my root space 100%.

Correct me if I was misleading then.

[Patrick Wallek]

Steven,

That should not have happened. I have used make_recovery adn make_tape_recovery tapes numerous times to install larger drives for VG00. I have never had any problems with not being able to use the entire drive.

Ignite has always worked quite well for me.

[Steven E. Protter]

Patrick,

Edward,

I need to apologize for the wording of my bunny post. For my first few years of full time admin work I used make_recovery.

I had a number of issues with it that required me to call the support center. Each and every time, I was "advised" that make_recovery was obsolete and might stop working or be de-supported at any time.

That made a bit of an impression on me and I converted to make_tape_recovery in 2001. I was merely parroting what the excellent team members of the HP Response Center said to me over the years.

I've gotten in a wee bit of trouble with fellow members over the years appearing to speak for HP.

I don't work for them. I don't speak for them. I did not mean to give that impression.

I apologize for any confusion caused.

I do strongly recommend to all readers that you use make_tape_recovery.

SEP