make_recovery -v -A -p

[Eddie Warren]

I am using a make_recovery tape to build a new root drive. With the -p option I can edit the config.recover file to designate the new hardware path and configure the file system layout. Once this was done, I did a make_recovery -r to dump it to tape. My concern is when I attempt to run this make_recovery tape will I lose the /etc/lvmtab, do I need to vgexport and create mapfiles for vg01 and above. I will be leaving the original boot drive alone, just in case I need to bail out. Thanks.

[Alan Riggs]

Unless you edit out the /etc/lvmtab during the pause phase, you will not lose it. Make_recovery is designed to re-install an image onto the same hardware, so it keps all device information static. It can also, of course, be used to clone systems onto identical hardware.

[Bernadette Keohan]

Hi Eddie,

There is one cautionary note with make_recovery. It was designed for OS system recovery, not as a regular backup utility. make_recovery -A does a complete system image of vg00, it does not back up data (by default) any other volume group. There is one exception to this and it is very well documented in the make_recovery man page.

The fact that vg01, vg02, etc., are restored when you do a system recovery is because the /etc/lvmtab is read on bootup causing the additional volume groups to be activated.

Hope this helps,
Bernie

[Eddie Warren]

Thanks for the response, I appreciate the help. I was able to build the new (18gb) root drive. I had previously setup the file system sizes by editing the /var/opt/ignite/recovery/config.recover file.
everything went smooth. thanks