A clone archive is based upon the system's active boot environment (BE) at the time the archive is created. Therefore, only one BE may be archived at a time. The clone archive type is intended for rapid creation and deployment of custom images. You can create an archive that includes both the global and non-global zones. The data for each archived system is stored independently, which enables each system to be independently deployable. To achieve independent deployment, clone relationships are not preserved within clone archives. Therefore, a cloned zone within a clone an archive will take up roughly the same amount of space as the original zone from which it is cloned. A clone archive is the default type of archive.
Also, a clone archive does not include any of the system configuration information from the OS instance, as well as any sensitive data such as SSH keys or passwords. Any system deployed from a clone archive will have all of the file systems and applications as the cloned system, but will not have the same host name, for instance. The system configuration information and sensitive data is only preserved in recovery archives.