This is how you find out by email when a backup fails, ends with warnings or does not happen at all. At the end you also know whether the emails of your website arrive.
Step 1: Enter recipients
In the WordPress menu, open cloneworx, then Settings. The tile Notifications is already expanded, in both views.
- Email addresses holds the recipients. In the empty field, the admin address of the website appears in grey.
- On errors and warnings is on by default.
- On success is off by default.
- When the last valid backup is older than the plan allows is on by default.
- Save saves the addresses.
- Subscribe to the newsletter opens the sign-up form for news from cloneworx in a new tab. This has nothing to do with the messages about your backups.
Enter up to 5 addresses, separated by commas, and click Save. The page reports Saved. If the field stays empty, the notifications go to the admin address of the website. The recipients are shown in the main tile after Notifications go to.
Step 2: Choose notifications
The three switches are saved immediately, without Save. The subject contains the name of the website in square brackets, for a backup also the name of the plan.
| Switch | An email comes | Subject |
|---|---|---|
| On errors and warnings | when a backup fails or ends with warnings, when a restore fails or has been undone, when a check finds a damaged backup, when a scheduled run could not start, when a plan that is switched on does not run on schedule and when cloneworx Backup Pro is installed but does not work |
[…] Backup failed: … […] Backup ended with warnings: … […] Restore failed […] Restore undone […] Backup check found damage: … backup(s) […] Scheduled backup of … could not start […] Scheduled backup of … did not run […] cloneworx Backup is not working correctly. You have to step in by hand! |
| On success | after every successful backup | […] Backup successful: … |
| When the last valid backup is older than the plan allows | when a plan becomes overdue, then every three days as a reminder |
[…] No valid backup for … […] Reminder: still no valid backup for … |
Every email is plain text in the language of the website. For a backup it lists the website, the plan, start, end, result, the targets with their state and a link to the Backup page, and in case of an error also the cause and the next step. No email contains credentials.
What the email says
For a failed backup the email states a cause and a next step:
| Cause | Next step |
|---|---|
| No target could be reached or written. | Check the targets on the Targets page and test the connection. |
| The plan encrypts its backups, but encryption is not possible at the moment. Nothing was written unencrypted instead. | With cloneworx Backup Pro active, the tile "Backup encryption" in the settings names what is missing. Without cloneworx Backup Pro or without a valid licence, save the plan in the plan editor to back up without encryption: this removes every setting of cloneworx Backup Pro from the plan. |
| The plan has exceptions of its own, but cloneworx Backup Pro is not active or its licence is not valid. Nothing was backed up. | Activate cloneworx Backup Pro with a valid licence, or save the plan in the plan editor: this removes every setting of cloneworx Backup Pro from the plan, also its exceptions. |
| The plan uses retention by age, but cloneworx Backup Pro is not active or its licence is not valid. Nothing was backed up: without cloneworx Backup Pro the backups of this plan would never be deleted. | Activate cloneworx Backup Pro with a valid licence, or save the plan in the plan editor with a number under Max. backups: this removes every setting of cloneworx Backup Pro from the plan. |
| Not enough free space. | Free up space in the uploads folder of the website or at the target. |
| This website is a Bedrock installation; cloneworx Backup does not back it up because such a backup could not be restored reliably. | Back up a Bedrock project with its own tools (repository, .env, composer). |
| The backup is larger than this 32-bit PHP can handle safely (limit 1.5 GiB). | Exclude large folders or files from the backup, or run the website on a 64-bit PHP. |
| The database is not MySQL or MariaDB. | This plugin can only back up MySQL and MariaDB databases. |
| A part of the package was damaged while it was written. | Run the backup again; if it happens again, have the disk of the server checked. |
| The job made no progress in ten steps in a row, so the watchdog ended it: either the server kills its steps before they get anywhere, or a target or the disk is so slow that a step does not finish one unit of work. | Look at the log. If the steps are being killed, lower the maximum time per step in the settings; if a target or the disk is slow, try again later or raise the maximum time per step. |
| The job stopped (…). | Look at the log of the backup. |
If a scheduled run could not start, the email states:
| Cause | Next step |
|---|---|
| The working folder in the uploads directory could not be created or written (no space, or no permission). | Free up space in the uploads folder of the website or fix its permissions, then run the plan by hand. |
| The database refused the entry of the job (a table of the plugin is missing or not writable). | Check the database tables of the plugin and the log, then run the plan by hand. |
| The job could not be prepared (…). | Look at the log, then run the plan by hand. |
Further sentences appear word for word in the emails:
| Sentence | |
|---|---|
| Backup with warnings | Warnings: … (unreadable …, vanished …, unsupported …, targets failed …, database notes …) |
| Check found damage |
Checked: … backup(s), damaged or incomplete: …, not reachable: … The backup list marks the damaged backups with a red cross. Make a new backup; a damaged one is never deleted automatically, delete it by hand when you have a new valid one. |
| Scheduled backup could not start | The plan “…” was due at …, but its run could not start. The plan counts as run and waits for its next time. |
| Scheduled backup did not run |
The plan “…” was due at …, but it did not run: without cloneworx Backup Pro only one plan runs on schedule, currently “…”. The plan “…” is switched on, but it does not run: its rhythm needs cloneworx Backup Pro, and cloneworx Backup Pro is not active or its licence is not valid. |
| cloneworx Backup Pro does not work |
cloneworx Backup Pro is installed on this website, but it does not work: it does not match the installed version of cloneworx Backup, or its installation is incomplete. This message comes until the problem is solved. |
| No valid backup |
The plan “…” has been active for … without a single valid backup. The plan “…” has been due for … since it was switched on or changed, without a new valid backup. The last valid backup of the plan “…” is … old; the plan allows …. |
| Reminder | You get this reminder every three days while the plan has no valid backup. |
| Test email |
This is a test email of cloneworx Backup. If you read it, notifications from this website reach this address. Sent at: … |
| every email, last line | Sent by cloneworx Backup. Notifications can be changed in the settings of the plugin. |
Step 3: Send a test email
In the main tile, click Send test email.
- Send test email sends an email to the recipients from step 1.
- The message Test email sent to …. lists the addresses.
The message means: WordPress has handed over the email. Only your inbox shows whether it arrives. The subject is […] Test email from cloneworx Backup.
The warning about an overdue backup
A plan is overdue when its last valid backup is older than its rhythm plus a fixed tolerance: half the rhythm, at least 6 hours. So a daily plan is overdue after 36 hours. A plan without a valid backup is overdue as soon as its first missed run is longer ago than the tolerance. A plan without a valid backup stays overdue until there is a valid backup, even if runs start and fail. After the plan is switched on, or after its rhythm or time is changed, an older backup does not count against the plan until its first scheduled time is exceeded by the tolerance.
The plugin checks this at every task source and when you open the dashboard or the plugin list of WordPress, at most every 15 minutes. The email states the cause and the next step. If the email cannot be handed over to the mail system, the plugin tries again after six hours. The next valid backup of the plan ends the warning, without an email.
You can also recognise an overdue plan in three places without an email:
- The status tile of the Overview page is red.
- On the WordPress dashboard and in the plugin list there is a red notice: A backup plan could not make a valid backup in time. Hide for three days hides it for you. With the next valid backup it disappears on its own. For each plan the notice states the cause and the next step; Open the Backup page opens the page of the plugin.
- Under Tools, Site Health, WordPress reports The last valid backup is too old as a critical issue.
Under Tools, Site Health, WordPress also reports Stored plugin data cannot be read if the plugin cannot read one of its stored settings. Otherwise WordPress reports The last backup failed, No backup plan is active or No valid backup yet there as a recommendation, and if none of these applies, Your website has a recent valid backup.
- The title states since when no backup has been made, with the name of the plan where applicable.
- Last valid backup shows the last valid backup and takes you to its log.
- The cause, the same as in the email.
- The next step, the same as in the email.
- Back up now starts a backup immediately.
Switching off the notification on errors
If you switch off On errors and warnings, the plugin asks: Switch off notifications?
- Cancel closes the dialog. The switch stays on.
- Yes, switch off switches the notification off.
Without this notification, no email is sent about failed backups
The plugin records the time of switching off. As long as the switch is off, the Overview page shows a red message below the status tile.
- Notification on errors and warnings is switched off in the settings. This is a security risk for your data.
- Dismiss removes the message until you open the page again.
- Open settings takes you to the Settings page.
If the email does not arrive
If sending the test email fails, the page shows it in two places:
- The main tile shows in red the last email that could not be sent, with reason and time.
- The red message states the reason for the failure.
- Show global log opens the global log.
| What happens | What you can do |
|---|---|
| The test email could not be sent. | The message is followed by the reason WordPress gives. Pass it on to your hosting provider. |
| No email address to send to. | The field is empty, and the website has no admin address. Enter an address. |
| One of the addresses is not valid. | Check the spelling of every address. Nothing is saved until all of them are valid. |
| The test email is sent but does not arrive. | Look in the spam folder. The plugin does not find out whether the email has arrived. |
Good to know
- No email is ever sent after an aborted backup.
- The red line in the main tile stays, even if later emails succeed. What counts is the time stated in it.
See also
- The “Settings” page
- The “Overview” page
- Start backups on time: set up a system cron
- When a backup fails or ends with warnings
- State, logs and support with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
You also set recipients and switches with WP-CLI. Switches accept on or off. There is no confirmation dialog before switching off on the command line.
# Show recipients, switches, warnings and last failure wp cloneworx-backup notify status # Set the recipients, separated by commas wp cloneworx-backup settings set notify_emails "eins@example.com, zwei@example.com" # Enable the email after every successful backup wp cloneworx-backup settings set notify_success on # Send a test email wp cloneworx-backup notify test # Check now whether a backup plan is overdue wp cloneworx-backup notify check