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 Alarm and Event Reference 04

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).
ALM-9206 Failure to Back up Data

ALM-9206 Failure to Back up Data

Description

The backup and restoration module automatically backs up the data to the local directory at 02:00 every day and uploads the backup files to the third-party server every 30 minutes.

This alarm is generated when the backup and restoration module fails to automatically back up data, execute backup operations, or upload the backup files to the third-party server. The corresponding error codes and error information will be displayed in the additional information about the alarm.

Attribute

Alarm ID

Alarm Severity

Auto Clear

9206

Major

Yes

Parameters

Name

Meaning

Fault Location Info

None

Additional Info

  • FTP_Address: specifies the address, IP address, or domain name of the FTP server.

Impact on the System

  • When the backup and restoration module fails to back up the data to the local directory, the data generated on that day is not backed up.
  • When a backup operation fails, data of this backup is absent from the system.
  • When the backup and restoration module fails to upload a backup file to the third-party server, the backup file will not exist on the third-party server.

Possible Causes

The backup and restoration module fails to automatically back up the data, execute the backup operation, or upload the backup files to the third-party server.

Procedure

  1. Identify the cause of the alarm.

    The following table can be used for reference.

    SN

    Error Code

    Description

    Troubleshooting Method

    1

    10409101

    The backup and restoration module fails to automatically back up the data because of an internal error.

    Perform the operations provided in Troubleshoot problem 8.

    2

    10409106

    The backup and restoration module fails to automatically back up the data because the database is abnormal.

    Perform the operations provided in Troubleshoot problem 1.

    3

    10409108

    The backup and restoration module fails to automatically back up the data because the local host has insufficient backup storage space.

    Perform the operations provided in Troubleshoot problem 2.

    4

    10409109

    The backup and restoration module fails to automatically back up the data because the serial number of the backup files on the local host exceeds the threshold.

    Perform the operations provided in Troubleshoot problem 3.

    5

    10409301

    The backup and restoration module fails to upload the backup files to a third-party server because of an internal error.

    Perform the operations provided in Troubleshoot problem 8.

    6

    10409309

    The backup and restoration module fails to upload the backup files to a third-party server because the number of the backup files on the local host exceeds the threshold.

    Perform the operations provided in Troubleshoot problem 4.

    8

    10409311

    The backup and restoration module fails to upload the backup files to a third-party server because the third-party server cannot be accessed.

    Perform the operations provided in Troubleshoot problem 6.

    9

    10409316

    The backup and restoration module fails to upload the backup files to a third-party server because the number of the backup files on the local host exceeds the threshold.

    Perform the operations provided in Troubleshoot problem 7.

    10

    10409327

    Backup timed out.

    Perform the operations provided in Troubleshoot problem 8.

Troubleshoot problem 1.

  1. Use PuTTY to log in to the host where Service OM is deployed.

    Ensure that the Service OM management floating IP address and username galaxmanager are used to establish the connection.

    Default username: galaxmanager ; default password: IaaS@OS-CLOUD9!

    NOTE:

    Log in to the FusionSphere OpenStack web client. For details, see Logging In to the FusionSphere OpenStack Web Client (ManageOne Mode). Choose Cloud Service > FusionSphere OpenStack OM and view VM List to obtain the management floating IP address.

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

    su - root

    The default password is IaaS@OS-CLOUD8!.

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  4. Run the following command to check the database status:

    galaxmanager status|grep gaussDB

  5. Check whether the database is normal.

    • If information displayed contains "status:abnormal", the database is abnormal. Go to 7.
    • If information displayed contains "status:normal", the database is normal. Go to 9.

  6. Run the following command to stop the database:

    gaussDB stop

  7. Wait for two minutes after the database is stopped, and perform 5 to check the database state.
  8. Log in to the Alarm page and manually clear the alarm.

    • If the alarm is cleared, no further action is required.
    • If the alarm fails to be cleared, go to 54.

