Once an archive has been created, you can store the archive as a file until it is needed. Deployment scenarios include system recovery and system migration, as well as system cloning. The three modes of archive deployment are:
Non-interactive network deployment using the Automated Installer
Zones deployment using the zones commands
Interactive deployment using bootable media
You can deploy archives by using the Oracle Solaris Automated Installer (AI). You have to modify the AI manifest to include the following information: the location of the archive and the name of the systems the archive should be deployed to. See How to Deploy a System From a Unified Archive Using AI for more information.
You use the Solaris Zones utilities zonecfg and zoneadm to configure and install new zones directly from an archive. When you create a new zone using an archive as a reference source, the new zone will mimic the original system's configuration. For specific instructions, see How to Deploy a Zone From a Unified Archive.
Zone creation and installation operations using archives are independent of each other. Although you can use the same archive to source both configuration and installation data, doing so is not a requirement. A zone configuration may already exist or may be created using any supported method.
You can deploy archives from bootable media using either ISO or USB images. You can use this form of deployment if the install client is not networked or if no AI services are available. These media images deploy the contents of the archive non-interactively when the install client is booted.
You can use archives in any Oracle Solaris deployment scenario that uses bootable media, such as installing logical domains, Oracle Solaris Kernel Zones and Oracle Solaris instances within Oracle VM from media. For more information about bootable media installations, see How to Deploy a System From a Unified Archive Using Bootable Media.