- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
-
UCS Clusters
- Overview
- Huawei Cloud Clusters
-
On-Premises Clusters
- Overview
- Service Planning for On-Premises Cluster Installation
- Registering an On-Premises Cluster
- Installing an On-Premises Cluster
- Managing an On-Premises Cluster
- Attached Clusters
- Multi-Cloud Clusters
- Single-Cluster Management
- Fleets
-
Cluster Federation
- Overview
- Enabling Cluster Federation
- Using kubectl to Connect to a Federation
- Upgrading a Federation
-
Workloads
- Workload Creation
-
Container Settings
- Setting Basic Container Information
- Setting Container Specifications
- Setting Container Lifecycle Parameters
- Setting Health Check for a Container
- Setting Environment Variables
- Configuring a Workload Upgrade Policy
- Configuring a Scheduling Policy (Affinity/Anti-affinity)
- Configuring Scheduling and Differentiation
- Managing a Workload
- ConfigMaps and Secrets
- Services and Ingresses
- MCI
- MCS
- DNS Policies
- Storage
- Namespaces
- Multi-Cluster Workload Scaling
- Adding Labels and Taints to a Cluster
- RBAC Authorization for Cluster Federations
- Image Repositories
- Permissions
-
Policy Center
- Overview
- Basic Concepts
- Enabling Policy Center
- Creating and Managing Policy Instances
- Example: Using Policy Center for Kubernetes Resource Compliance Governance
-
Policy Definition Library
- Overview
- k8spspvolumetypes
- k8spspallowedusers
- k8spspselinuxv2
- k8spspseccomp
- k8spspreadonlyrootfilesystem
- k8spspprocmount
- k8spspprivilegedcontainer
- k8spsphostnetworkingports
- k8spsphostnamespace
- k8spsphostfilesystem
- k8spspfsgroup
- k8spspforbiddensysctls
- k8spspflexvolumes
- k8spspcapabilities
- k8spspapparmor
- k8spspallowprivilegeescalationcontainer
- k8srequiredprobes
- k8srequiredlabels
- k8srequiredannotations
- k8sreplicalimits
- noupdateserviceaccount
- k8simagedigests
- k8sexternalips
- k8sdisallowedtags
- k8sdisallowanonymous
- k8srequiredresources
- k8scontainerratios
- k8scontainerrequests
- k8scontainerlimits
- k8sblockwildcardingress
- k8sblocknodeport
- k8sblockloadbalancer
- k8sblockendpointeditdefaultrole
- k8spspautomountserviceaccounttokenpod
- k8sallowedrepos
- Configuration Management
- Traffic Distribution
- Observability
- Container Migration
- Pipeline
- Error Codes
-
UCS Clusters
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
-
API
- UCS Cluster
-
Fleet
- Adding a Cluster to a Fleet
- Removing a Cluster from a Fleet
- Registering a Fleet
- Deleting a Fleet
- Querying a Fleet
- Adding Clusters to a Fleet
- Updating Fleet Description
- Updating Permission Policies Associated with a Fleet
- Updating the Zone Associated with the Federation of a Fleet
- Obtaining the Fleet List
- Enabling Fleet Federation
- Disabling Cluster Federation
- Querying Federation Enabling Progress
- Creating a Federation Connection and Downloading kubeconfig
- Creating a Federation Connection
- Downloading Federation kubeconfig
- Permissions Management
- Using the Karmada API
- Appendix
-
FAQs
- About UCS
-
Billing
- How Is UCS Billed?
- What Status of a Cluster Will Incur UCS Charges?
- Why Am I Still Being Billed After I Purchase a Resource Package?
- How Do I Change the Billing Mode of a Cluster from Pay-per-Use to Yearly/Monthly?
- What Types of Invoices Are There?
- Can I Unsubscribe from or Modify a Resource Package?
-
Permissions
- How Do I Configure Access Permissions for Each Function of the UCS Console?
- What Can I Do If an IAM User Cannot Obtain Cluster or Fleet Information After Logging In to UCS?
- How Do I Restore ucs_admin_trust I Deleted or Modified?
- What Can I Do If I Cannot Associate the Permission Policy with a Fleet or Cluster?
- How Do I Clear RBAC Resources After a Cluster Is Unregistered?
- Policy Center
-
Fleets
- What Can I Do If Cluster Federation Verification Fails to Be Enabled for a Fleet?
- What Can I Do If an Abnormal, Federated Cluster Fails to Be Removed from the Fleet?
- What Can I Do If an Nginx Ingress Is in the Unready State After Being Deployed?
- What Can I Do If "Error from server (Forbidden)" Is Displayed When I Run the kubectl Command?
- Huawei Cloud Clusters
- Attached Clusters
-
On-Premises Clusters
- What Can I Do If an On-Premises Cluster Fails to Be Connected?
- How Do I Manually Clear Nodes of an On-Premises Cluster?
- How Do I Downgrade a cgroup?
- What Can I Do If the VM SSH Connection Times Out?
- How Do I Expand the Disk Capacity of the CIA Add-on in an On-Premises Cluster?
- What Can I Do If the Cluster Console Is Unavailable After the Master Node Is Shut Down?
- What Can I Do If a Node Is Not Ready After Its Scale-Out?
- How Do I Update the CA/TLS Certificate of an On-Premises Cluster?
- What Can I Do If an On-Premises Cluster Fails to Be Installed?
- Multi-Cloud Clusters
-
Cluster Federation
- What Can I Do If the Pre-upgrade Check of the Cluster Federation Fails?
- What Can I Do If a Cluster Fails to Be Added to a Federation?
- What Can I Do If Status Verification Fails When Clusters Are Added to a Federation?
- What Can I Do If an HPA Created on the Cluster Federation Management Plane Fails to Be Distributed to Member Clusters?
- What Can I Do If an MCI Object Fails to Be Created?
- What Can I Do If I Fail to Access a Service Through MCI?
- What Can I Do If an MCS Object Fails to Be Created?
- What Can I Do If an MCS or MCI Instance Fails to Be Deleted?
- Traffic Distribution
- Container Intelligent Analysis
- General Reference
Copied.
Backup and Restoration
Context
After an on-premises cluster is registered with UCS, you can back up the certificates, encryption and decryption materials, and etcd data on the three master nodes to ensure cluster high availability and prevent data loss when the cluster is faulty. These backups can be used to restore data.
Constraints
The node IP addresses must remain unchanged regardless of whether a single master node or master nodes are faulty.
Cluster Backup
Local backup
- Create a path for storing the backup file package.
- Run the following backup command:
./ucs-ctl backup {Cluster name} --path {Backup path} --type local
Example:
./ucs-ctl backup gpu-test --path /home/ggz/gpu-test --type local
After the command is executed successfully, a backup file package in the format of {Cluster name}-backup-{Timestamp}.tar.gz is generated in the specified backup path.
The package stores the ha.yaml file and the etcd-snapshot and crt directories. The etcd-snapshot directory contains etcd data, and the crt directory contains certificates and encryption and decryption materials.
Remote backup
- Create a path for storing the backup file package on the remote host over SFTP.
- Run the following backup command:
./ucs-ctl backup {Cluster name} --path {Backup path} --type sftp --ip {IP address of the remote host} --user {Username of the remote host}
Example:
./ucs-ctl backup gpu-test --path /home/ggz/gpu-test --type sftp --ip 100.95.142.93 --user root
NOTICE:
- If you perform remote backup for the first time, enter the password of the remote host after "please input sftp password:" is displayed.
- The backup path in the backup command must be valid. Otherwise, the backup file generated on the remote host after the command is executed may be incorrect.
After the command is executed successfully, a backup file package in the format of {Cluster name}-backup-{Timestamp}.tar.gz is generated in the specified backup path on the remote host. The package stores the ha.yaml file and the etcd-snapshot and crt directories. The etcd-snapshot directory contains etcd data, and the crt directory contains certificates and encryption and decryption materials.
Periodic backup
Run the crontab -e command to compile a crontab expression so that the backup command is executed periodically.
Run the following command to execute the periodic local backup of the cluster at 16:40 every day:
40 16 * * * <ucs-ctl-path> backup <cluster-name> --path <backup-path> --type <local>
Example command:
40 16 * * * /root/cluster/ucs-ctl backup cluster-redhat --path /root/cluster/backup --type local
During periodic remote backup, you do not need to specify the password in the crontab expression after entering the password of the remote host for the first time.
To prevent the number of backup files from increasing, compile the crontab expression on the remote host to periodically execute the backup file aging script. The following is an example of the backup file aging script:
#!/bin/bash backup_dir=${1} # Path for storing backup files keep_days=${2} # Retention days of backup files if [ ! -d ""$backup_dir"" ]; then # Check whether the log path exists. echo "There is no backup file path." exit 1 fi find "$backup_dir" -type f -mtime +$keep_days -exec rm {} \; # Delete legacy logs. echo "Expired backup files have been deleted!"
Data Restoration
Restoring etcd Data
- Prepare an etcd data backup package in the format of {Cluster name}-backup-{Timestamp}.tar.gz.
Upload the package to each master/etcd node of the cluster.
- Stop the etcd service.
Run the following command on the node:
mv /var/paas/kubernetes/manifests/etcd*.manifest /var/paas/kubernetes/
Wait until the service is stopped.
crictl ps | grep etcd
If no etcd container is found, the service has been stopped.
- (Optional) Back up the etcd data on a node.
mv /var/paas/run/etcd/data /var/paas/run/etcd/data-bak mv /var/paas/run/etcd-event/data /var/paas/run/etcd-event/data-bak
- Run the restoration command on the node where the etcd database resides.
./ucs-ctl restore etcd {Path of the etcd data backup package}
Example:
./ucs-ctl restore etcd /home/ggz/gpu-test/backup-file-20230625164904.tar.gz
The etcd data is restored if the following command output is displayed:
Restore the etcd snapshot successfully.
- Restart the etcd service on the node. The restart takes several minutes.
mv /var/paas/kubernetes/etcd*.manifest /var/paas/kubernetes/manifests
Wait for the service to restart.
crictl ps | grep etcd
If the etcd containers are found, the service has been restarted and the etcd data is restored on the node.
Restoring a single master node
- Run the single-node fault recovery command on the executor:
./ucs-ctl restore node {IP address of the node} --name {Cluster name}
{IP address of the node} indicates the IP address of the faulty node. The following is an example:./ucs-ctl restore node 192.168.0.87 --name gpu-test
The fault on the single master node is rectified if the following command output is displayed:restore node 192.168.0.87 successfully.
- Restore etcd data on the node where etcd is located. For details about the commands, see 1 to 5.
Restoring master nodes
- Clear the data on all master nodes. Copy the uninstallation script in the executor directory to the master nodes and execute the script on each master node. (The script path is /var/paas/.ucs-package/ucs-onpremise/scripts/uninstall_node.sh.)
scp -r /var/paas/.ucs-package/ucs-onpremise/scripts/uninstall_node.sh root@{IP address of the target node}:/root sudo bash /root/uninstall_node.sh
- Run the cluster fault recovery command on the executor:
./ucs-ctl restore cluster {Cluster name} -b {Path of the backup file package}
Example command:
./ucs-ctl restore cluster gpu-test -b /home/ggz/gpu-test/backup-file-20230625164904.tar.gz
The faults on the master nodes are rectified if the following command output is displayed:restore cluster successfully.
- Restore etcd data on each node where etcd is located. For details about the commands, see 1 to 5.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot