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).
FAQs About the Unified Backup and Restoration of ETCD

FAQs About the Unified Backup and Restoration of ETCD

NOTE:

Replace variables in the following commands with true values when checking and rectifying faults.

  • backup directory: indicates the SFTP data backup directory configured in the tenant management zone.
  • name of the backup file: indicates the backup file name of a backup task selected in the tenant management zone during restoration.
  • etcd: indicates the name of the ETCD cluster that is backed up and restored.
  • namespace where the etcd cluster is deployed: indicates the name of a namespace where the ETCD cluster that is backed up and restored is deployed.
Table 3-27 List of FAQs

Error Message

Troubleshooting

cluster unhealthy

The ETCD cluster is in the abnormal state. You need to check the status of the ETCD cluster.

The troubleshooting procedure is as follows:

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

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

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

    su - root

    Default password: QAZ2wsx@123!

  3. Check whether all pod statuses are Running.

    kubectl get pods -n {namespace where the etcd cluster is deployed} | grep etcd

    • If the pod status is normal, the cluster status may be abnormal during task processing. Create a task again.
    • If the pod status is abnormal, rectify the cluster fault first.

failed to save snapshot

Snapshots fail to be saved on the local disk. There is a probability that it is caused by an I/O exception. Create a task and obtain logs for R&D engineers to locate the fault.

Obtain the log etcd-backup.log in the /var/paas/sys/log/etcd-backup/ directory from the host where the faulty instance resides.

NOTE:

To prevent logs from being dumped or aged, obtain logs in time.

failed to download file

The system is faulty when downloading a file.

In the UDS scenario, you need to check whether the target file is in a specified bucket and the bucket can be read.

  1. Log in to the console and go to the OBS page.
  2. Check whether a bucket exists in the bucket list.
    • If a bucket does not exist, all buckets have been deleted and backup data has been lost. Create a bucket again.
    • If there is a bucket, click the bucket to go to the bucket details page. On the bucket details page, check whether the bucket can be read.
    • If there is a bucket, click the bucket to go to the bucket details page. On the bucket details page, check whether the target file exists.

      If the target file does not exist, backup data has been lost.

      If the target file exists, obtain logs and contact R&D engineers for fault location.

In the SFTP scenario, you need to check whether the backup file exists and its directory can be read.

  1. Check whether the backup file exists.

    cd backup directory/etcd_backup/{etcd}/

    ls | grep {name of the backup file}

    If the command output does not contain the backup file, create a restoration task based on the backup file generated during backup.

    If the command output contains the backup file, go to 2.

  2. Check whether the SFTP server user can read the backup file.

    ls -al | grep {name of the backup file}

    Check whether the SFTP server user has the read permission (r). If no, run the chmod command to add the read permission. You can also create a restoration task as the SFTP server user. The SFTP server user is the user created using the backup file.

failed to upload file

The system is faulty when downloading a file.

In the UDS scenario, you need to check whether the target file is in a specified bucket and the bucket can be written

  1. Log in to the console and go to the OBS page.
  2. Check whether a bucket exists in the bucket list.
    • If a bucket does not exist, create a bucket and add the read/write permission to the bucket.
    • If there is a bucket, click the bucket to go to the bucket details page. On the bucket details page, check whether the bucket can be written.

In the SFTP scenario, you need to check whether the backup file directory exists and can be written.

  1. Log in to the SFTP server.
  2. Check whether the backup directory exists.

    cd {backup directory}

    • If "No such file or directory" is displayed, the backup directory does not exist. Create a backup directory and add the permission value 750 level by level.
    • If "Permission denied" is displayed, the user has no permission to access this directory. Add the read/write permission for the user or reconfigure SFTP information as the directory creator, and recreate a task.
    • If no exception is displayed, run the following command to check whether the SFTP server user has the write permission (w). If no, add the write permission for the user.

      cd ../ ; ll

have task running

