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

make_net_recovery(1M) make_net_recovery(1M)
• 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 vol-
ume 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 vol-
ume 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 vol-
umes 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.
8