Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy and Universal Replicator |
1. Replicating Data With Hitachi TrueCopy and Universal Replicator Software
2. Administering Hitachi TrueCopy and Universal Replicator Protection Groups
Strategies for Creating Hitachi TrueCopy and Universal Replicator Protection Groups
Creating a Protection Group While the Application Is Offline
Creating a Protection Group While the Application Is Online
Ensuring Data Consistency for Hitachi Universal Replicator in Asynchronous Mode
Understanding Data Consistency in Geographic Edition
Using Consistency Group IDs to Ensure Data Consistency
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 a Hitachi TrueCopy or Universal Replicator Protection Group
Validating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Validate a Hitachi TrueCopy or Universal Replicator Protection Group
How to Delete a Hitachi TrueCopy or Universal Replicator Protection Group
Administering Hitachi TrueCopy and Universal Replicator Application Resource Groups
Administering Hitachi TrueCopy and Universal Replicator Data Replication Device Groups
Validations Made by the Data Replication Subsystem
How the State of the Hitachi TrueCopy or Universal Replicator Device Group Is Validated
Determining the State of an Individual Hitachi TrueCopy or Universal Replicator Device Group
Determining the Aggregate Hitachi TrueCopy or Universal Replicator Device Group State
Validating the Local Role of the Protection Group Against the Aggregate Device Group State
How to Modify a Hitachi TrueCopy or Universal Replicator Data Replication Device Group
Activating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Activate a Hitachi TrueCopy or Universal Replicator Protection Group
Deactivating a Hitachi TrueCopy or Universal Replicator Protection Group
How to Deactivate a Hitachi TrueCopy or Universal Replicator Protection Group
Resynchronizing a Hitachi TrueCopy or Universal Replicator Protection Group
How to Resynchronize a Protection Group
Checking the Runtime Status of Hitachi TrueCopy and Universal Replicator Data Replication
Displaying a Hitachi TrueCopy or Universal Replicator Runtime Status Overview
How to Check the Overall Runtime Status of Replication
Displaying a Detailed Hitachi TrueCopy or Universal Replicator Runtime Status
3. Migrating Services That Use Hitachi TrueCopy and Universal Replicator Data Replication
A. Geographic Edition Properties for Hitachi TrueCopy and Universal Replicator
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 a Hitachi TrueCopy or Universal Replicator 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 as described in Table 2-3. 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 that are 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 Hitachi TrueCopy or Universal Replicator command that is used to stop data replication depends on the following factors:
Aggregate device group state
Local role of the protection group
Current pair state
The following table describes the Hitachi TrueCopy or Universal Replicator command used to stop data replication for each of the possible combinations of factors. In the commands, dg is the device group name.
Table 2-5 Commands Used to Stop Hitachi TrueCopy or Universal Replicator Data Replication
|
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information about RBAC, see Geographic Edition Software and RBAC in Oracle Solaris Cluster Geographic Edition System Administration Guide.
When you deactivate a protection group, its application resource groups are also unmanaged.
# 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.
Note - 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.
Example 2-19 How the Geographic Edition Software Issues the Command to Stop Replication
This example illustrates how the Geographic Edition software determines the Hitachi TrueCopy or Universal Replicator command that is used to stop data replication.
The current state of the Hitachi TrueCopy or Universal Replicator device group, devgroup1, is provided in the output of the pairdisplay command:
phys-paris-1# pairdisplay -g devgroup1 Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M devgroup1 pair1(L) (CL1-A , 0, 1) 12345 1..P-VOL PAIR ASYNC,54321 609 - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL PAIR ASYNC,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..P-VOL PAIR ASYNC,54321 610 - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL PAIR ASYNC,----- 2 -
A device group, devgroup1, is added to the protection group as follows:
phys-paris-1# geopg add-device-group -p fence_level=async devgroup1 tcpg
The Geographic Edition software runs the pairvolchk -g <DG> -ss command at the data replication level, which returns a value of 43.
# pairvolchk -g devgroup1 -ss Volstat is P-VOL.[status = PAIR fence = ASYNC] phys-paris-1# echo $? 43
Next, the protection group, tcpg, is deactivated by using the geopg stop command.
phys-paris-1# geopg stop -s local tcpg
The Geographic Edition software runs the pairsplit -g devgroup1 command at the data replication level.
If the command is successful, the state of devgroup1 is provided in the output of the pairdisplay command:
phys-paris-1# pairdisplay -g devgroup1 Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M devgroup1 pair1(L) (CL1-A , 0, 1) 12345 1..P-VOL PSUS ASYNC,54321 609 - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL SSUS ASYNC,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..P-VOL PSUS ASYNC,54321 610 - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL SSUS ASYNC,----- 2 -
Example 2-20 Deactivating a Protection Group on All Clusters
This example deactivates a protection group on all clusters.
# geopg stop -e global tcpg
Example 2-21 Deactivating a Protection Group on a Local Cluster
This example deactivates a protection group on the local cluster.
# geopg stop -e local tcpg
Example 2-22 Stopping Data Replication While Leaving the Protection Group Online
This example stops only data replication on a local cluster.
# geopg stop -e local -D tcpg
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 tcpg
Example 2-23 Deactivating a Hitachi TrueCopy or Universal Replicator Protection Group While Keeping Application Resource Groups Online
This example keeps two application resource groups, apprg1 and apprg2, online while deactivating their protection group, tcpg, on both clusters.
Remove the application resource groups from the protection group.
# geopg remove-resource-group apprg1,apprg2 tcpg
Deactivate the protection group.
# geopg stop -e global tcpg