You decide in two places what goes into a backup: each backup plan chooses its content, and the exclusions of the website apply to all plans. By default, a plan backs up everything.
You do not have to set anything here
Everything in this article is optional. By default, every plan backs up the database and all files of your website. Only what does not belong in any backup is left out: caches, logs and the folders of other backup plugins. You can adjust the scope, but you do not have to for your website to get its backup.
What you need
- the Extended view. The switch is at the bottom left of the page. Only this view shows content and exclusions.
Step 1: Choose the content of a plan
Open the Backup page. In the Backup plans tile, choose More … at the plan, then Edit. Under What is backed up, tick what the plan backs up and click Save. At least one checkbox must be ticked.
- Database means the tables of this website.
- wp-content is everything in this folder that does not belong to plugins, themes, must-use plugins or uploads: language files, drop-ins, folders of other plugins.
- WordPress core means the folders wp-admin and wp-includes and the files that WordPress ships in the root folder.
- Must-use plugins
- Plugins
- Themes
- Uploads
- Root folder is everything in the folder of the WordPress core except WordPress itself and wp-content: .htaccess, robots.txt, verification files, .well-known and your own files. If WordPress is installed in its own subfolder with its own address, the files of the web root belong to it as well: its index.php, .htaccess, robots.txt and verification files.
The file wp-config.php is never part of a backup: it contains the authentication keys and salts of the website. A restore leaves the wp-config.php of this website as it is.
Step 2: Look at the exclusion rules
Open the Settings page and expand the Exclusions tile. The rules apply to the whole website and to every plan. What a rule keeps out of the backup also stays in place during a restore, even inside a plugin or theme folder that the restore replaces as a whole.
- The notice says which rules are in effect: The default rules are in effect. or Your own rules are in effect.
- A rule. The cross after it removes it from the list.
- Folder, name with * or extension is the field for a new rule.
- Add puts the rule at the end of the list.
- Folders that other plugins report as their cache or their log. These folders are always excluded, even in a place other than the usual one.
The default has 28 rules: caches, folders of other backup plugins, logs and system leftovers, Git folders. A rule has one of these forms. Upper and lower case do not matter. The forms follow .gitignore; a path, however, always begins with a root.
| Form | Matches | Example |
|---|---|---|
| Name | a file or a folder with exactly this name, at any depth | Thumbs.db |
| Name with a slash at the end | the same, but folders only | updraft/ |
| Name with an asterisk at the start or at the end | every name that ends or begins like this |
*.log, backwpup*
|
| Path that begins with a root | this entry and everything below it. An asterisk is only allowed in the last part. | wp-content/cache |
Path with ** as a whole part |
any number of folders at this place, including none | wp-uploads/**/*.jpg |
The roots for paths are called wp-content, wp-uploads, wp-plugins, wp-themes, wp-mu-plugins, wp-core and wp-root.
Step 3: Add a rule of your own
Enter a rule in the field and click Add. The cross after a rule removes it. As soon as you change the list, the notice above the list refers to your own rules.
- The notice Your own rules are in effect. appears above the list as soon as you have changed it.
- The new rule is at the end of the list. The cross after it removes it.
- Add puts the rule from the field at the end of the list.
Nothing is saved until you click Save at the end of the tile. The plugin checks every rule when you do. If one is wrong, the reason appears in red at the rule, and nothing is saved. A rule saved earlier that runs through the folder of another root also shows the reason in red in the list.
Step 4: Back up tables as structure only
Some plugins keep tables for sessions, logs, caches or statistics. Such tables grow large, and the website also runs without their content. For ticked tables, the plugin backs up only the structure and leaves out the rows. During a restore, such a table stays as it is on the website, with its data. If it does not exist there, the plugin creates it empty.
- The group of candidates: Sessions, Logs, Caches or Statistics.
- A table with checkbox, name without the prefix, rows and size.
- Other tables are tables you have added yourself.
- Table name without the prefix is the field for another table of this website.
- Add table adds the table to the selection.
- The plugin’s own tables. For these, only the structure is ever backed up.
- Save saves rules and tables together.
- Reset to defaults restores the default rules immediately and saves the ticked tables at the same time.
The rows are missing from every backup
By default, the plugin backs up every table completely. Tick a table only if you can do without its content: it cannot be brought back from the backup. For Statistics, that is the visitor numbers themselves.
What is never backed up
- the plugin’s own folders with backups, logs and work files,
- every folder that holds a file named
.donotbackup, - another WordPress installation in a subfolder. That is a separate website with its own database. The message after the backup and the row of the backup in the list say so: Not backed up: another WordPress installation in …. Install the plugin there as well; see the log. If there are more than 20 folders, only the number is shown there; the log lists them all.
- tables of other websites in the same database.
- a Bedrock installation. The backup then ends with This website is a Bedrock installation; cloneworx Backup does not back it up because such a backup could not be restored reliably.
If the plugin finds the tables of another WordPress installation in the database, a line about it appears in the Exclusions tile, directly above Save.
- The notice Not backed up: … tables of another WordPress installation with prefix “…”. shows the number of tables and their prefix.
If something does not work
| Message | What you can do |
|---|---|
| must not start with a slash | Begin a path with a root, for example wp-content/cache. |
| unknown root: use wp-content, wp-uploads, wp-plugins, wp-themes, wp-mu-plugins, wp-core or wp-root | The first part of a path must be one of these roots. |
|
only one * is allowed * only at the start or the end of the name * only in the last part of the path |
Put a single asterisk at the start or the end of the last name. |
| **/ at the start works only with a single name after it; otherwise start with a root | Begin the path with a root, for example wp-content/**/a/b instead of **/a/b. |
| the path runs through the folder of another root and never matches; write it as … | Example wp-content/uploads/videos: the uploads are a root of their own. Enter the spelling that the message gives, here wp-uploads/videos. |
| the path names the folder of another root; a whole root cannot be excluded | Example wp-content/uploads. Deselect the root in the plan instead, under What is backed up. |
|
contains characters the database cannot store (for example an emoji) is not valid UTF-8 text |
Remove the rule and enter it again without these characters. |
| This table does not exist on this website. | Enter the name without the prefix, the way the tile shows the other tables. |
- The reason why the plugin refuses the rule. The cross after it removes the rule.
Remove a refused rule with the cross and enter it again correctly.
Good to know
- A change applies from the next backup on, not to a backup that is running right now.
- In the Extended view, the row of a plan shows its content. If all checkboxes are ticked, it says everything.
- The plugin never follows symbolic links in the folders. It backs up the link itself.
- If a second WordPress installation with a longer prefix is in the same database, the plugin does not back up its tables. The Exclusions tile shows the prefix.
See also
- Backup plans: tile and form
- The “Settings” page
- Restore only parts
- Manage backup plans with WP-CLI
- Settings and scope with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
With WP-CLI you can display what the plugin counts as part of the website, and you set rules, tables and the content of a plan. --set replaces the whole list of rules.
# Show what belongs to the website: roots, tables, rules wp cloneworx-backup scope # Show the exclusion rules in effect wp cloneworx-backup scope exclusions # Replace the list of rules wp cloneworx-backup scope exclusions --set="wp-content/cache,*.log,.DS_Store" # Back to the default rules wp cloneworx-backup scope exclusions --reset # Back up tables as structure only wp cloneworx-backup scope tables --structure-only="woocommerce_sessions,wfHits" # Change the content of a backup plan wp cloneworx-backup plan edit "Daily backup" --roots=db,wp-uploads