Ignite-UX Reference (March 2010, B3921-90005)

make_net_recovery(1M) make_net_recovery(1M)
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 recov-
ery 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 informa-
tion 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 miss-
ing 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:
7