Note:
  • You must perform the sync backup before initiating the restore operation.
  • If the backup was taken on VMware Telco Cloud Service Assurance 2.3.1 or earlier, you must perform the sync backup procedure given in the Data Migration From Older Version to New Version Using CLI section.
  • If the backup was taken on VMware Telco Cloud Service Assurance 2.4.0, you must perform the following sync backup procedure.
  1. After the backup is successful, configure MinIO on the target cluster and use the same settings as the source cluster and perform a sync operation.
    apiVersion: tcx.vmware.com/v1
kind: SyncBackup
metadata:
  name: sync-backup-tps
  namespace: tps-system
spec:
  overrideExisting: false       # set this if the backup with same name already exists in the cluster  # setting this to true will not delete the data
  filter:
    componentList:
      - postgres
    backupList:
      - group-backup
  pauseIntegrityCheck: true
  overrideNamespace:
    targetNamespace: tps-system

  #Uncomment the below two lines ONLY if the backup was taken on either 2.3.1 / 2.4.0. Set "name" to tcsa2.3.1 if the backup was taken on 2.3.1, or tcsa2.4.0 if taken on 2.4.0
  #cluster:
  #  name: tcsa2.4.0

  storage:
    minio:
      bucket: vmware-tcsa-backup
      endpoint: minio.tcsa-system.svc.cluster.local:9000
      secretRef:
        name: minio-secrets
        namespace: tcsa-system
        accessKey:
          key: root-user
        secretKey:
          key: root-password

---
apiVersion: tcx.vmware.com/v1
kind: SyncBackup
metadata:
  name: sync-backup-tcsa
  namespace: tcsa-system
spec:
  overrideExisting: false      # set this if the backup with same name already exists in the cluster  # setting this to true will not delete the data
  filter:
    componentList:
      - elasticsearch
      - collectors
      - zookeeper
      - kubernetesResources
    backupList:
      - group-backup
  pauseIntegrityCheck: true
  overrideNamespace:
    targetNamespace: tcsa-system
  cluster:
    name: tcsa2.4.0
  storage:
    minio:
      bucket: vmware-tcsa-backup
      endpoint: minio.tcsa-system.svc.cluster.local:9000
      secretRef:
        name: minio-secrets
        namespace: tcsa-system
        accessKey:
          key: root-user
        secretKey:
          key: root-password
  2. In the example yaml file, default bucket vmware-tcsa-backup is used. To override the bucket name, you must update the AWS S3/NFS File Server bucket in the yaml.
  3. Run the following command to sync the backup in the target cluster.
    kubectl apply -f <configuration yaml file>

After the sync operation is complete, you can see the status as SUCCESSFUL.

The backups stored in AWS S3 or NFS File Server are accessible in the new cluster. 
[root@wdc-10-214-150-193 backup-and-restore]#
kubectl get syncbackups -A
NAMESPACE   NAME               STATUS       CURRENT STATE   READY   AGE     MESSAGE
default     sync-backup-tcsa   SUCCESSFUL   syncBackup      True    4h51m   synced: 1, skipped: 0, failed: 0
default     sync-backup-tps    SUCCESSFUL   syncBackup      True    4h51m   synced: 1, skipped: 0, failed: 0

In case of any failure, the MESSAGE field is populated with the error message.