| Skip Navigation Links | |
| Exit Print View | |
|
Creating and Administering Oracle Solaris 11 Boot Environments Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Creating and Administering Oracle Solaris 11 Boot Environments Oracle Solaris 11 Information Library |
The beadm utility automatically handles all zones naming tasks related to the beadm processes. When the beadm utility is operating on boot environments in a global zone that also contains non-global zones, the zones naming conventions that are automatically used by the beadm utility are as follows.
A zone root dataset name is stated in the following format:
<zonepath dataset>/rpool/ROOT/<zone root>
For example:
rpool/zones/zone1/rpool/ROOT
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. Shared datasets are located outside the root dataset area of each boot environment.
Note - Shared datasets are user-defined directories, such as /export, that contain the same mount point in both the active and inactive boot environments.
A shared dataset is identified by using the following format:
<zonepath dataset>/rpool/export
For example:
rpool/zones/zone1/rpool/export
A shared dataset must be explicitly added during zones configuration. A shared dataset is not cloned when the zone dataset is cloned. See the examples in Chapter 3, Creating Boot Environments and Snapshots.
|