There are 2 versions of JumpStart:
1. JumpStart : Automatically install the Solaris software on SPARC based system just be inserting the Solaris CD and powering on the system. Need not to specify the boot command at OK prompt. The software that is installed in specified a default class file that is chosen based on the system’s model and the size of its disks; can’t choose the software that is to be installed. For new SPARC systems shipped from Sun, this is the default method of installing the operating system when the system is first powered on.
2. Custom JumpStart : Method of installing the operating system provides a way to install groups of similar systems automatically and identically. At a large site with several systems that are to be configured exactly the same, this task can be monotonous and time consuming. In addition, there is no guarantee that each system is setup is same. Custom JumpStart solves this problem by providing a method to create sets of configuration files earlier, so that the installation process can use them to configure each system automatically.
Flash Installation :
A complete snapshot of a Solaris operating system, including with patches and applications.
Limitation: Used to perform an initial installation, Flash cannot be used to upgrade a system.
Provides a method to store a snapshot of the Solaris operating system complete with all installed patches and applications. This archive can be stored on disk, Optical media or tape
media. This archive can be used for disaster recovery purposes or to replicate an environment on one or more other systems.
Solaris Live Upgrade:
Provides a method of upgrading a system whilst the system continues to operate.
While the current boot environment is running, it’s possible to duplicate the boot environment, and then upgrade the duplicate. Alternatively, rather than upgrading, it’s possible to install a Solaris Flash archive.
The original/current system configuration remains fully functional and unaffected by the upgrade or installation of an archive.
When ready, can activate the new boot environment by rebooting the system. If a failure occurs, can quickly revert to the original boot environment with a simple reboot.
Solaris Live Upgrade Process – Phase:
1. Creating an alternate boot environment (ABE) by cloning a current Solaris OS instance. The source for this cloning could also be a flash archive.
2. Changing the state of the system in the ABE for reasons including the following:
a. Upgrading to another OS release
b. Updating a release with patches or updates
3. Activating the new boot environment (BE).
4. Optionally falling back to the original BE.
Solaris Live Upgrade are supported by the following version:
Solaris 8 OS
Solaris 9 OS
Solaris 10 OS
Note - 1:
The only limitation to upgrading involves a Solaris Flash archive. When Solaris Flash archive is used to install, an archive that contains non-global zones are not properly installed on the system.
Note - 2:
Correct operation of Solaris Live Upgrade requires that a limited set of patch revisions be installed for a particular OS version. Before installing or running Solaris Live Upgrade, it’s required to install these patches.
Note - 3:
To estimate the file system size that is needed to create a boot environment, start the creation of a new boot environment. The size is calculated. Then abort the process.
Note - 4:
Solaris Live Upgrade packages are available from the release Solaris 10 05/09.
If the release is older, the packages can be installed by using the command # pkgadd.
Make a note that these packages MUST be installed in this order.