- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ignite-UX recovery overwrite
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
тАО09-14-2004 10:05 PM
тАО09-14-2004 10:05 PM
ignite-UX recovery overwrite
just one simple question: does ignite-ux overwite / delete files which it doesn't restore? I mean, for example, those included in a vg different from the boot vg.
thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 10:14 PM
тАО09-14-2004 10:14 PM
Re: ignite-UX recovery overwrite
Sunil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 10:16 PM
тАО09-14-2004 10:16 PM
Re: ignite-UX recovery overwrite
yes, because recovery process creates new disk structure and overwrites all disk contents.
Regards,
Zygmunt
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2004 10:20 PM
тАО09-14-2004 10:20 PM
Re: ignite-UX recovery overwrite
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2004 09:19 PM
тАО09-15-2004 09:19 PM
Re: ignite-UX recovery overwrite
using a recovery tape will definitely overwrite anything on your boot disk(s).
Therefore, like Pete says, it is best practice to use -x inc_entire=vg00 to include all of the vg00 or whatever name your root VG has.
You may use the -x include to include other VGs or filesystems or individual files.
*IF* you do that, then *anything* on those disks/in those vgs where the included files are will be deleted upon recovery because the VG will be newly created on the corresponding disk, the lvols will be recreated and newfs will be run. So in the end those non-root VG filessystems will be empty except for the files included in the recovery image.
There may be a problem with mount points under /etc if you mount non-root VG filesystems there. This is because /etc as a directory is considered a "minimun_runtime_essential" and included as a whole.
Run make_net_recovery using -v and refer to your /var/opt/ignite/recovery/latest/recovery.log to see in detail what filesystems are included.
Regards,
Bernhard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2004 02:13 AM
тАО09-16-2004 02:13 AM
Re: ignite-UX recovery overwrite
You should have a careful look at the Ignite-UX Admin Guide. Here's a link to it online:
http://docs.hp.com/hpux/onlinedocs/B2355-90837/B2355-90837.html
You can download a PDF copy by clicking a link at the top of this page.
In the Q&A section of the guide, there is an answer that deals with what you're asking. Here's an excerpt (from page 239 of the June 2004 edition):
-----------------------------------------
Beginning with the Ignite-UX A/B 2.0 releases, you can edit values in
any of the interface dialog boxes without turning off recovery_mode.
This is possible because critical system files are no longer automatically
overlaid by ones from the archive.
Recall that the /etc/fstab file that Ignite-UX created while configuring
the disks was saved to a backup copy prior to extracting the archive.
After Ignite-UX boots from the client disk, this fstab is merged with the
fstab file extracted from the recovery archive. This merging allows
Ignite-UX to preserve information from the old fstab, like entries for file
systems not included in the archive, NFS mounts, etc., while accurately
representing the configuration changes requested.
Special care needs to be taken when making changes affecting disks not
included in the archive. Imagine that you include vg00 and vg01 in your
recovery archive but not vg02. You intend to leave vg02 untouched and
simply let Ignite-UX import it for you.
You have also been planning on adding a new disk to the root volume
group, and you decide that this is as good a time as any to do it. You
choose your recovery configuration from the list and then go to the
Add/Remove Disks dialog box, where you choose a disk to add. By mistake
you choose a disk already in vg02 instead of your new disk. When your
system comes back up, vg00 and vg01 are fine, but vg02 is corrupted.
To avoid scenarios like this, Ignite-UX now "hides" disks intended to be
imported again. If you want to see these disks, click Additional... on the
Basic tab and change the setting there to show the disks.
-----------------------------------------
I hope this helps clear things up!
Best Regards,
Dave