During data replication, data from a primary cluster is copied to a backup or secondary cluster. The secondary cluster can be located at a geographically separated site from the primary cluster. This distance depends on the distance support that is available from your data replication product.
The Sun Cluster Geographic Edition software supports the use of Hitachi TrueCopy software for data replication. Before you start replicating data with Hitachi TrueCopy software, you must be familiar with the Hitachi TrueCopy documentation, have the Hitachi TrueCopy product, and have the latest Hitachi TrueCopy patches installed on your system. For information about installing the Hitachi TrueCopy software, see the Hitachi TrueCopy product documentation.
This chapter contains the procedures for configuring and administering data replication with Hitachi TrueCopy software. The chapter contains the following sections:
For information about creating and deleting data replication device groups, see Administering Hitachi TrueCopy Data Replication Device Groups. For information about obtaining a global and a detailed runtime status of replication, see Checking the Runtime Status of Hitachi TrueCopy Data Replication.
This section summarizes the steps for configuring Hitachi TrueCopy data replication in a protection group.
Table 1–1 Administration Tasks for Hitachi TrueCopy Data Replication
This section describes how to configure Hitachi TrueCopy software on the primary and secondary cluster. It also includes information about the preconditions for creating Hitachi TrueCopy protection groups. This section provides the following information:
Configuring Data Replication With Hitachi TrueCopy Software on the Primary Cluster
Configuring Data Replication With Hitachi TrueCopy Software on the Secondary Cluster
Initial configuration of the primary and secondary clusters includes the following:
Configuring a Hitachi TrueCopy device group, devgroup1, with the required number of disks
If you are using raw-disk device groups, configuring a raw-disk group rawdg
If you are using VERITAS Volume Manager:
Configuring the VERITAS Volume Manager disk group, oradg1
Configuring the VERITAS Volume Manager volume, vol1
Configuring the Sun Cluster device group for the VERITAS Volume Manager disk group, oradg1
Configuring the file system, which includes creating the file system, creating mount points, and adding entries to the /etc/vfstab file
Creating an application resource group, apprg1, which contains a HAStoragePlus resource
Observe the following requirements and guidelines:
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support using a Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
If you use the Hitachi TrueCopy Command Control Interface (CCI) for data replication, you must use RAID Manager. For information about which version you should use, see the Sun Cluster Geographic Edition Installation Guide.
This model requires specific hardware configurations with Sun StorEdgeTM 9970/9980 Array or Hitachi Lightning 9900 Series Storage. Contact your Sun service representative for information about Sun Cluster configurations that are currently supported.
Device pairs that have a requirement for I/O consistency must belong to the same device group.
A Hitachi TrueCopy device group that is managed by Sun Cluster Geographic Edition software must not share the same CTGID with any other Hitachi TrueCopy device group that is on the system.
Sun Cluster Geographic Edition software uses the default CCI instance to manage the Hitachi TrueCopy devices. Sun Cluster Geographic Edition software starts the default CCI instance whenever a TrueCopy device group is managed by Sun Cluster Geographic Edition software. Applications that are not under the control of Sun Cluster Geographic Edition software can also use the default CCI instance or any other instances without risk to Sun Cluster Geographic Edition or application processes or data.
Sun Cluster Geographic Edition software supports the hardware configurations that are supported by the Sun Cluster software. Contact your Sun service representative for information about current supported Sun Cluster configurations.
This section describes the steps you must perform on the primary cluster before you can configure Hitachi TrueCopy data replication in Sun Cluster Geographic Edition software. To illustrate each step, this section uses an example of two disks, or LUNs, that are called d1 and d2. These disks are in a Hitachi TrueCopy array that holds data for an application that is called apprg1.
Configure Hitachi TrueCopy device groups on shared disks in the primary cluster by editing the /etc/horcm.conf file on each node of the cluster that has access to the Hitachi array. Disks d1 and d2 are configured to belong to a Hitachi TrueCopy device group, devgroup1. The application, apprg1, can run on all nodes that have Hitachi TrueCopy device groups configured.
For more information about how to configure the /etc/horcm.conf file, see the Sun StorEdge SE 9900 V Series Command and Control Interface User and Reference Guide.
The following table describes the configuration information from our example that is found in the /etc/horcm.conf file.
Table 1–2 Example Section of the /etc/horcm.conf File on the Primary Cluster
dev_group |
dev_name |
port number |
TargetID |
LU number |
MU number |
devgroup1 |
pair1 |
CL1–A |
0 |
1 | |
devgroup1 |
pair2 |
CL1–A |
0 |
2 |
The configuration information in the table indicates that the Hitachi TrueCopy device group, devgroup1, contains two pairs. The first pair, pair1, is from the d1 disk, which is identified by the tuple <CL1–A , 0, 1>. The second pair, pair2, is from the d2 disk and is identified by the tuple <CL1–A, 0, 2>. The replicas of disks d1 and d2 are located in a geographically separated Hitachi TrueCopy array. The remote Hitachi TrueCopy is connected to the partner cluster.
Sun Cluster Geographic Edition supports the use of raw-disk device groups in addition to various volume managers. When you initially configure Sun Cluster, device groups are automatically configured for each raw device in the cluster. Use this procedure to reconfigure these automatically created device groups for use with Sun Cluster Geographic Edition.
For the devices that you want to use, unconfigure the predefined device groups.
The following commands remove the predefined device groups for d7 and d8.
phys-paris-1# cldevicegroup disable dsk/d7 dsk/d8 phys-paris-1# cldevicegroup offline dsk/d7 dsk/d8 phys-paris-1# cldevicegroup delete dsk/d7 dsk/d8 |
Create the new raw-disk device group, including the desired devices.
Ensure that the new DID does not contain any slashes. The following command creates a global device group rawdg containing d7 and d8.
phys-paris-1# cldevicegroup create -n phys-paris-1,phys-paris-2 \ -t rawdisk -d d7,d8 rawdg |
The following commands illustrate configuring the device group on the primary cluster, configuring the same device group on the partner cluster, and adding the group to a Hitachi TrueCopy protection group.
Remove the automatically created device groups from the primary cluster. phys-paris-1# cldevicegroup disable dsk/d7 dsk/d8 phys-paris-1# cldevicegroup offline dsk/d7 dsk/d8 phys-paris-1# cldevicegroup delete dsk/d7 dsk/d8 Create the raw-disk device group on the primary cluster. phys-paris-1# cldevicegroup create -n phys-paris-1,phys-paris-2 \ -t rawdisk -d d7,d8 rawdg Remove the automatically created device groups from the partner cluster. phys-newyork-1# cldevicegroup disable dsk/d5 dsk/d6 phys-newyork-1# cldevicegroup offline dsk/d5 dsk/d6 phys-newyork-1# cldevicegroup delete dsk/d5 dsk/d6 Create the raw-disk device group on the partner cluster. phys-newyork-1# cldevicegroup create -n phys-newyork-1,phys-newyork-2 \ -t rawdisk -d d5,d6 rawdg Add the raw-disk device group to the protection group rawpg. phys-paris-1# geopg create -d truecopy -p Nodelist=phys-paris-1,phys-paris-2 \ -o Primary -p cluster_dgs=rawdg -s paris-newyork-ps rawpg |
When configuring the partner cluster, create a raw-disk device group of the same name as the one you created here. See How to Replicate the Configuration Information From the Primary Cluster When Using Raw-Disk Device Groups for the instructions about this task.
Once you have configured the device group on both clusters, you can use the device group name wherever one is required in Sun Cluster Geographic Edition commands such as geopg.
Hitachi TrueCopy supports VERITAS Volume Manager volumes and raw-disk device groups. If you are using VERITAS Volume Manager, you must configure VERITAS Volume Manager volumes on disks d1 and d2.
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
Create VERITAS Volume Manager disk groups on shared disks in cluster-paris.
For example, the d1 and d2 disks are configured as part of a VERITAS Volume Manager disk group, which is called oradg1, by using commands, such as vxdiskadm and vxdg.
After configuration is complete, verify that the disk group was created by using the vxdg list command.
This command should list oradg1 as a disk group.
Create the VERITAS Volume Manager volume.
For example, a volume that is called vol1 is created in the oradg1 disk group. The appropriate VERITAS Volume Manager commands, such as vxassist, are used to configure the volume.
To complete your configuration , proceed to How to Configure the Sun Cluster Device Group That Is Controlled by Hitachi TrueCopy Software to create the Sun Cluster device group for this disk group.
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
Register the VERITAS Volume Manager disk group that you configured in the previous procedure.
Use the Sun Cluster command cldevicegroup.
For more information about this command, refer to the cldevicegroup(1CL) man page.
Create a mount directory on each node of the cluster.
phys-newyork-1# mkdir -p /mounts/sample phys-newyork-2# mkdir -p /mounts/sample |
Synchronize the VERITAS Volume Manager configuration with Sun Cluster software, again by using the cldevicegroup command.
After configuration is complete, verify the disk group registration.
# cldevicegroup status |
The VERITAS Volume Manager disk group, oradg1, should be displayed in the output.
For more information about the cldevicegroup command, see the cldevicegroup(1CL) man page.
Before you configure the file system on cluster-paris, ensure that the Sun Cluster entities you require, such as application resource groups, device groups, and mount points, have already been configured.
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
Create the required file system on the vol1 volume at the command line.
Add an entry to the /etc/vfstab file that contains information such as the mount location.
Whether the file system is to be mounted locally or globally depends on various factors, such as your performance requirements, or the type of application resource group you are using.
You must set the mount at boot field in this file to no. This value prevents the file system from mounting on the secondary cluster at cluster startup. Instead, the Sun Cluster software and the Sun Cluster Geographic Edition framework handle mounting the file system by using the HAStoragePlus resource when the application is brought online on the primary cluster. Data must not be mounted on the secondary cluster or data on the primary will not be replicated to the secondary cluster. Otherwise, the data will not be replicated from the primary cluster to the secondary cluster.
Add the HAStoragePlus resource to the application resource group, apprg1.
Adding the resource to the application resource group ensures that the necessary file systems are remounted before the application is brought online.
For more information about the HAStoragePlus resource type, refer to the Sun Cluster Data Services Planning and Administration Guide for Solaris OS.
This example assumes that the apprg1 resource group already exists.
Create a UNIX file system (UFS).
phys-paris-1# newfs dev/vx/dsk/oradg1/vol1 |
The following entry is created in the /etc/vfstab file:
# /dev/vs/dsk/oradg1/vol1 /dev/vx/rdsk/oradg1/vol1 /mounts/sample \ ufs 2 no logging |
Add the HAStoragePlus resource type.
phys-paris-1# clresource create -g apprg1 -t SUNW.HAStoragePlus \ -p FilesystemMountPoints=/mounts/sample -p Affinityon=TRUE \ -p GlobalDevicePaths=oradg1 rs-has |
This section describes the steps you must complete on the secondary cluster before you can configure Hitachi TrueCopy data replication in Sun Cluster Geographic Edition software.
You must configure the Hitachi TrueCopy device group on shared disks in the secondary cluster as you did on the primary cluster by editing the /etc/horcm.conf file on each node of the cluster that has access to the Hitachi array. Disks d1 and d2 are configured to belong to a Hitachi TrueCopy device group that is called devgroup1. The application, apprg1, can run on all nodes that have Hitachi TrueCopy device groups configured.
For more information about how to configure the /etc/horcm.conf file, see the Sun StorEdge SE 9900 V Series Command and Control Interface User and Reference Guide.
The following table describes the configuration information from the example that is found in the /etc/horcm.conf file.
Table 1–3 Example Section of the /etc/horcm.conf File on the Secondary Cluster
dev_group |
dev_name |
port number |
TargetID |
LU number |
MU number |
devgroup1 |
pair1 |
CL1–C |
0 |
20 | |
devgroup1 |
pair2 |
CL1–C |
0 |
21 |
The configuration information in the table indicates that the Hitachi TrueCopy device group, devgroup1, contains two pairs. The first pair, pair1, is from the d1 disk, which is identified by the tuple <CL1–C , 0, 20>. The second pair, pair2, is from the d2 disk and is identified by the tuple <CL1–C, 0, 21>.
After you have configured the /etc/horcm.conf file on the secondary cluster, you can see the status of the pairs by using the pairdisplay command as follows:
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) 54321 1.. SMPL ---- ------,----- ---- - devgroup1 pair1(R) (CL1-C , 0, 20)12345 609..SMPL ---- ------,----- ---- - devgroup1 pair2(L) (CL1-A , 0, 2) 54321 2.. SMPL ---- ------,----- ---- - devgroup1 pair2(R) (CL1-C , 0, 21)12345 610..SMPL ---- ------,----- ---- - |
Next, you need to configure any volume manager, the Sun Cluster device groups, and the highly available cluster file system. This process is slightly different depending upon whether you are using VERITAS Volume Manager or raw-disk device groups. The following procedures provide instructions:
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
Start replication for the devgroup1 device group.
phys-paris-1# paircreate -g devgroup1 -vl -f async 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) 54321 1..P-VOL COPY ASYNC ,12345 609 - devgroup1 pair1(R) (CL1-C , 0, 20)12345 609..S-VOL COPY ASYNC ,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 54321 2..P-VOL COPY ASYNC ,12345 610 - devgroup1 pair2(R) (CL1-C , 0, 21)12345 610..S-VOL COPY ASYNC ,----- 2 - |
Wait for the state of the pair to become PAIR on the secondary cluster.
phys-newyork-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-C , 0, 20)12345 609..S-VOL PAIR ASYNC,-----, 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PAIR ASYNC,12345, 609 - devgroup1 pair2(L) (CL1-C , 0, 21)12345 610..S-VOL PAIR ASYNC,-----, 2 - devgroup1 pair2(R) (CL1-A , 0, 2)54321 2..P-VOL PAIR ASYNC,12345, 610 - |
Split the pair by using the pairsplit command and confirm that the secondary volumes on cluster-newyork are writable by using the -rw option.
phys-newyork-1# pairsplit -g devgroup1 -rw phys-newyork-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-C , 0, 20)12345 609..S-VOL SSUS ASYNC, ----- 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PSUS ASYNC,12345 609 W devgroup1 pair2(L) (CL1-C , 0,21) 12345 610..S-VOL SSUS ASYNC,----- 2 - devgroup1 pair2(R) (CL1-A , 0, 2) 54321 2..P-VOL PSUS ASYNC,12345 610 W |
Import the VERITAS Volume Manager disk group, oradg1.
phys-newyork-1# vxdg -C import oradg1 |
Verify that the VERITAS Volume Manager disk group was successfully imported.
phys-newyork-1# vxdg list |
Enable the VERITAS Volume Manager volume.
phys-newyork-1# /usr/sbin/vxrecover -g oradg1 -s -b |
Verify that the VERITAS Volume Manager volumes are recognized and enabled.
phys-newyork-1# vxprint |
Register the VERITAS Volume Manager disk group, oradg1, in Sun Cluster.
phys-newyork-1# cldevicegroup create -t vxvm -n phys-newyork-1,phys-newyork-2 oradg1 |
Synchronize the volume manager information with the Sun Cluster device group and verify the output.
phys-newyork-1# cldevicegroup sync oradg1 phys-newyork-1# cldevicegroup status |
Add an entry to the /etc/vfstab file on phys-newyork-1.
phys-newyork-1# /dev/vx/dsk/oradg1/vol1 /dev/vx/rdsk/oradg1/vol1 \ /mounts/sample ufs 2 no logging |
Create a mount directory on phys-newyork-1.
phys-newyork-1# mkdir -p /mounts/sample |
Create an application resource group, apprg1, by using the scrgadm command.
phys-newyork-1# clresourcegroup create apprg1 |
Create the HAStoragePlus resource in apprg1.
phys-newyork-1# clresource create -g apprg1 -t SUNW.HAStoragePlus \ -p FilesystemMountPoints=/mounts/sample -p Affinityon=TRUE \ -p GlobalDevicePaths=oradg1 rs-hasp |
This HAStoragePlus resource is required for Sun Cluster Geographic Edition systems, because the software relies on the resource to bring the device groups and file systems online when the protection group starts on the primary cluster.
If necessary, confirm that the application resource group is correctly configured by bringing it online and taking it offline again.
phys-newyork-1# clresourcegroup switch -emM -n phys-newyork-1 apprg1 phs-newyork-1# clresourcegroup offline apprg1 |
Unmount the file system.
phys-newyork-1# umount /mounts/sample |
Take the Sun Cluster device group offline.
phys-newyork-1# cldevicegroup offline oradg1 |
Verify that the VERITAS Volume Manager disk group was deported.
phys-newyork-1# vxdg list |
Reestablish the Hitachi TrueCopy pair.
phys-newyork-1# pairresync -g devgroup1 phys-newyork-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-C , 0, 20)12345 609..S-VOL PAIR ASYNC,----- 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PAIR ASYNC,12345 609 W devgroup1 pair2(L) (CL1-C , 0,21) 12345 610..S-VOL PAIR ASYNC,----- 2 - devgroup1 pair2(R) (CL1-A , 0, 2) 54321 2..P-VOL PAIR ASYNC,12345 610 W |
Initial configuration on the secondary cluster is now complete.
This task copies the volume manager configuration from the primary cluster, cluster-paris, to LUNs of the secondary cluster, cluster-newyork, by using the VERITAS Volume Manager commands vxdiskadm and vxassist command.
The device group, devgroup1, must be in the SMPL state throughout this procedure.
Confirm that the pair is in the SMPL state.
phys-newyork-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-C , 0, 20)12345 609..SMPL ---- ------,----- ---- - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..SMPL ---- ------,----- ---- - devgroup1 pair2(L) (CL1-C , 0, 21)12345 610..SMPL ---- ------,----- ---- - devgroup1 pair2(R) (CL1-A, 0, 2) 54321 2..SMPL ---- ------,----- ---- - |
Create VERITAS Volume Manager disk groups on shared disks in cluster-paris.
For example, the d1 and d2 disks are configured as part of a VERITAS Volume Manager disk group, which is called oradg1, by using commands, such as vxdiskadm and vxdg.
After configuration is complete, verify that the disk group was created by using the vxdg list command.
This command should list oradg1 as a disk group.
Create the VERITAS Volume Manager volume.
For example, a volume that is called vol1 is created in the oradg1 disk group. The appropriate VERITAS Volume Manager commands, such as vxassist, are used to configure the volume.
Import the VERITAS Volume Manager disk group.
phys-newyork-1# vxdg -C import oradg1 |
Verify that the VERITAS Volume Manager disk group was successfully imported.
phys-newyork-1# vxdg list |
Enable the VERITAS Volume Manager volume.
phys-newyork-1# /usr/sbin/vxrecover -g oradg1 -s -b |
Verify that the VERITAS Volume Manager volumes are recognized and enabled.
phys-newyork-1# vxprint |
Register the VERITAS Volume Manager disk group, oradg1, in Sun Cluster.
phys-newyork-1# cldevicegroup create -t vxvm -n phys-newyork-1,phys-newyork-2 oradg1 |
Synchronize the VERITAS Volume Manager information with the Sun Cluster device group and verify the output.
phys-newyork-1# cldevicegroup sync oradg1 phys-newyork-1# cldevicegroup status |
Create a UNIX file system.
phys-newyork-1# newfs dev/vx/dsk/oradg1/vol1 |
Add an entry to the /etc/vfstab file on phys-newyork-1.
/dev/vx/dsk/oradg1/vol1 /dev/vx/rdsk/oradg1/vol1 /mounts/sample ufs 2 no logging |
Create a mount directory on phys-newyork-1.
phys-newyork-1# mkdir -p /mounts/sample |
Create an application resource group, apprg1, by using the clresourcegroup command.
phys-newyork-1# clresourcegroup create apprg1 |
Create the HAStoragePlus resource in apprg1.
phys-newyork-1# clresource create -g apprg1 -t SUNW.HAStoragePlus \ -p FilesystemMountPoints=/mounts/sample -p Affinityon=TRUE \ -p GlobalDevicePaths=oradg1 rs-hasp |
This HAStoragePlus resource is required for Sun Cluster Geographic Edition systems, because the software relies on the resource to bring the device groups and file systems online when the protection group starts on the primary cluster.
If necessary, confirm that the application resource group is correctly configured by bringing it online and taking it offline again.
phys-newyork-1# clresourcegroup switch -emM -n phys-newyork-1 apprg1 phs-newyork-1# clresourcegroup offline apprg1 |
Unmount the file system.
phys-newyork-1# umount /mounts/sample |
Take the Sun Cluster device group offline.
phys-newyork-1# cldevicegroup offline oradg1 |
Verify that the VERITAS Volume Manager disk group was deported.
phys-newyork-1# vxdg list |
Verify that the pair is still in the SMPL state.
phys-newyork-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-C , 0, 20)12345 609..SMPL ---- ------,----- ---- - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..SMPL ---- ------,----- ---- - devgroup1 pair2(L) (CL1-C , 0, 21)12345 610..SMPL ---- ------,----- ---- - devgroup1 pair2(R) (CL1-A, 0, 2) 54321 2..SMPL ---- ------,----- ---- - |
If you are using storage-based replication, do not configure a replicated volume as a quorum device. The Sun Cluster Geographic Edition software does not support Hitachi TrueCopy S-VOL and Command Device as a Sun Cluster quorum device. See Using Storage-Based Data Replication in Sun Cluster System Administration Guide for Solaris OS for more information.
Start replication for the devgroup1 device group.
phys-paris-1# paircreate -g devgroup1 -vl -f async 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) 54321 1..P-VOL COPY ASYNC ,12345 609 - devgroup1 pair1(R) (CL1-C , 0, 20)12345 609..S-VOL COPY ASYNC ,----- 1 - devgroup1 pair2(L) (CL1-A , 0, 2) 54321 2..P-VOL COPY ASYNC ,12345 610 - devgroup1 pair2(R) (CL1-C , 0, 21)12345 610..S-VOL COPY ASYNC ,----- 2 - |
Wait for the state of the pair to become PAIR on the secondary cluster.
phys-newyork-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-C , 0, 20)12345 609..S-VOL PAIR ASYNC,-----, 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PAIR ASYNC,12345, 609 - devgroup1 pair2(L) (CL1-C , 0, 21)12345 610..S-VOL PAIR ASYNC,-----, 2 - devgroup1 pair2(R) (CL1-A , 0, 2)54321 2..P-VOL PAIR ASYNC,12345, 610 - |
Split the pair by using the pairsplit command and confirm that the secondary volumes on cluster-newyork are writable by using the -rw option.
phys-newyork-1# pairsplit -g devgroup1 -rw phys-newyork-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-C , 0, 20)12345 609..S-VOL SSUS ASYNC, ----- 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PSUS ASYNC,12345 609 W devgroup1 pair2(L) (CL1-C , 0,21) 12345 610..S-VOL SSUS ASYNC,----- 2 - devgroup1 pair2(R) (CL1-A , 0, 2) 54321 2..P-VOL PSUS ASYNC,12345 610 W |
Create a raw-disk device group on the partner cluster.
Use the same device group name that you used on the primary cluster.
You can use the same DIDs on each cluster. In the following command, the newyork cluster is the partner of the paris cluster.
phys-newyork-1# cldevicegroup disable dsk/d5 dsk/d6 phys-newyork-1# cldevicegroup offline dsk/d5 dsk/d6 phys-newyork-1# cldevicegroup delete dsk/d5 dsk/d6 phys-newyork-1# cldevicegroup create -n phys-newyork-1,phys-newyork-2 \ -t rawdisk -d d5,d6 rawdg phys-newyork-1# /usr/cluster/lib/dcs/dgconv -d d5 rawdg phys-newyork-1# /usr/cluster/lib/dcs/dgconv -d d6 rawdg |
Synchronize the volume manager information with the Sun Cluster device group and verify the output.
phys-newyork-1# cldevicegroup sync rawdg1 phys-newyork-1# cldevicegroup status |
Add an entry to the /etc/vfstab file on each node of the newyork cluster.
/dev/global/dsk/d5s2 /dev/global/rdsk/d5s2 /mounts/sample ufs 2 no logging |
Create a mount directory on each node of the newyork cluster.
phys-newyork-1# mkdir -p /mounts/sample phys-newyork-2# mkdir -p /mounts/sample |
Create an application resource group, apprg1, by using the clresourcegroup command.
phys-newyork-1# clresourcegroup create apprg1 |
Create the HAStoragePlus resource in apprg1.
phys-newyork-1# clresource create -g apprg1 -t SUNW.HAStoragePlus \ -p FilesystemMountPoints=/mounts/sample -p Affinityon=TRUE \ -p GlobalDevicePaths=rawdg1 rs-hasp |
This HAStoragePlus resource is required for Sun Cluster Geographic Edition systems, because the software relies on the resource to bring the device groups and file systems online when the protection group starts on the primary cluster.
If necessary, confirm that the application resource group is correctly configured by bringing it online and taking it offline again.
phys-newyork-1# clresourcegroup switch -emM -n phys-newyork-1 apprg1 phs-newyork-1# clresourcegroup offline apprg1 |
Unmount the file system.
phys-newyork-1# umount /mounts/sample |
Take the Sun Cluster device group offline.
phys-newyork-1# cldevicegroup offline rawdg1 |
Reestablish the Hitachi TrueCopy pair.
phys-newyork-1# pairresync -g devgroup1 phys-newyork-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-C , 0, 20)12345 609..S-VOL PAIR ASYNC,----- 1 - devgroup1 pair1(R) (CL1-A , 0, 1) 54321 1..P-VOL PAIR ASYNC,12345 609 W devgroup1 pair2(L) (CL1-C , 0,21) 12345 610..S-VOL PAIR ASYNC,----- 2 - devgroup1 pair2(R) (CL1-A , 0, 2) 54321 2..P-VOL PAIR ASYNC,12345 610 W |
Initial configuration on the secondary cluster is now complete.