Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
Document
Volcengine Kubernetes Engine
What's New
History feature release notes
Kubernetes version release notes
Containerd runtime release notes
Add-on release notes
Monitoring add-ons
Scheduling add-ons
DNS add-ons
Security add-ons
GPU add-ons
Sandbox add-on
Security announcements
Product Announcement
Historical announcements
Overview
Getting started
User guide
Clusters
Creating clusters
Connecting to clusters
Upgrading clusters
Node pool
Creating node pools
Scaling out/in node pools
Nodes
Authorization management
Image
Namespaces
Networking
Cluster network
Container Network
Service
LoadBalancer
CLB
Ingress
APIG Ingress
ALB Ingress
Customize ALB Ingress forwarding rules
Certificate and security
CLB Ingress
Nginx Ingress
Gateway API
Workloads
Creating workloads
Configure workloads
Pods
Configuration management
Image acceleration
Storage
FSX client
EBS Volumes
TOS Volumes
NAS volumes
FSX access methods
NFS access methods
EFS volumes
vePFS volumes
FSX access methods
vePFS Client access methods
NFS access methods
CloudFS volumes
Local volumes
Autoscale
Node autoscaler
Workload autoscaler
Horizontal Pod Autoscaler (HPA)
Cron Horizontal Pod Autoscaler (CronHPA)
Intelligent Horizontal Pod Autoscaler (IHPA)
Horizontal Pod Autoscaler based on event-driven (KEDA)
Add-on management
Network add-ons
Storage add-ons
Monitoring add-ons
Scheduling add-ons
DNS add-ons
GPU add-ons
Core add-ons
Sandbox add-on
Upgrading add-ons
Heterogeneous computing
NVIDIA GPU
mGPU scheduling
RDMA high-performance computing
Scheduling management
Topology-aware scheduling
QoS-aware scheduling
Observability
Log management
Basic observation
Setup & Configuration
Cluster observation
Storage observation
Other observation
Using metrics
Full stack observation
Alert management
Diagnosis and inspection
Node check and self-healing
Application center
Backup center
Stability
Large-scale cluster management
Best practices
Authorization
Clusters
Nodes and node pools
Networking
Storage
Scheduling
Observability
Solution
Security and compliance
API reference
Cluster management
NodePool management
Node management
Virtual nodes management
Add-on management
Tag management
Access policy management
Instance images management
Cloud native observability
Inspection and diagnosis
Task management
Volcengine Container Instance
Appendix
SDK reference
Development guide
Terraform
FAQs
General FAQs
Cluster FAQ
cluster management
cluster network
cluster upgrade
Node and Node pool FAQs
Authorization FAQs
Workload FAQs
Service and Ingress FAQs
Storage FAQs
Heterogeneous computing FAQs
Observability FAQs
Quota FAQs
Add-on FAQs
Cloud-native AI
ServingKit
LLM applications
ComfyUI application
Deploying the Al inference application through Helm
Deepseek practices
Qwen practices
Kimi practice
Seed practices
Best practices
DeepSeek model deployment
GLM model deployment
MiniMax model deployment
Qwen model deployment
Kimi model deployment
Volcengine Container Instance
What's new
Historical feature release notes
Product Announcement
Overview
Billing
User guide
Integrating with VCI
Virtual node
VKE cluster uses virtual nodes
Self-managed/third-party cluster uses virtual node
Creating an instance
General purpose instance
GPU-accelerated computing instance
VCI Agent Sandbox
Startup acceleration
E2B-based management
Upgrade guide
Networking
Monitoring
Scheduling
Container configuration
VCI Image Cache
Best practices
Security and compliance
FAQs
- Documentation
Volcengine Kubernetes EngineVolcengine Kubernetes EngineUser guideBackup centerBackup center overview
Copy page
Download PDFBackup center
Backup center overview
Copy pageDownload PDFBackup center overview
The VKE backup center allows container application metadata and PersistentVolume data to be backed up to TOS, and supports one-click restore to a specified cluster based on backup data. This feature is applicable to scenarios such as disaster recovery for containerized applications, application migration from IDCs to the cloud, and cross-cloud application migration.
tip
[Public beta]: The backup center is currently in public beta.
How it works
The backup center is based on Velero to implement application backup and restore in clusters, with backup data securely stored in TOS buckets. For more details, see the Velero documentation.
Unlike other tools that directly access the Kubernetes etcd database for backup and restore, Velero uses the Kubernetes API to capture the status of cluster resources and restore them when necessary. This API-driven approach offers the following key advantages:
- Backups can capture a subset of cluster resources, which can be filtered by namespace, resource type, and/or label selector, providing a high degree of flexibility in what is backed up and restored.
- No direct access to etcd is required for backup or restore, which addresses scenarios where users of managed Kubernetes cannot access etcd directly.
- Resources exposed via the Aggregated API Server can be easily backed up and restored, even if they are stored in a separate etcd database.
Core resources
Backup repositories
VKE allows you to add Volcano Engine TOS to the backup center as backup repositories for storing and managing backups.
Backup/Restore target clusters
All VKE clusters, such as managed clusters and registered clusters, can serve as backup/restore target clusters.
warning
The recommended Kubernetes version range for backup/restore target clusters is v1.24.x to v1.32.x.
Backup/restore resource scope
The backup center provides namespace-level application metadata backup and restore, including Kubernetes-native resources, CustomResourceDefinition (CRD) resources, and volume resources. The following types of data are supported for backup and restore:
- Application metadata, which refers to the definition data of Kubernetes objects.
- Volume data, which refers to the data in volumes mounted to pods. Volume types include PVC, local, emptyDir, and more.
PV backup
The backup center currently provides storage volume backup using the CSI snapshot method. This method is typically applicable to backup and restore scenarios within the same cloud environment, cluster, and storage system. The following considerations should be noted when you back up PVs:
- Ensure that the corresponding VolumeSnapshotClass already exists in the Kubernetes cluster.
- Ensure that all PVCs are created through CSI.
- If there are multiple PVCs created by different CSI drivers within a namespace, ensure that each CSI driver has a corresponding VolumeSnapshotClass.
- If a single CSI driver has multiple eligible VolumeSnapshotClasses, a random VolumeSnapshotClass will be selected for backup.
Application scenarios
Cloud migration of container application data
The backup center provides an easy-to-use data migration method that enables enterprises to flexibly and independently select or switch cloud service providers while avoiding infrastructure lock-in.
System or hardware failure
Backup and restore effectively reduce the risk of business disruption caused by failures and ensure the continuity of core businesses in Kubernetes clusters.
Environment changes in development and testing
The backup center enables quick restoration of data backed up at any time or in any repository when the environment changes or configuration adjustments occur during development, testing, or similar processes.
Malicious attacks or misoperations
The backup center prevents data loss caused by malicious attacks or misoperations through backup and recovery, ensuring data integrity and availability.
Multi-cluster and multi-storage collaborative protection
With the capabilities of the backup center, you can easily implement multi-location, on-demand backup/restore and disaster recovery protection across infrastructure, including across clusters, cloud providers, and storage regions. Examples include backing up and restoring applications within a VKE cluster, migrating applications across VKE clusters in the same region, migrating applications across VKE clusters in different regions, and migrating applications from third-party clusters to VKE clusters.
Usage process
You can refer to the following tasks to back up and restore cluster data:
- Adding repositories: Use Volcano Engine TOS as backup repositories.
- Creating backup plans. Back up application metadata to TOS for subsequent restore jobs.
- Creating restore jobs. You can restore backup data in the Success or Partially failed status to the specified cluster with one click.
Last updated: 2026.06.24 11:15:03
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
