Storix Software SBAdmin Solaris System Recovery Guide - Manual (Page 57)

Starting the Installation
If all checks out, you are given one final warning:
Press “y” to continue the installation or “n” to return to the Main Menu .
If you choose to continue the install, the system will begin by reading additional information from the backup
media, then creating the devices and filesystems that are defined. After the devices are created, all filesystems
are created and mounted.
If the backup was encrypted when it was created, you will be asked to enter the encryption key to decrypt the
data during the installation. If the correct key is not entered, you will not be able to continue the installation.
Refer to
Installing from an Encrypted Backup for more information.
As the data is restored from the backup, a progress indicator will appear showing the status of the restore
including the estimated amount of data and time to completion. When all data for all filesystems, volumes,
partitions or meta-devices (if included on the backup) is restored, the system will perform some cleanup and
post-installation processing and attempt to make the system bootable.
Installation Errors
If any error occurs in creating the devices, creating or mounting the filesystems, or restoring the data, you will
be provided a message containing the details and the failing command and asked to correct the process
manually before continuing the installation. At this point you are placed at a shell prompts where you can
diagnose and correct the problem. The command which failed must be completed before the installation can
continue successfully. When the problem is corrected, type “exit” to exit the shell and continue the installation.
System Boot Problems
The SBAdmin installation process does its best to prevent you from making any changes that might prevent the
system from booting. For example, you are not allowed to put the /boot filesystem on a meta-device since boot
loaders can’t read the boot configuration or kernel from a meta-device.
The most common boot problem after an install is simply that your system firmware is trying to boot from the
wrong device. First remove any removable boot media from the system and try again. If you changed the disk
containing the /boot (or root if no /boot) filesystem, you may need to tell your firmware to boot from the new
disk. Each firmware used has different menu options, and also names the disks differently, so you will have to
refer to your system documentation for details.
Once the root filesystem is available during reboot, control is turned over to the normal system initialization
procedures. Any errors that occur at this point will not usually render the system unusable, but may require
additional customization (beyond the scope of SBAdmin) to restart all system processes in the correct order.
Should all else fail, at least we know that the system has been configured and restored successfully, so we just
need to figure out how to get it to boot. Your SBAdmin Boot CDROM can help. You can boot from the CDROM,
and when the menus appear, select “
Enter a Maintenance Shell ”. You can then perform system maintenance
commands to mount any filesystems, diagnose the problem and make the system bootable.
Storix System Backup Administrator 57 Version 8.2 Solaris System Recovery Guide