non-vg00 volume groups and ignite recovery

[Valisha Bradford]

Hello All.

If two volume groups are on an ignite tape, vg00 and vg01, will I be able to see them in the File System tab when doing an interactive recovery? When I create an ignite tape containing on vg00, then go into the File System tab, I see all of vg00's mount directories. Will this still be true when the ignite tape containing both vg00 and vg01.

Thanks in advance.

Valisha

[Pete Randall]

Valisha,

That may be a hard question to get answered around here because the standard recommendation is to limit your Ignite backups to just vg00. I've never tried to do additional VGs, so I couldn't tell you and I'm not sure if anyone else will be able to either.


Pete

[Valisha Bradford]

I know it's best practice to only ignite vg00. Unfortunately, that isn't an option. VG00 has run out of space. The adm before created vg01 and it has space. Since I'm using the ignite to restore different hardware, ( Ignite tape is for a D380 and I'll use it to recover a K580) I'll need additional drivers. Since there isn't space available in vg00, the drivers were downloaded to vg01.

Thanks anyway, Pete.

Valisha

[Robert-Jan Goossens]

Hi,

As Pete mentioned this is a hard question, resoring to a differrent cpu base. I "THINK" this could be done, but to be very sure call HP support.

Hope it helps,

Robert-Jan.

[Krishna Prasad]

Hello,

I just thought I would put this on the table.

The new system or different hardware that you will be restoring the Ignite to?

Would it be possible to simply install the OS with the newer version of the OS and patches then move the critical configuration files you need from the orginal box. Then data.

I don't know your environment to know what applications are also moving, number of users, services you have in production.

I have 'sometimes' found it easier to start fresh if there is a major difference in hardware when moving systems. It depends on how much configuration and data movement is involved.

[Steven E. Protter · Accepted solution]

Ignite is never going to get a good backup of any databases in vg01, unless they are down.

What its really good at is this:

Getting a good backup of vg00

Restoring vg00 with fstab and all other connections to vg01 or any other vg's without changing their data.

When you boot off of a tape, and you interupt the process with a keystroke, you will see all disks and volume groups.

Depending on what is on the tape, is what get laid down. If you just do vg00, you'll see the disks, but they won't be touched.

SEP

[Valisha Bradford]

Here's a little more info to clarify my situation.

I will be doing this at an offsite Disater recovery facility. My ignite tape of a D380 was created in my office. I will be taking this tape to an offsite DR facility. They're giving me a K580. I'll use my ignite tape of the D380 to recover the K580. If I weren't pressed for time, I would just do a cold install of the OS, patches, and app CD's. It isn't an option to add the K580 drivers to my D380, then make an ignite tape, then uninstall the drivers.

Thanks.

[Pete Randall]

Valisha,

Are the drivers the only thing you're trying to get out of vg01? Can't you store them somewhere in vg00 without installing them? Maybe put them in /tmp or in /home or something?


Pete

[Valisha Bradford]

Yes, the drivers and a few patches are the only things I need from vg01. Since vg00 doesn't have enough space, the drivers and patches were stored in vg01.

[Pete Randall]

They take that much room, huh?

How about dumping them to tape via tar and bringing that tape with you? Or blowing away vg01 and using that disk to expand vg00, creating an extra lvol/filesystem, and putting the drivers/patches there?


Pete

[Tim Adamson_1]

Hi Valisha,

I think it should be possible because some of the typical vg00 stuff can actually belong in vg01 or some other volume group.

It would be easy to simply give it a try, boot from your tape and interact. The go and check out the filesystem tab.

make_tape_recovery -A -a /dev/rmt/0mn -I -x inc_entire=vg00 -x inc_entire=vg01

Something like that should work (depending on the version of Ignite).


Cheers!!!