Last updated on MAY 02, 2017
Applies to:Solaris Cluster - Version OSC 4.2 to OSC 4.2 [Release 4.2]
Information in this document applies to any platform.
When a zone on a Solaris Cluster is failed over and the zone is booted to a new BE boot environment you may see that an additional backup boot environment was created. In addition if there is no boot environment of global zone is associated with zone's BE it is essentially an orphan boot environment as it can no longer be updated or changed and it is not automatically deleted either. Before Solaris 11.3 these BEs may not be easy to recognize.
Solaris 11.3 has been incorporated code change to better handle orphan zone boot environments and Oracle Solaris Cluster 4.3 is using those enhancements.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms