The boot environment management software uniquely identifies BEs in both the global zone and non-global zones through the use of boot environment FMRIs (BeFMRIs). It interprets BeFMRIs based on the environment in which the FMRI is used.
Depending on whether you are working in the global zone or a non-global zone, the BE name is interpreted differently, based on two schemes that represent BeFMRIs:
be
zbe
If you are in the global zone, the BE name specified in the be scheme is interpreted as the name of a global zone BE. If you are in the non-global zone, the BE name specified is interpreted as the name of a non-global zone BE. Additionally, while in the global zone, a user can specify the name of the storage pool on which the BE resides.
The string format for the be scheme is be://[zpool-name]/be-name[@snapshot-name], as shown in the following examples:
be://rpool/be1 – the boot environment be1 in the storage pool called rpool.
be://rpool/be1@backup – the snapshot backup for the boot environment be1 in the currently running storage pool called rpool.
be://rpool2/be1 – the boot environment be1 in the storage pool called rpool2.
The zbe scheme is supported in the global zone only. This scheme manages non-global zone BEs from the global zone. The zone name specified in the zbe scheme must be defined in the running environment. The string format of the zbe scheme is zbe://[zpool-name]/zbe-name[@snapshot-name], as shown in the following examples:
zbe://zone2/ngz_be2 – a non-global zone boot environment called ngz_be2 in a zone called zone2.
zbe://zone1/ngz_be2@backup – a snapshot called backup of the boot environment ngz_be2 in zone1.
When you display a list of boot environments on the system, the information includes the BE's corresponding FMRI designations. See examples in Listing Existing Boot Environments and Snapshots.
For more information, see the beadm(8) man page. See also beadm Zones Support for examples of the use of the beadm command to manage boot environments.