Operating System - HP-UX
1748053 Members
4876 Online
108758 Solutions
New Discussion юеВ

Re: ignite-UX recovery overwrite

 
Andrea Rossi
Frequent Advisor

ignite-UX recovery overwrite

Hi all

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
5 REPLIES 5
Sunil Sharma_1
Honored Contributor

Re: ignite-UX recovery overwrite

Yes it is.

Sunil
*** Dream as if you'll live forever. Live as if you'll die today ***
Zygmunt Krawczyk
Honored Contributor

Re: ignite-UX recovery overwrite

Hi,

yes, because recovery process creates new disk structure and overwrites all disk contents.

Regards,
Zygmunt
Pete Randall
Outstanding Contributor

Re: ignite-UX recovery overwrite

I think this would depend on what you backed up. If you include other VGs besides vg00 in your backup via the "-x inc_entire=vgXX" option, I *think* (since I don't advocate doing this I've never tried it) that the other VGs would get restored. On the other hand, if you only backup vg00, then only vg00 will get restored and you'll need to re-create other VGs yourself.


Pete

Pete
Bernhard Mueller
Honored Contributor

Re: ignite-UX recovery overwrite

Andrea,

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
Dave Unverhau_1
Honored Contributor

Re: ignite-UX recovery overwrite

Andrea,

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
Romans 8:28