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 when your application uses disk volumes and you want Cloud Backup to handle all volume types, or when 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 component 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-* under the restore account. For more information, see Create a backup vault.

3. Create a backup task for sts-oss. For more information, see Create a backup plan or back up instantly.

   • sts-oss uses the original OSS bucket directly — no volume data backup is needed. When configuring the backup task, set Backup Volume to Disable.

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

   • On the Backup Records tab of the Application Backup page, confirm the task status changes from InProgress to Completed. Click the backup record name and verify that sts-oss resources (StatefulSet, pod, PVC, PV, and the Secret storing the AccessKey pair) are all backed up.

4. Create a backup task for sts-nas and sts-disk. For more information, see Create a backup plan or back up instantly.

   • Set Backup Volume to Mounted Volumes.

   • Because enable_ecs_snapshot is false, Cloud Backup also 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 when your application uses disk volumes and data consistency is critical.

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 component 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-* under the restore account. For more information, see Create a backup vault.

3. Create a backup task for sts-oss. For more information, see Create a backup plan or back up instantly.

   • Set Backup Volume to Disable — sts-oss uses the original OSS bucket and does not require volume data backup.

   • Select the oss namespace. Add labels to select only sts-oss if other applications are in the namespace.

   • Confirm the backup completes on the Backup Records tab. Verify that all sts-oss resources are backed up.

4. Create a backup task named backup-nas-disk for sts-nas and sts-disk. For more information, 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 verify, log on to the ECS console, click Snapshots, and check the Disk Snapshots tab.

   • NAS volume data is backed up using Cloud Backup. Monitor progress in the Cloud Backup console under Container Backup > Backup Jobs.

Cloud Backup solution

1. Restore sts-oss.

   1. On the Application Backup page, click Back up Now, then select and initialize a backup vault. Wait for the system to synchronize the backup file to the restore cluster.

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

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

2. Restore sts-nas and sts-disk using StorageClass conversion.

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

   2. Verify the applications and data in the restore cluster. Log on to the ECS console and confirm that a new disk is created under the restore account and mounted to the corresponding node.

ECS snapshot solution

1. Restore account — Restore sts-oss in the restore cluster.

   1. On the Application Backup page, click Back up Now, select and initialize a 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 sts-oss is running correctly. Run kubectl exec to log on to the container and confirm data consistency.

2. Backup account — Log on to the ECS console and share the snapshot with the restore account. For more information, see Share a snapshot. Snapshots created by the backup center start with snapshot-. Find the correct snapshot by matching the creation time of the backup record.

3. Backup account — Record the PVC-to-snapshot mappings to simplify the manual restore steps.

   1. In the ECS console, record the mapping between snapshot IDs and disk IDs.

   2. Log on to the backup cluster and record which PVC maps to which disk. Run the following command to query the PVC, namespace, and disk ID for a given PV:

      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

      • PVC: PVC name

      • Namespace: namespace of the PVC

      • VolumeHandle: disk ID

   3. Combine the information from steps 1 and 2 to map each PVC to its corresponding snapshot ID.

4. Restore account — Log on to the Resource Management console and accept the shared snapshot. For more information, see Share a snapshot. The shared snapshot retains its original name in the restore account, but gets a new ID. Use the snapshot name and the mapping from step 3 to map each PVC to the new snapshot ID.

5. Restore account — Manually restore disk volumes in the restore cluster.

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

   2. Create a PVC with the same name as the original to reference the VolumeSnapshot. For more information, see Step 6 in Create a snapshot of a disk volume. The new PVC has the same configuration as the original, plus a dataSource parameter pointing to the VolumeSnapshot.

6. Restore account — Create a restore task for sts-nas and sts-disk. Because the disk volumes for sts-disk are already restored in step 5, the restore task skips them and mounts the PVC with the same name. For more information, see Restore applications and volumes.

   1. On the Application Backup page, click Back up Now and select backup-nas-disk. Skip StorageClass conversion to use the original StorageClass — make sure it exists in the restore cluster.

   2. Verify the applications and data in the restore cluster. Log on to the ECS console and confirm that a new disk is created under the restore account and mounted to the corresponding node.