Service group behavior with the RemoteGroup agent
Consider the following potential actions to better understand this solution.
Bringing the Apache service group online
-
The Apache resource depends on the RemoteGroup resource.
-
The RemoteGroup agent communicates to the remote cluster and authenticates the specified user.
-
The RemoteGroup agent brings the database service group online in cluster2.
-
The Apache resource comes online after the RemoteGroup resource is online.
Thus, you have established an application-level dependency across two different VCS clusters. The Apache resource does not go online unless the RemoteGroup goes online. The RemoteGroup resource does not go online unless the database service group goes online.
Unexpected offline of the database service group
-
The RemoteGroup resource detects that the database group has gone offline or has faulted.
-
The RemoteGroup resource goes into a faulted state.
-
All the resources in the Apache service group are taken offline on the node.
-
The Apache group fails over to another node.
-
As part of the fail over, the Oracle service group goes online on another node in cluster2.
Taking the Apache service group offline
-
All the resources dependant on the RemoteGroup resource are taken offline.
-
The RemoteGroup agent tries to take the Oracle service group offline.
-
Once the Oracle service group goes offline, the RemoteGroup goes offline.
Thus, the Web server is taken offline before the database goes offline.
