In a GCO environment where HDS TrueCopy technology is used to replicate between clusters, the HTC agent can be used to control this replication.
In a CVM environment the importing of replicated diskgroups can fail if the HTC resource is incorrectly configured.
The importing of CVM disk groups is done by the CVM Cluster resource. CVM uses the following criteria when importing disk groups:
- Shared flag is set
- Hostid flag is populated with the clusterID as set in the main.cf
As the hostid flag (referred to as the clusterID flag when the disk group is marked as shared) is held in the private region of a disk group, it will be replicated to the destination cluster. Therefore, by default CVM on the destination cluster will not import this disk group.
In order to allow the import of CVM groups, HTC takes control of import/deport of cvm groups. In order to do this the following needs to be configured:
- The Supported Actions must be set on the CVMVolDg agent (as documented on the HTCAgent Guide)
- The HTC resource must be the immediate child of the CVMVolDG resource
When the above is set, it is the HTC resource and not the cvm_clus resource that will import and deport the shared disk group. The disk group that the HTC resource will control is the one defined in it's parent CVMVolDg resource.
A side-effect of the HTC resource taking control in this way is that when the diskgroup is deported on all nodes, it will not show with the 'shared' flag.