Adding a RemoteGroup resource from the Java Console

A RemoteGroup resource is typically useful in scenarios where resources configured in a local service group are dependant on the state of a remote service group. For example, a web-server application running in a local cluster could be dependant on a database application running in a remote cluster.

Note:

The RemoteGroup agent represents that state of a failover service group; the agent is not supported with parallel service groups.

A RemoteGroup resource monitors the state of a remote service group in a local cluster. Once you have added the RemoteGroup resource to a local service group, you can link the resource to the existing resources of the service group.

You must have administrative privileges to configure RemoteGroup resources.

To add a RemoteGroup resource

  1. On the Tools menu, click Add Remote Group Resource...

    or

    Click Configure Remote Group Resource Wizard in the Cluster Explorer toolbar.

  2. Read the information on the Welcome dialog box and click Next.
  3. In the Remote Group Resource Name dialog box, specify the name of the resource and the service group to which the resource will be added. Click Next.
  4. In the Remote Cluster Information dialog box:

    • Specify the name or IP address of a node in the remote cluster.

    • Specify the port on the remote node on which the resource will communicate.

    • Specify a username for the remote cluster.

    • Specify a password for the user.

    • Select the check box if you wish to specify advance options to connect to a cluster running in secure mode. Otherwise, click Next and proceed to the last step.

      • Specify the domain of which the node is a part.

      • Select a domain type.

      • Specify the authentication broker and port.

    • Click Next.

  5. In the Remote Group Resource Details dialog box, do the following:

    • Select a group you wish to monitor.

    • Select the mode of monitoring.

      • Choose the MonitorOnly option to monitor the remote service group. You will not be able to perform online or offline operations on the remote group.

      • Choose the OnlineOnly option to monitor the remote service group and bring the remote group online from the local cluster.

      • Choose the OnOff option to monitor the remote service group, bring the remote group online, and take it offline from the local cluster.

    • Specify whether the RemoteGroup resource should monitor the state of the remote group on a specific system or any system in the remote cluster.

      • Choose the Any System option to enable the RemoteGroup resource to monitor the state of the remote service group irrespective of the system on which it is online.

      • Choose the Specific System option to enable the RemoteGroup resource to monitor the state of the remote group on a specific system in the remote cluster. You must configure both service groups on the same number of systems.

        This option provides one-to-one mapping between the local and remote systems. The Local Systems list displays the systems on which the RemoteGroup resource is configured. Click the fields under the Remote Systems list and select the systems from drop-down list. If the remote group fails over to another system in the remote cluster, the RemoteGroup resource also will fail over to the corresponding system in the local cluster.

    • Click Next.

  6. Review the text in the dialog box and click Finish to add the RemoteGroup resource to the specified service group in the local cluster.
  7. Create dependencies between the RemoteGroup resource and the existing resources of the service group.

More Information

About configuring the RemoteGroup agent

Linking resources