ALM-12034 Periodical Backup Failure

Description

The system executes the periodic backup task every 60 minutes. This alarm is generated when a periodical backup task fails to be executed. This alarm is cleared when the next backup task is executed successfully.

Attribute

Parameters

Impact on the System

The periodic backup task failed, resulting in no available backup packages during the time period when the backup failed. When a system exception occurs and you need to use the backup package to restore data, no backup package is available during the failure period. As a result, data during the failure period cannot be restored.

Possible Causes

The alarm cause depends on the task details. Handle the alarm according to the logs and alarm details.

Procedure

Check whether the disk space is sufficient.

1. In the FusionInsight Manager portal, click O&M > Alarm > Alarms.
2. In the alarm list, click in the row where the alarm is located and obtain TaskName from Location.
3. Log in to the active node of the cluster as the root user and check the backup and restoration logs in /var/log/Bigdata/controller/backup/.

   For details about how to log in to a cluster node, see Logging In to an MRS Cluster Node.

   cd /var/log/Bigdata/controller/backup/

   Run the ll command to view the log name. The following is an example of the command output:

   [root@xxx backup]#ll
   total 4476
   -rw------- 1 omm wheel    4205 Jun 10 14:14 backupplugin_ctl.log
   -rw------- 1 omm wheel  158640 Jun 11 00:02 backupplugin.log
   -rw------- 1 omm wheel 4405518 Jun 11 10:28 controller_backup.log

   Run the following command to check the backup and restoration logs:

   vi Log file name

   Check whether the log file contains information similar to the following:

   Upload backup files to *** file failed, error info: ***

   • If yes, go to Step 4.
   • If no, go to Step 7.

4. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management. Locate the backup task based on TaskName, click Configure in the Operation column, and check whether all configuration items are correctly configured.
   • If yes, go to Step 7.
   • If no, modify the configuration, save the modification, and go to Step 5.

5. Choose More > Back Up Now to start the backup task and check whether the backup task is successfully executed.
   • If yes, go to Step 6.
   • If no, go to Step 7.

6. After 2 minutes, check whether the alarm is cleared.
   • If yes, no further action is required.
   • If no, go to Step 7.

7. Choose More > View History in the Operation column. In the displayed dialog box view the task details.
   Figure 1 View History
   

8. In the displayed dialog box and click to check whether the following message is displayed: Failed to backup xx due to insufficient disk space, move the data in the /srv/BigData/LocalBackup directory to other directories.
   • If yes, go to Step 9.
   • If no, go to Step 16.

9. Choose Backup Path > View and obtain the Backup Path.
10. Log in to the node as user root and run the following command to view the node mounting details.

    df -h

11. Check whether the available space of the node to which the backup path is mounted is less than 20 GB.
    • If yes, go to Step 12.
    • If no, go to Step 16.

12. Check whether there are many backup packages in the backup directory.
    • If yes, go to Step 13.
    • If no, go to Step 16.

13. Remove the backup package from the backup directory or delete the backup package to ensure that the available space of the node to which the backup directory is mounted is greater than 20 GB.
14. After the problem is resolved, perform the backup task again and check whether the backup task execution is successful.
    • If yes, go to Step 15.
    • If no, go to Step 16.

15. After 2 minutes, check whether the alarm is cleared.
    • If yes, no further action is required.
    • If no, go to Step 16.

Collect fault information.

16. On the FusionInsight Manager portal, choose O&M > Log > Download.
17. Select Controller from the Service and click OK.
18. Click in the upper right corner, and set Start Date and End Date for log collection to 10 minutes ahead of and after the alarm generation time, respectively. Then, click Download.
19. Contact the O&M personnel and send the collected log information.

Alarm Clearing

After the fault is rectified, the system automatically clears this alarm.

Related Information

None