A task is being processed. You cannot create another task until the task is successfully processed.

uds not available

  • Check whether AK/SK authentication information in UDS parameters is correct.
  • Check whether the IP address information in UDS parameters is correct.
  • Check the bucket, permission, and target file.
    1. Log in to the console and go to the OBS page.
    2. Check whether a bucket exists in the bucket list.

      If a bucket does not exist, all buckets have been deleted or uncreated. Create a bucket.

      If there is a bucket, click the bucket to go to the bucket details page. On the bucket details page, check whether the bucket can be read and written.

      NOTE:

      If there is a bucket during restoration, click the bucket to go to the bucket details page. On the bucket details page, check whether the target file exists.

sftp not available

You need to check whether it is caused by the following conditions:

  • The backup directory does not exist on the SFTP server or the permission is restricted.
    1. Log in to the SFTP server.
    2. Check whether the backup directory exists.

      cd {backup directory}

      If "No such file or directory" is displayed, the backup directory does not exist. Create the directory level by level and assign the permission value 750 to the directory level by level.

      If "Permission denied" is displayed, the user has no permission to access this directory. Run the chmod command to add the read/write permission for the user or reconfigure SFTP information in the tenant management zone as the directory creator, and recreate a task.

  • You cannot create a subdirectory in the backup directory as the SFTP server user.
    1. Log in to the SFTP server.
    2. Create a subdirectory.

      cd {backup directory}

      mkdir etcd_backup

      If the command output shows that the SFTP server user has no permission to create a subdirectory, run the chmod command to add the read/write permission for the user.

  • The file to be restored does not exist or has been damaged.
    1. Log in to the SFTP server.
    2. Check whether the restoration file exists.

      cd {backup directory}/etcd_backup/{etcd}/

      ls | grep {name of the backup file}

      If the command output does not contain the restoration file, create a restoration task based on the backup file generated during backup.

      If the command output contains the restoration file, go to 3.

    3. Check whether the restoration file is normal.

      tar -xzf {name of the backup file}

      cd backup

      vi snapshot.db

      If the restoration file can be opened and data is displayed, the restoration file is normal. Otherwise, the restoration file has been damaged and cannot be restored. In this case, back up the file again.

  • The entered sftp user name or password is incorrect.

    Use tools, such as PuTTY, to log in to the SFTP server and check whether the password is correct.

execute ssh command failed

You need to check whether it is caused by the following conditions:

  • OCheck whether the trust relationship among nodes manage_lb1_ip, manage_lb2_ip has been added.
    1. Check the trust relationship between nodes.

      Log in to the manage_lb1_ip node as the paas user and check its trust relationship with the manage_lb2_ip node.

      scp -o StrictHostKeyChecking=no paas@manage_lb2_ip node ip:/opt/paas/backup_cfe/etcd_backup/test file/var/paas/run/

      If you can copy a test file without the password input warning, the trust relationship is normal. Otherwise, re-add the trust relationship between nodes and go to 3.

      Repeat the preceding operations to check the trust relationship between other nodes.

    2. Check whether the node is free of encryption.

      Log in to the manage_lb1_ip node as the paas user and run the following command:

      scp -o StrictHostKeyChecking=no paas@manage_lb1_ip node ip:/opt/paas/backup_cfe/etcd_backup/test file/var/paas/run/

      If you can copy a test file without the password input warning, the trust relationship is normal. Otherwise, re-add the trust relationship between nodes and go to 3.

    3. Add the trust relationship on the manage_lb1_ip node.

      ./fsadm solution HEC -c addvm -p all

  • Log in to the background and check whether the paas user password has expired.

    Log in to the manage_lb1_ip, manage_lb2_ip nodes respectively as the paas user. If the login password has expired, reset it.

Others

Contact Technical Support.

Translation
Download
Updated: 2019-06-14

Document ID: EDOC1100062366

Views: 824

Downloads: 9

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