Whether it is a backup, a check or a restore: while the plugin is working, it shows its progress, and at the end it reports the result. Both look the same on every page. This article explains what the progress display, the messages and the dialog window Log tell you.
Jobs and steps
A backup, a check, the deletion of a backup and a restore are jobs. A job never runs in one go, but in many short steps: web servers often stop a program like this plugin after about 30 seconds. Every step saves its state; the next step continues from there.
- Only one job runs at a time. As long as one is running, Back up now is blocked. If you start another job via a menu during that time, for example a check, the page reports in red A job is already running.
- A button that is disabled because a job is running names the reason in a tooltip: A job is already running.
- A job keeps running when you close the page. If you open it again, it shows the running job.
- The Overview and the Backup page also show jobs that the schedule or the command line started.
- While a job is running, you can change settings, backup plans and targets and read logs. The changes apply from the next job on. Deleting a backup or removing a target together with its backups is possible only after the end of the job: both are jobs themselves.
The progress display
- What the running backup is backing up and to which target, for example “Database, Files → SFTP 1”.
- The progress display shows the phase, the entries, the amount and the remaining time.
- Abort backup stops the job at the next step.
- Back up now is blocked as long as a job is running.
The parts of the line are separated by a dot. A part is missing if the phase does not count it.
| Part | Example | Meaning |
|---|---|---|
| Phase | Packing files | What the job is working on right now. |
| Entries | … of … entries | How many entries of the phase are done. During the export of the database these are rows of the tables, during packing files and folders. |
| Amount | “412 MB / 1.8 GB” | The amount done and the whole amount of the phase. From 1 GB on it is given in GB, below that in MB. |
| Time | about … left | The estimated remaining time. |
The line is refreshed every second from the saved state of the job. Where it appears depends on the page:
| Page | Location of the progress display |
|---|---|
| Overview | in the status tile |
| Backup | in the tile Backup |
| Targets | below the status tile, when checking, cleaning up, finding backups and removing together with backups |
| Restore | in the main tile, together with the step of the restore and a bar; during an import in the tile of the import |
| Settings | in the Extended view in the tile System and support, in the block Diagnosis |
The phases of a backup
| Display | What happens |
|---|---|
| Checking targets | The plugin connects once to every target. A target that cannot be reached is skipped and results in a warning. If no target remains, the job ends. |
| Listing files | The list of files and folders is built. |
| Checking free space | The plugin checks the free space in the work folder and at every target. |
| Exporting the database | The tables of the website are written to the backup. |
| Packing files | The files are written to the backup. The plugin reads every finished part once more to verify it. |
| Transferring to the targets | A finished part is transferred to all targets of this run and is then deleted from the work folder. While a part is being transferred to a target, the line reads Transferring to … with the name of the target and, if there are several targets, the number of the target, for example “Transferring to SFTP 1 (2 of 3)”. |
| Finishing the package | The index and, last, the info file are created. Only with the info file is a backup complete. |
| Updating the catalog | The plugin enters the backup into the catalog of every target. |
Exporting, packing and transferring alternate: every finished part is transferred to the targets before the next one is built. The line therefore jumps back and forth between these phases.
The phases of a restore
During a restore, the progress display shows these phases:
| Display | What happens |
|---|---|
| Preparing the build folders | The plugin creates its build folder inside every root folder. |
| Building the files next to the live folders | The plugin writes the files of the backup into the build folders. |
| Creating the tables | The plugin creates the tables of the backup next to the tables of the website. |
| Importing the rows | The plugin fills these tables with the rows from the backup. |
| Counting files that are not in the backup | The plugin counts the files in the uploads and in the root folder that are not in the backup. |
| Switching uploads and root files | The plugin switches uploads and files in the root folder file by file, outside the maintenance mode. |
| Switching over | In the maintenance mode of WordPress the plugin switches all tables at once, then core, plugins, themes and the rest of wp-content. After that the new website confirms itself. |
| Bringing the previous state back | Only after an error: the switch-over failed or the new website did not confirm itself, and the plugin switches back. |
| Completing in the new WordPress | Only when the database is restored, after the confirmation: the plugin flushes the object cache, rewrites the permalinks and sets up its schedule again. |
| Setting folder permissions | The plugin sets the permissions of the folders. It never sets owner and group. |
When the rollback is deleted, the phase is called Removing the previous state; when a restore is undone, it is called Undoing the restore.
Other jobs
| Display | Job |
|---|---|
| Checking backup | The check of one backup or of all backups at a target. |
| Deleting backup | Deleting a backup by hand. The same line is shown when you remove a target together with its backups. |
| Deleting outdated backups | The follow-up after a backup: the plugin deletes what exceeds Max. backups. |
| Cleaning up leftovers | Cleaning up leftovers of aborted jobs. |
| Finding backups | Finding backups at a target. |
| Verifying a part | The import of a backup from a file: the plugin reads every part against its checksum before it stores the backup at the target. The same line is shown during the database export of the diagnosis while it reads the export back. |
| Probe run | The probe run of the diagnosis. |
If the job reports no phase, the line reads Backup running for a backup and Job running for every other job. The steps of a restore are explained in The “Restore” page.
- The progress display of a check. Instead of entries it counts backups: Backup … of … shows the backup that the check is working on right now. If there is only one backup, this detail is omitted.
- Abort check
The follow-up after a backup
After every valid backup a second job starts on its own. It deletes the backups at the targets that exceed Max. backups and cleans up leftovers of aborted jobs. Its progress display appears only if it actually deletes something. A message also appears only then: One old backup deleted., … old backups deleted. or Leftovers cleaned up: … folders. If the deletion fails, it reports in yellow Deleting old backups failed.
The remaining time
The plugin estimates the time from the speed of the running phase: during the export of the database from the rows per second, during packing from the amount per second. During packing, the transfer that is still pending counts as well.
- about … left shows the time, rounded, in one unit: seconds, minutes, hours or days.
- calculating the remaining time … is shown at the start of a job as long as the plugin has not measured enough. An estimate from the first seconds would be unreliable.
- Once the line has shown a time for a job, this sentence does not appear again. In the last phases, often no time is shown any more.
While the database is being exported, the files do not count yet: the speed of packing is not known yet. In this phase, the time shown applies only to the database.
Abort a job
The link for aborting is directly below the progress display. It is named after the job: Abort backup for a backup, Abort deletion for deleting by hand, Abort cleanup for cleaning up leftovers and for retention, Abort check for a check, Abort search when finding backups, Abort restore for a restore, Abort import for an import, Abort probe run for a probe run and Abort diagnostic run for every other diagnosis. When a restore is being kept or undone, there is no link. There is no confirmation dialog.
- Abort requested; the job stops at the next step. The sentence replaces the link. If the job can no longer be aborted, it reads The job can no longer be aborted at this point.
The job does not stop immediately, but at the next point where it saves its state. What applies after that depends on the job:
- Backup: An aborted backup cleans up: it removes its work files and everything it has already transferred to the targets. The page reports in yellow Backup aborted. In the list of backups, the entry has a grey dot; the column Type reads Aborted. An aborted backup does not change the result of the status tile on the Overview.
- Checking a backup: The page reports in yellow Check aborted.
- Deleting a backup by hand: The message is red, for example The backup could not be deleted. See the log. What was deleted before the abort stays deleted; the backup may still be in the list. More on this: Delete a backup.
- Restore: A restore can be aborted until the switch-over begins. Until then the Restore page additionally shows the button Cancel. After that, the plugin refuses the abort, and the only option left is Undo restore.
The message
Every page shows its messages in one place: directly below the main tile. Only the message of the last action is visible at any time. If you start a new action, the previous message disappears, even a red one.
| Colour | Meaning | Behaviour |
|---|---|---|
| green | The action succeeded. | The message closes by itself after 8 seconds. |
| yellow | A warning: not everything went smoothly, or something is still missing. | The message stays until you close it or start a new action. |
| red | The action failed. | The message stays until you close it or start a new action. |
- The green message, here Backup complete.
- The bar at the top edge shrinks to the left and shows the remaining time. While the mouse pointer is on the message, the time stops.
- Dismiss closes the message immediately.
- The yellow message, here after a backup with warnings.
- Dismiss
- The link Log opens the log of this backup.
When the interface cannot reach the server
If a call from the interface to the server fails, a red message shows the reason:
| Message | Meaning |
|---|---|
| The connection between browser and server failed. Check your connection and try again. | The browser did not reach the server. |
| Your login is no longer valid. Open this page in a new tab. If WordPress asks you to log in there, log in. Then it continues. | Your login to WordPress is no longer valid. |
| The server did not answer in the expected form (HTTP …). Beginning of the answer: … | The answer of the server could not be read. The message shows the HTTP status and the beginning of the answer. |
| The server answered with HTTP … without a message. | The server answered with an error status and sent no text. |
| Error … | The server returned only a code; the message shows it. |
| Unexpected error in the browser: … | An error occurred in the browser that the interface does not know; the message shows it. |
| The page could not be drawn: …. Reload the page; if this happens again, send the support report. | The interface of the plugin ran into an error and shows this message instead of the page. |
| The status of the restore could not be read (…); trying again. | During a restore the page could not fetch the state. It keeps trying by itself. |
When the plugin refuses an action
If the plugin refuses an action, the message gives the reason. Every refusal is also recorded as a warning in the global log. The messages in detail:
Jobs
| Message | Meaning |
|---|---|
| Another job is running. | Only one job runs at a time. Wait until it has finished. |
| This job can no longer be aborted. | From the switch-over on, a restore can no longer be aborted. |
|
The job secret is not valid. The request is not valid. |
The call did not contain the data the plugin expects; the plugin discarded it. |
Targets
| Message | Meaning |
|---|---|
| The settings are not valid. | When a target is saved, a field holds a value the target type does not accept. |
| The target could not be saved. | Saving failed. The global log has the details. |
|
The folder does not exist or cannot be read. The folder could not be created. |
In the folder chooser of a local target: the web server cannot access this folder or is not allowed to create anything there. |
| No usable target yet: set one up on the Targets page. | The action needs a usable target. |
|
Nothing to check: no backup is complete at this target. Nothing to check: the backup is complete at no target. |
The check reads only backups that are stored completely at a target. |
| Locked backups are stored at this target. Unlock them first, or remove the target without its backups. | When removing a target together with its backups. More about this: Remove a target. |
| This target cannot list its files, so leftovers cannot be found there. | When cleaning up leftovers at a target. |
| The catalog at the target belongs to another website. Only a website that moved there may add these backups to its list. | When adding backups to the list. More about this: The website has moved or is a copy. |
Plans and settings
| Message | Meaning |
|---|---|
| The plan does not exist. | The page refers to a plan that no longer exists. Reload the page. |
|
The plan settings are not valid. These settings are not valid. An exclusion rule is not valid. |
The plugin refused a value or a rule. |
|
The plan could not be saved. The settings could not be saved. The exclusions could not be saved. |
Saving failed. The global log has the details. |
Backups
| Message | Meaning |
|---|---|
| The backup is still running. | A running backup cannot be deleted. |
| The backup is locked. Unlock it first. | A locked backup cannot be deleted. More about this: Protect a backup from deletion. |
| The backup could not be marked. | Locking or unlocking could not be saved. |
|
Nothing to delete at these targets. The entry could not be removed. |
When deleting a backup: nothing of this backup is stored at the chosen targets, or the list entry could not be removed. |
| No complete local copy of this backup is available for download. | Downloading is possible only if the backup is stored completely in a local folder. More about this: Download a backup. |
Restore and import
| Message | Meaning |
|---|---|
| A previous restore is still open. Keep or undo it first. | As long as a rollback is open, no new restore starts. More about this: Keep or undo a restore. |
| This restore does not exist. | The page refers to a restore that does not exist in the list. |
| The upload got out of step; it continues at the expected position. | During an import from a file, a chunk did not arrive at the expected position. |
| The upload is not complete yet. | During an import from a file, chunks of the file are still missing. |
| The server received an empty chunk; the chunk is probably larger than the server allows. | The server discarded the chunk, probably because of its limit for the size of a request. More about this: Import a backup from a file. |
| A different backup with the same identifier is in the list; the file is not imported. | The list already contains another entry with this identifier. |
Finding backups again
| Message | Meaning |
|---|---|
|
This is not a folder name of the plugin (cloneworx-backup- followed by 32 characters). No backup folder with this name was found at the target. |
The folder you entered is not a folder of the plugin, or it does not exist at the target. |
| This folder already belongs to this installation. Add its backups to the list instead. | The installation’s own folder is not taken over; its backups are added to the list with Add them to the list. |
|
Taking over is not possible right now. The folder could not be taken over. |
Taking over is blocked or failed. More about this: Find backups again after a reinstallation. |
Key and sign-in
| Message | Meaning |
|---|---|
| The key could not be renewed. | The tile Key shows the reason. More about this: The “Settings” page. |
|
The address of this website cannot be used for the sign-in. The address of the sign-in service is not valid. |
When connecting with Google or Dropbox: the sign-in cannot begin with this address. |
The link to the log
If there is a problem, you do not have to search for the log. The link is in the message:
- A red message after a job contains the link Log. It opens the log of this job. The yellow message after a backup, a check, the deletion of old backups, the cleanup, the finding of backups and a diagnosis contains the same link, for example after warnings or after an abort.
- A red message without a job contains the link Show global log. It opens the global log. Examples: a backup could not be started, or the test email could not be sent. The yellow message after a failed connection test contains the same link.
- No link is shown in green messages and in messages for which there is nothing to look up, for example A job is already running. The yellow messages after a restore also have no link, for example after a restore with warnings or after an aborted restore. The yellow message after keeping or undoing contains the link Log. You open the log of a restore on the Restore page in the Extended view under Recent restores. The yellow message after Check task sources on the Settings page also has no link.
- The red message, here The backup could not be started: … The cause follows the colon.
- Show global log opens the global log.
The messages after a backup
| Message | Meaning |
|---|---|
|
green Backup complete. |
Every target has the complete backup, and nothing was left out. |
|
yellow Backup complete. Not backed up: another WordPress installation in …. Install the plugin there as well; see the log. |
The backup is there. It left out another WordPress installation inside the website. |
|
yellow Backup complete with warnings. |
The backup is there, but something did not go smoothly. The number and kind of warnings follow the sentence. |
|
yellow Backup aborted. |
You aborted the job. |
|
red Backup failed. |
The backup failed. The plugin removes what was already transferred from the targets again. The cause follows the sentence in plain language, for example Not enough free space. or No target is reachable. |
Other jobs report in the same colours with their own text, for example Backup checked: readable and complete. or Backup deleted. On the Targets page the messages mention the target by name.
With warnings
After a backup with warnings, the message itself says what did not go smoothly. The message gives a count for each kind:
| In the message | Meaning |
|---|---|
| … not readable | Files or folders that the plugin could not read. |
| … vanished | Files that no longer existed during packing. |
| … unsupported | Entries that are not files, folders or links and therefore cannot be backed up. |
| … changed while being read | Files that changed while the plugin was reading them. |
| … target(s) failed | Targets at which the backup did not arrive while another target has it. |
| … database note(s) | Notes from the export of the database. |
The names are in the log of the job: it lists every affected entry with its path inside the website. For each reason it lists at most 50 entries; it counts further ones without listing them.
The message from the target in the original
If a job or a connection test fails at an external target, the plugin shows its own explanation and below it what the target and the transfer reported.
- The failed target and the cause in plain language, in the form Target “…”: …
- The message in the original: 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 the job.
- The message is not translated: the text is shown as the target and the client reported it.
- Before the message appears, the plugin masks what does not belong on a screen. The folder of the target becomes
<folder>, the user<user>, the server and every IP address<host>, the name of a backup<job>. A password or key is replaced by asterisks. - If sending breaks off in the middle of the upload, cURL does not know the answer of the target. The plugin then gives both possible causes: Sending the data failed. Possible causes: the connection was interrupted, or there is no space left at the target.
The message appears in four places: in the result of the connection test on the Targets page, in the message after a job, in the status tile of the Overview and in the log. On the command line it appears below the messages of a job: after target: the message from the target, after client: the message from the client, for cURL with its number.
The “Log” dialog window
The dialog window is always called Log, no matter what it shows. What happened and when is in its lines. This is how you open it:
- via the link Log or Show global log in a message,
- via the link Log in the status tile of the Overview,
- via More …, then Log in the row of a backup,
- via Show global log in the result of a failed connection test,
- via Log in the list Recent restores on the Restore page, in the Extended view,
- via Show global log on the Settings page, in the Extended view in the tile Log.
- Log is the title of the dialog window.
- The cross closes the dialog window.
- A line: the time, the level and the message. Below it, in small print, are the details about the message.
- A warning: the level is shown in yellow. For an error it is shown in red.
There are two kinds of logs:
| Kind | Content | Time in the line |
|---|---|---|
| Log of a job | Everything that happened during this one backup, this check or this restore. | time |
| global log | Everything that cloneworx Backup and cloneworx Backup Pro write: connection tests of targets, changes to settings, the schedule and every line of every job. | date and time |
- A line of the global log. The date precedes the time, because this log spans several days.
How to read a line
| Level | Colour | Meaning |
|---|---|---|
INFO |
none | An ordinary step. |
WARNING |
yellow | Something did not go smoothly; the job continued. |
ERROR |
red | An error. |
DEBUG |
grey | Detailed lines. They exist only as long as debugging is switched on. |
- The times are given in the time zone of the website.
- The newest line is at the bottom.
- Logs are in English, in every language of the interface.
- The dialog window shows the last 500 lines. If the log is longer, this is shown above it: Only the last … lines are shown.
- Passwords and keys are never in the log: the plugin replaces them with asterisks.
When the log is missing
| The dialog window reads | Meaning |
|---|---|
| There is no log for this backup any more. Logs are kept for … days. | The file of the log no longer exists, for example because the retention period has expired or the website has moved. The plugin keeps the logs of jobs for 30 days by default; 7 to 365 days are possible. You change the number on the Settings page, in the Extended view in the tile Log, in the field Keep logs for. |
| There is no global log yet. | The plugin has not written anything into the global log yet. |
| The log is empty. | The file is there but contains no line. |
| The log could not be loaded. | The server did not deliver the log. The cause follows the message. |
See also
- Read the log
- When a backup fails or ends with warnings
- Adapt the plugin to your server
- Get help: support report, troubleshooting and diagnostics
- State, logs and support with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
You also see the running job on the command line, and you can abort it there. The dialog window Log does not exist there: the command line lists the log files and writes them into a tar file. The output is in English.
# Show the running job with phase and progress wp cloneworx-backup job status # Cancel the running job wp cloneworx-backup job abort # List the log files wp cloneworx-backup logs # Write all logs to a tar file wp cloneworx-backup logs --to=logs.tar # Enable debugging for 24 hours wp cloneworx-backup debug on