 | ||
| Configuring the agents | ||
|---|---|---|
| Prev | Configuring Volume Replicator in a VCS environment | Next |
This section explains how you can cover replication under a cluster.
Before that, you must first create the application service group for the application whose data Volume Replicator is replicating. The following figure illustrates a typical configuration after the application service group has been created using the application-specific wizard.
For more information about creating the application service group, see Cluster Server Administrator's Guide.
You can create the replication service group using the Volume Replicator agent configuration wizard to cover replication under a cluster. However, the replication setup must exist before it can be covered under a cluster. Create a Replicated Data Set (RDS) using an IP address that is available in the setup.
For a cluster setup you need to set the Primary and Secondary to a virtual IP address. The Volume Replicator agent configuration wizard creates the resource for this IP address. Currently however, the resource for this is not created. Therefore you need to use the Change Replication Settings wizard to set the replication IP to a non-existent virtual IP. When using the Volume Replicator Agent Configuration Wizard you can specify this IP for which the resource is then created.
Use the Volume Replicator agent configuration wizard to create the replication service group along with the IP resource for replication. Using this wizard you can specify the IP address used in the existing replication setup to create the corresponding IP resource in the replication service group, when necessary. If you already have an IP resource created then you can choose to use this resource by either copying or linking to the resource.
After the replication service group has been created, the RVG resource must be dependent on the IP address of the local host that is used for replication. In some cases, it is possible that an RVG uses more than one IP on the local host, for replication. This is especially true if the RVG is a Primary with more than one Secondary and different IPs on the Primary are used to create RLINKs to each Secondary. In this case, a resource should be present for each of these IPs in the replication service group. The resource for this Primary RVG should then depend on each of the IP resources.
The following table lists the procedures and description related to agent configuration.
Table: Procedures and related description for agent configuration.
|
Procedure |
Description |
|---|---|
|
Creating the application service group |
You must first create the application service group. After creating it on the Primary, take the application service group offline before creating it on the Secondary. For more information, see Cluster Server Administrator's Guide. |
|
Taking the application group offline |
Before creating the replication service group, take the application service group offline, but make sure that the disk group is imported. |
|
Setting up Replication |
Use the setup RDS wizard. |
|
Changing the Primary and Secondary IP |
Use the Change Replication Settings option from the Secondary to change the Primary and Secondary IP to one that is intended for replication and currently does not have any resources created. |
|
Creating RLINKs between each pair of Secondaries |
If your setup has multiple Secondary hosts, the RLINKs are automatically created when a Secondary is added to the RDS. |
|
Running the Volume Replicator agent configuration wizard |
Run the Volume Replicator agent configuration wizard. See Creating the replication service group. For a setup using multiple IP addresses for replication, run the wizard in the modify mode to create the IP resources for each of these IPs and make the VvrRvg resource dependent on each of them. See Modifying an existing resource in the replication service group. |
