Sun Cluster System Administration Guide for Solaris OS

ProcedureHow to Configure DID Devices for Replication

Before You Begin

After you have configured a device group for your replicated device, you must configure the device identifier (DID) driver that the replicated device uses.

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands.

  1. Become superuser or assume a role that provides solaris.cluster.modify RBAC authorization on any node of the cluster.

  2. Confirm that the horcm daemon is running on all nodes.

    # /usr/bin/
  3. Determine which node contains the secondary replica by running the pairdisplay command.

    # pairdisplay -g group-name
    Group PairVol(L/R) (Port#,TID,LU),Seq#,LDEV#,P/S,Status,Fence,Seq#,P-LDEV# M 
    group-name pair1(L) (CL1-C , 0, 9) 54321   58..P-VOL PAIR DATA ,12345 29   -
    group-name pair1(R) (CL1-A , 0, 29)12345   29..S-VOL PAIR DATA ,----- 58   -

    The node with the local (L) device in the S-VOL state contains the secondary replica.

  4. On the node with secondary replica (as determined by the previous step), configure the DID devices for use with storage-based replication.

    This command combines the two separate DID instances for the device replica pairs into a single, logical DID instance. The single instance enables the device to be used by volume management software from both nodes.

    Caution – Caution –

    If multiple nodes are connected to the secondary replica, run this command on only one of these nodes.

    # cldevice replicate -D primary-replica-nodename -S secondary replica-nodename

    Specifies the name of the remote node that contains the primary replica.


    Specifies a source node other than the current node.

    secondary replica-nodename

    Specifies the name of the remote node that contains the secondary replica.

    Note –

    By default, the current node is the source node. Use the -S option to specify a different source node.

  5. Verify that the DID instances have been combined.

    # cldevice list -v device
  6. Verify that the TrueCopy replication is set.

    # cldevice show device |
  7. If the DID remapping did not successfully combine all replicated devices, combine the individual replicated devices manually.

    Caution – Caution –

    Exercise extreme care when combining DID instances manually. Improper device remapping can cause data corruption.

    1. On the node that contains the secondary replica, run the cldevice combine command. This node must be local.

      # cldevice combine -d destination-instance source-instance
      -d destination-instance

      The remote DID instance, which corresponds to the primary replica.


      The local DID instance, which corresponds to the secondary replica.

    2. Verify that the DID remapping occurred successfully.

      # cldevice list desination-instance source-instance

    One of the DID instances should not be listed.

  8. On all nodes, verify that the DID devices for all combined DID instances are accessible.

    # cldevice list -v
Next Steps

To complete the configuration of your replicated device group, perform the steps in the following procedures.