NAME
make_net_recovery - network based system recovery archive creation
SYNOPSIS
/opt/ignite/bin/make_net_recovery -s Ignite-UX_server
[-a archive_server:archive_directory] [-A] [-N] [-b] [-d
tag_string] [-f content_file] [-i|-ib] [-l LLA] [-n
number_archives] [-p]
[-P s|w|e] [-m tar|cpio|pax] [-r] [-u] [-v] [-x content-options]
[XToolkit_Options] [-?]
DESCRIPTION
make_net_recovery creates a system recovery archive and stores the
archive on the network. The archive created by make_net_recovery is
specific to the system for which it was created and its identity
includes hostname, IP address, networking information, etc. In the
event of a root disk failure, the recovery archive may be installed
via Ignite-UX to restore the system.
The contents of the system recovery archive will always include all
files and directories which are considered essential for bringing up a
functional system. This "essential list" is predefined by
make_net_recovery. By running make_net_recovery in interactive mode,
the directories and files which make up the "essential list" may be
displayed. In addition to the essential list, data may be included in
the archive on a disk/volume group, file, or directory basis.
Nonessential files and directories may also be excluded.
Starting with the March 2008 release of HP-UX 11i v3, LVM supports
Volume Group Version 2.0. Refer to lvm(7) for more details on
different Volume Group Versions supported by LVM. Please read the
WARNINGS section for the limitations and restrictions of this command
with regard to supportability of LVM Volume Groups having Volume Group
Versions 2.0 or higher.
Options
make_net_recovery recognizes the following options:
-s Ignite-UX_server
Specifies the hostname of the Ignite-UX server. The
configuration files, defaults and contents files for the
client system will be written to the Ignite-UX server in
/var/opt/ignite/clients/0xLLA/recovery. The
make_net_recovery tool will NFS mount the per-client
directory to access this information.
-a archive_server:archive_directories
Specifies the NFS server and location onto which to store
the archive. The archive directory must be NFS exported (see
the section Exporting Archive Directory), and sufficient
disk space is required. The default is the hostname of the
Ignite-UX server followed by the directory which holds the
archive, e.g.,
Serverhost:/var/opt/ignite/recovery/archives/hostname. The
hostname is the name of the system being archived. Each
make_net_recovery client will create a subdirectory named
for the client hostname under the specified directory to
store the archives.
-A Based on the files that are specified for inclusion, this
option determines which disk(s) and/or volume group(s)
contain those specified files, and includes all files from
those disk(s) and/or volume group(s) in the archive.
-N Indicates no compression for archive. By default, archives
are compressed using gzip.
-b When used in combination with the -i option, causes
make_net_recovery to run in the background after the
interactive user interface (UI) completes.
-d tag_string
One line tag_string for the system recovery archive. If the
tag_string includes spaces, it must be enclosed in quotation
marks. The tag_string will be displayed when choosing the
archive as a configuration from the Ignite-UX interactive
user interface. The default tag_string is Recovery Archive.
The tag_string is specified in the INDEX file as the value
for the cfg keyword, and must not exceed 80 characters.
-f content_file
Location of the file which identifies keywords to specify
inclusions and exclusions for the archive. The default is
/var/opt/ignite/clients/0xLLA/recovery/archive_content.
This default file is located on the Ignite-UX server and
accessed by the client through an NFS mount. The absolute
path name to the archive_content file must be supplied as an
argument to the -f option. This option may be useful when
there is a desire to manage multiple files which specify the
content of the archive. The -f option is not allowed when
using the -x or -A options to specify the contents of the
archive. (See the Including and Excluding From Archive
section for file format.)
-i Causes make_net_recovery to run interactively to allow
selection of files and directories that are to be included
in the recovery archive. The options -x, -A and -f are not
allowed with -i. It is preferable to use the ignite GUI
menu command on the Ignite-UX server when running an
interactive make_net_recovery session. Running it from
ignite ensures that any server configuration of NFS mounts
is already done. It also provides a better progress report
and an easier to use interface.
-l LLA
The LLA (link-level address) of the system being archived.
Used to create the per-client directory on the Ignite-UX
server.
-n number_archives
Specifies the number of archives that should remain on the
server at any given time. The default is two (2). If
number_archives is two and there are already two archives
present when a third is being created, make_net_recovery
will remove the oldest archive after successfully creating
the newest archive.
-p Previews the processing that would take place without
actually creating the archive. This is a way of verifying
the directory /var/opt/ignite/recovery/latest (which is
linked to the latest archive directory of the form
/var/opt/ignite/recovery/date,time) on the local (client)
system. To access this directory on a specified Ignite-UX
server, the directory is located at
/var/opt/ignite/clients/0xLLA/recovery/date,time. The
directory contains the files archive_cfg, control_cfg, and
system_cfg that were created with the configuration
information desired. It also contains the file flist that
lists the files that make up the archive. It is best not to
modify this file. However, it may be edited to exclude some
files/directories from the archive by deleting the entire
line, if desired. Only files or directories that are known
to be user created should be deleted. The files that end in
_cfg contain configuration information that may be changed.
For example, converting from HFS to VxFS. No further checks
are done by make_net_recovery. The creation of the System
Recovery Archive may then be resumed using the -r option.
-P s|w|e
When a disk or volume group is partially included in the
system recovery archive, generate an ERROR (e), WARNING (w),
or SUPPRESS (s) any warning messages that would normally be
generated when partial inclusions occur. The default is w,
causing WARNING messages to be produced when partial
inclusions of disks and/or volume groups are detected. When
e is specified, an error message will be displayed to both
stdout and to the log file, and execution of
make_net_recovery will stop once the error message is
displayed.
-m tar|cpio|pax
Specify in which format (tar, pax, or cpio) the
files/directories image in the archive will be stored. tar,
pax, or cpio may be specified. If this option is not
specified, tar is the default format.
-r Resumes creation of the System Recovery Archive after the -p
option was used to create the
/var/opt/ignite/recovery/latest directory, and its *_cfg
files have possibly been edited. If the -A and -r options
are both used, the -A option will be ignored, since the file
list, flist, and other configuration files, *_cfg, have been
created and possibly modified.
-u Updates the Ignite-UX software from the Ignite server
specified by the -s option. This is done only when the
version of software on the server is newer than the client.
The software update uses the depot on the server in the
location: /var/opt/ignite/depots/recovery_cmds. If this
depot does not exist, you may use the
/opt/ignite/lbin/pkg_rec_depot command to create it. When
the -u option causes the software to be updated, it then
automatically restarts the command with the same options.
-v Display verbose progress messages while creating the system
recovery archive. Includes information such as which volume
groups/disks will be included in the system recovery
archive.
-x include=file|directory
Includes the file or directory in the recovery archive, but
does not cross any mount points. Note, file names may NOT
end with a space.
-x inc_cross=file|directory
Includes the file or directory in the recovery archive and
crosses mount points to access any directories that are
mounted or files contained in directories that are mounted.
This option is for crossing local files system mounts only;
not remote file system mounts. Note, file names may NOT end
with a space.
-x inc_entire=disk|vg_name
Includes all file systems contained on the specified disk or
volume group. Use a block device file (e.g.,
"/dev/dsk/c0t5d0") when specifying a whole-disk (non-volume
manager) file system. Use the volume group name (such as
vg00) when you want all file systems that are part of that
LVM volume group to be included in the archive.
-x exclude=file|directory
Excludes the file or directory from the archive. When a
directory is specified, no files beneath that directory will
be stored in the archive. If the excluded directory is an
unmounted file system shown in the /etc/fstab file, a
WARNING ("Filesystem xxx is not mounted. It will be
ignored.") message will be displayed.
Note, file names may NOT end with a space.
-x print_manifest_args=<print_manifest arguments>
Passes the given <print_manifest arguments> to the
print_manifest command. This can be done to reduce the
amount of time required by make_net_recovery. Please see
print_manifest(1M) for more details.
XToolkit-Options
The make_net_recovery command supports a subset of the
standard X Toolkit options to control the appearance of the
GUI when the -i option is specified. The supported options
are: -bg, -background, -fg, -foreground, -display, -name, -
xrm, and -synchronous. See the X(1) manual entry for a
definition of these options.
-? Displays the help screen.
Including and Excluding From Archive
The contents of the archive may be controlled from the contents file
(see -f). The full path for the contents file is
/var/opt/ignite/clients/0xLLA/recovery/archive_content on the Ignite-
UX Server. This file consists of keyword identifiers which specify
the inclusion of files, directories, or entire disks and volume
groups. The keyword identifiers also instruct make_net_recovery
whether to follow mount points when creating the system recovery
archive. The contents file has the following keyword identifiers:
include filename | directory
Includes the specified filename or directory and all
subdirectories and associated files. Mount points are not
crossed and symbolic links are not followed. Note, file
names may NOT end with a space.
inc_cross filename | directory
Include the specified filename or directory and all
subdirectories and files contained underneath
subdirectories. Local mount points are crossed but symbolic
links are not followed. Note, file names may NOT end with a
space.
inc_entire volume group | disk
Include the entire specified volume group (e.g., "vg00") or
disk (block device - e.g., "/dev/dsk/c0t5d0"). Do not
specify a disk if it is part of a volume group.
inc_all_affected
Is equivalent to using -A option. Based on the files that
are specified for inclusion, this option determines which
disk(s) and/or volume group(s) contain those specified
files, and includes all files from those disk(s) and/or
volume group(s) in the archive.
exclude filename | directory
Exclude the specified filename or directory and all
subdirectories and files contained under the subdirectories.
Note, file names may NOT end with a space.
make_net_recovery reads the contents file to generate the list of
files that will be used to create the system recovery archive. The
contents file may be modified by hand or by running make_net_recovery
in interactive mode. When modifying the contents file, keep the
following points in mind:
+ No essential file or directory may be excluded. Exclusions of
essential files or directories will be ignored.
+ Exclusions take precedence over inclusions. Anything that is
both included and excluded will be excluded from the archive.
+ The ordering of inclusions and exclusions within the defaults
file is not significant.
+ File names may NOT end with a space.
+ The files and directories under NFS or LOFS mounts will not be
archived.
Using Settings From Previous Archive Creation
The defaults file stores input specified by interacting with the
make_net_recovery GUI. Options are preserved until the next archive is
generated by interacting with the GUI. Command-line options will
override settings in the defaults file. The full path for the defaults
file is /var/opt/ignite/clients/0xLLA/recovery/defaults on the
Ignite-UX server. This directory is accessed via NFS from the client.
###### defaults file ######
RECOVERY_LOCATION=15.1.2.3:/var/opt/ignite/recovery/archives/client_name
RECOVERY_DESCRIPTION="Recovery Archive"
SAVE_NUM_ARCHIVES=2
ARCHIVE_TYPE=tar
Saving the LIF Area
The LIF area of a disk will be archived and restored if it is
different from the default LIF area. This means if either the auto-
boot line in the AUTO LIF file is not "hpux" or the LIF files in
addition to ISL, HPUX, LABEL, and AUTO are present, then the LIF files
will be copied to /usr/lib/ignite_bootlif. These LIF files will be
restored to the LIF area unless a LIF file with the same name already
exists or the AUTO file contains something other than hpux.
Using the Recovery Archive
To recover a failed system using the network recovery archive:
+ If the client system is being replaced, or the LAN card has
changed since make_net_recovery was last used, you should
manually rename the old client directory prior to starting the
recovery. Not doing so will cause a new directory to be
created and you will not see the recovery archives created
under the old client directory. To rename the client
directory, obtain the new LAN address (you can use the
LanAddress boot-ROM command in the information menu), then use
the mv command. For example:
cd /var/opt/ignite/clients
mv 0x00108305463A 0x0060B0C43AB7
If you have already booted the new system, you will need to
remove the new client before renaming the old directory. Be
careful not to remove the old directory containing the
recovery information.
+ Boot the system using either a network boot, a tape created
using make_boot_tape, or using the bootsys command if the
system is still running.
+ Do not interact with ISL.
+ Select: [ Install HP-UX ].
+ From the Ignite-UX GUI, select the icon for the client.
+ Choose Install/New Install.
+ Select the recovery configuration to use.
Exporting Archive Directory
The directory used to store the archives must be exported from the
archive server to each client. Exporting the archive directory from
the system where the archive will be stored enables make_net_recovery
to create and access the archive via NFS. The archive server by
default is the Ignite-UX server but may be changed using the -a option
to be a different remote server, or even the local client if you want
to capture the archives as part of the client's regular backup. Note
however, that if the archives are stored on the client itself, they
must be put onto a remote server if the client ever needs to be
recovered using them.
For security reasons, it is best to export each client-specific
archive directory to just the individual client. If the recovery
archive creation is initiated from the ignite GUI on the Ignite-UX
server, and the archive server is the same as the Ignite-UX server,
the /etc/dfs/dfstab or /etc/exports file will be edited automatically
so the archive may be stored in the desired location. Otherwise, if
make_net_recovery is run directly on the client, the following steps
are required to be performed on the archive server.
+ On the archive server, create a directory for each client to
contain the archive of the client's files. It is important that
the directory be owned by the user bin. Replace client in the
commands below with the hostname of the client. If you use the -a
option to make_net_recovery to specify an alternate location for
the archives, you will need to use that path instead of the
default which is shown below.
mkdir -p /var/opt/ignite/recovery/archives/client
chown bin:bin /var/opt/ignite/recovery/archives/client
+ For 11.31 or later, edit /etc/dfs/dfstab to add an entry for each
client. Replace client with the client's fully qualified hostname
in the example shown:
share -F nfs -o sec=sys,anon=2,rw=client
/var/opt/ignite/recovery/archives/client
For other releases, edit /etc/exports to add an entry for each
client. Replace client with the client's hostname in the example
shown:
/var/opt/ignite/recovery/archives/client -anon=2,access=client
+ For 11.31 or later, run the shareall command to have the edits to
the exports file take effect:
/usr/sbin/shareall -F nfs
For other releases, run the exportfs command to have the edits to
the exports file take effect:
/usr/sbin/exportfs -av
Networking Features
Two NFS mount points are established on the client by
make_net_recovery. The /var/opt/ignite/clients directory on the
Ignite-UX server is mounted to the client system to store
configuration files which describe the client configuration and
location of the recovery archive. The second mount point is made to
the archive_server:archive_directory (see the -a option) and is used
to store the recovery archive of the client system. After successful
or unsuccessful completion of the system recovery archive, the NFS
mount points are unmounted.
The NFS mount for the archive directory may be exported on a per-
client basis. A separate archive directory is used for each client.
This allows the NFS export of each directory only to the individual
client owning the archive, which provides security.
If the default NFS mount options are unsuitable for your network
environment, you can pre-mount those directories with whatever options
are necessary. make_net_recovery will discover that they are already
mounted and not attempt to mount them. For example, you can do the
following if the read and write buffers had to be 1KB in size:
mount -F nfs -orsize=1024,wsize=1024 archive_server:archive_directory \
/var/opt/ignite/recovery/arch_mnt
mount -F nfs -orsize=1024,wsize=1024 archive_server:/var/opt/ignite/clients \
/var/opt/ignite/recovery/client_mnt
The actual arguments must match those for the -a option if it is used
in the first mount command.
If the client system does not have the most recent versions of
Ignite-UX tools, the Ignite-UX GUI uses swinstall to install the
recovery package which includes all necessary files to perform the
recovery.
International Code Set Support
Ignite-UX uses a variety of system commands to accomplish its
functionality. Because the output of many of these commands is
parsed, Ignite-UX ensures that the POSIX locale is normally used by
modifying environment variables. Help text and some command output
not parsed by Ignite-UX will be left in the user's specified locale.
RETURN VALUE
make_net_recovery returns the following values:
0 No warnings or failures occurred; the execution completed
successfully.
1 A failure occurred.
2 A warning occurred.
EXAMPLES
Since make_net_recovery actually runs on the client instead of the
server, all examples have the -s server command-line option. This
option is required for the command, so that the client (local system)
will know what system to contact as the Ignite-UX server.
Create a system recovery archive by interacting with the Ignite-UX GUI
from the Ignite-UX server:
export DISPLAY=hostname:0
ignite
Create a system recovery archive from the client, using settings from
the last invocation of the Ignite-UX GUI:
make_net_recovery -s myserver
Create a system recovery archive with all the files/directories on the
disk(s)/volume group(s) containing the files specified by the default
essentials file list /opt/ignite/recovery/mnr_essentials or the user-
defined version of this file, that replaces this file,
/var/opt/ignite/recovery/mnr_essentials:
make_net_recovery -s myserver -A
Create a system recovery archive that includes files from all file
systems in the vg00 volume group:
make_net_recovery -s myserver -x inc_entire=vg00
Create a system recovery archive that includes all of the vg00 and
vg01 volume groups, but that excludes the /depots directory:
make_net_recovery -s myserver -x inc_entire=vg00 -x inc_entire=vg01
-x exclude=/depots
Preview the creation of the System Recovery Archive:
make_net_recovery -p
Use the -u option to have the Ignite-UX software automatically updated
when needed from the Ignite server:
make_net_recovery -s myserver -A -u
This example assumes that the
/var/opt/ignite/depots/recovery_cmds software depot has been
created on the Ignite server. This depot is created by running
the ignite GUI at least once to make a recovery archive of a
system or by running pkg_rec_depot (see also pkg_rec_depot(1M)).
Once created, this depot will automatically be updated each time
Ignite-UX is updated on the server.
Use the -x option to pass arguments to the print_manifest command. In
this example the -d option will be passed so that disk capacity
collection via diskinfo is skipped to improve performance. Also the
-e option will be passed which causes the output file to be printed
with HP-PCL3 control codes for enhanced printer output.
make_net_recovery -s myserver -A -x print_manifest_args="-de"
WARNINGS
General Backup/Recover Not Recommended
The make_net_recovery toolset is intended only to create or recover a
recovery archive. The recovery archive will include the operating
system and a reasonable amount of user data. It is NOT intended to be
a general purpose backup and restoration tool, and should not be used
for that objective.
Creating and Restoring from a Minimal-Recovery Archive
Creating a minimal-recovery archive means creating a recovery archive
that contains just enough information to bring a system back up into a
minimal-operating state. This allows you to then restore all
additional information from a backup created with a general
backup/restore utility.
When restoring from a minimal-recovery archive, the boot process will
often contain errors due to the missing content. These errors are
corrected once the regular system backup is restored and the system is
rebooted.
Once the system has been rebooted, you may see the following note:
NOTE: The "/opt/upgrade/bin/tlinstall" command was not part of the
system that was installed. It was not possible to run it in
order to correctly set the permissions of the "transition"
symlinks. You may consider running:
"/opt/upgrade/bin/tlinstall -vf" after the system is
completely restored.
If software has not yet been installed using SD, the tlinstall command
may need to be executed at this time as described above.
Standards May Impose Limits on What May Be Archived
The pax command is used to create and recover recovery archives.
There maybe limitations in the pax command that impose limits on what
can or cannot be placed into a recovery archive. Some examples of
this are:
+ ustar format archives may contain raw uids and gids up to 2097152.
Because the text user and group name are stored, it may be
possible to recover uids and gids larger than 2097152.
+ cpio format archives are strictly limited to uids and gids up to
262144.
+ ustar format archives cannot contain a file name pointed to by a
link that is more than 100 bytes long (required by POSIX.1).
+ pax format archives can contain files that are larger then 8 GB,
ustar and cpio can not.
Disks Will be Reformatted
If any file from a disk or volume group is included in the recovery
archive, that disk (or all disks in the volume group) will be
reformatted during the recovery, and only the files included will be
recovered. Any files that were not included in the archive, will have
to be restored from normal backups.
Disks and volume groups that did not have any files included in the
archive are not reformatted during a recovery and are reimported and
remounted at the end of the recovery.
Logical Volume Physical Extent Allocation Not Preserved
The make_net_recovery tool captures enough information from the system
so that during a recovery it may reconstruct all visible aspects of
the prior LVM configuration. This includes logical volume and volume
group names, attributes, and even minor number values. The tool also
ensures that the new logical volumes reside on the same disks within
the volume group as they did before.
make_net_recovery does not, however, ensure that logical volumes are
extended in the same exact order as they were originally. This means
the LVM physical extents allocated to a logical volume may be in a
different location on the disk than before. The recovery tools use a
very specific and complex algorithm for extending logical volumes to
ensure success (such as extending contiguous volumes before non-
contiguous). An example effect of this is that swap/dump volumes will
reside on the root disk ahead of some other volumes even though that
may not have been the original layout.
Logical Volume Distributed Allocation Policy Not Preserved
If logical volumes that are part of the volume groups being archived
were configured using the distributed allocation policy (also known as
"extent based stripes"), those volumes will be re-created during a
recovery with this policy turned off.
VxVM Disk Groups
The root-disk groups managed by VERITAS Volume Manager (VxVM) may be
included in the Ignite-UX archive since the B.3.8 release. However,
prior to B.3.8 release,the VxVM disk groups cannot be included in the
Ignite-UX archive. If they are included, make_net_recovery will error.
Those disk groups will be left undisturbed and reintegrated into the
system after the recovery is complete.
LVM Disk Mirrors Not Restored
The make_net_recovery tool will create a recovery backup for a system
with mirrored disks but it will not restore the mirrored disk
configuration. If the system is later recovered, previously mirrored
volumes will no longer be mirrored. They may be manually remirrored
after the system is up. Using the config.local file in the clients
directory, you may specify the LVM commands to restore mirrored disks
to be executed automatically after the system has been restored. For
more details, see the /opt/ignite/share/doc/diskmirror.pdf white
paper.
File System Volume Size May Be Modified
The file system volume size(s) in the recovery archive may be modified
when the archive is installed. By default, Ignite-UX will ensure 10%
free space for each volume and modify the file system volume size
accordingly.
If you do not want Ignite-UX to modify the file system volume size(s)
automatically, add:
init _hp_ignore_sw_impact=1
to the /var/opt/ignite/clients/0xLLA/recovery/latest/system_cfg file.
Warning: Setting _hp_ignite_sw_impact to 1 may cause recoveries to
fail if any file system sizes are reduced below the minimum required.
Note that changes to the system_cfg file must be done after a preview
has been created (-p). After making the above changes, resume the
creation of the tape recovery archive (-r).
File Names with Non-Printable Characters
Although permissible within HP-UX, it is inadvisable to use characters
that do not have a printable graphic on the hardware you commonly use,
or that are likely to confuse your terminal. Filenames with these
characters cause a warning message to be displayed by
make_net_recovery. In addition, files that contain these non-printable
characters are not included in the archive.
Running Commands in Single User Mode
HP recommends that the make_tape_recovery and make_net_recovery
commands be run in default mode of multi-user (run level 3 or 4
depending on how the system is configured). However, HP does support
execution of make_tape_recovery in single-user mode using the
supported method documented in Ignite-UX FAQs. (See Section 11,
Network/Tape Recovery, Question 23.) A copy of the Ignite-UX FAQs is
installed with Ignite-UX in /opt/ignite/share/doc/FAQ, and the latest
version of the Ignite-UX FAQ may be obtained by sending an email to
iux_faq@hpfcdn.fc.hp.com. HP does not recommend running
make_net_recovery in single-user mode.
Non-Responding NFS Servers
The make_tape_recovery and make_net_recovery tools can handle non-
responding automounted file systems accessed via indirect maps or the
-hosts map without hanging. However, the tools will hang if there are
automounted file systems accessed via direct maps or directly mounted
NFS file systems.
Unmounted File Systems in /etc/fstab file
If unmounted file system in /etc/fstab is detected, a WARNING message
will be displayed and the make_tape_recovery and make_net_recovery
will complete with return code 2.
Data Recovery from Raw Logical Volumes
Only file system data is included in recovery archives created by
make_net_recovery. Data included in raw logical volumes (like those
that contain database data) is not included in recovery archives, and
must be backed up as part of the overall backup stategy of a system.
Auto Port Aggregate (APA) Limitation
If a system has an auto port aggregate (APA) configured while the
recovery archive is created, Ignite-UX requires that at least one lan
interface exists that is not part of any aggregate. The same interface
must also be used to recover the system. On some systems this may
require an aggregate lan interface be disaggregated before creating
the recovery archive. If a system has an auto port aggregate (APA)
configured while the recovery archive is created, Ignite-UX does not
support cloning using that recovery archive. It is only supported to
recover the archive to the system on which it was created. This
assumes that the lan interfaces are still configured for APA, on the
switch they are connected to, in exactly the same way as when the
archive was created.
LVM Volume Group Version 2.x or higher
Ignite-UX does not support the system recovery archive creation using
the make_net_recovery command for Volume Groups having Volume Group
Version 2.0 or 2.1. If any LVM Volume Group having unsupported Volume
Group Versions is provided as arguments to make_net_recovery command,
the command fails and reports the unsupported volume groups. In such
situations, either omit the unsupported volume groups as input to
make_net_recovery command or migrate all those unsupported volume
group version to 2.2 or higher (using LVM's Volume Group Version
migration tool, vgversion) and rerun the command.
For LVM Volume Groups having Volume Group Version 2.2 or higher, if
the LVMP_CONF_PATH_NON_BOOT configuration variable in /etc/lvmrc file
is modified to store LVM configuration backups in a directory that is
not backed up by default, user may need to consider including that
directory for recovery.
Non-default Device Files May Not Be Recovered Correctly
Any custom agile device files may not be correct after a recovery.
Ignite-UX does not inventory or re-create custom agile DSFs. They may
be present post-recovery and may refer to the wrong device. It is up
to the person or application that created the custom agile DSFs to
verify that they point to the correct device and recreate them as
required or not use them. This includes custom agile pass-through
device files created by HP Integrity VM on 11.31 systems (on the host
system only). After recovery hpvmdevmgmt must be run on the host
system to recreate pass-through DSFs before starting a VM guest.
Failure to do so may cause HPVM host issues. Refer to hpvmdevmgmt(1M)
for more details.
In the event of instance changes during recovery, custom legacy DSFs
may point to the wrong legacy device. Post-recovery in the event of
instance changes in legacy devices it should be verified that any
required custom legacy DSF points to the correct device. It is the
responsibility of the person or application who created the custom
legacy DSF to ensure that they point to the correct device in these
circumstances before attempting to use them.
DEPENDENCIES
The Ignite-UX GUI must be run from the Ignite-UX Server, see
ignite(5). make_net_recovery depends on several other Ignite-UX
tools. When running the Ignite-UX server GUI, Ignite-UX checks
whether the client system that make_net_recovery runs on has the same
versions of Ignite-UX tools.
If running make_net_recovery from the command line without ever
interacting with the Ignite-UX GUI, commands will need to be installed
using swinstall(1M) from the Ignite-UX server to the client system on
which make_net_recovery will be run.
make_net_recovery requires the following filesets of the Ignite-UX
product be installed on the system:
Ignite-UX.MGMT-TOOLS
Ignite-UX.RECOVERY
AUTHOR
Ignite-UX and make_net_recovery were developed by the Hewlett-Packard
Company.
DIAGNOSTICS
All major steps within network recovery are logged on the server and
displayed via the Ignite-UX Server GUI.
FILES
/opt/ignite/recovery/mnr_essentials
Lists the files and directories that are considered essential and
are always included in the archive if they exist on the system.
/var/opt/ignite/recovery/mnr_essentials
Lists the files and directories that are essential, but acts as
the user modifiable version so that the original mnr_essentials
file may be maintained. When this file exists, its content is
checked before the file /opt/ignite/recovery/mnr_essentials.
/var/opt/ignite/clients/0xLLA/CINDEX
This file contains a list of Ignite-UX configurations that are
specific to the particular client with a network LLA as shown in
the path. This file supplies Ignite-UX with the configuration
files created by make_net_recovery and provides a list of
client-specific selections from which a user may choose during a
system recovery.
/var/opt/ignite/clients/0xLLA/recovery
The per-clients recovery directory. It holds the client's
recovery configuration, log, and status files as described below.
/var/opt/ignite/clients/0xLLA/recovery/archive_content
Supplies files and directories to be included or excluded. Using
the -x command line arguments will cause this file to be ignored.
/var/opt/ignite/clients/0xLLA/recovery/latest
A symlink to the date,time directory containing the newest set of
recovery files as described below.
/var/opt/ignite/clients/0xLLA/recovery/date,time
Directory containing files pertaining to the make_net_recovery
command that was run at the date and time indicated in the
directory name. An example path looks like:
/var/opt/ignite/clients/0x080009123456/2000-12-20,13:50
/var/opt/ignite/clients/0xLLA/recovery/date,time/system_cfg
Configuration file which describes the file system and networking
configuration of the system (generated by the save_config(1M)
command).
/var/opt/ignite/clients/0xLLA/recovery/date,time/archive_cfg
Configuration file which supplies the location and access method
to the archive containing the files to be restored.
/var/opt/ignite/clients/0xLLA/recovery/date,time/control_cfg
Configuration file which supplies control parameters and the
command scripts to import volume groups that will be preserved
and not created during the recovery.
/var/opt/ignite/clients/0xLLA/recovery/date,time/flist
"File" list file which supplies the list of files that are to be
archived. This is a plain text file, but should not be modified.
Each line is in a special format that, if altered, could cause
problems with the archive process.
/var/opt/ignite/clients/0xLLA/recovery/config.local
An optional configuration file that the user may create to add
configuration information to be used during the recovery of the
client. For example, you may want to add to this file to a
post_config_cmd to remirror disks that the recovery process
unmirrored. See the document
/opt/ignite/share/doc/diskmirror.pdf for an example. Once this
file is created, make_net_recovery will automatically add it to
any new configurations that it adds to the CINDEX file.
/var/opt/ignite/clients/0xLLA/recovery/date,time/recovery.log
Default log file location for make_net_recovery.
/var/opt/ignite/clients/0xLLA/recovery/date,time/manifest
Software and hardware manifest information installed and
configured for the system at the time the archive was created.
See print_manifest(1M).
/var/opt/ignite/recovery/archives/hostname
The default location on the Ignite-UX server for the client to
store the recovery archive. The hostname directory must be NFS
exported to the individual client with the matching hostname.
/var/opt/ignite/clients/0xLLA/recovery/defaults
Supplies the default options to make_net_recovery. Created when
run interactively using the -i option or by using the ignite GUI.
/var/opt/ignite/clients/0xLLA/recovery/client_status
File used to communicate the status of the make_net_recovery
command back to the ignite GUI running on the Ignite-UX server.
SEE ALSO
make_boot_tape(1M), make_medialif(1M), make_tape_recovery(1M),
manage_index(1M), pkg_rec_depot(1M), print_manifest(1M),
save_config(1M), swinstall(1M), vgcfgbackup(1M), vgversion(1M),
instl_adm(4), ignite(5), lvm(7).
