Container Service for Kubernetes:Cross-account application backup and restore with a registered cluster

Cloud Backup solution

Choose this for a simpler setup with disk volumes, or when your application has no disk volumes.

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:

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

2. If the restore account has no backup vault, create one and associate it with the cnfs-oss-* OSS bucket in the restore account.

3. Create a backup task for the sts-oss application.

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

   • 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 status to change from InProgress to Completed. Click the record name and confirm that the StatefulSet, pod, PVC, PV, and Secret (containing the AccessKey pair) are backed up.

4. Create a backup task for the sts-nas and sts-disk applications.

   • Set Backup Volume to Mounted Volumes.

   • With enable_ecs_snapshot set to false, Cloud Backup handles disk volume data. Monitor progress in the Cloud Backup console under Container Backup > Backup Jobs.

ECS snapshot solution

Choose this when 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 has no backup vault, create one and associate it with the cnfs-oss-* OSS bucket in the restore account.

3. Create a backup task for the sts-oss application.

   • 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 all related resources are backed up.

4. Create a backup task named backup-nas-disk for the sts-nas and sts-disk applications.

   • Set Backup Volume to Mounted Volumes.

   • Disk volume data is backed up using ECS snapshots by default. View snapshots in the ECS console under Snapshots > Disk Snapshots.

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

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.

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

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

2. Restore the sts-nas and sts-disk applications with 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. alicloud-disk defaults to the alicloud-disk-topology-alltype StorageClass from the CSI plugin. You can also use a custom StorageClass.

   2. Verify the applications and data. In the ECS console, confirm that new disks are created in the restore account and mounted to the correct nodes.

ECS snapshot solution

1. With the restore cluster's account, 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 sts-oss is running with kubectl exec.

2. Use the backup cluster's account to share the disk snapshots with the restore account. In the ECS console, share each snapshot. Backup center snapshots are prefixed with snapshot-. Match them to backup records by creation time.

3. Before accepting the shared snapshots, record the PVC-to-snapshot mappings in the backup account. These mappings are required for manual restoration.

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

   2. In the backup cluster, 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. Snapshot names stay the same but IDs change. Use the names and step 3 mappings 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 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 snapshotHandle 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 matches the original configuration 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 sts-disk volumes automatically because they were restored in step 5. The restore task mounts the same-name PVC to the application.

   1. On the Application Backup page, click Back up Now and select backup-nas-disk. Without StorageClass conversion, volumes restore with the original StorageClass. Ensure that StorageClass exists in the restore cluster.

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