Creating replication CR object for custom copy group

Replication Plug-in for Containers Installation and User Guide

Version
3.18.x
Audience
anonymous
Part Number
MK-92ADPTR155-10
ft:lastEdition
2026-07-07
  1. Create a replication CR manifest file using user-defined custom copy group and parent replication group name in the primary site. Enter:
    apiVersion: hspc.hitachi.com/v1
    kind: Replication
    metadata:
      name: <custom replication name>
      namespace: <namespace>
    spec:
      persistentVolumeClaimName: <PVC name>        #1
      storageClassName: <Storage class name>       #2
      copyGroupName: <copy group name>             #3
      copyPairName: <copy pair name>               #4
      replicationType: <UR or TC >                                  #5
      fenceLevel:<NEVER/DATA/STATUS>                                #6
      consistencyGroupId: <consistency group ID>   #7
      pvolJournalId: <primary volume journal ID>   #8
      svolJournalId: <secondary volume journal ID> #9
      parentName: <Replication Group CR name>      #10
    Legend:
    • #1: Specify a target PVC protected by TrueCopy or Universal Replicator.
    • #2: Specify a storage class name from which the target PVC is created.
    • #3 (Optional): Specify a unique, case-sensitive copyGroupName between 1–29 characters, starting with the spc- prefix. Omitting the prefix will cause an error.
    • #4: Specify a unique, case-sensitive copyPairName between 1–31 characters, starting with the spc- prefix. Omitting the prefix will cause an error.

      You cannot specify a copyPairName if you have not specified the copyGroupName. When the copyGroupName is specified, it is optional to specify the copyPairName.

      Note: When multiple replication CRs are created with the same copy group name but different copy pair names, all replication copy pairs are grouped under the same copy group.
    • #5: Specify the replication type, TC for TrueCopy pair or UR for Universal Replicator pair.
    • #6: Specify either NEVER, DATA, or STATUS. It is mandatory to specify the fenceLevel for the TrueCopy replication type. However, it is optional for Universal Replicator replication type.
    • #7 (Optional): Specify the consistency Group ID. The consistency group ID must be a numeric value between 0 and 255.

      For VSP E590 and VSP E790 storage systems, the numeric value must be between 0 and 127.

      You cannot specify consistencyGroupId if you have not specified the copyGroupName. When the copyGroupName is specified, it is optional to specify the consistencyGroupId. You cannot have multiple consistency group IDs for the same copyGroupName.

      Note: Assign a unique consistencyGroupId for each copy group name.
    • #8: Specify the pvolJournalId when you specify the copyGroupName. This parameter is optional for TrueCopy replication type, and is mandatory for Universal Replicator replication type.
    • #9: Specify the svolJournalId when you specify the copyGroupName. This parameter is optional for TrueCopy replication type, and is mandatory for Universal Replicator replication type.
      Note: Assign unique Pvol/Svol Journal IDs for each copy group name.
    • #10 (Optional): Specify name of the replication group to manage the replication operations for copy groups.
  2. Create a replication CR object for the custom copy group. Enter:
    KUBECONFIG=${KUBECONFIG_P} kubectl create -f hspc_v1_replication.yaml