tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary

Backup Management

Mode fokus
Ukuran font
Terakhir diperbarui: 2025-09-29 14:40:20

Introduction

TKE Backup Center provides integrated solutions for the backup, restoration and migration of applications. This document describes how to create a backup task and a scheduled backup policy.

Prerequisite

Note:
If you have installed a community-based open source backup tool, such as Velero, please uninstall it first.
Install the tke-backup add-on in the target cluster. You can go to the Add-on management module of the cluster to install the add-on. For operation details, see Add-on Installation.




Directions

Creating a backup

1. Log in to the TKE console and select Backup Center > Backup Management in the left sidebar.
2. Click Create backup on the page that appears.
3. Enter backup information.



Field description:
Backup name: Enter the backup task name that meets the requirements prompted.
Backup type:
Instant backup: Create a backup task and implement the backup operation instantly.
Scheduled backup: Create the resource object BackupSchedule, which will create backup tasks in a scheduled way based on the rules you set.
Backup repository: Select a backup repository you created.
Namespace: Select a specific namespace or all namespaces, in which all applications are backed up.
Backup validity: Retaining period of the backup data, after which the data is deleted and cannot be restored.
Advanced settings:
Exclude namespace: You can specify the namespace that will not be backed up when you select "All" for Namespace.
Backup resource: All Kubernetes resources in the corresponding namespace are backed up when you select "All". Otherwise, back up the specific Kubernetes resource.
Exclude resource: You can specify the resource that will not be backed up when you select "All" for Backup resource.
Specify label: Only the applications with the label in the target namespace are backed up.
4. Click OK.
Note:
The following types of Kubernetes resources are backed up: Deployment, StatefulSet, DaemonSet, Job, CronJob, ConfigMap and Secret.

Viewing backup

You can view the backup on Instant backup and Scheduled backup tabs on the Backup management page.




Viewing backup status

Status
Description
Initializing
The backup task is being created.
Executing
The backup task is being implemented.
Acceleration
The backup operation is completed.
Partially failed
Some resource objects are backed up successfully, and others are failed. You can check "Status" in YAML to learn the number of successfully backed up resource objects and the failure reasons.
Failed.
The backup is failed. You can learn the failure reasons in the console or by checking "Status" in YAML.

Viewing backup content

You can view the backup data of the storage in the COS console. Each backup task is named in the format of "Backup name-Cluster name-YYYYMMDDHHmmss".




Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan