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 centerApplication backupCreating backup plans
Copy page
Download PDFApplication backup
Creating backup plans
Copy pageDownload PDFCreating backup plans
The backup center supports backing up application metadata and PersistentVolume (PV) data to TOS. This topic describes how to create a backup plan.
Background
- Backup/Restore target clusters: All VKE clusters, such as managed clusters and registered clusters, can be used as backup/restore target clusters.
- 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.
Usage limits
- The recommended Kubernetes version range for backup/restore target clusters is v1.24.x to v1.32.x.
- The PV backup feature supports only cluster version v1.20.x and later.
Prerequisites
- The migrate-plugin add-on has been installed. For details, see migrate-plugin.
- A backup repository has been created and is available. For details, see Adding repositories.
Procedure
- Log in to the VKE console.
- In the left navigation bar, click Backup center > Application backup to enter the application backup page.
- Click the Backup plan tab and click Create backup plan to specify the parameters of the backup plan.
- Basic information
- ParameterDescriptionParameterDescriptionPlan nameEnter a custom name for the backup plan.Backup repositoriesSelect a TOS warehouse that has already been added. The TOS warehouse is used as the backup warehouse.Region IDSelect a region.Source clusterSelect the source cluster containing the application data to be backed up. Make sure that the migrate-plugin add-on is installed in the selected cluster.tip
- If the selected cluster does not have the required migrate-plugin add-on installed, click Install and wait for the add-on to be installed successfully.
- If the selected cluster cannot access the backup warehouse, the backup warehouse cannot be used. You need to check connectivity and try again later if it is unavailable.
Source namespaceSelect a namespace within the source cluster. Backup plans only at the namespace level are supported. You can select one or more namespaces in the source cluster according to your backup requirements.Backup typeSelect a backup policy for the backup based on your actual requirements.- Scheduled backup: After the backup plan is created, application data will be backed up on a schedule according to the configured backup cycle.
- Backup now: After the backup plan is created, a backup job will be executed immediately and only once.
Backup cycleWhen the backup type is scheduled backup, this setting is required. Configure the repeat cycle and trigger time of the backup job.- Time settings: Visually configure the repetition cycle and trigger time of the backup job. The repetition cycle can be set on a monthly, weekly, or daily basis. The trigger time can be specified by time interval or fixed time.
- Cron expression: Set the backup cycle using a Cron expression. The China region (UTC+8) supports crontab syntax. For details, see the official Crontab documentation.
tipClick Trigger time preview to preview the specific trigger times of the latest four backup jobs (accurate down to seconds).Backup validity dateThe retention period for backup jobs is 30 days by default and can be configured as needed.warningBackup jobs that exceed the specified duration will be deleted. Deleted resources include backup jobs, application files backed up in TOS, and all PV snapshots.Resources for backupBy default, all resources in the selected namespaces are backed up. You can specify labels or exact resource types for data backup according to actual needs, or exclude certain resources from data backup. The resource backup conditions are combined using logical AND. For example:- If no label, resource, or exclusion condition is configured, all resources in the selected namespaces will be backed up.
- If a label is specified, only resources that are in the selected namespaces and have the label will be backed up.
- If both labels and specific resources are configured, the AND logic will be applied to filter resources for data backup.
Specify label for backup: Filter resources within the selected namespaces by label. When multiple labels are specified, a resource is included in the backup only if all labels match.Specify resources for backup: Specify resource types for data backup. Only the specified types of resources will be backed up. You can add one or more resource types, for example, Deployment and ConfigMap.Exclude resources for backup: Exclude specific resources from the backup. Example resources include Pod and Secret.
- PersistentVolume
- ParameterDescriptionParameterDescriptionBackup PersistentVolumeThe PersistentVolume backup switch is disabled by default and can be configured as needed.warningThis setting is supported only by cluster version v1.20.x or later.Available methodSelect the backup method for PV backup. Currently, CSI snapshots are supported. For details, see PersistentVolume backup method.
- Click Confirm.
Subsequent operations
- After the backup plan is created, backup jobs will be triggered according to the backup cycle. You can go to the details page to view the backup jobs for the backup plan or go to the backup job management page to view all backup jobs. For details, see Viewing backup jobs.
- You can manage an existing backup plan. For details, see Managing backup plans.
Last updated: 2026.06.24 11:15:04
All rights reserved © Beijing Volcano Engine Technology Co., Ltd2024
