For information on the VCS commands for global clusters:
See the Cluster Server Administrator's Guide.
If you have two clusters configured to use VVR for replication, the following replication use cases are supported:
Table: Replication use cases for global parallel clusters
Management option |
Description |
---|---|
Migration of the role of the primary site to the remote site |
Migration is a planned transfer of the role of primary replication host from one cluster to a remote cluster. This transfer enables the application on the remote cluster to actively use the replicated data. The former primary cluster becomes free for maintenance or other activity. |
Takeover of the primary site role by the secondary site |
Takeover occurs when an unplanned event (such as a disaster) causes a failure, making it necessary for the applications using the replicated data to be brought online on the remote cluster. |
Migrate the role of primary site to the secondary site |
See “To migrate the role of primary site to the remote site”. |
Migrate the role of new primary site back to the original primary site |
See “To migrate the role of new primary site back to the original primary site”. |
Take over after an outage |
|
Resynchronize after an outage |
|
Update the rlink |
After configuring the replication objects within VCS, you can use VCS commands to migrate the role of the cluster on the primary site to the remote cluster. In the procedure below, VCS takes the replicated database service group, database_grp, offline on the primary site and brings it online on the secondary site; the secondary site now assumes the role of the primary site.
Note: |
The hagrp -switch command cannot migrate a parallel group within a cluster or between clusters in a global cluster environment. |
To migrate the role of primary site to the remote site
# hagrp -offline database_grp -any
Wait for VCS to take all database service groups offline on the primary site.
For example:
# vxrlink -g data_disk_group status rlk_clus2_dbdata_rvg
Where rlk_clus1_dbdata_rvg is the RLINK.
# hagrp -online database_grp -any
After migrating the role of the primary site to the secondary site, you can use VCS commands to migrate the role of the cluster on the new primary site to the original primary site. In the procedure below, VCS takes the replicated database service group, database_grp, offline on the new primary (former secondary) site and brings it online on the original primary site; the original primary site now resumes the role of the primary site.
Note: |
The hagrp -switch command cannot migrate a parallel group within a cluster or between clusters in a global cluster environment. |
To migrate the role of new primary site back to the original primary site
Issue the following command on the remote site:
# hagrp -offline database_grp -any
For example:
# vxrlink -g data_disk_group status rlk_clus1_dbdata_rvg
Where rlk_clus1_dbdata_rvg is the RLINK.
# hagrp -online database_grp -any
Takeover occurs when the remote cluster on the secondary site starts the application that uses replicated data. This situation may occur if the secondary site perceives the primary site as dead, or when the primary site becomes inaccessible (perhaps for a known reason). For a detailed description of concepts of taking over the primary role:
See the Veritas InfoScale™ Replication Administrator's Guide.
Before enabling the secondary site to take over the primary role, the administrator on the secondary site must "declare" the type of failure at the remote (primary, in this case) site and designate the failure type using one of the options for the haclus command.
Takeover options are:
Table: Takeover options on global parallel clusters
The examples illustrate the steps required for an outage takeover and resynchronization.
To resynchronize after an outage
# vxrvg -g data_disk_group -F snapshot dbdata_rvg1
See the Veritas InfoScale™ Replication Administrator's Guide for details on RVG snapshots.
# hares -action dbdata_vvr_shpri fbsync -sys sys3
# vxdctl -c mode
Perform one of the following commands, depending on whether the resynchronization of data from the current primary site to the original primary site is successful:
If the resynchronization of data is successful, use the vxrvg command with the snapback option to reattach the snapshot volumes on the original primary site to the original volumes in the specified RVG:
# vxrvg -g data_disk_group snapback dbdata_rvg1
A failed attempt at the resynchronization of data (for example, a disaster hits the primary RVG when resynchronization is in progress) could generate inconsistent data.
You can restore the contents of the RVG data volumes from the snapshot taken in step 1:
# vxrvg -g data_disk_group snaprestore dbdata_rvg1
If the rlink is not up to date, use the hares -action command with the resync action token to synchronize the RVG.