- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NON ROOT VG'S restore for DR
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 07:32 AM
тАО06-29-2009 07:32 AM
For DR, you can recover the vg00 using Ignite. Ignite will boot the server and rebuild your vg00 and restore vg00. Once you have working OS, you can use restore method for other vg's from frecover/omniback/veritas and you are back in business.
My Question is:
ON THE DR SITE:
wERE the external vgтАЩs made manually or did a vgimport on the external vgтАЩs at restoration time was used to get the vg configuration back. If u used vgimport then of course u got the same disk device files. But at the DR site they donтАЩt have the same device filesтАж. Does that matter?., In DR we just give them disk space size as to how much we want and they just assign space through SAN.
In conclusion, the vg configuration for non root vg's... R they created manually again on DR site or vgimport is used to get those configuration back and if so what about the difference in disk device files??? (the original ones and the ones provided at DR site).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 07:47 AM
тАО06-29-2009 07:47 AM
SolutionAt the DR site you should plan to build volume groups just as you originally did. That is, you will be given some set of physical disks with the server on which you will recover. You should 'pvcreate' the physical disks (of your choice); 'vgcreate' your volume groups; 'lvcreate' your logical volumes within those volume groups; 'newfs' filesystems in those logical volumes; and lastly restore their data from your backup.
The actual device files used don't matter to your recovery.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 07:47 AM
тАО06-29-2009 07:47 AM
Re: NON ROOT VG'S restore for DR
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 07:59 AM
тАО06-29-2009 07:59 AM
Re: NON ROOT VG'S restore for DR
Since you are recovering the system from the ignite backup, you have to manually create the VGs & restore from backup in the space assigned thru SAN.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-29-2009 08:23 AM
тАО06-29-2009 08:23 AM
Re: NON ROOT VG'S restore for DR
Most DR sites are not exact hardware copies of production.
What I want at an offline site is:
1) Ignite system backup of vg00.
2) Backup of shared storage data.
3) Documentation on how to bring the system up. The assumption should be I am not available to do the build.
The plan is restore the system from Ignite, have a plan for setting up shared storage to handle the step 2 data and then restore it.
There are almost always manual steps in a DR site unless you use Service Guard Continental Cluster to keep it up to date.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com