After a cluster boots or services fail over to another node, global devices and local and cluster file systems might require time to become available. However, a data service can run its START method before global devices and local and cluster file systems come online. If the data service depends on global devices or local and cluster file systems that are not yet online, the START method times out. In this situation, you must reset the state of the resource groups that the data service uses and restart the data service manually.
To avoid these additional administrative tasks, use the HAStoragePlus resource type. Add an instance of HAStoragePlus to all resource groups whose data service resources depend on global devices or local and cluster file systems. Instances of these resource types can perform operations, such as forcing the START method of the other resources in the same resource group to wait until global devices and local and cluster file systems become available.
If an application resource is configured on top of an HAStoragePlus resource, the application resource must define the offline restart dependency on the underlying HAStoragePlus resource. This ensures that the application resource comes online after the dependent HAStoragePlus resource comes online, and goes offline before the HAStoragePlus resource goes offline.
The following command creates an offline restart dependency from an application resource to a HAStoragePlus resource:
# clrs set -p Resource_dependencies_offline_restart=hasp_rs applicaton_rs
To create an HAStoragePlus resource, see How to Set Up the HAStoragePlus Resource Type for New Resources.