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-31000 Failed to Automatically Back Up Database Instance

ALM-31000 Failed to Automatically Back Up Database Instance

Description

This alarm is generated when automatic database backup fails.

Attribute

Alarm ID

Alarm Severity

Alarm Type

31000

Major

Integrity violation

Parameters

Parameter Name

Parameter Description

Database instance

Indicates the name of the database instance for which this alarm is generated.

NOTE:

If the value of this parameter is managerFile, this alarm is triggered by a file backup failure, not by a database instance backup failure. This alarm is generated only when the scheduled backup of database instances in the OM zone fails.

Host

Indicates the IP address of the node running the database instance for which this alarm is generated.

Location Infor

The database instance ID and the IP address of the slave node where the alarm occurred.

Impact on the System

The automatic backup fails, and no backup data is generated for recovery.

Possible Causes

  • The database instance status is abnormal.
  • The backup directory does not exist or relevant permissions are incorrect.
  • Sufficient disk space is not available for the backup directory (either local or remote) or the /var/share directory on the host.
  • The network connection between the server where the backup path is located and the backup node is abnormal.

Procedure

Figure 17-7 shows the alarm handling procedure.

Figure 17-7 Alarm handling flowchart
  1. View the alarm location information in the alarm list to confirm the instance and node where data fails to be backed up.

    1. Use a browser to log in to the FusionStage OM zone console.
      1. Log in to ManageOne Maintenance Portal.
        • Login address: https://Address for accessing the homepage of ManageOne Maintenance Portal:31943, for example, https://oc.type.com:31943.
        • The default username is admin, and the default password is Huawei12#$.
      2. On the O&M Maps page, click the FusionStage link under Quick Links to go to the FusionStage OM zone console.
    2. Choose Application Operations > Application Operations > Alarm Center > Alarm List from the main menu on the FusionStage OM system. On the Alarm List page, click the icon next to this alarm to open the Alarm Details page.
    3. On the Alarm Details page, view and record Generation Time, Database instance, and Host.

  2. Check the policy used for backing up the database instance.

    1. Choose Application Development > Database > Backup List page, search for the historical backup task that is collected in 1.

      The search meets the following conditions:

      • Timestamp is close to the alarm occurrence time collected.
      • Operation Type is auto.
      • Result is Failure.
    2. Choose Application Development > Database > Backup Policy from the main menu on the FusionStage OM system. On the Backup Policy page, view details of the backup policy with the name recorded in 1. Check whether the backup mode is local backup or remote backup.

  3. Check the instance status.

    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 the status of the database instance for which this alarm is generated:

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

      ./dbsvc_adm -cmd query-db-instance

      • If the instance status is Abnormal, rectify the fault by referring to "DBM Cases" > "Checking the Database Instance Replication Status Is Abnormal" in the "Troubleshooting Guide".
      • If the instance status is Normal, go to the next step.

  4. Check the backup directory.

    NOTE:

    According to the backup mode queried in 2, if the backup mode is local backup, perform 4.a to 4.c. For remote backup, perform 4.a to 4.d.

    1. Use PuTTY to log in to the active and standby database nodes.

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

    2. Run the following command to switch to the root user:

      su - root

      The default password is QAZ2wsx@123!.

    3. Check whether the /opt/pub/backup_local directory is available in the local backup directory and whether the owner is dbuser:dbgroup and the permission is 750.

      ls -ald /opt/pub/backup_local

      If the directory does not exist or the owner or permission is improper, run the following commands to create the directory and change the owner and permission:

      mkdir -p /opt/pub/backup_local

      chown dbuser:dbgroup /opt/pub/backup_local

      chmod 750 /opt/pub/backup_local

    4. Connect to the remote backup server and check the backup directory and the owner and permission.

      In this section, the remote backup username is sftpuser, the user group is sftpgroup, the server IP address is 10.60.30.12, and the backup directory is /ftpboot/remote_backup. Replace them as required.

      sftp sftpuser@10.60.30.12

      Input password:

      After the connection is successful, run the following command to check the owner and permission:

      ls -al /ftpboot/

      If the directory does not exist or the owner or permission is improper, run the following commands to create the directory and change the owner and permission:

      mkdir -p /ftpboot/remote_backup

      chown sftpuser:sftpgroup /ftpboot/remote_backup

      chmod 750 /ftpboot/remote_backup

  5. Check whether the disk space is sufficient.

    NOTE:

    According to the backup mode queried in 2, if the backup mode is local backup, perform •Local backup. For remote backup, perform •Local backup and •Remote backup.

    • Local backup
    1. Use PuTTY to log in to the node where the database backup is deployed.

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

    2. Run the following command to switch to the root user:

      su - root

      The default password is QAZ2wsx@123!.

    3. Run the following command to check whether the disk space is sufficient:

      df -h

      If the disk space is insufficient, contact the environment administrator to clear the disk.

    • Remote backup
    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 command to connect to the remote server:

      sftp sftpuser@Remote server IP address

      Input password:
    3. After the connection is successful, run the following command to check whether the disk space is sufficient:

      df -h

      If the disk space is insufficient, contact the environment administrator to clear the disk.

  6. Check the network connection between the server where the backup directory is located and the backup node.

    1. Use PuTTY to log in to the database nodes manage_db1_ip and manage_db1_ip.

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

    2. Run the following command to check the network connection:

      ping Backup server node IP address

      • If the network connection is normal, go to 7.
      • If the network connection is abnormal, contact the environment administrator to rectify the network connection fault.

  7. Manually back up the database instance.

    1. Choose Application Development > Database > RDBMS from the main menu of the FusionStage OM system.
    2. On the RDBMS page, select the database instance.
    3. Click Manual Backup. In the displayed dialog box, select the backup policy identified in 2.
    4. Click OK to issue the manual backup task.
    5. Check whether the backup task is successful.
      • If the task is successful, no further action is required.
      • If the task fails, go to 8.

  8. Collect information generated during alarm handling and send it to the administrator for further troubleshooting.

Alarm Clearing

  • This alarm is automatically cleared after the fault is rectified.
  • This alarm is automatically cleared when the same backup policy bound to the same instance is automatically backed up again.

Related Information

None

Translation
Download
Updated: 2019-08-30

Document ID: EDOC1100062365

Views: 37538

Downloads: 31

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