System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Capture Existing Info for VG's, LVs etc for DR

SOLVED
Go to solution
MSwift
Regular Advisor

Capture Existing Info for VG's, LVs etc for DR

We are going to do DR for a Production node and i need to capture the existing details so that i can use the exact same information to build volumes, file systems , raw volumes, VG's, LV's, kernel etc for xomplete DR. Does some one has a script for this so that we could use that to build the DR machine?

Thanks

Mike.
4 REPLIES
James R. Ferguson
Acclaimed Contributor

Re: Capture Existing Info for VG's, LVs etc for DR

Hi Mike:

Simply record your configuration with standard LVM commands ('lvdisplay', 'vgdisplay') and/or examine your Ignite print_manifest.

From this, you can easily create a "script" that performs 'pvcreate'; 'vgcreate', 'lvcreate' and 'mkfs' commands at the Disaster Recovery site. You can simply stub-in physical device addresses ('/dev/rdsk/cXtYdZ') since you won't know these until you are actually at the site.

Regards!

...JRF...
Stephan.
Honored Contributor

Re: Capture Existing Info for VG's, LVs etc for DR

Hi,
for the LVM Part vgcfgbackup(1M)could help you:

http://docs.hp.com/en/B2355-90692/vgcfgbackup.1M.html

You can as well export all vg's with preview option to a map file.

3rd Party tool would be config2html:

http://come.to/cfg2html

As last step i would take a fresh ignite of the box.

hth
Bill Hassell
Honored Contributor
Solution

Re: Capture Existing Info for VG's, LVs etc for DR

As mentioned, vgdisplay is the primary source but it MUST be vgdisplay -v to get the details. Then you must get a copy of the mapfiles. Although they are usually accurate in /etc/lvmconf, I would make a fresh set with:

vgexport -ps -m myvg.mapfile myvgname

The only practical way to restore the DR system is with Ignite/UX. Naturally you need similar (ideally, identical) hardware. And finally a copy of /etc/fstab. I would spend time writing down all the steps to creating needing information, then the steps to bringing the system(s) up at the DR site. This includes networking, power and UPS, physical access control and security, etc.

Finally, rehearse, rehearse, rehearse. Assume the worst (smoke and rubble) at your production site and then start writing down all the questions...


Bill Hassell, sysadmin
Lijeesh N G_1
Respected Contributor

Re: Capture Existing Info for VG's, LVs etc for DR

Hi,

You can get information's by the below simple script,

#script /tmp/info.txt <<==Staring the script and the output will save in /tmp/info.txt file.
#echo "General System informations"
#echo "==========================="
#uname -a
#model
#ioscan
#echo "LVM Informations"
#echo "================="
#vgdisplay -v
#lvdisplay -v
#strings /etc/lvmtab
#bdf
#cat /etc/fstab
#lvlnboot -v
#setboot
#echo "Kernel informations"
#echo "==================="
#kcmodule
#kctune
#echo "Disk Informations"
#echo "================="
#ioscan -fnC disk
#diskinfo
#echo "Installed software informations"
#echo "==============================="
#swlist -l bundle
#swlist -l product
#swlist -l product|grep PH
#exit
#echo "Network informations"
#echo "===================="
#ioscan -funC lan
#netstat -in
#netstat -rn
#exit <<===Exit the script

Check /tmp/info.txt file, it will have all the above command outputs.

Hope this will help you.

Regards,
LIJEESH N G