No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

HUAWEI CLOUD Stack 6.5.0 Backup and Restoration Guide 03

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Backup Description

Backup Description

Operation Mode

The system uses two types of data backup and restoration policies: unified backup and restoration as well as service-specific backup and restoration.

Data can be backed up to a local or remote server. If you want to restore local backup data, use service-specific backup and restoration.

Unified data backup includes the following backup modes:

  • Remote backup:
    1. Set configuration parameters.
    2. Set the remote backup policy.
    3. Set and execute the backup task.
  • Local backup
    1. Set the local backup policy.
    2. Set and execute the backup task.

Data

The data of Gauss, persisted Redis, cfe-etcd, and the software repository (SWR) needs to be backed up.

  • The unified backup of Gauss refers to the backup of all data, including the data of routine FusionStage O&M, installation and deployment, upgrade, audit logs, O&M monitoring, login authentication, and information of FusionStage's own database.
  • The unified backup of Redis refers to the backup of the persisted Redis data, that is, data of service menus in Febs.
  • The backup of cfe-etcd refers to the backup of Kubernetes object data, network configuration data, and event data of etcd clusters.
  • The backup of SWR refers to the backup of the software packages and image files in the data directory of the node where the SWR service resides.

Backup Policy Description

  • Gauss and Redis
    • aaddbsvr, apmdbsvr, fstdbsvr, iamdbsvr, and monitordbsrv service instances support unified backup and unified restoration.
    • paasdbsvr, deploydbsvr, and febsdb service instances support unified backup and service-specific restoration.
    • The method for backing up and restoring a single service is similar to that for unified backup and restoration.
    • If full backup is required, you are advised to use unified backup for the aaddbsvr, apmdbsvr, fstdbsvr, iamdbsvr, monitordbsrv, paasdbsvr, and deploydbsvr service instances of Gauss and the febsdb service instance of Redis. If full restoration is required, you are advised to use unified restoration for the aaddbsvr, apmdbsvr, fstdbsvr, iamdbsvr, and monitordbsrv service instances of Gauss, and use service-specific restoration for the paasdbsvr and deploydbsvr service instances of Gauss and the febsdb service instance of Redis.
  • cfe-etcd supports unified backup, unified restoration, and service-specific backup, and does not support service-specific restoration. For local restoration of cfe-etcd, see Restoring Tenant Management Zone cfe-etcd.
  • SWR supports only service-specific backup and restoration.

Reserved Space

The required backup space varies according to networking modes and the number of backups. The required backup space is calculated based on the corresponding backup policy.

  • Full backup

    Reserve the data disk space as required by the networking. You are advised to reserve the disk space to 800 GB x Number of backups.

    NOTE:

    ETCD requires 20 GB; Gauss requires 300 GB; SWR requires 300 GB; the reserved space requires 180 GB. 800 GB is required in total.

  • Service-specific backup

    You can log in to the data storage node manage_db1_ip to view the size of one copy of data.

    • The path for storing Gauss data is /opt/gauss/data.
    • The path for storing Redis data is /opt/redis/data/.
    • The path for storing etcd data is /opt/paas/run.
    • The path for storing SWR data is /opt/paas/dockyard.

    You can run the du -sh <Path for storing data> command to view the size of one copy and multiply the size by the number of backups to calculate the reserved space.

Backup Policy

For details about the unified backup policy, see Setting Backup Policies.

For service-specific backup policies, see Table 1-14.

Table 1-14 Service-specific backup policies

Service

Backup Policy

Gauss

Scheduled backup

  • A database instance is attached with this policy by default.
  • Back up data by days. The triggering time is 00:00.
  • The backup data is stored in the backup directory on the remote server.

Redis

Manual backup

The backup data is stored in the backup directory on the remote server.

CFE-ETCD

The backup of cfe-etcd refers to the backup of Kubernetes object data, network configuration data, and event data of etcd clusters.

You can back up cfe-etcd using the following backup modes:

  • Manual backup

    You are advised to back up data when services are not busy. During the backup, you must back up the Gauss and software repository data at the same time to ensure that the backup data is normal.

  • Scheduled backup
    • Scheduled backup is performed on a daily basis.
    • A full backup is triggered at 02:00 every day.

The backup data of cfe-etcd can be stored to the local or SFTP server.

  • For local backup, data files are stored in the /opt/paas/backup_cfe/etcd_backup/ directory of the node where each etcd cluster is located.
    NOTE:

    The local backup path is on the etcd-backup node.

  • For backup to the SFTP server, data files are stored in the backup directory on the SFTP server. If the backup directory on the SFTP server is not configured during the installation, the data will be stored in /home/backup by default.

SWR

Manual backup

  • Back up data from the /var/paas/dockyard/ directory to the backup directory on the current node.
  • Back up data from the /var/paas/dockyard/data directory on the SWR to the backup directory on the current node.

Precautions

  • After data restoration, data of the software package applications deployed later than the backup time will not be automatically deleted. You need to manually delete the data.
  • GUI theme settings or favorite menus cannot be backed up or restored.
  • The backup and restoration scenario where nodes in the management zone are fully reinstalled is not supported.

Node Description

Following procedure can be used to query database nodes:

  1. Use PuTTY to log in to the manage_db1_ip node.

    The default username is paas, and the default password is QAZ2wsx@123!.

  2. Run the following commands to check information about database:

    cd /opt/paas/oss/manager/apps/DBAgent/bin

    ./dbsvc_adm -cmd query-db-instance -type gauss

    Information similar to the following is displayed:

    DBInstanceId                                     ClassId  InstNumber                      Tenant  IP               Port   State  DBType  Version            Role    Rpl Status  MasterID                        GuardMode  DataCheckSum  isSSL 
    deploydbsvr-10_109_178_191-4@10_109_211_34-4   primary  deploydbsvr-10_109_178_191-4   fst-manage  10.109.178.191  32084  Up     gauss   V100R003C20SPC112  Master  Normal      --                              --         717445868     off
    deploydbsvr-10_109_178_191-4@10_109_211_34-4   primary  deploydbsvr-10_109_211_34-4    fst-manage  10.109.211.34   32084  Up     gauss   V100R003C20SPC112  Slave   Normal      deploydbsvr-10_109_178_191-4   --         717445868     off
    • Master indicates the master instance, and Slave indicates the standby instance.
    • 10.109.178.191 indicates the IP address of the node where the database instance resides, and 32084 indicates the number of the port used by the database instance.
    • -- indicates a single-instance node. There is no replication status for a single node.

  3. Run the following command and enter the password of the root user to switch to the root user:

    su - root

    Default password: QAZ2wsx@123!

  4. Run the following command to query the node where etcd is deployed:

    kubectl get pod -n fst-manage | grep etcd-server

    etcd-server-paas-10-118-29-104               1/1       Running   0          1h
    etcd-server-paas-10-118-29-122               1/1       Running   0          1h
    etcd-server-paas-10-118-29-79                1/1       Running   0          1h

    The following command uses the etcd-server-paas-10-118-29-104 container as an example:

    kubectl -n fst-manage describe pod etcd-server-paas-10-118-29-104 | grep Node

    Node:           manage-cluster2-042b265b-7wk4r/10.118.29.104

Translation
Download
Updated: 2019-06-14

Document ID: EDOC1100062366

Views: 775

Downloads: 9

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next