Troubleshoot problem 2.

  1. Use PuTTY to log in to the host where Service OM is deployed.

    Ensure that the management IP address of the host accommodating Service OM and username galaxmanager are used to establish the connection.

  2. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  3. Run the following command to query the space of the partition where the backup directory is stored:

    df -m

    Filesystem                     Size  Used Avail Use% Mounted on
    /dev/vda1                      6.0G  1.3G  4.7G  22% /
    devtmpfs                       4.8G     0  4.8G   0% /dev
    tmpfs                          4.8G     0  4.8G   0% /dev/shm
    tmpfs                          4.8G  505M  4.4G  11% /run
    tmpfs                          4.8G     0  4.8G   0% /sys/fs/cgroup
    /dev/mapper/vg_om-lv_home      5.0G   33M  5.0G   1% /home
    /dev/mapper/vg_om-lv_sysback  1014M   33M  982M   4% /sysback
    /dev/mapper/vg_om-lv_var       4.0G   98M  3.9G   3% /var
    /dev/mapper/vg_om-lv_tmp       3.0G   33M  3.0G   2% /tmp
    /dev/mapper/vg_om-lv_log       6.0G   87M  6.0G   2% /var/log
    /dev/mapper/vg_om-lv_goku      8.0G   81M  8.0G   1% /var/log/goku
    /dev/mapper/vg_om-lv_opt        10G  2.0G  8.0G  20% /opt
    /dev/mapper/vg_om-lv_gmbackup  6.0G   55M  6.0G   1% /opt/gmbackup
    /dev/mapper/vg_om-lv_data       21G   43M   21G   1% /opt/goku/data
    /dev/mapper/vg_om-lv_db        6.0G  418M  5.6G   7% /opt/goku/data/db
    tmpfs                          983M     0  983M   0% /run/user/0
    tmpfs                          983M     0  983M   0% /run/user/2000    

    Information about the space occupied in each partition is displayed.

    Locate /opt in the sixth column (Mounted on), locate the fourth column (Avail) in the row that contains /opt, and check whether the available disk space is less than 900:

    • If yes, go to 13.
    • If no, go to 9.

      900 in this step is only a reference value. The disk space required in the backup task in practice depends on the actual volume of data to be backed up. If a large amount of data needs to be backed up, reserve a large disk space for the backup task.

  4. Run the following command to switch to the /opt/gmbackup/db directory:

    cd /opt/gmbackup/db

  5. Run the following command to query the files and directories in the /opt/gmbackup/db directory:

    ls

  6. Check whether invalid files and directories exist in the /opt/gmbackup/db directory.

    • If yes, go to 16.
    • If no, go to 18.
    NOTE:

    For details about the method for verifying the validity of a directory or file, see Related Information.

  7. Run the following command to delete each invalid file and directory from the /opt/gmbackup/db directory one by one:

    rm -r Name of an invalid file or directory

  8. Go to 12.
  9. Run the following command to switch to the /opt/gmbackup/db/manualbk directory:

    cd /opt/gmbackup/db/manualbk

  10. Run the following command to query files and directories in the /opt/gmbackup/db/manualbk directory:

    ls

  11. Check whether invalid files and directories exist in the /opt/gmbackup/db/manualbk directory.

    • If yes, go to 21.
    • If no, go to 23.

  12. Run the following command to delete each invalid file and directory from the /opt/gmbackup/db/manualbk directory one by one:

    rm -r Name of an invalid file or directory

  13. Go to 12.
  14. Run the following command to switch to the /opt/gmbackup/db directory:

    cd /opt/gmbackup/db

  15. Run the following command to view the configured number of the files that are automatically backed up:

    modConfig backup -l | grep "MAX_AUTO_BACKUP_NUM"

    NOTE:

    If the number is not set, the default value is 7.

  16. Run the following command to view the backup files in the /opt/gmbackup/db directory:

    ls

    NOTE:

    For details about the naming rules of backup files, see Related Information.

  17. Check whether the number of backup files in the /opt/gmbackup/db directory is greater than the configured number of the files that are automatically backed up.

    • If yes, go to 27.
    • If no, go to 29.

  18. Run the following command to delete the backup file with the smallest serial number:

    rm -r Name of the file with the smallest serial number

    NOTE:

    For details about how to obtain the serial number of a backup file, see Related Information.

  19. Go to 12.
  20. Run the following command to switch to the /opt/gmbackup/db/manualbk directory:

    cd /opt/gmbackup/db/manualbk

  21. Run the ls command to check whether the backup files exist in the /opt/gmbackup/db/manualbk directory.

    • If yes, go to 31.
    • If no, go to 54.

  22. Run the following command to delete the backup file with the smallest serial number:

    rm -r Name of the file with the smallest serial number

  23. Go to 12.

