How to Create an Archive of the System Image

Perform this procedure to archive the file systems of the global zone that you will transform to a solaris zone.

  1. Become a zone administrator.
  2. Verify that no non-global zones are installed on the source system, including kernel zones.

    A recovery archive that contains non-global zones would fail to install in a solaris zone.

    global$ zoneadm list -cv
      ID NAME             STATUS      PATH                         BRAND      IP
       0 global           running     /                            solaris    shared

    If there are non-global zones or kernel zones on the system, delete them by following procedures in Uninstalling and Deleting a Non-Global Zone.

  3. Create a recovery archive of the global zone on network storage.

    Specify the fully-qualified path of the recovery archive to create and end the file name with the .uar extension.

    source$ pfbash archiveadm create -r -z global recovery-archive.uar

Next Steps

The Unified Archive generated with the archiveadm command contains a zone configuration that serves as a starting point for the converted zone. Additional configuration might be needed to configure the zone in a way that is optimal for the target system.

For more information, see Using Unified Archives for System Recovery and Cloning in Oracle Solaris 11.4 and the archiveadm(8) man page.

Troubleshooting

Tip:

In some deployments, data for the operating system and applications are segregated into separate ZFS pools. In this case, a backup and recovery system other than Unified Archives is used for protecting application data. You might want to create root-only archives. A root-only archive includes only the root pool, typically rpool. The action is the equivalent of using ‐-exclude-dataset for each ZFS pool that is not the root pool.
source$ pfbash archiveadm create -z global --recovery --root-only /archives/server1.uar