extreme ignite backup test.. ??

[someone_4]

Hello
I just did an ignite backup using

/opt/ignite/bin/make_tape_recovery -a /dev/rmt/0mn -I -v -x inc_entire=vg00

It finished and everything went fine.Now I want to test it. I was thinking of moving some files around like /stand/vmunix or /etc/rc.config.d/* and then boot from the ignite tape to see if it will recreate the moved files and boot right.

Now I am wondering is this too extereme? I just want to know without a dout that I can recover a system from an ignite tape if i have to. On that note if anyone has any tips on ignite recovery please do share them. From my understanding I just have to
Interupt the boot process and boot from the tape. Is it really that easy?

Richard

[Sandip Ghosh]

Yes it is really that easy. But it will not only replace the specific files but it also put all the files and it will take 2 reboots.

[Helen French · Accepted solution]

Richard,

I wouldn't do these tests if it is a production server ! If you have a test server of your own, then you can try that. You don't need to test the recreation of files, instead you can test the media, the recovery speed, the recovery options etc. Because during recover, it will recreate everything on the vg00.

HTH,
Shiju

[someone_4]

It is a test server not a production box.My main concern is I want to be totaly prepared and know without a dout that I can bring a system up from an ignite tape if I need to.

Richard

[Helen French]

Hi Richard,

You can do this safely just by booting from the tape. For safety, I would create 2 ignite tapes. Update us once you have done this ( the steps, any issues etc.)

HTH,
Shiju

[Patrick Wallek]

Since this is a test machine, sure you can boot from the Ignite tape.

There is no reason to move or delete anything before you boot from the tape though. When Ignite/UX starts the installation it will do a pvcreate, mkboot, etc. on the disk(s) that will comprise VG00. Any data that was there will be wiped out and overwritten.

If you're not familiar with the Ignite process, then this is the best way to learn.

[Sridhar Bhaskarla]

Richard,

1. You can use copy_boot_tape command to copy the boot area into /tmp/bootarea.

copy_boot_tape -u /dev/rmt/0mn -b -d /tmp/bootarea

It should create a file called /tmp/bootarea/bootimage.

It will also list out the boot file contents once it is done. You can use regular lifls and lifcp commands against this file..

lifls /tmp/bootarea/bootimage
lifcp /tmp/bootarea/bootimage:AUTO -

This should give out the INSTALL string.

2. To view the archive later to bootimage use

mt -t /dev/rmt/0mn rew
mt -t /dev/rmt/0mn fsf 1
tar xvf /dev/rmt/0m specific files

If the above is successful, then tape will work.

There is also another useful command called make_check_recovery. Look the man page.

-Sri

[Patrick Wallek]

The command Sridhar is thinking of is actually check_recovery.

This command won't do anything for though. There are 2 reasons for this: 1) You used the make_tape_recovery command to create your tape. check_recovery only works if you use make_recovery and the '-C' option. 2) check_recovery doesn't do what I think Sridhar thinks it does. From the check_recovery man page: "check_recovery compares the current state of the system to the System Recovery status file (created by the last invocation of make_recovery) to determine if a new System Recovery Tape needs to be created."

check_recovery, contrary to what MANY people believe, does NOT check to make sure your make_recovery, or make_tape_recovery, tape is good.

Keep creating your tape with make_tape_recovery. Don't worry about make_recovery and the '-C' option. It adds unnecessary time to the tape creation process and its just easier to go ahead and create a new tape. If you think you need a new make_tape_recovery tape, then you probably do.

[Sridhar Bhaskarla]

Patrick is right that I meant check_recovery (used to typing make_ for every ignite command :-). Thanks for the correction.

But he might be wrong thinking that I thought check_recovery is to check the ignite tape. That is the reason why I only mentioned that it was a useful command and advised to check the man page. In a nut shell, it tells you whether you need a fresh ignite tape based on the previous session. This was the answer to one of your questions about "tips". I always use -C option so that I can later use check_recovery.


-Sri

[someone_4]

Whooo hoooo! I just did a recover and it worked great!!It took a bit of time to recover and 2 reboots but everything went fine. It was an intresting process.I did move the vmunix and some of the files in rc.config.d files. But it was good stuff.

Thanks everyone
Richard

[James R. Ferguson]

Hi Richard:

I'll make two additonal comments for you. First, I agree with Patrick in regard to using 'check_recovery' -- in my opinion it doesn't gain you much. It is much simpler to remake the Ingite recovery tape/archive on a routine basis or whenever configuration changes have been made. Moreover, it is likely that the command will disappear in a later Ignite release.

Secondly, if you ever implement (and I hope you do) an off-site Disaster Recovery plan, you will be utilizing your Ignite recovery tapes on hardware with (certainly) different I/O configurations.

In these cases, choose the "Advanced Installation" mode. This will give you the ability to select and control filesystem properties and/or choose whether you want to manually run '/sbin/set_parms' to setup the hostname and networking characteristics after the initial Ignite or let it be automatically done.

Map files on your volume groups were captured by the 'make_tape_recovery' process, and included on the tape you created. The Ignite recovery will attempt to 'vgimport' using these specifications. If you have different and/or missing device files as on a different server, then this will "fail". You will see a block-letter "FAILURE" message at the end of the ignition for this reason, but you *will* have a viable vg00. Review the install.log to confirm this and manually 'vgimport' your volume groups. If you have any mirrored logical volumes, you will have to re-mirror them manually since Ignite does not handle this.

Regards!

...JRF...

[Darrell Allen]

Hi Richard,

My 2 cents...

copy_boot_tape will read a make_tape_recovery tape. It will extract either the bootimage, archive, or both. Sri's command should write bootimage to /tmp/bootarea (providing it exists and has enough space - guessing about 60MB). I use this regularly after doing make_tape_recovery:

copy_boot_tape -u /dev/rmt/0mn -d /var/tmp -b

You can use lifls and lifcp again bootimage just as you would against the lif area of a disk.

I do agree that the best test is to boot from the tape but for me, that's not something I can do everytime I create a tape. I boot off one occassionally but the rest of the time I rely on copy_boot_tape.

Darrell

[Sridhar Bhaskarla]

It is surprizing to see that there are misconceptions about misconception of using -C option.

My environment is where there are a number of administrators and hundreds of systems. Change is almost constant. When we do the change, we do it on multiple systems together and I can't run around with many tapes each time I make change. The best way is to check what changed since the last time the other administrator took the ignite. I don't care if nothing changed since then. This process is working like a charm for us and we don't mind spending a couple of minutes extra while taking the ignite.

So, it is not a general and recommended rule not to use -C option. If it fits to you, use it. I don't think HP would spend on developers to develop useless programs for no reasons.

-Sri

[John Carr_2]

Hi

I have no answer but I would like to know the outome. please tell us what happened

and please assign some points to those who helped you , cheers

John.

[Magdi KAMAL]

Hi Richard,

You can do this test in a test environment. If it is a production server and you do not have an test server you can try doing it by friday night so that in case of troubles you still have stareday and sunday for recovering ! ( of course if your production do not work in the weekend ).

Attention :

The only thing that Ignite-UX is not able to do and you must do it manuely IS :

Mirroring the internal disks ( of course if they are !).

Have alot of fun.

Magdi