The configuration requirements in this section apply only to HA for Solaris Zones.
Caution - If your data service configuration does not conform to these requirements, the data service configuration might not be supported.
The dependencies between the HA for Solaris Zones components are described in the following table:
These dependencies are set when you register and configure HA for Solaris Zones. For more information, see Registering and Configuring HA for Solaris Zones.
The sczbt_register script defines a resource dependency of type Resource_dependencies_offline_restart as follows:
If you set the SC_LH variable within the sczbt_config file, then the Resource_dependencies_offline_restart property of the sczbt component will contain the SUNW.LogicalHostname resource name as set with the SC_LH variable.
If you set the HAS_RS variable within the sczbt_config file, then the Resource_dependencies_offline_restart property of the sczbt component will contain the storage resource name as set with the HAS_RS variable.
When you configure a solaris-kz brand zone for warm migration, where the suspend image is hosted on a file system managed by HASP or on any other cluster resource managing that file system, you need to set HAS_RS to the corresponding resource name. This will ensure that the resource dependency to the storage resource is setup when the sczbt resource is getting registered.
The zone script resource and SMF resource are optional. If used, multiple instances of the zone script resource and SMF resource can be deployed within the same resource group as the zone boot resource. Furthermore, if more elaborate dependencies are required then refer to the r_properties (5) and rg_properties (5) man pages for further dependencies and affinities settings.
If the sczbt component is configured for a kernel zone with Migrationtype=warm set, it will still perform the start and stop operations on the corresponding services that are managed by the sczsh or the sczsmf component. If you need to have all the services running within the kernel zone during warm migration, then do not configure the sczsh or the sczsmf component for those services.