• Cloud-Native Container ProductsCloud-Native Container Products
    • KubeSphere Enterprisehot
    • KubeSphere Virtualizationhot
    • KubeSphere Enterprise HCI
  • Cloud-Native ServiceCloud-Native Service
    • KubeSphere Backuphot
    • KubeSphere Litenew
    • KubeSphere Inspectornew
  • Public Cloud Container ServicePublic Cloud Container Service
    • KubeSphere on AWS
    • KubeSphere on DigitalOcean

FAQs

Lists frequently asked questions about KubeSphere Backup.

This topic lists frequently asked questions about KubeSphere Backup.

Cluster-related questions:

Object storage repository-related questions:

Backup/recovery-related questions:

Why my cluster is not ready when creating a backup/recovery plan?

  • After you import a cluster, it will take about 5 minutes to install backup and recovery components on the cluster. The actual installation speed is dependent on the network speed. The cluster remains as not ready until the components are up and running.
  • If the kubeconfig used for connecting the cluster is invalid, the cluster is not ready.

Do I need to buy a S3-compatible storage repository from QingCloud?

No. You just need to ensure the object storage repository to be added is compatible with AWS S3 Standard and accessible to the internet.

What resources will be covered in a backup?

A backup covers all the resources and other data selected by you for backup in the source namespace, including workloads, projects, user permissions, and persistent data.

Can I execute multiple backup/recovery jobs associated with the same cluster at the same time?

No. You can execute multiple backup/recovery jobs associated with the same cluster, but they can only be executed once at a time in sequence.

Why certain resources have recovery errors when source Kubernetes cluster version is different from target cluster version?

Errors may occur when the resource (Kubernetes built-in objects or CRDs) versions in the source cluster is different from the target cluster. Please ensure that the resource versions in the source cluster are compatible with the target cluster.

Why the status of recovery job remains in progress during execution?

The Service does not support storage class detection for now. If the target cluster does not have the storage class backed up by the backup job associated with the recovery job, the persistent volume created through the storage class in the source cluster in the target cluster will remain in pending status, which causes the recovery job remains in progress. Please check the storage class in the target cluster when creating a recovery plan.

Can I back up multiple namespaces at once?

Not supported for now and will be available in the future.

Can I back up cluster-level resources?

Not supported for now and will be available in the future.

Can I create CSI volume snapshots?

Yes. You have to ensure that your Kubernetes cluster has the appropriate volume snapshot class. For more information, see Create volume snapshot class.

Can I back up/recover KubeSphere multi-cluster projects and applications?

Not supported for now and will be available in the future.

Where are the resources and data in the cluster stored after backup?

If you use a hosted repository, resources and data will be stored in the cloud storage repository in QingCloud. If you use a S3-compatible repository, resources and data will be stored in the storage repository you added.

Can I select multiple source namespaces when creating a backup plan?

Not supported for now and will be available in the future.

Can I delete multiple backup jobs at once?

Not supported for now and will be available in the future. If you need to delete multiple backup jobs, you can delete the backup plan to delete all the backup jobs under the backup plan.

Can I delete a backup/recovery job in progress?

Not supported.

KubeSphere ®️ © QingCloud Technologies 2022