Creating a Noninteractive Disk Image
If you wish to perform a
noninteractive restore from an NFS mount,
you should have a properly configured Solaris network boot server configured on your
network and boot using the boot
net
–
install command. In this case, how your individual
environment is set up dictates where the server configuration files (profile, rules, and
sysidcfg) should be stored.
To perform a noninteractive restore:
-
First, ensure that the system is powered on and that it is at the ok> prompt.
-
Check whether your boot and recovery devices are available by performing a
probe:
-
ok> probe-scsi-all
-
A list of locally attached devices should be displayed. Ensure that, at a
minimum, the local boot disk, a CD/DVD drive (if applicable), and the correct SCSI
tape drives are listed.
-
If you plan to restore from tape, insert the tape into a local tape
drive.
Tip
In the example profile file, there is one
tape drive connected to the server (/dev/rmt/0n).
If a tape drive is hardcoded into the profile
file, that same drive must be used here. To avoid this requirement, use a begin script
to create a profile, on the fly, during the restore process.
-
Boot the system.
-
If you are restoring from tape, insert the Solaris Installation CD into the
appropriate device on the system you want to restore. At the ok> prompt, enter:
-
boot cdrom - install tape=/dev/rmt/0n
-
The system boots, and the installation process starts. The system boots from
the CD/DVD and looks for the required files on tape. If present, any prerecovery
scripts execute, and the archive extraction begins. The extracted rules.ok,
profile, and sysidcfg files
are used to configure the server.
-
If you are restoring from an NFS mount, you need to have a network boot
server configured and boot from the network using the boot
net
–
install command. The system looks for the
network boot server to provide the location of the required configuration files
and flash image.
Here’s the output from a noninteractive restore:
ok boot cdrom - install tape=/dev/rmt/0n
Resetting ...
SPARCstation 5, No Keyboard
ROM Rev. 2.15, 96 MB memory installed, Serial #7760400.
Ethernet address 8:0:20:76:6a:22, Host ID: 80766a00.
Rebooting with command: cdrom - install tape=/dev/rmt/0n
Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@6,0:d
File and args: - install tape=/dev/rmt/0n
SunOS Release 5.9 Version Generic_118558-11 32-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Skipping interface le0
Skipping interface hme0
Searching for configuration file(s)...
Using sysid configuration file from /dev/rmt/0n position 0
Search complete.
The system is coming up. Please wait.
Begin system identification...
Starting remote procedure call (RPC) services: sysidns done.
System identification complete.
Generating software table of contents [this may take a few minutes...]
Table of contents complete.
Starting Solaris installation program...
Searching for JumpStart directory...
Using rules.ok from tape.
Checking rules.ok file...
Using profile: standard.profile
Executing JumpStart preinstall phase...
Searching for SolStart directory...
Checking rules.ok file...
Using begin script: install_begin
Using finish script: patch_finish
Executing SolStart preinstall phase...
Executing begin script "install_begin"...
Begin script install_begin execution completed.
Processing profile
- Opening Flash archive
- Validating Flash archive
- Selecting all disks
- Configuring boot device
- Configuring / (c0t1d0s0)
- Configuring swap (c0t1d0s1)
- Configuring /export/home (c0t3d0s7)
Verifying disk configuration
- WARNING: Unused disk space (c0t1d0)
- WARNING: Unused disk space (c0t3d0)
Verifying space allocation
NOTE: 1 archives did not include size information
Preparing system for Flash install
Configuring disk (c0t1d0)
- Creating Solaris disk label (VTOC)
Configuring disk (c0t3d0)
- Creating Solaris disk label (VTOC)
Creating and checking UFS file systems
- Creating / (c0t1d0s0)
- Creating /export/home (c0t3d0s7)
Beginning Flash archive processing
Predeployment processing
8 blocks
16 blocks
8 blocks
No local customization defined
Extracting archive: sun2.flar
Extracted 0.00 MB ( 0% of 448.73 MB archive)
Extracted 1.95 MB ( 0% of 448.73 MB archive)
~truncated~
Extracted 448.72 MB ( 99% of 448.73 MB archive)
Extraction complete
Postdeployment processing
No local customization defined
Customizing system files
- Mount points table (/etc/vfstab)
- Network host addresses (/etc/hosts)
Cleaning devices
Customizing system devices
- Physical devices (/devices)
- Logical devices (/dev)
Installing boot information
- Installing boot blocks (c0t1d0s0)
Installation log location
- /a/var/sadm/system/logs/install_log (before reboot)
- /var/sadm/system/logs/install_log (after reboot)
Flash installation complete
Executing JumpStart postinstall phase...
The begin script log 'begin.log'
is located in /var/sadm/system/logs after reboot.
syncing file systems... done
rebooting...
Resetting ...
Once the restore completes successfully, any post-recovery scripts are then
executed, and the system reboots. If you did not specify an encrypted root password in
the sysidcfg file, you are prompted to enter a root
password during the next boot. The recovery is now complete.
Regardless of the method you use (interactive or noninteractive), once the flash
archive has been restored, some post recovery work may need to be completed. How
much and how complex that work is varies depending on the system configuration. It is
very important to understand how your systems are set up to allow for the building of a
successful end-to-end recovery procedure.
For example, if a system with a VxVM encapsulated root disk has been restored, the
system will not boot following the flash recovery. It doesn’t boot because Veritas
Volume Manager is expecting to find an encapsulated root disk, which no longer exists.
In this scenario, you must boot from the Solaris CD into single-user mode and make the
necessary changes to disable the loading of VxVM for the system to boot properly.
If you restore to a system with a different root disk, you may need to reconfigure
the boot device EEPROM:
Original Server Root Disk Target Server Root Disk
c0t0d0s0 c1t0d0s0
