Consider the following recommendations when using Unified Archives:
Archive components are consistent with one another. When an archive is deployed, all data present post-deployment should be from the same point in time from the origin system's perspective. Consistency is guaranteed on a per-pool basis. If an Oracle Solaris instance spans multiple pools, as when an application or data pool is used separately from a root pool, quiesce any active workloads prior to archive creation. This step ensures consistency between the pools once they are deployed.
The archiveadm create -D syntax enables you to exclude datasets not needed for redeployment. Remove temporary or unnecessary directories and data prior to archive creation. Or, place these in their own datasets so you can exclude them using the –D option.
When creating the archive, specify an informative name. For example noscratch-recovery.uar is a recovery file without the scratch dataset. However, archiveadm info also displays informatioin about the archive contents.
To take advantage of IPS functionality during archive creation, convert SVR4 packages to IPS packages and install the packages onto a ZFS dataset. The archiveadm command only works on data that is managed by ZFS. For more information, see Converting SVR4 Packages To IPS Packages in Packaging and Delivering Software With the Image Packaging System in Oracle Solaris 11.4.