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

Restoration Management

Mode fokus
Ukuran font
Terakhir diperbarui: 2024-01-19 14:09:34

Introduction

TKE Backup Center provides integrated solutions for the backup, restoration and migration of applications. This document describes how to restore resources from the target cluster where the backup task has been created.
Note:
Only backup and restoration in a cluster are supported. Cross-cluster migration is not available currently.

Prerequisite

Create a backup task in the target cluster.

Directions

Creating a restoration task

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



Field description:
Task name: Enter the restoration task name that meets the requirements prompted.
Backup repository: Select a backup repository you created.
Select backup: Select a backup task to restore.
Restore namespace: Select namespaces from which you want to restore resources.
All namespaces: Restore resources in all namespaces found in the backup.
Specific namespace: Restore resources in the specific namespace that is selected in the backup task.
Conflict treatment:
Do not override (recommended): The backup resource with the same name in the namespace of the target cluster will not be overridden.
Update: The backup resource with the same name in the namespace of the target cluster will be overridden.
4. Click OK.
Note:
The success of the restoration tasks cannot be guaranteed.
Deleting the backup task only removes the operation log of restoration from the restoration list.

Viewing restoration status

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


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan