JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Managing Boot Environments With Oracle Solaris 11 Express     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

1.  Introduction to Boot Environments

2.  Using beadm Utility (Tasks)

3.  beadm Zones Support

Zones Support Limitations

Zones Support Specifications

Zones Naming Conventions

Additional Resources

4.  Appendix: beadm Reference

Zones Naming Conventions

The beadm utility automatically handles all zones naming tasks related to the beadm processes. Just for your reference, this section describes the zones naming conventions that are automatically used by the beadm utility.

A zone root dataset name is stated in the following format:

<zonepath dataset>/ROOT/<zone root>

For example:


When a zone is copied from one boot environment to another boot environment, only the datasets that are under the zone's root dataset are copied.

A dataset can be shared between zone boot environments. A shared dataset is identified by using the following format:

<zonepath dataset>/export

For example:


A shared dataset must be explicitly added during zones configuration. A shared dataset is not cloned when the zone dataset is cloned.

Example 3-1 Non-Global Zones Example

This example shows the zones impact of the beadm create command when cloning a boot environment that contains two non-global zones.

Perform the following command to clone the boot environment and name the new boot environment opensolaris-1:

beadm create opensolaris-1

The root dataset for the new boot environment is at rpool/ROOT/opensolaris-1. The copy of zone z1 for the new boot environment has its root dataset at rpool/zones/z1/ROOT/zbe-1.

Note - ZFS properties for each dataset track the relationships between original and cloned datasets, and track the relationships between non-global zones and their parent boot environments.