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
When you activate a protection group, the protection group assumes the role that you assigned to it during configuration. For more information about configuring protection groups, see How to Create and Configure a Hitachi TrueCopy or Universal Replicator Protection Group That Does Not Use Oracle Real Application Clusters.
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 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 a protection group is compared with the aggregate device group state as described in Table 2-3. If validation is successful, data replication is started.
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.
When a protection group is activated on the secondary cluster, the application resource groups are not started.
The Hitachi TrueCopy or Universal Replicator command that is used to start data replication depends on the following factors:
Aggregate device group state
Local role of the protection group
Current pair state
In Oracle Solaris Cluster Geographic Edition 3.2 11/09, if a protection group has a consistency group defined, the fence level is async and the device group is in SMPL state, then you create the device group with the paircreate command when the geopg start command is run with the -f flag . If a protection group has a consistency group defined, the fence level is not async and the device group is in SMPL state then you create the device group with the paircreate command when you run the geopg start command with the -fg flags. On arrays that only support the Hitachi TrueCopy software, the -fg fence level option to the geopg command is not supported. Thus, on such arrays, the user should only define the ctgid on the protection group, if that protection group only has device groups of fence level async.
The following table describes the Hitachi TrueCopy or Universal Replicator command that is used to start data replication for each of the possible combinations of factors. In the commands, dg is the device group name and fl is the fence level that is configured for the device group.
Table 2-4 Commands Used to Start 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 activate a protection group, its application resource groups are also brought online.
# 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.
Note - The property values, such as 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 Oracle Solaris Cluster commands to bring resource groups and resources online.
Example 2-16 How the Geographic Edition Software Issues the Command to Start Replication
This example illustrates how the Geographic Edition determines the Hitachi TrueCopy or Universal Replicator command that is used to start data replication.
First, the Hitachi TrueCopy or Universal Replicator protection group is created.
phys-paris-1# geopg create -s paris-newyork-ps -o primary -d truecopy tcpg
A device group, devgroup1, is added to the protection group.
phys-paris-1# geopg add-device-group -p fence_level=async devgroup1 tcpg
The current state of a 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..SMPL ---- ----, ----- ---- - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..SMPL ---- ----, ----- ---- - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..SMPL ---- ----, ----- ---- - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..SMPL ---- ----, ----- ---- -
The aggregate device group state is SMPL.
Next, the protection group, tcpg, is activated by using the geopg start command.
phys-paris-1# geopg start -e local tcpg
The Geographic Edition software runs the paircreate -g devgroup1 -vl -f async 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 COPY ASYNC,54321 609 - devgroup1 pair1(R) (CL1-C , 0, 20)54321 609..S-VOL COPY ASYNC,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 12345 2..P-VOL COPY ASYNC,54321 610 - devgroup1 pair2(R) (CL1-C , 0,21) 54321 610..S-VOL COPY ASYNC,----- 2 -
Example 2-17 Activating a Hitachi TrueCopy or Universal Replicator Protection Group Globally
This example activates a protection group globally.
# geopg start -e global tcpg
The protection group, tcpg, is activated on both clusters where the protection group is configured.
Example 2-18 Activating a Hitachi TrueCopy or Universal Replicator Protection Group Locally
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 tcpg