Note

You are viewing the documentation for an older release of Interworx (7.1). To see documentation for the current generally available release of Interworx, click here: 7.13.

InterWorx Database Backup Failed Message

How the Issue Manifests

  • The InterWorx Database Backup problem detector sends an email stating “InterWorx database backup has failed. InterWorx will attempt to make a backup at the next daily cron run. If you continue to receive this message please restore your latest InterWorx backup or contact support.”

  • The following message appears in NodeWorx under Server > System Health:

    iworxdb backup fail problem detector

Cause of the Issue

Every day, the iworx daily cron attempts to create a backup of the iworxdb (the internal InterWorx database, not to be confused with the system MySQL/user databases). Part of this task is to check all of the tables for potential corruption. If any table crashes or database corruptions are found, instead of backing up the iworxdb, a database tuneup script runs to resolve those issues. The backup process is then flagged to attempt again the next day. This is to prevent the possibility of backing up a corrupt database.

How to Resolve

Generally speaking, nothing needs to be done to resolve this issue. 99% of the time, when the next daily cron runs, the backup will succeed, and the problem detector alert will clear itself. It is only to be considered an issue if there is an alert two or more days in a row. If that occurs, submit a ticket to the InterWorx support desk.

If clearing the message immediately is required, this can be completed by manually running the iworx daily cron.

Warning

Running the daily cron manually is not recommended on servers with many accounts, as doing so will re-trigger tasks such as log rotation and scheduled daily backups, which may take a long time to complete and cause unexpected higher load during peak hours. Waiting until the next daily cron runs automatically is the recommended procedure.

  1. Log in to the server at the CLI as root, either via SSH or from the terminal

  2. At the CLI, run the following:

    ~iworx/cron/iworx.pex --daily

  3. After the daily cron completes, log into NodeWorx from the browser (https://ip.ad.dr.ess:2443/nodeworx)

  4. In NodeWorx, navigate to Server > System Health

  5. Click Refresh at the top of the page