test

Sun Cluster Geographic Edition Data Replication Guide for Hitachi TrueCopy

Configuring the Other Entities on the Secondary Cluster

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:

ProcedureHow to Replicate the VERITAS Volume Manager Configuration Information From the Primary Cluster

Before You Begin

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.

  1. 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   -

  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   -

  3. 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

  4. Import the VERITAS Volume Manager disk group, oradg1.


    phys-newyork-1# vxdg -C import oradg1

  5. Verify that the VERITAS Volume Manager disk group was successfully imported.


    phys-newyork-1# vxdg list

  6. Enable the VERITAS Volume Manager volume.


    phys-newyork-1# /usr/sbin/vxrecover -g oradg1 -s -b

  7. Verify that the VERITAS Volume Manager volumes are recognized and enabled.


    phys-newyork-1# vxprint

  8. 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

  9. 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

  10. 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

  11. Create a mount directory on phys-newyork-1.


    phys-newyork-1# mkdir -p /mounts/sample

  12. Create an application resource group, apprg1, by using the scrgadm command.


    phys-newyork-1# clresourcegroup create apprg1

  13. 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.

  14. 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

  15. Unmount the file system.


    phys-newyork-1# umount /mounts/sample

  16. Take the Sun Cluster device group offline.


    phys-newyork-1# cldevicegroup offline oradg1

  17. Verify that the VERITAS Volume Manager disk group was deported.


    phys-newyork-1# vxdg list

  18. 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.

ProcedureHow to Create a Copy of the Volume Manager Configuration

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.

Note –

The device group, devgroup1, must be in the SMPL state throughout this procedure.

  1. 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 ---- ------,----- ----   -

  2. 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.

  3. 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.

  4. 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.

  5. Import the VERITAS Volume Manager disk group.


    phys-newyork-1# vxdg -C import oradg1

  6. Verify that the VERITAS Volume Manager disk group was successfully imported.


    phys-newyork-1# vxdg list

  7. Enable the VERITAS Volume Manager volume.


    phys-newyork-1# /usr/sbin/vxrecover -g oradg1 -s -b

  8. Verify that the VERITAS Volume Manager volumes are recognized and enabled.


    phys-newyork-1# vxprint

  9. 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

  10. 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

  11. Create a UNIX file system.


    phys-newyork-1# newfs dev/vx/dsk/oradg1/vol1

  12. 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

  13. Create a mount directory on phys-newyork-1.


    phys-newyork-1# mkdir -p /mounts/sample

  14. Create an application resource group, apprg1, by using the clresourcegroup command.


    phys-newyork-1# clresourcegroup create apprg1

  15. 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.

  16. 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

  17. Unmount the file system.


    phys-newyork-1# umount /mounts/sample

  18. Take the Sun Cluster device group offline.


    phys-newyork-1# cldevicegroup offline oradg1

  19. Verify that the VERITAS Volume Manager disk group was deported.


    phys-newyork-1# vxdg list

  20. 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 ---- ------,-----  ----  -

ProcedureHow to Replicate the Configuration Information From the Primary Cluster When Using Raw-Disk Device Groups

Before You Begin

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.

  1. 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   -

  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   -

  3. 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

  4. 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

  5. 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

  6. 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

  7. 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

  8. Create an application resource group, apprg1, by using the clresourcegroup command.


    phys-newyork-1# clresourcegroup create apprg1

  9. 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.

  10. 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

  11. Unmount the file system.


    phys-newyork-1# umount /mounts/sample

  12. Take the Sun Cluster device group offline.


    phys-newyork-1# cldevicegroup offline rawdg1

  13. 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.