The make_[tapenet]_recovery tools have few differences aside from using different media. Both system recovery tools share the same basic recovery image creation options, data structures, recovery image file content, and installation dialog boxes. The main differences are that make_tape_recovery does not require an Ignite server and make_net_recovery can be run from the client with a small subset of the Ignite product.
The make_[tapenet]_recovery tools are not intended for backup of all your system data. Use a restore tool such as fbackup in conjunction with your recovery image. See fbackup(1M ) for more information.
Recovery Tool Comparison
To determine which system recovery tool is best suited for your needs, consider the following:
Use make_tape_recovery to:
•Manage single or a limited number of systems locally.
•Manage systems that are not networked.
•Create tape media for an
•Create recovery images for clients on a different subnet than the
Use make_net_recovery to:
•Centrally manage networked systems.
•Avoid tape issues (handling,
•Use disk space for image storage.
•Perform unattended creation of recovery images without tape handling.
•Create recovery images for clients on a different subnet than the
The following table summarizes and compares some of the features of the make_[tapenet]_recovery tools:
Table 12 Comparing System Recovery Tool Features
| make_tape_recovery | make_net_recovery | ||
|
|
|
|
|
Minimum hardware | • | Stand alone system | • | Two networked systems |
configuration | • | Local tape drive | • Sufficient disk space to hold image | |
| ||||
|
|
|
|
|
Creation interfaces | • | Client command line | • | Client command line |
| • | • | ||
| • | Client TUI | • | Client TUI |
|
|
|
| |
Recovery image | • | Self contained | • Requires an | |
personality | • Written to the client’s tape drive | • Written to NFS mounted file system | ||
| ||||
|
|
|
|
|
System Recovery 189