This is how you remove a target you no longer need: without the backups stored there, or together with them.
What happens when you remove a target
- The backups at the target stay where they are. The plugin deletes them only if you ask for it in the confirmation prompt.
- The plugin deletes the settings and the credentials of the target. For a target in Dropbox, it then revokes the access at Dropbox; see the section “Targets in Dropbox and Google Drive”.
- The target is removed from every backup plan. A plan without a target is paused. It can only be switched on again once you assign a target to it.
- If backups in the list still refer to the target, its entry stays as removed. This way an old backup never points to a different target.
Step 1: Choose Remove
Open the Targets page. In the row of the target, click More …, then Remove.
Step 2: Answer the confirmation prompt
- The checkbox shows the number of backups at the target. With the checkbox ticked, the plugin first deletes these backups and then removes the target. Without the tick, the backups stay where they are.
- Cancel closes the confirmation prompt without changing anything.
- Remove removes the target.
What the confirmation prompt shows depends on what is stored at the target:
| Stored at the target | The confirmation prompt shows |
|---|---|
| no backups | only the question Remove “…”? |
| backups | the question and the checkbox Also delete the … backups stored at this target, for a single backup Also delete the one backup stored at this target |
| locked backups | the question and a note instead of the checkbox; see below |
Tick the checkbox only if you no longer need the backups at this target. Then click Remove.
With the checkbox ticked, the backups at this target are gone
The plugin deletes every backup at this target. If a backup is stored at no other target, there is no copy of it left afterwards.
Step 3: Read the result
| Message | Meaning |
|---|---|
| “…” deleted. | No backup in the list refers to the target. Its entry is completely gone. |
| “…” removed. … backups in the history still refer to it, so its entry stays. | The target is removed. Its entry stays without settings and without credentials; the Extended view shows it. |
| “…” is being removed: the backups at the target are deleted first. | You ticked the checkbox. The deletion runs as a job; a line below the status tile shows the progress. |
| “…” removed; … backups deleted at the target. | The job deleted the backups and the catalog files at the target and removed the target. |
With the checkbox ticked, the page looks like this while the plugin deletes the backups:
- The message: the target is being removed, the backups at the target are deleted first.
- The progress: Deleting backup, then how many entries are done and how long it will still take.
- Abort deletion stops the deletion at the next step. What has been deleted by then stays deleted; the target stays set up.
If locked backups are stored at the target
- The note shows the number of locked backups: unlock them first to remove the target together with its backups.
- Remove removes only the target here. The backups stay where they are.
As long as a backup is locked, the plugin does not delete it, not even together with the target. That is why the checkbox is missing. You have two options:
- Remove the target without its backups.
- Or unlock them first: on the Backup page in the More … menu of the backup with Unlock backup. After that, the confirmation prompt shows the checkbox. More on this: Protect a backup from deletion.
Targets in Dropbox and Google Drive
Instead of a password, a target of these target types has an access that the provider issued after your consent. The plugin deletes it from the database of the website when removing the target. What happens at the provider depends on the target type:
| Target type | At the provider | What you can do |
|---|---|---|
| Dropbox | The plugin revokes at Dropbox the access the target had. Other websites that you have connected with the same Dropbox account have their own access and stay connected. | Nothing. If the revocation does not succeed, the plugin removes the target anyway. The access then stays valid at Dropbox until you disconnect the app in your Dropbox account. |
| Google Drive | The plugin revokes nothing: the access the target had stays valid at Google. The consent stays listed in your Google account, in the Security area under third-party apps and services. | Remove the consent there if you no longer need it. If you remove it there, you disconnect every website that is connected with this Google account. |
In both cases the backups stay at the provider if you do not tick the checkbox. More on the target types: Store backups in Dropbox and Store backups in Google Drive.
The revocation at Dropbox does not always succeed:
- The plugin does not send it if it can no longer read the stored credentials of the target, for example after changed security keys in wp-config.php, or if the web server lacks cURL.
- If you permanently delete the entry of a target that has already been removed, the plugin sends no further revocation. It already tried that when removing the target.
- The revocation fails if Dropbox or the sign-in service cannot be reached at that moment. The plugin needs the sign-in service when the access has expired: then it fetches a new one first.
A target of the type Dropbox that you do not remove keeps its access even if you deactivate the plugin or delete it without the uninstall switch. How deleting with the switch revokes the access: Uninstall the plugin.
Permanently deleting the entry of a removed target
At the bottom of the page, switch to Extended. The list now also shows removed targets: with the name struck through and the label removed. The More … menu of such an entry offers only Delete permanently.
- The text shows two numbers: how many backups in the list still refer to the target and lose the reference, and how many of them disappear from the list.
- Cancel
- Delete permanently deletes the entry of the target. Nothing is deleted at the target.
The text about the references appears if backups in the list still refer to the target: … entries in the backup list still refer to it. They drop the reference; … of them disappear from the list because they were stored only there. This is what happens to these entries:
- A backup that is also stored at another target stays in the list. It only loses the reference to the removed target: its row then no longer shows this target.
- A backup that was stored only at this target disappears from the list. Its files stay at the target.
If no backup refers to the target any more, the text does not appear.
Afterwards the page reports “…” deleted. … entries dropped the reference, … disappeared from the list. If no backup referred to the target any more, the message reads “…” deleted.
If locked backups refer to the target
- … of these entries are locked: unlock them first, then the target can be deleted.
- Delete permanently is greyed out as long as locked backups refer to the target.
As long as a locked backup refers to the removed target, the plugin does not delete the entry of that target, and no backup loses the reference. Unlock the backup first: on the Backup page in the More … menu of the backup with Unlock backup. Then choose Delete permanently once more. More on this: Protect a backup from deletion.
If something does not work
| Message | What you can do |
|---|---|
| “…” was not removed: … backups could not be deleted; it keeps its settings, the remaining backups stay in the list. | At least one backup could not be deleted; it stays at the target and in the list. The target stays set up. The link in the message takes you to the log. If the target is no longer reachable, remove it without ticking the checkbox. |
| “…” was not removed: its folder belongs to another installation, nothing was deleted there. | The catalog in the folder at the target belongs to another installation. The target stays set up. More on this: The website has moved or is a copy. |
| “…” was not removed: … backups there were locked meanwhile. Unlock them first. | Backups at this target were locked while the deletion was running. The target stays set up. Unlock them and then remove the target again. |
| A job is already running. | You ticked the checkbox while another job was running. Deleting the backups is itself a job, and only one job runs at a time. The plugin deleted nothing and did not remove the target. Wait until the running job has finished, then remove the target once more. |
| … of these entries are locked: unlock them first, then the target can be deleted. | Locked backups refer to the removed target. As long as that is the case, its entry stays. Unlock these backups and then choose Delete permanently once more; see the section “Permanently deleting the entry of a removed target”. |
Good to know
- The name of a removed target stays taken as long as its entry exists.
- The plugin never assigns the identifier of a target, for example
ftp-2, a second time, not even after deletion. - If you later set up the same storage with the same folder as a target again, the plugin looks there after saving and the successful connection test. It adds the backups that are still stored there to the list again on its own, or the tile Backups found at “…” offers to add them. A backup whose entry is still in the list gets the new target added; a backup without an entry is added to the list as a new entry, with reclaimed in the Plan column. More on this: Find backups again after a reinstallation, section “Other cases”.
See also
- The “Targets” page
- Delete a backup
- Protect a backup from deletion
- Backup plans: tile and form
- Manage targets with WP-CLI
On the command line
WP-CLI not set up yet? How to install WP-CLI.
You specify the target by its identifier or its name. Without a parameter, the backups stay at the target. With --with-backups, the command first deletes the backups at the target; if locked backups are stored there, it refuses. A second remove on a target that is already removed deletes its entry permanently, without asking: backups in the list that still refer to it lose the reference, and backups that were stored only at this target disappear from the list. If locked backups refer to the target, the command refuses.
# Show targets with ID and state wp cloneworx-backup target list # Remove a target; the backups there are kept wp cloneworx-backup target remove local-1 # First delete the backups at the target, then remove the target wp cloneworx-backup target remove local-1 --with-backups # Permanently delete the entry of an already removed target wp cloneworx-backup target remove local-1