This chapter contains the procedures for configuring and administering data replication with EMC Symmetrix Remote Data Facility software. The chapter contains the following sections:
Strategies for Creating EMC Symmetrix Remote Data Facility Protection Groups
Creating, Modifying, Validating, and Deleting an EMC Symmetrix Remote Data Facility Protection Group
Administering EMC Symmetrix Remote Data Facility Application Resource Groups
Administering EMC Symmetrix Remote Data Facility Data Replication Device Groups
Activating an EMC Symmetrix Remote Data Facility Protection Group
Deactivating an EMC Symmetrix Remote Data Facility Protection Group
Resynchronizing an EMC Symmetrix Remote Data Facility Protection Group
Checking the Runtime Status of EMC Symmetrix Remote Data Facility Data Replication
Before you begin creating protection groups, consider which of the following strategies is best for you:
Creating the protection group while the application remains online.
This strategy allows you to create a protection group without any application outage.
Taking the application offline before creating the protection group.
The following sections describe the steps for each strategy:
To create a protection group while the application resource groups is offline, complete the following steps.
Create the protection group from a node on one cluster.
For more information, see How to Create and Configure an EMC Symmetrix Remote Data Facility Protection Group.
Add the data replication device group to the protection group.
For more information, see How to Add a Data Replication Device Group to an EMC Symmetrix Remote Data Facility Protection Group.
Take the application resource group offline.
Add the application resource group to the protection group.
For more information, see How to Add an Application Resource Group to an EMC Symmetrix Remote Data Facility Protection Group.
On the other cluster, retrieve the protection group configuration.
For more information, see How to Replicate the EMC Symmetrix Remote Data Facility Protection Group Configuration to a Partner Cluster.
From either cluster, start the protection group globally.
For more information, see How to Activate an EMC Symmetrix Remote Data Facility Protection Group.
To add an existing application resource group to a new protection group without taking the application offline, complete the following steps on the cluster where the application resource group is online.
Create the protection group from a cluster node.
For more information, see How to Create and Configure an EMC Symmetrix Remote Data Facility Protection Group.
Add the data replication device group to the protection group.
For more information, see How to Add a Data Replication Device Group to an EMC Symmetrix Remote Data Facility Protection Group.
Start the protection group locally.
For more information, see How to Activate an EMC Symmetrix Remote Data Facility Protection Group.
Add the application resource group to the protection group.
For more information, see How to Add an Application Resource Group to an EMC Symmetrix Remote Data Facility Protection Group.
Complete the following steps on the other cluster.
Retrieve the protection group configuration.
For more information, see How to Replicate the EMC Symmetrix Remote Data Facility Protection Group Configuration to a Partner Cluster.
Activate the protection group locally.
For more information, see How to Activate an EMC Symmetrix Remote Data Facility Protection Group.
This example creates a protection group without taking the application offline.
In this example, the apprg1 resource group is online on the cluster-paris cluster.
Create the protection group on cluster-paris.
phys-paris-1# geopg create -d srdf -p cluster_dgs=dg1 \ -o Primary -s paris-newyork-ps srdfpg Protection group "srdfpg" has been successfully created |
Add the device group, devgroup1, to the protection group.
phys-paris-1# geopg add-device-group devgroup1 rdfpg |
Activate the protection group locally.
phys-paris-1# geopg start -e local srdfpg Processing operation.... this may take a while... Protection group "srdfpg" successfully started. |
This command starts data replication.
Add an application resource group that is already online to the protection group.
phys-paris-1# geopg add-resource-group apprg1 srdfpg Following resource groups were successfully inserted: "apprg1" |
Verify that the application resource group was added successfully.
phys-paris-1# geoadm list srdfpg |
On one node of the partner cluster, retrieve the protection group.
phys-newyork-1# geopg get -s paris-newyork-ps srdfpg Protection group "srdfpg" has been successfully created. |
Activate the protection group locally on the partner cluster.
phys-newyork-1# geopg start -e local srdfpg Processing operation.... this may take a while... Protection group "srdfpg" successfully started. |
Verify that the protection group was successfully created and activated.
Running the geoadm status command on cluster-paris produces the following output:
phys-paris-1# geoadm status Cluster: cluster-paris Partnership "paris-newyork-ps" : OK Partner clusters : newyork Synchronization : OK ICRM Connection : OK Heartbeat "hb_cluster-paris~cluster-newyork" monitoring \ "paris-newyork-ps": OK Plug-in "ping-plugin" : Inactive Plug-in "tcp_udp_plugin" : OK Protection group "srdfpg" : OK Partnership : paris-newyork-ps Synchronization : OK Cluster cluster-paris : OK Role : Primary Configuration : OK Data replication : OK Resource groups : OK Cluster cluster-newyork : OK Role : Secondary Configuration : OK Data Replication : OK Resource Groups : OK |
This section contains the following topics:
How to Create and Configure an EMC Symmetrix Remote Data Facility Protection Group
Requirements to Support Oracle Real Application Clusters With Data Replication Software
How to Create a Protection Group for Oracle Real Application Clusters
How the Data Replication Subsystem Validates the Device Group
How to Modify an EMC Symmetrix Remote Data Facility Protection Group
Validating an EMC Symmetrix Remote Data Facility Protection Group
How to Delete an EMC Symmetrix Remote Data Facility Protection Group
You can create protection groups that are not configured to use data replication. To create a protection group that does not use a data replication subsystem, omit the -d datareplicationtype option when you use the geopg command. The geoadm status command shows a state for these protection groups of Degraded.
For more information, see Creating a Protection Group That Does Not Require Data Replication in Sun Cluster Geographic Edition System Administration Guide.
Before you create a protection group, ensure that the following conditions are met:
The local cluster is a member of a partnership.
The protection group you are creating does not already exist.
Protection group names are unique in the global Sun Cluster Geographic Edition namespace. You cannot use the same protection group name in two partnerships on the same system.
You can also replicate the existing configuration of a protection group from a remote cluster to the local cluster. For more information, see Replicating the EMC Symmetrix Remote Data Facility Protection Group Configuration to a Partner Cluster.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Create a new protection group that uses SRDF replication by using the geopg create command.
This command creates a protection group on all nodes of the local cluster.
# geopg create -s partnershipname -o localrole -d srdf [-p property [-p...]] \ protectiongroupname |
Specifies the name of the partnership.
Specifies the role of this protection group on the local cluster as either primary or secondary.
Specifies that the protection group data is replicated by the EMC Symmetrix Remote Data Facility software.
Specifies the properties of the protection group.
You can specify the following properties:
Description – Describes the protection group.
Timeout – Specifies the time-out period for the protection group in seconds.
Nodelist – Lists the host names of the machines that can be primary for the replication subsystem.
Cluster_dgs – Lists the device groups where the data is written.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun Cluster Geographic Edition System Administration Guide.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
For more information about the geopg command, refer to the geopg(1M) man page.
This example creates an EMC Symmetrix Remote Data Facility protection group on cluster-paris, which is set as the primary cluster.
# geopg create -s paris-newyork-ps -o primary -d srdf \ -p cluster_dgs=dg1 srdfpg |
Sun Cluster Geographic Edition software supports Oracle Real Application Clusters with EMC Symmetrix Remote Data Facility software. Observe the following requirements when you configure Oracle Real Application Clusters:
Each CRS OCR and Voting Disk Location must be in its own device group on each cluster and cannot be replicated.
Static data such as CRS and database binaries are not required to be replicated. But this data must be accessible from all nodes of both clusters.
You must create a SUNW.ScalDeviceGroup resource in its own resource group for the device group that holds dynamic database files. This resource group must be separate from the resource group that holds the clusterware SUNW.ScalDeviceGroup resource.
To be able to leave RAC infrastructure resource groups outside of Sun Cluster Geographic Edition control, you must run Sun Cluster Geographic Edition binaries on both cluster partners and set the RAC protection group External_Dependency_Allowed property to true.
Do not add the CRS OCR and Voting Disk device group to the protection group's cluster_dgs property.
Do not add RAC infrastructure resource groups to the protection group. Only add the rac_server_proxy resource group and resource groups for device groups that are replicated to the protection group. Also, you must set to false the auto_start_on_new_cluster resource group property for the rac_server_proxy resource group and resource groups and for device groups that are replicated.
When you use a cluster file system for an Oracle RAC file system, such as a flash recovery area, alert, or trace log files, you must manually create on both clusters a separate resource group that uses the HAStoragePlus resource to bring online these corresponding file systems. You must set a strong resource dependency from nonClusterware SUNW.ScalDeviceGroup resources to this HAStoragePlus resource. Then add this HAStoragePlus resource group to the RAC protection group.
Before you create a protection group for Oracle Real Application Clusters (RAC), ensure that the following conditions are met:
Read Requirements to Support Oracle Real Application Clusters With Data Replication Software.
The node list of the protection group must be the same as the node list of RAC framework resource group.
If one cluster is running RAC on a different number of nodes than another cluster, ensure that all nodes on both clusters have the same resource groups defined.
If you are using the VERITAS Volume Manager cluster feature to manage data, you must specify the cluster feature disk group and Sun Cluster device groups for other data volumes in the cluster_dgs property.
When a cluster and the VERITAS Volume Manager cluster feature software restart, the RAC framework automatically tries to import all cluster feature device groups that were imported already before cluster went down. Therefore, the attempt to import the device groups to the original primary fails.
Log in to a cluster node on the primary cluster.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Create a new protection group by using the geopg create command.
This command creates a protection group on all nodes of the local cluster.
# geopg create -s partnershipname -o localrole -d srdf \ -p External_Dependency_Allowed=true [-p property [-p...]] protectiongroupname |
Specifies the name of the partnership.
Specifies the role of this protection group on the local cluster as primary.
Specifies that the protection group data is replicated by the EMC Symmetrix Remote Data Facility software.
Specifies the properties of the protection group.
You can specify the following properties:
Description – Describes the protection group.
External_Dependency_Allowed - Specifies whether to allow any dependencies between resource groups and resources that belong to this protection group and resource groups and resources that do not belong to this protection group. For RAC, setting this property to true.
Timeout – Specifies the timeout period for the protection group in seconds.
Nodelist – Lists the host names of the machines that can be primary for the replication subsystem.
Cluster_dgs – Specifies the VERITAS Volume Manager cluster feature disk group where the data is written.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun Cluster Geographic Edition System Administration Guide.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
For more information about the geopg command, refer to the geopg(1M) man page.
Add an EMC Symmetrix Remote Data Facility device group to the protection group.
# geopg add-device-group [-p property [-p...]] protectiongroupname |
Specifies the properties of the protection group.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun Cluster Geographic Edition System Administration Guide.
Specifies the name of the protection group.
Add to the protection group only the rac_server_proxy resource group and the resource groups for device groups that are replicated.
Do not add the RAC framework resource group to the protection group. This ensures that, if the protection group becomes secondary on the node, the framework resource group does not become unmanaged. In addition, multiple RAC databases can be on the cluster, and the databases can be under Sun Cluster Geographic Edition control or not under its control.
# geopg add-resource-group resourcegroup protectiongroupname |
Specifies a comma-separated list of resource groups to add to or delete from the protection group. The specified resource groups must already be defined.
The protection group must be online before you add a resource group. The geopg add-resource-group command fails when a protection group is offline and the resource group that is being added is online.
If a protection group has already been started at the time that you add a resource group, the resource group remains unmanaged. You must start the resource group manually by running the geopg start command.
Specifies the name of the protection group.
This example creates the protection group pg1 which uses RAC and the cluster feature.
A cluster feature disk group oracle-dg controls the data which is replicated by the EMC Symmetrix Remote Data Facility device group DG01. The node list of the RAC framework resource group is set to all nodes of the cluster.
Create the protection group on the primary cluster with the cluster feature disk group oracle-dg.
# geopg create -s pts1 -o PRIMARY -d srdf -p cluster_dgs=racdbdg \ -p external_dependency_allowed=true pg1 Protection group "pg1" successfully created. |
Add the EMC Symmetrix Remote Data Facility device group DG01 to protection group pg1.
# geopg add-device-group DG01 pg1 Device group "DG01" successfully added to the protection group "pg1". |
Add the rac_server_proxy_rg resource group and the replicated device-group resource groups, hasp4rac-rg and scaldbdg-rg, to the protection group.
# geopg add-resource-group rac_server_proxy-rg,hasp4rac-rg,scaldbdg-rg pg1 |
The Sun Cluster Geographic Edition data replication layer validates the protection group's replication role against the configuration of the EMC Symmetrix Remote Data Facility RDF1 and RDF2 devices. If the configurations do not match, the validation returns an error.
If the Cluster_dgs property is specified, then the data replication layer verifies that the device group specified is a valid Sun Cluster device group. The data replication layer also verifies that the device group is of a valid type.
The device groups that are specified in the Cluster_dgs property must be written to only by applications that belong to the protection group. This property must not specify device groups that receive information from applications outside the protection group.
A Sun Cluster replication resource group is automatically created when the protection group is created.
Do not change, remove, or bring offline these resources or resource groups. Use only Sun Cluster Geographic Edition commands to administer replication resource groups and resources that are internal entities managed by Sun Cluster Geographic Edition software. Altering the configuration or state of these entities directly with Sun Cluster commands could result in unrecoverable failure.
Before modifying the configuration of your protection group, ensure that the protection group you want to modify exists locally.
Log in to one of the cluster nodes.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Modify the configuration of the protection group.
This command modifies the properties of a protection group on all nodes of the local cluster. If the partner cluster contains a protection group of the same name, this command also propagates the new configuration information to the partner cluster.
# geopg set-prop -p property [-p...] protectiongroupname |
Specifies the properties of the protection group.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun Cluster Geographic Edition System Administration Guide.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
For more information about the geopg command, refer to the geopg(1M) man page.
This example modifies the Timeout property of the protection group that was created in Example 2–2.
# geopg set-prop -p Timeout=2700 srdfpg |
During protection group validation, the EMC Symmetrix Remote Data Facility data replication layer of the Sun Cluster Geographic Edition software validates the following:
The SYMCLI is installed on each of the nodes in the Nodelist property.
The specified device group is a valid Sun Cluster device group. The data replication layer uses the scstat -D command if the Cluster_dgs property is specified. The data replication layer also verifies that the device group is of a valid type.
The properties are valid for each EMC Symmetrix Remote Data Facility device group that has been added to the protection group.
When the geoadm status output displays that the Configuration status of a protection group is Error, you can validate the configuration by using the geopg validate command. This command checks the current state of the protection group and its entities.
If the protection group and its entities are valid, then the Configuration status of the protection groups is set to OK. If the geopg validate command finds an error in the configuration files, then the command displays a message about the error and the configuration remains in the error state. In such a case, you can fix the error in the configuration, and run the geopg validate command again.
Ensure that the protection group you want to validate exists locally and that the common agent container is online on all nodes of both clusters in the partnership.
Log in to one of the cluster nodes.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Validate the configuration of the protection group.
This command validates the configuration of the protection group on the local cluster only. To validate the protection group configuration on the partner cluster, run the command again on the partner cluster.
# geopg validate protectiongroupname |
Specifies a unique name that identifies a single protection group
This example validates a protection group.
# geopg validate protectiongroupname |
If you want to delete the protection group everywhere, you must run the geopg delete command on each cluster where the protection group exists.
Before deleting a protection group, ensure that the following conditions are met:
The protection group you want to delete exists locally.
The protection group is offline on all clusters from which you want to delete it.
You must remove the application resource groups from the protection group in order to keep the application resource groups online while deleting the protection group. See Example 2–9 for examples of this procedure.
Log in to one of the nodes on the primary cluster, cluster-paris.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Delete the protection group.
This command deletes the configuration of the protection group from the local cluster. The command also removes the replication resource group for each EMC Symmetrix Remote Data Facility device group in the protection group. This command does not alter the pair state of the EMC Symmetrix Remote Data Facility device group.
# geopg delete protectiongroupname |
Specifies the name of the protection group
To also delete the protection group on the secondary cluster, repeat step 1 and step 2 on cluster-newyork.
This example deletes a protection group from both partner clusters. The protection group is offline on both partner clusters.
In this example, cluster-paris is the primary cluster. For a reminder of the sample cluster configuration, see Example Sun Cluster Geographic Edition Cluster Configuration in Sun Cluster Geographic Edition System Administration Guide.
# rlogin phys-paris-1 -l root phys-paris-1# geopg delete srdfpg # rlogin phys-newyork-1 -l root phys-newyork-1# geopg delete srdfpg |
This example keeps online two application resource groups, apprg1 and apprg2, while deleting their protection group, srdfpg from both partner clusters. Remove the application resource groups from the protection group, then delete the protection group.
phys-paris-1# geopg remove-resource-group apprg1,apprg2 srdfpg phys-paris-1# geopg stop -e global srdfpg phys-paris-1# geopg delete srdfpg phys-newyork-1# geopg delete srdfpg |
To make an application highly available, the application must be managed as a resource in an application resource group.
All the entities you configure for the application resource group on the primary cluster, such as resources and the application resource group, must be replicated to the secondary cluster. The resource group names must be identical on both clusters. Also, the data that the application resource uses must be replicated to the secondary cluster.
This section contains information about the following tasks:
You can add an existing resource group to the list of application resource groups for a protection group. Before you add an application resource group to a protection group, ensure that the following conditions are met:
The protection group is defined.
The resource group exists on both clusters and is in an appropriate state.
The Auto_start_on_new_cluster property of the resource group is set to False. You can view this property by using the clresourcegroup command.
# clresourcegroup show -p auto_start_on_new_cluster apprg |
When you bring a protection group online on the primary cluster, bring the application resources groups that participate in that protection group online only on the same primary cluster. Setting the Auto_start_on_new_cluster property to False prevents the Sun Cluster resource group manager from automatically starting the application resource groups. In this case, the startup of resource groups is reserved for the Sun Cluster Geographic Edition software.
Application resource groups should be online only on primary cluster when the protection group is activated.
Set the Auto_start_on_new_cluster property to False as follows:
# clresourcegroup set -p Auto_start_on_new_cluster=False apprg1 |
The application resource group must not have dependencies on resource groups and resources outside of this protection group. To add several application resource groups that share dependencies, you must add the application resource groups to the protection group in a single operation. If you add the application resource groups separately, the operation fails.
The HAStoragePlus resource must exist in the application resource group, so that it can bring online the devices and mount the file systems.
The protection group can be activated or deactivated and the resource group can be either Online or Offline.
If the resource group is Offline and the protection group is Active after the configuration of the protection group has changed, the local state of the protection group becomes Degraded.
If the resource group to add is Online and the protection group is deactivated, the request is rejected. You must activate the protection group before adding an activate resource group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Add an application resource group to the protection group.
This command adds an application resource group to a protection group on the local cluster. Then the command propagates the new configuration information to the partner cluster if the partner cluster contains a protection group of the same name.
# geopg add-resource-group resourcegrouplist protectiongroup |
Specifies the name or names of the application resource group.
You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
If the add operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.
If the application resource group configuration is OK on the local cluster, the application resource group gets added to the protection group on the local and remote cluster. If the subsequent configuration validation on the remote cluster does not result in a status of OK on the partner, the status is set to Error on the partner cluster.
After the application resource group is added to the protection group, the application resource group is managed as an entity of the protection group. Then the application resource group is affected by protection group operations such as start, stop, switchover, and takeover.
This example adds two application resource groups, apprg1 and apprg2, to srdfpg.
# geopg add-resource-group apprg1,apprg2 srdfpg |
You can remove an application resource group from a protection group without altering the state or contents of an application resource group.
Ensure that the following conditions are met:
The protection group is defined on the local cluster.
The resource group to be removed is part of the application resource groups of the protection group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Remove the application resource group from the protection group.
This command removes an application resource group from the protection group on the local cluster. If the partner cluster contains a protection group of the same name, then the command removes the application resource group from the protection group on the partner cluster.
If resource groups in the protection group have dependencies between them, you must remove all affected resource groups in the same geopg remove-resource-groupcommand.
# geopg remove-resource-group resourcegrouplist protectiongroup |
Specifies the list of application resource groups.
You can specify more than one resource group in a comma-separated list.
Specifies the name of the protection group.
If the remove operation is unsuccessful on the local cluster, the configuration of the protection group is not modified. Otherwise, the Configuration status is set to OK on the local cluster.
If the Configuration status is OK on the local cluster, but the remove operation is unsuccessful on the partner cluster, the Configuration status is set to Error on the partner cluster.
This example removes two application resource groups, apprg1 and apprg2, from srdfpg.
# geopg remove-resource-group apprg1,apprg2 srdfpg |
This section provides the following information about administering EMC Symmetrix Remote Data Facility data replication device groups:
How to Add a Data Replication Device Group to an EMC Symmetrix Remote Data Facility Protection Group
How the State of the EMC Symmetrix Remote Data Facility Device Group Is Validated
How to Modify an EMC Symmetrix Remote Data Facility Data Replication Device Group
For details about configuring a EMC Symmetrix Remote Data Facility data replication protection group, see How to Create and Configure an EMC Symmetrix Remote Data Facility Protection Group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Create a data replication device group in the protection group.
This command adds a device group to a protection group on the local cluster and propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.
# geopg add-device-group -p property [-p...] devicegroupname protectiongroupname |
Specifies the properties of the data replication device group.
You can specify the following EMC Symmetrix Remote Data Facility properties:
DG_or_CG – Specifies that the device group is an EMC Symmetrix Remote Data Facility device group.
You must set this property to DG.
R1SID – Specifies the primary (RDF1) EMC Symmetrix ID of the EMC Symmetrix devices.
The data replication layer automatically sets the value of this property. You should specify the primary (RDF1) EMC Symmetrix ID of the EMC Symmetrix devices if you change the settings of the EMC Symmetrix host.
R2SID – Specifies the secondary (RDF2) EMC Symmetrix ID of the EMC Symmetrix devices.
The data replication layer automatically sets the value of this property. You should specify the secondary (RDF2) EMC Symmetrix ID of the EMC Symmetrix devices if you change the settings of the EMC Symmetrix host.
Specifies the name of the new data replication device group.
Specifies the name of the protection group that will contain the new data replication device group.
For information about the names and values that are supported by Sun Cluster Geographic Edition software, see Appendix B, Legal Names and Values of Sun Cluster Geographic Edition Entities, in Sun Cluster Geographic Edition System Administration Guide.
For more information about the geopg command, refer to the geopg(1M) man page.
This example adds the EMC Symmetrix Remote Data Facility data replication device group to the srdfpg protection group.
# geopg add-device-group devgroup1 srdfpg |
When the EMC Symmetrix Remote Data Facility device group is added to a protection group, the data replication layer makes the following validations.
The specified device group name exists in the EMC Symmetrix Remote Data Facility configuration.
The replication role matches the EMC Symmetrix Remote Data Facility protection group role.
The EMC Symmetrix source, R1SID, and the EMC Symmetrix target, R2SID, can be reached.
When an EMC Symmetrix Remote Data Facility device group is added to a protection group, a Sun Cluster data replication resource is automatically created by this command. This resource monitors data replication state. The name of the resource is sc_ggeo_dr-SRDFprotectiongroupname-devicegroupname. This resource is placed in the corresponding Sun Cluster resource group, which is named sc_geo_dr-SRDFprotectiongroupname.
Do not change, remove, or bring offline these resources or resource groups. Use only Sun Cluster Geographic Edition commands to administer replication resource groups and resources that are internal entities managed by Sun Cluster Geographic Edition software. Altering the configuration or state of these entities directly with Sun Cluster commands could result in unrecoverable failure.
The state of each EMC Symmetrix Remote Data Facility device group is mapped to the Sun Cluster Geographic Edition resource group state. The symrdf -g dgname query command returns this state.
The remainder of this section describes the individual device group states and how these states are validated against the local role of the protection group.
An individual EMC Symmetrix Remote Data Facility device group can be in one of the following states:
Synchronized
SynInProg
Failedover
R1 Updated
R1 UpdInProg
Split
Suspended
Partitioned
Invalid
If a protection group contains only one EMC Symmetrix Remote Data Facility device group, then the aggregate device group state is the same as the individual device group state.
When a protection group contains multiple EMC Symmetrix Remote Data Facility device groups, the aggregate device group state is obtained as described in the following table.
Table 2–1 Conditions That Determine the Aggregate Device Group State
Condition |
Aggregate Device Group State |
---|---|
Any of the individual device group states are Invalid. |
Invalid |
Any of the individual device groups states are Partitioned and none of the individual device group states is Invalid. |
Partitioned |
One or more of the individual device groups states are Suspended and none of the individual device group states is Invalid, or Partitioned. |
Suspended |
One or more of the individual device groups states are Split and none of the individual device group states is Invalid, Partitioned, or Suspended. |
Split |
One or more of the individual device groups states are R1 UpdInProg and none of the individual device group states is Invalid, Partitioned, Suspended, or Split. |
R1 UpdInProg |
One or more of the individual device groups states are R1 Updated and none of the individual device group states is Invalid, Partitioned, Suspended, Split, or R1 UpdInProg. |
R1 Updated |
One or more of the individual device groups states are Failedover and none of the individual device group states is Invalid, Partitioned, Suspended, Split, R1 UpdInProg, or R1 Updated. |
Failedover |
One or more of the individual device groups states are SynInProg and none of the individual device group states is Invalid, Partitioned, Suspended, Split, R1 UpdInProg, R1 Updated, or Failedover. |
SynInProg |
All of the individual device group states are Synchronized. |
Synchronized |
The resource status message reflects the role and state of the RDF pair. For example, the resource status and status message of Faulted Split, is reported when the RDF pair is in a Split state.
The RDF pair state is mapped to the associated resource status as described in the following table.
Table 2–2 Mapping From the RDF Pair State to the Resource Status
Condition |
Resource Status |
Status Message |
---|---|---|
The RDF pair state is Invalid and the pair state is not Incorrect Role. |
Faulted |
Invalid state |
The RDF pair state is Partitioned and the pair state is not Incorrect Role, or Invalid. |
Faulted |
Partitioned |
The RDF pair state is Suspended and the pair state is not Incorrect Role, Invalid, or Partitioned. |
Faulted |
Suspended |
The RDF pair state is SyncInProg and the pair state is not Incorrect Role, Invalid, Partitioned, or Suspended. |
Degraded |
SyncInProg |
The RDF pair state is R1 UpdInProg and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended, or SyncInProg. |
Faulted |
R1 UpdInProg |
The RDF pair state is Split and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, or R1 UpdInProg. |
Faulted |
Split |
The RDF pair state is Failed over and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, R1 UpdInProg, or Split. |
Faulted |
Failed over |
The RDF pair state is R1 Updated and the pair state is not Incorrect Role, Invalid, Partitioned, Suspended,SyncInProg, R1 UpdInProg, Split, or Failed over. |
Faulted |
Replicating with role change |
The RDF pair state is Synchronized. |
Online |
Replicating |
The state of the RDF pair determines the availability of consistent data in the partnership. When the state of the RDF resource on the primary or secondary cluster is Degraded or Faulted, the data volumes might not be synchronized even if the application can still write data from the primary volume to the secondary volume. The RDF pair will be in a Partitioned state and the invalid entries will be logged as the data is written to the primary volume. Manual recovery operations are required to resolve the error and resynchronize the data.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Modify the device group.
This command modifies the properties of a device group in a protection group on the local cluster. Then the command propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.
# geopg modify-device-group -p property [-p...] srdfdevicegroupname protectiongroupname |
Specifies the properties of the data replication device group.
For more information about the properties you can set, see Appendix A, Standard Sun Cluster Geographic Edition Properties, in Sun Cluster Geographic Edition System Administration Guide.
Specifies the name of the new data replication device group.
Specifies the name of the protection group that will contain the new data replication device group.
This example modifies the R1SID property of a data replication device group that is part of an EMC Symmetrix Remote Data Facility protection group.
# geopg modify-device-group -p R1SID=215 srdfdg srdfpg |
You might delete a data replication device group from a protection group if you added a data replication device group to a protection group. Normally, after an application is configured to write to a set of disks, you would not change the disks.
Deleting a data replication device group does not stop replication or change the replication status of the data replication device group.
For information about deleting protection groups, refer to How to Delete an EMC Symmetrix Remote Data Facility Protection Group. For information about deleting application resource groups from a protection group, refer to How to Delete an Application Resource Group From an EMC Symmetrix Remote Data Facility Protection Group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Remove the device group.
This command removes a device group from a protection group on the local cluster. Then the command propagates the new configuration to the partner cluster if the partner cluster contains a protection group of the same name.
# geopg remove-device-group devicegroupname protectiongroupname |
Specifies the name of the data replication device group
Specifies the name of the protection group
When a device group is deleted from an EMC Symmetrix Remote Data Facility protection group, the corresponding Sun Cluster resource, sc_geo_dr-SRDF-protectiongroupname-devicegroupname, is removed from the replication resource group. As a result, the deleted device group is no longer monitored. The replication resource group is removed when the protection group is deleted.
This example removes an EMC Symmetrix Remote Data Facility data replication device group srdfdg from the srdfpg protection group.
# geopg remove-device-group srdfdg srdfpg |
After you have configured data replication, resource groups, and resources on your primary and secondary clusters and you have created a protection group for those entities on the primary cluster, you can replicate the configuration of the protection group to the secondary cluster.
Before you replicate the configuration of an EMC Symmetrix Remote Data Facility protection group to a partner cluster, ensure that the following conditions are met:
The protection group is defined on the remote cluster, not on the local cluster.
The device groups in the protection group on the remote cluster exist on the local cluster.
The system files on all nodes that can master the application have been updated for the application.
The application resource groups in the protection group on the remote cluster exist on the local cluster.
The Auto_start_on_new_cluster property of the application resource group is set to False. You can view this property by using the clresourcegroup command.
# clresourcegroup show -p auto_start_on_new_cluster apprg1 |
Setting the Auto_start_on_new_cluster property to False prevents the Sun Cluster resource group manager from automatically starting the resource groups in the protection group. Therefore, after the Sun Cluster Geographic Edition software restarts and communicates with the remote cluster to ensure that the remote cluster is running and that the remote cluster is the secondary cluster for that resource group. The Sun Cluster Geographic Edition software does not automatically start the resource group on the primary cluster.
Application resource groups should be online only on primary cluster when the protection group is activated.
Set the Auto_start_on_new_cluster property to False as follows:
# clresourcegroup set -p Auto_start_on_new_cluster=False apprg1 |
The HAStoragePlus resource exists in the application resource group to enable devices and mount file systems.
Log in to phys-newyork-1.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
phys-newyork-1 is a node on the secondary cluster. For a reminder of which node is phys-newyork-1 , see Example Sun Cluster Geographic Edition Cluster Configuration in Sun Cluster Geographic Edition System Administration Guide.
Replicate the protection group configuration to the partner cluster by using the geopg get command.
This command retrieves the configuration information of the protection group from the remote cluster and creates the protection group on the local cluster.
phys-newyork-1# geopg get -s partnershipname protectiongroup |
Specifies the name of the partnership from which the protection group configuration information should be retrieved and the name of the partnership where the protection will be created locally.
Specifies the name of the protection group.
If no protection group is specified, then all protection groups that exist in the specified partnership on the remote partner are created on the local cluster.
The geopg get command replicates Sun Cluster Geographic Edition related entities. For information about how to replicate Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
This example replicates the configuration of srdfpg from cluster-paris to cluster-newyork.
# rlogin phys-newyork-1 -l root phys-newyork-1# geopg get -s paris-newyork-ps srdfpg |
When you activate a protection group, the protection group assumes the role that you assigned to it during configuration. You can activate a protection group in the following ways:
Globally – Activates a protection group on both clusters where the protection group is configured
On the primary cluster only – Secondary cluster remains inactive
On the secondary cluster only – Primary cluster remains inactive
Activating an EMC Symmetrix Remote Data Facility protection group on a cluster has the following effect on the data replication layer:
The data replication configuration of the protection group is validated. During validation, the current local role of a protection group is compared with the configuration of the EMC Symmetrix Remote Data Facility device groups.
If the EMC Symmetrix Remote Data Facility device group is not in a Failedover state, the local role of the protection group should match the role of the EMC Symmetrix Remote Data Facility device group.
If the EMC Symmetrix Remote Data Facility device group is in a Failedover state, then the local role of the protection group becomes secondary while the role of the EMC Symmetrix Remote Data Facility device group remains primary.
Data replication is started on the data replication device groups that are configured for the protection group, no matter whether the activation occurs on a primary or secondary cluster. Data is always replicated from the cluster on which the local role of the protection group is primary to the cluster on which the local role of the protection group is secondary.
Application handling proceeds only after data replication has been started successfully.
Activating a protection group has the following effect on the application layer:
When a protection group is activated on the primary cluster, the application resource groups that are configured for the protection group are also started. The Sun Cluster Geographic Edition software uses the following Sun Cluster commands on the primary cluster to bring the resource groups online:
# scswitch -Z -g rglist |
When a protection group is activated on the secondary cluster, the application resource groups are not started. The resource groups are put into the unmanaged state.
When you activate a protection group using the command in this procedure, application resource groups in the protection group are also brought online. For details about how the -e (scope) option affects resource groups in the protection group, see the geopg(1M) man page.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Activate the protection group.
# geopg start -e scope [-n] protectiongroupname |
Specifies the scope of the command.
If the scope is local, then the command operates on the local cluster only. If the scope is global, the command operates on both clusters that deploy the protection group.
The property values global and local are not case sensitive.
Prevents the start of data replication at protection group startup.
If you omit this option, the data replication subsystem starts at the same time as the protection group.
Specifies the name of the protection group.
The geopg start command uses the scswitch -Z -g resourcegrouplist command to bring resource groups and resources online. For more information about using this command, see the scswitch(1M) man page.
In this example, the Sun Cluster Geographic Edition software starts data replication of an EMC Symmetrix Remote Data Facilitydevice group.
First, the EMC Symmetrix Remote Data Facility protection group is created.
phys-paris-1# geopg create -s paris-newyork-ps -o primary -d srdf srdfpg |
The device group devgroup1 is added to the protection group.
phys-paris-1# geopg add-device-group devgroup1 srdfpg |
The current RDF pair state of an EMC Symmetrix Remote Data Facility device group, devgroup1, is returned in the output of the symrdf query command as follows:
phys-paris-1# symrdf -g devgroup1 query Device Group (DG) Name : devgroup1 DG's Type : RDF1 DG's Symmetrix ID : 000187401215 Source (R1) View Target (R2) View MODES -------------------------------- ------------------------ ----- ------------ ST LI ST Standard A N A Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair Device Dev E Tracks Tracks S Dev E Tracks Tracks MDA STATE -------------------------------- -- ------------------------ ----- ------------ DEV001 00E4 RW 0 36 NR 00E4 RW 36 0 S.. Split DEV002 00E5 RW 0 36 NR 00E5 RW 36 0 S.. Split DEV003 00E6 RW 0 36 NR 00E6 RW 36 0 S.. Split |
The aggregate device group state is Split.
Next, the protection group, srdfpg, is activated by using the geopg start command.
phys-paris-1# geopg start -e local srdfpg |
The Sun Cluster Geographic Edition software runs the symrdf -g devgroup1 establish command at the data replication level. If the command is successful, the state of devgroup1 is returned in the output of the symrdf query command as follows:
phys-paris-1# symrdf -g devgroup1 query Device Group (DG) Name : devgroup1 DG's Type : RDF1 DG's Symmetrix ID : 000187401215 Source (R1) View Target (R2) View MODES -------------------------------- ------------------------ ----- ------------ ST LI ST Standard A N A Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair Device Dev E Tracks Tracks S Dev E Tracks Tracks MDA STATE -------------------------------- -- ------------------------ ----- ------------ DEV001 00E4 RW 0 0 RW 00E4 WD 0 0 S.. Synchronized DEV002 00E5 RW 0 0 RW 00E5 WD 0 0 S.. Synchronized DEV003 00E6 RW 0 0 RW 00E6 WD 0 0 S.. Synchronized |
This example activates a protection group globally.
# geopg start -e global srdfpg |
The protection group, srdfpg, is activated on both clusters where the protection group is configured. The application resource groups in srdfpg are brought online on the primary cluster.
This example activates a protection group on a local cluster only. This local cluster might be a primary cluster or a secondary cluster, depending on the role of the cluster.
# geopg start -e local srdfpg |
If the local cluster is the primary cluster, the resource groups in srdfpg also brought online on that cluster.
You can deactivate a protection group on the following levels:
Globally – Deactivates a protection group on both clusters where the protection group is configured.
On the primary cluster only – Secondary cluster remains active.
On the secondary cluster only – Primary cluster remains active.
Deactivating an EMC Symmetrix Remote Data Facility protection group on a cluster has the following effect on the data replication layer:
The data replication configuration of the protection group is validated. During validation, the current local role of the protection group is compared with the aggregate device group state. If validation is successful, data replication is stopped.
Data replication is stopped on the data replication device groups that are configured for the protection group, whether the deactivation occurs on a primary or secondary cluster.
Deactivating a protection group has the following effect on the application layer:
When a protection group is deactivated on the primary cluster, all of the application resource groups configured for the protection group are stopped and unmanaged.
When a protection group is deactivated on the secondary cluster, the resource groups on the secondary cluster are not affected. Application resource groups that are configured for the protection group might remain active on the primary cluster, depending on the activation state of the primary cluster.
The EMC Symmetrix Remote Data Facility command that is used to stop data replication depends on the RDF state of the EMC Symmetrix Remote Data Facility device group.
The following table describes the EMC Symmetrix Remote Data Facility command that is used to stop data replication for each of the possible combinations of factors.
Table 2–3 Commands Used to Stop EMC Symmetrix Remote Data Facility Data Replication
Aggregate Device Group State |
Valid Local Protection Group Role |
EMC Symmetrix Remote Data Facility Command |
---|---|---|
Split, Suspended, Partitioned, or Failover |
primary or secondary |
No command is run because no data is being replicated. |
Synchronized or R1Updated |
primary or secondary |
The symrdf split command is run. |
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Deactivate the protection group.
When you deactivate a protection group on the primary cluster, its application resource groups are also taken offline.
# geopg stop -e scope [-D] protectiongroupname |
Specifies the scope of the command.
If the scope is Local, then the command operates on the local cluster only. If the scope is Global, the command operates on both clusters where the protection group is deployed.
The property values, such as Global and Local, are not case sensitive.
Specifies that only data replication should be stopped and the protection group should be online.
If you omit this option, the data replication subsystem and the protection group are both stopped.
Specifies the name of the protection group.
This example illustrates how the Sun Cluster Geographic Edition software determines the EMC Symmetrix Remote Data Facility command that is used to stop data replication.
The current state of the EMC Symmetrix Remote Data Facility device group, devgroup1, is returned in the output of the symrdf query command as follows:
phys-paris-1# symrdf -g devgroup1 query Device Group (DG) Name : devgroup1 DG's Type : RDF1 DG's Symmetrix ID : 000187401215 Source (R1) View Target (R2) View MODES -------------------------------- ------------------------ ----- ------------ ST LI ST Standard A N A Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair Device Dev E Tracks Tracks S Dev E Tracks Tracks MDA STATE -------------------------------- -- ------------------------ ----- ------------ DEV001 00E4 RW 0 0 RW 00E4 WD 0 0 S.. Synchronized DEV002 00E5 RW 0 0 RW 00E5 WD 0 0 S.. Synchronized DEV003 00E6 RW 0 0 RW 00E6 WD 0 0 S.. Synchronized DEV004 00E7 RW 0 0 RW 00E7 WD 0 0 S.. Synchronized DEV005 00E8 RW 0 0 RW 00E8 WD 0 0 S.. Synchronized DEV006 00E9 RW 0 0 RW 00E9 WD 0 0 S.. Synchronized |
A device group, devgroup1, is added to the protection group as follows:
phys-paris-1# geopg add-device-group -p DG_or_CG=DG devgroup1 srdfpg |
Next, the protection group, srdfpg, is deactivated by using the geopg stop command.
phys-paris-1# geopg stop -s local srdfpg |
The Sun Cluster Geographic Edition software runs the symrdf -g devgroup1 split command at the data replication level.
If the command is successful, the state of devgroup1 is returned in the output of the symrdf query command as follows:
phys-paris-1# symrdf -g devgroup1 query Device Group (DG) Name : devgroup1 DG's Type : RDF1 DG's Symmetrix ID : 000187401215 Source (R1) View Target (R2) View MODES -------------------------------- ------------------------ ----- ------------ ST LI ST Standard A N A Logical T R1 Inv R2 Inv K T R1 Inv R2 Inv RDF Pair Device Dev E Tracks Tracks S Dev E Tracks Tracks MDA STATE -------------------------------- -- ------------------------ ----- ------------ DEV001 00E4 RW 0 0 NR 00E4 RW 0 0 S.. Split DEV002 00E5 RW 0 0 NR 00E5 RW 0 0 S.. Split DEV003 00E6 RW 0 0 NR 00E6 RW 0 0 S.. Split DEV004 00E7 RW 0 0 NR 00E7 RW 0 0 S.. Split DEV005 00E8 RW 0 0 NR 00E8 RW 0 0 S.. Split DEV006 00E9 RW 0 0 NR 00E9 RW 0 0 S.. Split |
This example deactivates a protection group on all clusters.
# geopg stop -e global srdfpg |
This example deactivates a protection group on the local cluster.
# geopg stop -e local srdfpg |
This example stops only data replication on both partner clusters.
# geopg stop -e local -D srdfpg |
If the administrator decides later to deactivate both the protection group and its underlying data replication subsystem, the administrator can rerun the command without the -D option:
# geopg stop -e local srdfpg |
This example keeps two application resource groups, apprg1 and apprg2, online while deactivating their protection group, srdfpg, on both clusters.
Remove the application resource groups from the protection group.
# geopg remove-resource-group apprg1,apprg2 srdfpg |
Deactivate the protection group.
# geopg stop -e global srdfpg |
You can resynchronize the configuration information of the local protection group with the configuration information that is retrieved from the partner cluster. You need to resynchronize a protection group when its Synchronization status in the output of the geoadm status command is Error.
For example, you might need to resynchronize protection groups after booting the cluster. For more information, see Booting a Cluster in Sun Cluster Geographic Edition System Administration Guide.
Resynchronizing a protection group updates only entities that are related to Sun Cluster Geographic Edition software. For information about how to update Sun Cluster entities, see Replicating and Upgrading Configuration Data for Resource Groups, Resource Types, and Resources in Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
The protection group must be deactivated on the cluster where you are running the geopg update command. For information about deactivating a protection group, see Deactivating an EMC Symmetrix Remote Data Facility Protection Group.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Resynchronize the protection group.
This command synchronizes the local Sun Cluster Geographic Edition protection group configuration information on the local cluster with the protection group configuration information retrieved from the partner cluster.
# geopg update protectiongroupname |
Specifies the name of the protection group
This example resynchronizes a protection group.
# geopg update srdfpg |
You can obtain an overall view of the status of replication as well as a more detailed runtime status of the EMC Symmetrix Remote Data Facility replication resource groups. The following sections describe the procedures for checking each status:
Displaying an EMC Symmetrix Remote Data Facility Runtime Status Overview
Displaying a Detailed EMC Symmetrix Remote Data Facility Runtime Status
The status of each EMC Symmetrix Remote Data Facility data replication resource indicates the status of replication on a particular device group. The status of all the resources under a protection group are aggregated in the replication status. This replication status is the second component of the protection group state. For more information about the states of protection groups, refer to Monitoring the Runtime Status of the Sun Cluster Geographic Edition Software in Sun Cluster Geographic Edition System Administration Guide.
To view the overall status of replication, look at the protection group state as described in the following procedure.
Access a node of the cluster where the protection group has been defined.
You must be assigned the Basic Solaris User RBAC rights profile to complete this procedure. For more information about RBAC, see Sun Cluster Geographic Edition Software and RBAC in Sun Cluster Geographic Edition System Administration Guide.
Check the runtime status of replication.
# geoadm status |
Refer to the Protection Group section of the output for replication information. The information that is displayed by this command includes the following:
Whether the local cluster is enabled for partnership participation
Whether the local cluster is involved in a partnership
Status of the heartbeat configuration
Status of the defined protection groups
Status of current transactions
Check the runtime status of data replication for each EMC Symmetrix Remote Data Facility device group.
# clresourcegroup status sc_geo_dr-SRDF-protectiongroupname # clresource status sc_geo_dr-SRDF-protectiongroupname-srdf dgname |
Refer to the Status and Status Message fields for the data replication device group you want to check.
For more information about these fields, see Table 2–4.
The Sun Cluster Geographic Edition software internally creates and maintains one replication resource group for each protection group. The name of the replication resource group has the following format:
# sc_geo_dr-SRDF-protectiongroupname |
If you add an EMC Symmetrix Remote Data Facility device group to a protection group, Sun Cluster Geographic Edition software creates a resource for each device group. This resource monitors the status of replication for its device group. The name of each resource has the following format:
# sc_geo_dr-SRDFprotectiongroupname-srdfdevicegroupname |
You can monitor the status of replication of this device group by checking the Status and Status Message of this resource. Use the clresourcegroup status command to display resource status and the status message.
The following table describes the Status and Status Message values that are returned by the clresource status command when the State of the EMC Symmetrix Remote Data Facility replication resource group is Online.
Table 2–4 Status and Status Messages of an Online EMC Symmetrix Remote Data Facility Replication Resource Group
Status |
Status Message |
---|---|
Online |
Replicating |
Degraded |
Suspended |
Degraded |
SyncInProg |
Faulted |
Incorrect role |
Faulted |
Invalid state |
Faulted |
Partitioned |
Faulted |
R1 UpdInProg |
Faulted |
Split |
Faulted |
Failed over |
For more information about these values, refer to the EMC Symmetrix Remote Data Facility documentation.
For more information about the clresource command, see the clresource(1CL) man page.