Troubleshoot problem 3.

  1. Use WinSCP to log in to the host where Service OM is deployed as user galaxmanager.
  2. Switch to the /opt/gmbackup/db directory and check whether the backup files whose serial number is greater than 4294967295 exist.

    • If yes, delete such files and go to 9.
    • If no, go to 9.
    NOTE:

    For details about how to obtain the serial number of a backup file, see Related Information.

Troubleshoot problem 4.

  1. Use WinSCP to log in to the host where Service OM is deployed as user galaxmanager.
  2. Switch to the /opt/gmbackup/db directory and check whether the backup files whose serial number is greater than 4294967295 exist.

    • If yes, delete such files and go to 37.
    • If no, go to 37.
    NOTE:

    For details about how to obtain the serial number of a backup file, see Related Information.

  3. Switch to the /opt/gmbackup/db/manualbk directory and check whether the backup files whose serial number is greater than 4294967295 exist.

    • If yes, delete such files and go to 9.
    • If no, go to 9.

Troubleshoot problem 6.

  1. Obtain the IP address of the third-party server and the guide for configuring the FTPS service on the third-party server.
  2. Use PuTTY to log in to the host where Service OM is deployed.

    Ensure that the management IP address of the host accommodating Service OM and username galaxmanager are used to establish the connection.

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  4. Run the following command to check whether the communication between the host accommodating Service OM and the third-party server is normal:

    ping IP address of the third-party server, for example, ping 192.168.41.10

    The network communication is normal if the following information is displayed:

    ping 192.168.41.10 (192.168.41.10) 56(84) bytes of data. 
    64 bytes from 192.168.41.10: icmp_seq=1 ttl=64 time=0.035 ms 
    64 bytes from 192.168.41.10: icmp_seq=2 ttl=64 time=0.028 ms 
    64 bytes from 192.168.41.10: icmp_seq=3 ttl=64 time=0.025 ms     

  5. Check whether the communication between the host and the third-party server is normal.

    • If yes, go to 43.
    • If no, go to 54.

  6. Check whether the FTPS service on the third-party server is normal.

    • If yes, go to 9.
    • If no, restore the service by following the steps in the guide for configuring the FTPS service on the third-party server.
    NOTE:

    Check whether the FTPS service is normal by following the steps in the guide for configuring the FTP service on the third-party server.

  7. Go to 9.

Troubleshoot problem 7.

  1. Use PuTTY to log in to the host where Service OM is deployed.

    Ensure that the management floating IP address of the host accommodating Service OM and username galaxmanager are used to establish the connection.

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

    su - root

    The default password is IaaS@OS-CLOUD8!.

  3. Run the following command to disable user logout upon system timeout:

    TMOUT=0

  4. Run the following command to switch to the /opt/gmbackup/db directory:

    cd /opt/gmbackup/db

  5. Run the following command to view the configured number of the files that are automatically backed up:

    modConfig backup -l | grep "MAX_AUTO_BACKUP_NUM"

    NOTE:

    If the number is not set, the default value is 7.

  6. Run the following command to view the backup files in the /opt/gmbackup/db directory:

    ls

    NOTE:

    For details about the naming rules of backup files, see Related Information.

  7. Check whether the number of backup files in the /opt/gmbackup/db directory is greater than the configured number of the files that are automatically backed up.

    • If yes, go to 52.
    • If no, go to 9.

  8. Run the following command to delete the backup files whose serial number is relatively small until the number of backup files in this directory is equal to that of the files that are automatically backed up:

    rm -r Name of the file with the relatively small serial number

    NOTE:

    For details about how to obtain the serial number of a backup file, see Related Information.

  9. Go to 9.

Troubleshoot problem 8.

  1. Contact technical support for assistance.

Related Information

  1. The naming rule for backup files is as follows: gmdb-YYYY-MM-DD-serial number.dump. YYYY indicates the year, MM indicates the month, and DD indicates the day. The serial numbers are positive integers that are not greater than 4294967295. For example, gmdb-2012-07-12-1.dump was generated on July 12, 2012 and its serial number is 1.
  2. The valid directory in the /opt/gmbackup/db directory is: manualbk
  3. The valid file in the /opt/gmbackup/db directory is in the following formats:
    • gmdb-YYYY-MM-DD-serial number.dump
    • lftp.out
  4. The valid file in the /opt/gmbackup/db/manualbk directory is in the following formats:
    • gmdb-YYYY-MM-DD-serial number.dump
    • lftp.out
Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 34370

Downloads: 31

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