- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- make recovery
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
тАО05-16-2001 06:26 AM
тАО05-16-2001 06:26 AM
The following is where I would like some clarification. Will the make recovery create a new lvmtab? More importantly, will all of my volume groups, lvm and directory structures be lost (besides the vg00)? If so, I guess I would have to create a script to go in and rebuild all of that information before I did a restore of non-root data. I take it secondary swap will also have to be recreated (if not on vg00).
Thanks for any help you can provide.
We currently use /opt/ignite/bin/make_recovery -A -d /dev/rmt/0m to create our make recovery tape.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 06:31 AM
тАО05-16-2001 06:31 AM
Re: make recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 06:34 AM
тАО05-16-2001 06:34 AM
Re: make recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 06:47 AM
тАО05-16-2001 06:47 AM
Re: make recovery
Vincenzo...I will read through your link...thx
Jim... I have some follow up questions...So when you make recover on the same server the lvmtab will be there...is it there because it still exists on the server or because it was archived on the make recovery tape and put back on the server...2nd..Why is the lvmtab good for the same server but not for a d/r server (different server)?
Finally, let me go back to step one...if you use a make recovery on your current server it will rebuild your vg00. Does it destroy everthing else...all of your vg's, data, etc and make the server 'clean' or does it ONLY build vg00 and not touch anything else...leaving any non-root informatin there.
thx again...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:01 AM
тАО05-16-2001 07:01 AM
SolutionAnd for your last question. make_recovery actually uses tar to copy your vg00 data to tape. The first step in make_recovery it to put a LIF at the beginning of the tape to make it bootable. Always use /dev/rmt/Xmn no-rewind when running make_recovery. So what make recovery does is copies everything in your vg00 to tape. That includes all volume information. It won't destroy anything at all. It's harmless. If you are forced to restore on your existing system. The only thing you need to do is to boot off your most current make_recovery tape. Once vg00 is restored and you reboot. Your volume information for all other vg's will already exist and your logical volumes will mount.
I hope this helps.
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:05 AM
тАО05-16-2001 07:05 AM
Re: make recovery
That is norewind.
Make recovery writes a LIF area on tape as the 1st file set and then does the archive. I was unable to recover when I had used 0m.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:07 AM
тАО05-16-2001 07:07 AM
Re: make recovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:18 AM
тАО05-16-2001 07:18 AM
Re: make recovery
thx for the heads up...before the restore, when the tape is loaded cant you just do a rewind on the tape
mt ?t /dev/rmt/
and then boot using the tape drive path obtained from
ioscan ?fnCtape
I have never used a make recovery to restore.. but this is how we have our current procedures...and I believe they have worked in the past.
Let me know your thoughts as I am just trying to fully understand this process.
Jim - thx for the info
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:30 AM
тАО05-16-2001 07:30 AM
Re: make recovery
Jim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-16-2001 07:57 AM
тАО05-16-2001 07:57 AM
Re: make recovery
I'd like to add several comments.
> 'make_recovery' is being replaced by a richer 'make_tape_recovery'. I'd go to the Ignite website and download the newest Ignite software:
http://www.software.hp.com/products/IUX/index.html
> To create a recovery tape for vg00 you can do this:
make_tape_recovery -x inc_entire=vg00 -I -v -a /dev/rmt/0mn
> Notice the new 'inc_entire' option. This allows you to collect data from volume groups other than vg00.
> 'vgexport' map files of all volume groups are captured by 'make_tape_recovery' and placed on its tape. Ignite will use these to 'vgimport' non-vg00 volumes during a recovery. This is quite nice if you are merely using Ignite to resize or repair vg00.
If you are restoring onto "unlike" hardware, as for instance at an off-site disaster recovery center, then you will need to create your volume groups using available disk and restore your data.
...JRF...