A backup ends with one of three results: Complete, With warnings or Failed. This article explains what the message means, where to find the reason and what you can do.
The three results
| Result | In the list of backups | Meaning |
|---|---|---|
|
green Complete |
green dot, type Full | Every target has the complete backup. Nothing was left out. |
|
yellow With warnings |
yellow dot, type Full | The backup counts as a valid backup. Something did not go smoothly, for example a file could not be read. |
|
red Failed |
red dot, type Failed | No target has the backup. The plugin removes what was already transferred from the targets again. |
A backup that you abort yourself is not an error: it appears with a grey dot in the list; the Type column says Aborted. The status tile of the Overview does not change because of it.
Step 1: Read the message
The result appears as a message below the main tile. A yellow or red message stays until you close it or start a new action.
- Below the reason for the error are the failed target and the cause.
- The original message: Message from the target is the last answer of the target, that is, of the server, the service or the provider behind it; Message from the client is the message of the software through which the plugin talks to the target: for SFTP that of the SSH library, for WebDAV, S3, Google Drive and Dropbox that of cURL.
- Log opens the log of this backup.
The message is not translated. Credentials, folders, users and server names are masked in it. The message is also in the log, there with the numbers from cURL and from the target.
If the message is already closed
The result of the last backup is also in the status tile of the Overview page. In the list of backups, More …, then Log takes you to the log.
- The last backup failed.
- Time, cause and the link to the log.
- Per target, the reason and the original message.
- The next step, matching the cause.
- Last valid backup shows time, size and target.
- Next attempt shows the next scheduled run.
Step 2: Open the log
Click Log. The lines of the log are in English.
- The time in the time zone of the website.
- The level: INFO, WARNING or ERROR. The message follows it.
- The details of the message.
- A warning. The details show the entry that was not backed up, and the reason.
- Copy log copies the log to the clipboard.
The log lists every entry that was not backed up with its path inside the website, at most 50 per reason. It only counts further ones. How to read the lines: Read the log.
Step 3: Fix the cause
The backup ended with warnings
- The message shows the number and kind of the warnings.
- The link opens the log of this backup.
- The cross closes the message.
| Kind | Meaning | What you can do |
|---|---|---|
| … not readable | A file or a folder could not be read. | On the server, check the permissions of the entry shown in the log. |
|
… vanished … changed while being read |
The file was no longer there during the backup, or it changed while being read. In that case the backup contains what was read. | If it keeps affecting the same folder, exclude it: Define what gets backed up. |
| … unsupported | The entry is not a file, not a folder and not a link. | Nothing. |
| … target(s) failed | One target does not have the backup, another has it complete. | See “Error at a target”. |
| … database note(s) | Notes from the export of the database. | Read them in the log. |
If a step is aborted three times at the same file, the plugin skips it, and the backup ends with warnings.
The backup failed
| Message | What you can do |
|---|---|
| No target is reachable. | Before backing up, the plugin connects to every target. No connection could be established. On the Targets page, choose More … at the target, then Test connection. |
| A target is not usable. | The target is disconnected or has no successful connection test. Test the connection or renew the credentials: Renew the credentials of a target. You connect a disconnected target in Google Drive or Dropbox on the Targets page with Connect again: Store backups in Google Drive, Store backups in Dropbox. |
| No target has the backup. | The transfer failed. The line about the target gives the reason. |
| Not enough free space. | The plugin checks the space before it writes: in the work folder on the web server and at every target. The backup ends with this message if the work folder does not have enough space or if no target has enough space. Nothing has been written then. Free up space there. If the space is insufficient at only one of several targets, the backup is transferred to the other targets and ends with warnings: see “Error at a target”. |
| The backup is larger than this 32-bit PHP can handle safely (limit 1.5 GiB). | The server runs a 32-bit PHP. The backup ends before it writes if files and database together would exceed the limit. Exclude large folders or files from the backup, or run the website with a 64-bit PHP. |
|
A part failed verification twice. Too many steps without progress. |
Start the backup again. If it fails again: Get help: support report, troubleshooting and diagnostics. |
| The database is not MySQL or MariaDB. | The plugin cannot back up this database. |
| This website is a Bedrock installation; cloneworx Backup does not back it up because such a backup could not be restored reliably. | The plugin does not back up a Bedrock installation. |
| The job state could not be saved. See the log. | The log has the details. Start the backup again. |
|
A table could not be read behind its key; the backup stopped instead of writing rows twice. See the log. A table failed three times at the same place; the job ended. See the log for the table. |
The log shows the table. If the backup fails again: Get help: support report, troubleshooting and diagnostics. |
Error at a target
| Message | What you can do |
|---|---|
| The target cannot be reached. Check the server name and the port; the host of this website may block the port. | Check the settings of the target and test the connection. |
| The target refused the login. Check user name and password. | The plugin tries the login again after 5 and after 15 seconds. Only after a repeated refusal does it mark the target as Disconnected. Then enter the credentials again. |
| Not enough free space there for a backup of this size. | The plugin checked the space before writing and skipped this target. The line below shows the space needed, the reserve and the free space: Needed: about … plus a reserve of …; free: …. Free up space at the target. |
| The target reports that there is no space left. | Free up space at the target. |
| Sending the data failed. Possible causes: the connection was interrupted, or there is no space left at the target. | Check the space at the target and start the backup again. |
If an error may be temporary, the plugin tries up to three times, with a pause in between.
Step 4: Start the backup again
Once the cause is fixed, start the backup by hand: Create a backup right now. The status tile of the Overview assesses the last finished backup.
Good to know
- With On errors and warnings, the plugin sends an email after such a backup: Set up email notifications.
- If the backup does not start, the page reports The backup could not be started: … with the reason. Show global log opens the global log.
See also
- Progress, messages and log
- Read the log
- The “Targets” page
- Adapt the plugin to your server
- State, logs and support with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
With WP-CLI you can see the state, test the target and start the backup again. If it fails, the command shows the last messages, the state of every target and the reason, in English. For an error at a target, the original messages are below: after target: the message from the target, after client: the message from the client, for cURL with its number.
# Show the state of the website, like the overview wp cloneworx-backup status # Show the backups with status and state per target wp cloneworx-backup backup list # Show the targets with ID and state wp cloneworx-backup target list # Test the connection of a target wp cloneworx-backup target test sftp-1 # Run the backup plan again wp cloneworx-backup plan run "Daily backup" # Write all logs to one file wp cloneworx-backup logs --to=logs.tar