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

Cloud Backup solution

If your application uses disk volumes and you want to use Cloud Backup, choose this solution. Perform the following steps to back up data:

1. Make sure the ECS snapshot feature is disabled.

   1. Run the following command to modify the csdr-config ConfigMap:

      kubectl -ncsdr edit cm csdr-config 

   2. Set the enable_ecs_snapshot field to false. Save the file and exit.

   3. Run the following command to restart the component for the modification to take effect:

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

2. If the account of the restore cluster does not have a backup vault, create one and associate it with the OSS bucket named cnfs-oss-* within the account of the restore cluster. For more information, see Create a backup vault.

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

   • The sts-oss application needs to use the original OSS bucket. Therefore, you do not need to back up the data in the OSS volume. Create a backup task for the application. When configuring the backup task, select Disable for Backup Volume.

   • Assume that the sts-oss application belongs to the oss namespace. When you create the backup task, select the oss namespace. If the namespace contains other applications, add labels to select the sts-oss application.

   • On the Backup Records tab of the Application Backup page, confirm that the status of the backup task changes from InProgress to Completed. Click the name of the backup record and confirm that resources related to the sts-oss application, such as the StatefulSet, pod, PVC, PV, and Secret that stores the AccessKey pair, are backed up.

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

   • When creating the backup task, select Mounted Volumes for Backup Volume.

   • Data in disk volumes is also backed up by Cloud Backup because enable_ecs_snapshot is set to false. You can log on to the Cloud Backup console, click Container Backup in the left-side navigation pane, and view the backup progress and result of each PVC on the Backup Jobs tab.

ECS snapshot solution

If your application uses disk volumes and you want to use the ECS snapshot solution to back up cloud disks, choose this solution. Perform the following steps to back up data:

1. Make sure that the ECS snapshot feature is enabled.

   1. Run the following command to modify the csdr-config ConfigMap:

      kubectl -ncsdr edit cm csdr-config 

   2. Set the enable_ecs_snapshot field to true. Save the file and exit.

   3. Run the following command to restart the component for the modification to take effect:

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

2. If the account of the restore cluster does not have a backup vault, create one and associate it with the OSS bucket named cnfs-oss-* within the account of the restore cluster. For more information, see Create a backup vault.

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

   • The sts-oss application needs to use the original OSS bucket. Therefore, you do not need to back up the data in the OSS volume. Create a backup task for the application. When configuring the backup task, select Disable for Backup Volume.

   • Assume that the sts-oss application belongs to the oss namespace. When you create the backup task, select the oss namespace. If the namespace contains other applications, add labels to select the sts-oss application.

   • On the Backup Records tab of the Application Backup page, confirm that the status of the backup task changes from InProgress to Completed. Click the name of the backup record and confirm that resources related to the sts-oss application, such as the StatefulSet, pod, PVC, PV, and Secret that stores the AccessKey pair, are backed up.

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

   • When you create the backup task, select Mounted Volumes for Backup Volume.

   • Data in disk volumes is backed up by using the ECS snapshot feature by default. You can log on to the ECS console, click Snapshots in the left-side navigation pane, and view the snapshot of each disk on the Disk Snapshots tab.

   • Data in NAS volumes is backed up by using Cloud Backup. You can log on to the Cloud Backup console, click Container Backup in the left-side navigation pane, and view the backup progress and result of each PVC on the Backup Jobs tab.

Cloud Backup solution

Use the account of the restore cluster to perform the following steps in the restore cluster.

1. Create a restore task to restore the sts-oss application. For more information, see Restore applications and volumes.

   1. On the Application Backup page, click Back up Now, select and initialize a backup vault, and 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. Check whether the sts-oss application runs as normal in the restore cluster. Run the kubectl exec command to log on to the container and check whether the data is consistent.

2. Create a restore task to restore the sts-nas and sts-disk applications, and use StorageClass conversion to restore data to a volume of the desired type. For more information, see Restore applications and volumes.

   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.

      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 for StorageClass conversion.

   2. Confirm that the application and data in the restore cluster are normal. You can log on to the ECS console and confirm whether a new disk is created within the account of the restore cluster and mounted to the corresponding node.

ECS snapshot solution

1. Use the account of the restore cluster to create a restore task in the restore cluster to restore the sts-oss application. For more information, see Restore applications and volumes.

   1. On the Application Backup page, click Back up Now, select and initialize a backup vault, and 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. Check whether the sts-oss application runs as normal in the restore cluster. Run the kubectl exec command to log on to the container and check whether the data is consistent.

2. Use the account of the backup cluster to log on to the ECS console and share the snapshot with the account of the restore cluster. For more information, see Share a snapshot.

   Snapshots created by the backup center start with snapshot-. You can find the snapshot based on the creation time of the corresponding backup record.

3. To facilitate manual restoration from the snapshot to a disk volume, we recommend that you perform the following operations to record the following mappings within the account of the backup cluster:

   1. Go to the ECS console and record the mapping between the snapshot ID and the corresponding disk ID.

   2. Log on to the backup cluster and record the PVC used to mount a disk volume and the corresponding disk ID.

      Run the following command to query the PVC bound to a PV that is used to mount a disk volume and the corresponding disk:

      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

      In the output, the PVC field indicates the PVC name, the Namespace field indicates the namespace of the PVC, and the VolumeHandle field indicates the ID of the disk.

   3. The preceding information helps you map the ID of the PVC used to mount a disk volume to the ID of the corresponding snapshot.

4. Use the account of the restore cluster to log on to the Resource Management console and accept the shared snapshot. For more information, see Share a snapshot.

   The name of the shared snapshot within the account of the restore cluster remains unchanged but its ID is changed.

   You can map the new snapshot ID to the original one based on the snapshot name. You can refer to the mapping information in Step 3 to map the ID of the PVC used to mount a disk volume to the ID of the new snapshot.

5. Manually restore a disk volume in the restore cluster. Perform the following steps:

   1. Use the static provisioning method to create a VolumeSnapshotContent and a VolumeSnapshot in the restore cluster. For more information, see Create a snapshot of a disk volume. The VolumeSnapshot must be created in the same namespace as the PVC that you create. Set the snapshotHandle parameter in the VolumeSnapshotContent configurations to the ID of the new snapshot.

   2. Create a PVC with the same name as the original one to reference the VolumeSnapshot. For more information, see Step 6 in Create a snapshot of a disk volume. The new PVC has the same configurations as the original one, except that the new PVC has an additional dataSource parameter.

6. Create a restore task in the restore cluster to restore the sts-nas and sts-disk applications. For more information, see Restore applications and volumes.

   This step skips the restoration of the volumes used by the sts-disk application by default because they are already restored. When you restore the sts-disk application, a new PVC with the same name as the original one is mounted 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 based on the original StorageClass by default. Make sure that the StorageClass already exists in the restore cluster.

   2. Confirm that the application and data in the restore cluster are normal. You can log on to the ECS console and check whether a new disk is created within the account of the restore cluster and mounted to the corresponding node.