Container Service for Kubernetes:Use a registered cluster to back up and restore applications across clusters that belong to different accounts

Cloud Backup solution

Use this solution if your application uses disk volumes and you want a simpler setup, or if your application does not use disk volumes at all.

1. Disable the ECS snapshot feature.

   1. Edit the csdr-config ConfigMap:

      kubectl -ncsdr edit cm csdr-config

   2. Set enable_ecs_snapshot to false. Save and exit.

   3. Restart the controller for the change to take effect:

      kubectl -ncsdr delete pod -l control-plane=csdr-controller

2. If the restore account does not have a backup vault, create one and associate it with the OSS bucket named cnfs-oss-* in the restore account. See Create a backup vault.

3. Create a backup task for the sts-oss application. See Create a backup plan or back up instantly.

   • Set Backup Volume to Disable — the sts-oss application maps to the original OSS bucket and does not need volume data backed up.

   • Select the oss namespace. If the namespace contains other applications, add labels to select only sts-oss.

   • On the Backup Records tab of the Application Backup page, wait for the backup status to change from InProgress to Completed. Click the backup record name and confirm that the StatefulSet, pod, PVC, PV, and Secret (containing the AccessKey pair) are all backed up.

4. Create a backup task for the sts-nas and sts-disk applications. See Create a backup plan or back up instantly.

   • Set Backup Volume to Mounted Volumes.

   • Because enable_ecs_snapshot is false, Cloud Backup handles disk volume data. To monitor progress, log on to the Cloud Backup console, click Container Backup in the left-side navigation pane, and check the Backup Jobs tab.

ECS snapshot solution

Use this solution if your application uses disk volumes and requires data consistency.

1. Enable the ECS snapshot feature.

   1. Edit the csdr-config ConfigMap:

      kubectl -ncsdr edit cm csdr-config

   2. Set enable_ecs_snapshot to true. Save and exit.

   3. Restart the controller:

      kubectl -ncsdr delete pod -l control-plane=csdr-controller

2. If the restore account does not have a backup vault, create one and associate it with the OSS bucket named cnfs-oss-* in the restore account. See Create a backup vault.

3. Create a backup task for the sts-oss application. See Create a backup plan or back up instantly.

   • Set Backup Volume to Disable.

   • Select the oss namespace. If the namespace contains other applications, add labels to select only sts-oss.

   • On the Backup Records tab, wait for the status to change to Completed and verify that all related resources are backed up.

4. Create a backup task named backup-nas-disk for the sts-nas and sts-disk applications. See Create a backup plan or back up instantly.

   • Set Backup Volume to Mounted Volumes.

   • Disk volume data is backed up using ECS snapshots by default. To view the snapshots, log on to the ECS console, click Snapshots in the left-side navigation pane, and check the Disk Snapshots tab.

   • NAS volume data is backed up using Cloud Backup. To monitor progress, log on to the Cloud Backup console, click Container Backup, and check the Backup Jobs tab.

Cloud Backup solution

Use the restore cluster's account to perform these steps.

1. Restore the sts-oss application. See Restore applications and volumes.

   1. On the Application Backup page, click Back up Now, select and initialize the backup vault, and wait for the backup file to sync to the restore cluster.

   2. Select the backup-oss backup file and create a restore task.

   3. Verify that sts-oss is running correctly. Run kubectl exec to log in to the container and confirm data consistency.

2. Restore the sts-nas and sts-disk applications using StorageClass conversion. See Restore applications and volumes.

   1. On the Application Backup page, click Back up Now and select backup-nas-disk. For StorageClass conversion, select alicloud-disk for pvc-disk and alibabacloud-cnfs-nas for pvc-nas. By default, alicloud-disk refers to the alicloud-disk-topology-alltype StorageClass provided by the CSI plug-in. You can also create a custom StorageClass in the cluster.

   2. Verify that the applications and data are running correctly. In the ECS console, confirm that new disks have been created in the restore account and mounted to the corresponding nodes.

ECS snapshot solution

1. Use the restore cluster's account to restore the sts-oss application. See Restore applications and volumes.

   1. On the Application Backup page, click Back up Now, select and initialize the backup vault, and wait for the backup file to sync.

   2. Select the backup-oss backup file and create a restore task.

   3. Verify that sts-oss is running correctly using kubectl exec.

2. Use the backup cluster's account to share the disk snapshots with the restore account. Log on to the ECS console and share each snapshot. See Share a snapshot. Snapshots created by the backup center are named with the prefix snapshot-. Identify them by matching the creation time to the corresponding backup record.

3. Before accepting the shared snapshots, record the PVC-to-snapshot mappings in the backup account. This information is required for the manual restoration steps.

   1. In the ECS console, record the mapping between each snapshot ID and its corresponding disk ID.

   2. In the backup cluster, run the following command to query the PVC and disk ID for each PV that uses a disk volume:

      kubectl get pv <PV-Name> -o jsonpath='{"PVC: "}{.spec.claimRef.name}{"\nNamespace: "}{.spec.claimRef.namespace}{"\nVolumeHandle: "}{.spec.csi.volumeHandle}'

      Expected output:

      PVC: <disk-pvc-name>
      Namespace: <disk-pvc-namespace>
      VolumeHandle: d-2ze323ra0h2v5lxxxxx

      Use these mappings to link each PVC to its corresponding snapshot ID.

4. Use the restore cluster's account to log on to the Resource Management console and accept the shared snapshots. See Share a snapshot. The snapshot names remain unchanged in the restore account, but the IDs change. Use the snapshot names and the mappings from step 3 to map each PVC to the new snapshot ID.

5. Manually restore the disk volumes in the restore cluster.

   1. Use static provisioning to create a VolumeSnapshotContent and a VolumeSnapshot in the restore cluster. See Create a snapshot of a disk volume. Create the VolumeSnapshot in the same namespace as the target PVC. Set the snapshotHandle parameter in the VolumeSnapshotContent to the new snapshot ID.

   2. Create a PVC with the same name as the original, referencing the VolumeSnapshot. See step 6 in Create a snapshot of a disk volume. The new PVC has the same configuration as the original, with an additional dataSource parameter pointing to the VolumeSnapshot.

6. Restore the sts-nas and sts-disk applications. See Restore applications and volumes. The backup center skips the sts-disk volumes automatically because they are already restored in step 5. The restore task mounts the PVC with the same name to the application.

   1. On the Application Backup page, click Back up Now and select backup-nas-disk. If you do not select StorageClass conversion, the volume is restored using the original StorageClass. Make sure that StorageClass exists in the restore cluster.

   2. Verify the result. In the ECS console, confirm that new disks have been created in the restore account and mounted to the correct nodes.