CloudScale Backup & Restore

By andrewjbaker

★ 5.0/5 (2 ratings)10+ active installationsVersion 3.2.901

Back up any size site to S3, R2, B2, Wasabi, Google Drive, Dropbox, OneDrive, SFTP, WebDAV or Managed Cloud. Free full restore and automated DR.

Description

A backup is only worth the restore behind it. CloudScale Backup & Restore is built for the day something goes wrong: a multi-gigabyte site, a dead server, a plugin update that takes the site down. It backs up to every destination you choose at once, restores your whole site in one click, and can keep a second server ready to take over. No size limit, no destination limit, no paid restore button.

Why CloudScale

  • Free full restore. Files and database, from a local backup, an upload or any connected cloud. No premium tier is needed to get your site back.
  • Built for large sites. The database streams in 500-row pages, never loaded into memory. Uploads go in chunks, retried and resumed after a dropped connection or throttle.
  • Back up anywhere, to several places at once. A dozen storage services plus your own servers, listed under Where Backups Go.
  • Ten storage regions on six continents. Managed Cloud keeps backups on Amazon S3 in the Americas, Europe, Africa, Asia and Australia. Automatic mode uses the nearest region, so copies and restores take the lowest-latency path, or pick one for data residency.
  • Backoff protection, so a backup does not overwhelm your server or connection. Set a maximum CPU temperature and compression pauses until the host cools. Set a share of your upload speed and cloud uploads are spaced out to average within it. Both are off until you set them.
  • Automated disaster recovery. A standby server restores itself from the newest cloud backup on a schedule, refuses a stale one, and reports recovery time and a file-by-file reconciliation.
  • Self-healing backups. A backup killed mid-run is detected and finished or restarted, and you are told. Archives can be integrity-checked before upload.
  • Rollback for bad plugin updates. Automatic Crash Recovery copies a plugin before an update and rolls it back if the site starts failing.
  • Recovery from a hack, not only from a crash. Protected Mode locks out whoever got in while you repair the site.
  • Alerts that reach you. Email and Telegram alerts for failed backups, restores and recoveries, including PHP fatal errors.

Where Backups Go

  • This server: every backup is kept in a protected folder on your own server first, ready to download or restore
  • Amazon S3, with access keys or an EC2 instance role
  • S3-compatible storage: Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google Cloud Storage, Hetzner Object Storage, MinIO, or any other S3-compatible service through a custom endpoint
  • Google Drive, Dropbox, Microsoft OneDrive
  • Your own server: SFTP, FTPS or FTP, and WebDAV (Nextcloud, ownCloud, Synology, QNAP)
  • CloudScale Managed Cloud, with nothing to set up
  • Amazon EC2 AMI snapshots: a full machine image of an AWS-hosted server, beside your file backups

Every cloud and own-server destination gets the same retention, resumable transfers, one-click restore and Automated Restore. An AMI snapshot is restored from its own card, as a whole server.

Backup: Everything, Any Size

Pick any combination; it is packaged into one .zip whose name says what it holds, with a backup-meta.json inside:

  • Database (all tables), media uploads, plugins, themes
  • Must-use plugins, languages, drop-ins, .htaccess, wp-config.php and WordPress core files
  • Site root extras (robots.txt, favicon, .well-known/) and a snapshot of your server, PHP and MySQL settings
  • Optional AES-256 encryption with your own password
  • Schedule by day of the week and time, with retention (keep the last N) on every destination
  • Space check and “delete oldest” for cloud destinations that are filling up

Restore: One Click, Server-Side

  • Full restore puts back the backup’s files, then its database. It runs on the server, so you can close the page
  • Specific tables only or a single post or page with its metadata, no maintenance mode needed
  • Restore from this server, an uploaded .zip or .sql, or straight from any connected cloud. S3 and Managed Cloud downloads run in parallel when faster, and resume
  • Encrypted backups are checked against your password first
  • Visitors see a maintenance page; it is removed whether the restore succeeds or fails
  • wp-config.php is never overwritten, so the site keeps its own database credentials
  • Afterwards: file-by-file reconciliation, drop-in health check, and an old-versus-new server comparison

Restoring a Hacked Site

A plain restore of a hacked site is usually re-hacked within hours: it puts back the vulnerable plugin and leaves stolen credentials working. Tick This site was hacked on a full restore and, before visitors return, Protected Mode:

  • Rotates the security keys, signing everyone out everywhere, and revokes every application password
  • Makes every administrator set a new password
  • Locks sign-in, wp-admin, XML-RPC and changing REST requests to browsers holding a device pass, which the restoring browser is given
  • Blocks installing plugins and themes and the file editor, while updates stay allowed because updating is the cure

It stays on until you complete an exit checklist, with no timer that could reopen a site you have not finished repairing.

Disaster Recovery and Failover

  • Standby & DR tab: turn a second install into a hot standby or a refreshed test copy
  • Automated Restore: the standby lists your cloud storage, copies the newest backup straight to the server and restores it on a schedule. A backup older than your limit (36 hours by default) is refused and alerted
  • Safe by design: an armed standby never takes or uploads its own backups, so it cannot overwrite production’s. While it is serving traffic, refreshes pause so nothing visitors wrote is lost
  • DNS failover: a Cloudflare script in the plugin’s GitHub repository repoints DNS at the standby when production fails, and back when it recovers
  • EC2 AMI snapshots: create and restore full machine images of an AWS-hosted server from the plugin

Staging Clones

Clone any backup into a separate WordPress install on the same server, with its own directory and database. URLs are rewritten everywhere, including serialized data and JSON. It refuses this site’s own directory or database, and can refresh after each scheduled backup.

Security

  • Signed backups: every backup is signed with your site’s key. A standby holding that key automatically restores only what your site made, and refuses anything else placed in your storage
  • Backup folder with a random name, deny rules for Apache, nginx and IIS, and 0700 permissions
  • A daily self-check confirms backups are not publicly downloadable, and shows the server rule to add if they are
  • Cloud credentials and the encryption password are kept in a protected file outside the database, so they never travel inside your backups
  • Storage addresses cannot reach a cloud metadata service, or your server’s private network unless you allow it in wp-config.php
  • Plain FTP and FTPS are labelled for what they protect, and automatic restore refuses a source that can be altered in transit unless your backups are signed

WP-CLI

wp csbr restore, `wp csbr cloud-list`, `wp csbr cloud-pull`, `wp csbr sync-from-cloud`, `wp csbr auto-restore`, `wp csbr role` and `wp csbr doctor` let a system timer keep a standby in sync without WP-Cron.

Managed Cloud

Don’t have a cloud account? CloudScale Managed Cloud is $5/month for 750 GB on Amazon S3 Glacier Instant Retrieval, in ten regions worldwide: the one nearest your site by default, or the one you choose. Instant Retrieval means a restore downloads straight away, with no archive thaw. Your own destinations are always free.

Automatic backups are off by default. Run your first backup by hand to confirm your server, then switch on a schedule. Full documentation: help.cloudscale.consulting.

External services

Nothing below is contacted until you set it up or click something, and your keys go only to the service they belong to. Full reference, with every data item and endpoint: https://cloudscale.consulting/external-services/backup-restore/

Storage you connect (optional)

Only the backup zip is sent, to your own account, when you connect that destination. A backup holds your whole site, so choose Encrypt backups if you want it unreadable to the provider.

  • Amazon S3: the Amazon S3 host for the bucket’s own AWS region, for example s3.eu-west-1.amazonaws.com. Terms https://aws.amazon.com/service-terms/ Privacy https://aws.amazon.com/privacy/
  • S3-compatible storage: the endpoint shown in the S3 card. Cloudflare R2: Terms https://www.cloudflare.com/terms/ Privacy https://www.cloudflare.com/privacypolicy/ Backblaze B2: Terms https://www.backblaze.com/company/policy/terms-of-service Privacy https://www.backblaze.com/company/policy/privacy Wasabi: Terms https://wasabi.com/legal/customer-agreement Privacy https://wasabi.com/legal/privacy-policy DigitalOcean Spaces: Terms https://www.digitalocean.com/legal/terms-of-service-agreement Privacy https://www.digitalocean.com/legal/privacy-policy Google Cloud Storage: Terms https://cloud.google.com/terms Privacy https://policies.google.com/privacy Hetzner: Terms https://www.hetzner.com/legal/terms-and-conditions/ Privacy https://www.hetzner.com/legal/privacy-policy/
  • Google Drive: www.googleapis.com and oauth2.googleapis.com, after you complete its sign-in. Terms https://policies.google.com/terms Privacy https://policies.google.com/privacy
  • Dropbox: api.dropboxapi.com and content.dropboxapi.com, after you complete its sign-in. Terms https://www.dropbox.com/terms Privacy https://www.dropbox.com/privacy
  • Microsoft OneDrive: https://graph.microsoft.com/ and https://login.microsoftonline.com/, after you complete its sign-in. Terms https://www.microsoft.com/en-us/servicesagreement/ Privacy https://www.microsoft.com/en-us/privacy/privacystatement
  • Your own SFTP, FTP or WebDAV server: only the server you enter. Its owner’s terms apply.

CloudScale Managed Cloud (optional, paid)

Service: CloudScale Consulting, https://cloudscale.consulting/. Nothing is sent until a licence key is entered, except the PayPal button’s checkout details below.
Data sent: licence key and hostname to the broker for a short-lived storage token; backup zips go straight to CloudScale’s Amazon S3 storage in its ten regions, never through the broker. Timing averages pick the nearest region. Leave us a message sends what you type. The PayPal button sends the product name, hostname and optional email.
Endpoints: https://api.cloudscale.consulting/backup/token, https://api.cloudscale.consulting/backup/list, https://api.cloudscale.consulting/status, https://api.cloudscale.consulting/checkout, https://api.cloudscale.consulting/checkout-start, https://api.cloudscale.consulting/recover, https://api.cloudscale.consulting/recover/verify, https://api.cloudscale.consulting/refund-request and https://api.cloudscale.consulting/contact.
Terms https://cloudscale.consulting/terms/ Privacy https://cloudscale.consulting/privacy/

CloudScale community (optional, off until you choose Yes)

Service: CloudScale Consulting, https://cloudscale.consulting/. Nothing in the plugin depends on it, and nothing is sent until you click Yes. No thanks sends nothing.
Data sent: https://api.cloudscale.consulting/v1/usage/checkin, once when you click Yes and then weekly: a random install id, site address without paths, plugin, WordPress and PHP versions, setup date, the day an administrator last opened the plugin, and which features are set up (yes or no per storage destination, schedule on or off, backups kept, days since the last backup). Never bucket names, folders, server addresses, keys or emails. Leaving, or deleting the plugin, sends one request that erases it. Never used to contact you.
https://api.cloudscale.consulting/v1/usage/leave: only if you choose to give a reason when deactivating, the reason, your note, plugin version and days active.
Terms https://cloudscale.consulting/terms/ Privacy https://cloudscale.consulting/privacy/

PayPal (optional, pays for Managed Cloud)

When you subscribe, your email and the $5.00 USD amount go to api-m.paypal.com (or api-m.sandbox.paypal.com when testing), and PayPal’s script loads from www.paypal.com/sdk/js on the checkout screen only. PayPal’s own origin must serve that script. Card details never reach the plugin or your site. https://developer.paypal.com/api/rest
Terms https://www.paypal.com/us/legalhub/paypal/useragreement-full Privacy https://www.paypal.com/us/legalhub/paypal/privacy-full

Other optional features

  • Telegram Bot API: alerts with the site name, event status and, for errors, the PHP error, file and line, via sendMessage on api.telegram.org, once you enter a bot token and chat ID. Terms https://telegram.org/tos Privacy https://telegram.org/privacy
  • AWS EC2 snapshots: instance details from the local metadata address 169.254.169.254, then snapshot requests to the EC2 host for your region, for example ec2.eu-west-1.amazonaws.com, when you use the AMI feature. Terms and privacy as for Amazon S3.
  • Crash Recovery health check: a plain GET to the URL you set, by default your own site.
  • Gmail port check: Send Test in Notifications opens and closes a connection to smtp.gmail.com on ports 587, 465 and 25. No email or data is sent. Terms https://policies.google.com/terms Privacy https://policies.google.com/privacy

Privacy Policy

The plugin sends no telemetry or analytics unless you join the optional CloudScale community (see External services). Backups stay on your server in wp-content/uploads/cloudscale-backup-<random>/ and leave it only for destinations you configure, listed under External services. CloudScale Managed backups are encrypted at rest; Encrypt backups adds your own password.

Installation

  1. In WordPress admin go to Plugins > Add New Plugin, search for CloudScale Backup & Restore, then click Install Now and Activate
  2. Open Tools > CloudScale Backup & Restore
  3. Click Back up my site now to take your first backup
  4. Optional: connect S3, Google Drive, Dropbox, OneDrive, SFTP/FTP, WebDAV or Managed Cloud, then turn on a schedule

To install by hand, upload the cloudscale-backup folder to /wp-content/plugins/ and activate it under Plugins > Installed Plugins.

FAQ

Is restore really free?

Yes. Full restore, selective table restore, single post restore, cloud restore, staging clones and automated standby restore are all in the free plugin. Only Managed Cloud storage is paid; your own cloud accounts cost nothing extra.

Which storage can I back up to, and how do I set it up?

Any of the destinations under Where Backups Go, several at once. Each has its own card on the Cloud Backups tab with Test Connection and Diagnose buttons. Step-by-step setup for every provider, including where to create the bucket and key and which region and endpoint to enter: https://help.cloudscale.consulting/plugin-help/backup-restore/s3/ (Amazon S3 and S3-compatible), https://help.cloudscale.consulting/plugin-help/backup-restore/sftp/ and https://help.cloudscale.consulting/plugin-help/backup-restore/webdav/.

Will it work on a large site?

Yes. The database is dumped in 500-row pages, so memory stays flat whatever its size. Backups and restores run without PHP’s time limit, large uploads are sent in retried chunks, and an S3 or Managed Cloud download that stops part way resumes. A backup killed mid-run is picked up and finished or restarted. The System Info panel shows your server’s limits and the methods in use.

Will a backup slow my site down or use all my bandwidth?

Not if you set Backup Limits on the Local Backups tab; both are off by default. A maximum CPU temperature pauses compression until the processor is 5°C cooler, up to 5 minutes at a time and 30 minutes per backup, so a host that never cools still gets its backup. This needs PHP 8.0 or newer and a host that exposes its temperature, and the card says when yours does not. A maximum share of your stated upload speed spaces out uploads to S3, Managed Cloud, Google Drive, Dropbox and OneDrive. It limits the average, not the peak, and does not cover SFTP, FTP or WebDAV.

Where are backups stored?

On your server in wp-content/uploads/cloudscale-backup-<random>/. The random part makes the folder name unguessable, and it carries deny rules for Apache, nginx and IIS plus an index.php and 0700 permissions. Download any backup from the admin with the Download button. Copies go to every cloud destination you enable.

Where are Managed Cloud backups stored?

In one of ten Amazon S3 regions. Automatic picks the region nearest your site by measuring it; you can also choose one, for example to keep data in Europe. Changing region sends new backups there; backups in the old region expire within 90 days.

Can a hacked site erase its Managed Cloud backups?

No. A compromised site can remove a backup from the list, but storage keeps the deleted copy for 30 days and neither your site nor the CloudScale broker can erase it. Contact support to recover it. After those 30 days it is permanently deleted, so a backup that reaches the 90-day limit is erased by day 120.

Can I restore only the database, or only some tables?

Yes. In the Restore window choose Full restore (files, then database), Specific tables only (just the tables you tick) or Single post or page. Upload a .sql file to restore a database only. On the command line, wp csbr restore takes --db-only, --files-only and --components=<list>.

Can I migrate to a new host or domain?

Yes. Install WordPress and this plugin on the new host, then restore the backup from an upload or straight from your cloud storage. Files and database are both restored. If the domain changed, run wp search-replace 'old.example' 'new.example' --all-tables afterwards. To copy a site onto the same server under a new URL, use Clone Targets, which rewrites URLs for you.

How does scheduling work?

Choose the days of the week and the time of day; cloud copies run a set delay after the local backup. For reliable timing, point a real system cron job at wp-cron.php instead of relying on visitor traffic. Your server’s time and timezone are shown next to the schedule.

How do I set up a standby or disaster-recovery copy of my site?

Install WordPress and this plugin on the second server, then open the Standby & DR tab there (never on the live site). Choose a hot standby or a refreshed copy, label its alerts, type MAKE THIS A COPY and press Apply. On the Automated Restore tab connect the cloud storage the live site backs up to, choose the site to copy from, and switch on the schedule. The checklist shows anything still missing. A hot standby also needs something outside WordPress to move your DNS; the plugin’s GitHub repository has a Cloudflare script for that.

How do I clone my site to a staging copy on the same server?

Create an empty directory the web server can write to, with a wp-config.php naming an empty database (or one your database user can create). Take a backup that includes WordPress core files. On the Clone Targets tab add the directory, its URL and that wp-config.php, press Verify, then Clone Now. Everything in the target is replaced and every URL is rewritten. The wp-config.php must hold literal database values, and cloning needs the PHP mysqli extension. A clone is a complete copy, including mail settings and scheduled tasks, so block outgoing email on it before you browse it. Hook csbr_clone_post_restore to run your own steps afterwards.

What happens if a restore fails?

Maintenance mode is removed even when a restore fails, including on a PHP fatal or out-of-memory error, and you are alerted with the reason. The restore result lists anything that could not be written. There is no automatic rollback of a partly restored database, so take a server snapshot first (the Restore window asks you to confirm you have) and restore again or from that snapshot.

Can I run backups and restores from WP-CLI or cron?

Yes. wp csbr restore <file> restores a local backup, wp csbr cloud-pull --newest downloads the newest S3 backup, wp csbr sync-from-cloud pulls and restores in one step, and wp csbr auto-restore runs a standby’s configured restore. Run wp help csbr for every option.

Does it work on WordPress multisite?

No. A restore would overwrite every site in the network, while each site’s own administrator holds the permission its screens check. On a multisite network the plugin shows a notice and does nothing else.

Do I need ZipArchive or a recent PHP?

PHP 8.1 or newer and the PHP zip extension, which nearly every host includes. AES-256 encryption needs a zip extension built with encryption support; the plugin tells you if yours is not.

What is inside the backup zip?

The parts you chose: database.sql, the uploads, plugins, themes and other folders, plus backup-meta.json, which records the plugin and WordPress versions, site URL, table prefix and components, so you can check a backup without restoring it.

Which third-party libraries are bundled?

Two, both under the MIT licence and used only for SFTP: phpseclib 3.0.57 (https://phpseclib.com) and paragonie/constant_time_encoding 3.1.3 (https://github.com/paragonie/constant_time_encoding). They are renamed under the CSBR_Vendor namespace so they cannot clash with another plugin’s copy. Licence texts are in vendor/.

Does the plugin contact help.cloudscale.consulting?

No. The plugin’s header links to its help pages there. It is an ordinary link the administrator may choose to open; the plugin itself never requests that host and sends it no data.

What files does the plugin write outside its own folder?

The Automatic Crash Recovery feature writes a single file outside the plugin
folder when it is enabled: wp-content/fatal-error-handler.php. This is a
WordPress-recognised drop-in file (documented in the WordPress Developer
Handbook under get_dropins()). WordPress core checks for this file on every
request; if present, it replaces the default fatal-error screen with a custom
handler. The plugin uses this mechanism to show a branded recovery page to
visitors while a crash is being fixed, instead of a blank white screen.

The file is written using the WordPress Filesystem API (WP_Filesystem). It is
only written when the feature is enabled, only overwritten if it was written by
this plugin (identified by an internal marker), and is deleted when the feature
is disabled or the plugin is uninstalled. No personal data is stored in this file.

The plugin also writes the following. Uninstalling removes them, except where noted:

  • wp-content/uploads/cloudscale-backup-<random>/ – the backup archives themselves,
    plus an .htaccess, a web.config and an index.php that block public access to
    them. The directory name carries a per-site random token because a fixed, guessable
    name meant sequentially-named archives could be downloaded by anyone who guessed a
    filename. Kept on uninstall so a reinstall or a manual restore can still use your
    backups; delete the folder yourself if you no longer want them. The token is kept in
    wp-content/csbr-state/dir-token (with the same deny rules), which also stays so a
    reinstall finds the folder.
  • wp-content/csbr-state/ – the plugin’s hardened state directory: the automatic restore
    schedule, the backup run lock and the crash-recovery configuration. Removed on
    uninstall, apart from dir-token and its deny rules (above).
  • wp-content/csbr-failover-mode.json, csbr-site-id.json and csbr-restore-ledger.json –
    small markers for the standby, failover and restore features, kept outside the database
    because a restore replaces the database. Removed on uninstall.
  • wp-content/csbr-site-role.json and wp-content/cloudscale-alert-env-label.json – the
    site’s role (primary or standby) and its alert label. Kept on uninstall, because the
    other CloudScale plugins read them too; delete them by hand if no CloudScale plugin
    remains.
  • wp-content/maintenance.php and wp-content/csbr-restore-progress.json – the visitor
    page and progress file shown while a restore runs, removed when it ends. Uninstall
    removes maintenance.php only if it is this plugin’s copy.
  • wp-content/csbr-secrets.php – cloud storage credentials, the licence key and the
    backup encryption password, held outside the database so they are not carried inside
    the database dumps this plugin creates. It begins with a PHP exit guard so it cannot
    be read over HTTP, is written 0600, and is excluded from every backup. A lock file
    and a short-lived temporary file sit alongside it during a write.
  • wp-content/cloudscale-backup-par.json – the Automatic Crash Recovery state file,
    recording which plugins are being monitored.
  • wp-content/csbr-state/csbr-auto-restore.json – on a standby site only, the automatic
    restore schedule and the source it pulls from. The directory carries the same deny-all
    rules as the backup directory, so the file is not readable over HTTP. Installs upgrading
    from an earlier version have their existing wp-content/csbr-auto-restore.json moved
    here automatically.
  • <WordPress root>/.maintenance – WordPress’s own maintenance-mode file, written only
    while a restore is running and removed when it finishes or fails. This is the
    mechanism WordPress itself uses during core updates.
  • A temporary staging directory under the system temp path while a backup is built or
    a restore is unpacked, deleted when the operation ends.
  • wp-content/csbr-state/plugin-auto-recovery/ – Automatic Crash Recovery only: a copy of
    a plugin taken just before WordPress updates it, so a bad update can be rolled back. It is
    removed when the monitoring window closes and otherwise after 72 hours, and on uninstall.
    It sits outside the uploads folder because it holds PHP, and it carries deny rules.
  • Clone Targets only, and only after an administrator adds a target and presses Clone Now
    or enables its schedule: a complete WordPress install (core, plugins, themes, uploads and
    the wp-config.php the administrator named) is written into the directory the
    administrator chose for that target, which is normally outside wp-content, and the
    tables in that target’s own database are dropped and recreated. It never writes to this
    site’s own directory, and no script is generated or run. The target list is stored in
    the csbr_clone_targets option.

No personal data is stored in any of these files beyond what the site itself already
holds.

Screenshots

Changelog

3.2.901

  • Fix: on a standby, the automatic restore’s daily run no longer reports a failure when the waiting check has already started copying the same backup. The second run now steps aside quietly.

3.2.900

  • Security: requests from visitors who are not signed in can no longer write entries into the Activity Log.

3.2.899

  • Security: a restore you start by hand now checks who made the backup. A backup this site did not sign (from another site, a bare .sql file, or a file changed after it was written) is restored only after you confirm, and the choice is logged. WP-CLI needs –accept-unsigned for the same.
  • Security: a restore refuses SQL that reads files or other databases anywhere in a statement, not only at its start.

3.2.898

  • Improvement: the maximum CPU temperature setting now also pauses uploads between chunks, not only compression, so a hot host cools down while sending a large backup.

3.2.897

  • Fix: the Managed backup subscribe button did nothing on most sites. It now opens a secure PayPal checkout in a new tab and the plugin activates when you finish.
  • Security: the Managed licence key is no longer in the page source; Copy Key fetches it when clicked.

3.2.895

  • New: an optional CloudScale community, asked on Getting Started and Cloud Backups. Off until you choose Yes; No thanks sends nothing, every feature works either way, and leaving or deleting the plugin erases what was sent. An optional reason can be given on deactivating; Skip sends nothing.

3.2.894

  • Security: storage requests to S3 and S3-compatible services no longer follow redirects, WebDAV uploads re-check the server address on their own connection, and the crash-recovery health test re-checks its URL, so a storage address cannot be pointed at the local network.

3.2.891

  • Internal: every build now checks that each AJAX handler has a capability and nonce check, and that dangerous calls are safe or explained. No change to how the plugin behaves.

3.2.890

  • Security: Managed Cloud keeps deleted backups recoverable for 30 days, so a hacked site cannot erase them. Storage tokens now grant only what each task needs.

3.2.889

  • Improved: Dashboard widget buttons share one height, and Explain buttons stay on one line on a phone.
  • Added: Explain windows for destinations and main features link to their full guide.

3.2.887

  • Fixed: licence checkout only opens approved addresses, and test sessions are refused.

3.2.886

  • Added: Backup Limits. A maximum CPU temperature pauses compression until the host cools, and a maximum share of your stated upload speed spaces out cloud uploads. Both are off until you set them.

3.2.885

  • IMPROVED: The readme now leads with what the plugin does. Each external service keeps a short disclosure, with the full reference at cloudscale.consulting/external-services/backup-restore/.

3.2.884

  • SECURITY: The plugin no longer runs on WordPress multisite, where a single site’s administrator could overwrite the whole network. It shows a notice instead.
  • SECURITY: Automatic restore refuses plain FTP, FTPS and http sources unless the site holds the primary’s signing key.
  • FIX: A cloud upload retry killed part way no longer ends the retries silently.

3.2.879

  • FIX: A readable state file no longer raises the “your backups are publicly downloadable” warning. It is reported on the plugin’s own screen, with the nginx rule that closes it.

3.2.878

  • SECURITY: Storage destinations can no longer point at the server’s private network or a cloud server’s metadata service. A NAS on your own network needs define( ‘CSBR_ALLOW_PRIVATE_DESTINATIONS’, true ); in wp-config.php.

3.2.877

  • SECURITY: The daily exposure check now also tests whether the plugin’s state files can be downloaded, which matters on nginx. Uploads abandoned for more than a day are cleaned out of staging. Managed-storage failure alerts now say what the licence service replied.

3.2.876

  • SECURITY: The crash recovery watchdog script shown on the page hides the Telegram bot token; Copy fetches the full script after a confirm.

3.2.875

  • SECURITY: The Telegram bot token is no longer written into the plugin page. Leave its field blank to keep it, or clear the Chat ID to turn Telegram off.

3.2.874

  • SECURITY: The backup encryption password is no longer written into the plugin page; Show and Copy fetch it after a confirm, and the Activity Log records it. The crash-alert config holding the Telegram bot token can no longer be downloaded from an nginx server.

3.2.873

  • IMPROVED: The plugin page loads faster and makes far fewer background requests: the account listing waits for the Recover tab, the Activity Log polls less when idle, and long cloud backup histories are built only when shown.

3.2.872

  • SECURITY: backups are signed, and a standby given the primary’s key (Local Backups, Backup signing) refuses automatic restores of anything else. Restores refuse SQL a backup never contains. OAuth connects check a state value. Protected Mode closes more ways in.

3.2.871

  • NEW: Protected Mode. Tick “This site was hacked” on a full restore: new security keys, application passwords revoked, administrators must set new passwords, and only your browser can sign in until an exit checklist is done. Updates stay allowed.

3.2.870

  • IMPROVED: Getting Started, Restore, the restore confirmation, Automatic Restore, Standby & DR, the Dashboard widget and the toolbar menu now each have an Explain button.
  • NEW: Activity Log Copy now copies a support report with versions, PHP limits, destinations, the last failure and the last 200 log lines, ready to email to support. It also has an Explain.
  • IMPROVED: every failed request is written to the Activity Log, failure emails include the same report, and error messages show the server’s reason and HTTP status instead of “Request failed” or “Network error”.

3.2.869

  • IMPROVED: Cloud Backup History has its own Explain covering golden images, the counters, Delete Soon, every column and action. Backup Schedule, Cloud Backup Settings and Local Backup History Explains now cover every control.
  • FIXED: Dropbox, OneDrive, SFTP/FTP and WebDAV now enforce the limit of 4 golden images, as S3, Google Drive and AMI already did.
  • IMPROVED: S3 Region is a drop-down of each provider’s regions, with Other for anything unlisted.
  • FIXED: On phones, checkbox ticks sat outside their boxes, the key copy buttons were too faint, and the SFTP Sign in with choices were cramped.
  • FIXED: Every Backup Now button (Dashboard widget, admin toolbar, Run Backup Now, Getting Started) now asks OK/Cancel first. A stray tap no longer starts a backup.
  • IMPROVED: The plugin page lists every destination under Where Backups Go, including each S3-compatible provider, and the FAQ links step-by-step setup for each.
  • IMPROVED: The MIT licence texts of the two bundled SFTP libraries, phpseclib and constant_time_encoding, now ship with the plugin, and the FAQ credits them.

3.2.868

  • IMPROVED: Alerts say which storage failed. An Automated Restore alert names its source, for example “Source: CloudScale Managed, andrewbaker.ninja”, in the subject and the body, and a backup whose upload failed names the failed destinations in the subject.
  • FIXED: A backup whose cloud upload failed, for example because the internet connection dropped, was not uploaded again until the next night’s backup, so a standby waiting for it went stale. Failed uploads are now retried every 30 minutes for up to 4 hours, only to destinations that do not have the file yet. You get one notice when it succeeds and one alert if it gives up.

3.2.866

  • IMPROVED: Every Explain panel and help line that lists cloud destinations now names all of them: S3 or S3-compatible storage (R2, B2, Wasabi and more), Google Drive, Dropbox, OneDrive, SFTP/FTP, WebDAV and Managed Cloud. The S3 card’s Explain covers the provider choice and the endpoint field.

3.2.865

  • NEW: Automated Restore reads the whole backup and checks every file before it touches the site. A damaged backup skips that day’s restore, sends an alert, deletes the damaged copy and leaves the standby as it was; the next scheduled run takes the next backup.
  • IMPROVED: A standby keeps no backups. Automated Restore deletes its downloaded copy once the restore is done, so a standby’s disk no longer fills with a copy of every night’s backup.

3.2.864

  • FIX: Automated Restore on a standby could fail with “already being copied by another process” when a large backup needed more than one download pass. The download lock from 3.2.863 now recognises its own process.

3.2.863

  • FIX: A restore from a damaged backup file can no longer empty your site’s files. Every file is written to a temporary copy first and swapped in only when complete, and the restore stops at the first file it cannot read, leaving everything else untouched.
  • FIX: Two processes can no longer download the same backup at once. Overlapping copies could produce a file of the right size with damaged contents.

3.2.862

  • NEW: SFTP, FTPS and FTP destination. Back up to your own server or NAS with a password or a private key. SFTP is built in and works on any host; the server’s SSH key is pinned on first connection. Uploads stream, resume after a dropped connection, and appear only when complete.
  • NEW: WebDAV destination for Nextcloud, ownCloud, Synology, QNAP or any WebDAV server, with free-space checks where the server reports a quota.
  • Both have the full set: scheduled uploads, retention, golden backups, Backup History, Restore tab copy-to-server, and Automated Restore on a standby.

3.2.861

  • NEW: S3-compatible storage. The S3 card now takes a provider: Amazon S3, Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google Cloud Storage, Hetzner, or any S3-compatible endpoint. Same bucket, keys and region fields, and the same multipart upload, parallel download and resume.
  • IMPROVED: Cloud Backups cards that are not set up yet start collapsed to their title bar. Click the bar, or a “configure below” link, to open one.
  • FIX: The retention storage warning compared the backups you want to keep with free space alone, so it fired when there was plenty of room. It now counts the space your current backups already use. The card also says when older backups are over the new limit, which are deleted after the next backup run, not on Save.
  • FIX: The Saved confirmation sits beside the retention Save button, vertically centred.

3.2.860

  • IMPROVED: Copies from Amazon S3 and CloudScale Managed (restores, standby refreshes, wp csbr cloud-pull) download four ranges at a time when that is faster. Each copy times both ways and keeps the faster, since on a link that is already full four connections are slower. Each range is checked before it is added, and an interrupted copy still resumes where it stopped.
  • IMPROVED: wp csbr cloud-pull resumes a partial download instead of starting again.

3.2.858

  • FIX: Uninstall now removes the plugin’s state files in wp-content. Backup archives, the token naming their folder, and the site-role and alert-label markers shared with other CloudScale plugins are kept on purpose.
  • TWEAK: Rewrote the plugin description and FAQ.

3.2.857

  • TWEAK: The restore modal’s “Full database, drop and recreate all tables” option is now “Full restore”. It always restored the backup’s files as well as its database, and the label and warning now say so.

3.2.856

  • FIX: OneDrive and Dropbox uploads retry a chunk that fails on a dropped connection, a throttle (429) or a server error (5xx), up to 5 attempts, instead of losing the whole upload. They resume where the provider says it is and honour Retry-After. Google Drive follows the same rules and now retries a 429 too.
  • FIX: Dropbox refreshes an access token that expires during a long upload.
  • FIX: wp csbr restore and wp csbr sync-from-cloud now run the same restore as the Restore button. The password check, file check, drop-in health check and alerts now apply to WP-CLI, and files-only backups work there.
  • TWEAK: Removed 12 server actions that nothing in the plugin called.

3.2.855

  • FIX: Test Connection for Google Drive, Dropbox and OneDrive failed to detect revoked credentials; it now shows the provider’s error.
  • FIX: A failed cloud listing no longer erases which backups are golden, so they can’t be pruned by mistake.
  • FIX: Delete oldest on Google Drive could delete the newest backup.
  • FIX: Saving the AMI card no longer resets “Max Cloud Backups to Keep” to 10.
  • FIX: Backups are verified before old ones are pruned; a corrupt or half-written backup is reported as failed and not uploaded.
  • FIX: Database read errors during a backup now fail it instead of producing a short dump.
  • FIX: Dropbox can be connected on a fresh install; cloud downloads refresh expired tokens and no longer stop at 300 seconds.
  • FIX: CloudScale Managed uploads once, and managed storage is pruned when S3 is unticked.
  • FIX: S3, Google Drive and OneDrive listings follow every page.
  • FIX: Restore fails if file extraction stops part way; files-only backups restore without touching the database.
  • FIX: Clone URL rewrite failures are reported; nested serialized values are rewritten correctly.
  • FIX: Crash recovery finds its settings again (alerts and recovery page), and rollback never deletes the plugin before the old version is ready.
  • FIX: Auto-restore fixed time is saved; an empty backup-day list stays empty; Telegram test sends once.
  • NEW: System Info health checks (PHP, folder, ZIP/AES, WP-Cron, overdue schedule, last result per destination) and wp csbr doctor.
  • NEW: S3 Test checks list and delete permissions and removes its test file; Managed Test checks storage credentials.
  • NEW: Activity log records skipped uploads, OAuth and token errors, dump/archive timings, skipped days and undelivered alerts.

3.2.854

  • FIX: Google Drive’s “Authorised redirect URI” box now shows the URI Connect sends (admin.php), so registering it no longer fails with redirect_uri_mismatch.
  • FIX: OneDrive gets the pre-sync space check and Delete oldest, like Dropbox and Google Drive.
  • FIX: A skipped cloud upload says to tick the provider under “Include in cloud backup” and Save, instead of “not configured”.
  • FIX: S3 Diagnose shows bucket, prefix, credentials source, last sync and the Include setting.
  • Changed: S3 and AMI text no longer say the AWS CLI is required; the plugin talks to AWS directly.

3.2.852

  • FIX: OneDrive uploads no longer report “OneDrive not configured” after a successful Test Connection. The OneDrive tick under “Include in cloud backup” is now saved; tick it and save once after updating.
  • Changed: Dropbox and OneDrive Explain and Diagnose describe the built-in API connection, not rclone, which is not needed.

3.2.848

  • Changed: alert-sync hooks use literal, prefixed names for WordPress.org Plugin Check.

3.2.847

  • Changed: alert settings (Telegram, environment label, mute) are stored under this plugin’s own prefix, migrated automatically, and kept in sync with the other CloudScale plugins.

3.2.846

  • IMPROVED: The Managed card reads “Use a password for extra security” with a Set a password button, or confirms backups are encrypted with your password.
  • FIX: Saving the backup encryption password checks the request’s nonce itself, not only in its callers.

3.2.845

  • IMPROVED: CloudScale Managed storage adds Oregon (US West), Frankfurt and Tokyo, ten regions in all. N. Virginia now reads as US East.

3.2.844

  • NEW: The Managed card suggests a backup password for extra security. Setting or changing the encryption password now asks for it twice and a confirmation that a copy is kept.
  • FIX: A restore of an encrypted backup without the matching password stops before changing anything.
  • FIX: A database-only backup can be restored again; it was refused for having no files.

3.2.843

  • FIX: Uploading a large backup to S3 or CloudScale Managed no longer grows the PHP process by the size of the backup. A 3 GB backup could be stopped by the server’s memory limit partway through its cloud uploads.
  • FIX: The Automatic Restore card no longer logs “Undefined variable $show_hour” and now pre-fills the suggested restore time.

3.2.842

  • FIX: A standby restoring its primary’s Managed backups reads the region the primary backs up to, not its own region choice or nearest region.

3.2.841

  • IMPROVED: WordPress.org review pass: output escaped where it is printed, every request value sanitised where it is read, admin scripts attached to the plugin’s script handle, and the External services section completed. Notification emails now show the site name in the header.
  • FIX: A restore request with an empty file name is refused instead of resolving to the backup folder.

3.2.840

  • NEW: Choose the CloudScale Managed backup region on the Cloud Backups tab: Automatic (nearest this site) or any of seven regions. Changing region sends new backups there; backups in the old region stop showing and expire there within 90 days, and switching back shows them.
  • IMPROVED: CloudScale Managed storage adds Singapore, Mumbai and São Paulo, so the regions are US, South America, Europe, Africa, India, Asia and Australia.

3.2.838

  • IMPROVED: CloudScale Managed storage adds a bucket in Sydney (ap-southeast-2), so the nearest region is now one of US, Europe, Africa or Australia.
  • IMPROVED: Backup alerts say where a Managed backup is stored, for example “CloudScale Managed: OK, stored in Africa (Cape Town)”. The Managed card and the Explain panel show the region too, instead of saying all storage is in the EU.

3.2.836

  • IMPROVED: CloudScale Managed storage now has a bucket in Cape Town (af-south-1) and N. Virginia (us-east-1) as well as Ireland (eu-west-1). On its first managed backup a site times ten requests to each region, and the account is kept in the nearest one from then on. A site in South Africa uploads to Cape Town instead of Ireland, roughly fifteen times faster per connection.

3.2.835

  • IMPROVED: Large backups now upload to S3 and CloudScale Managed up to four parts at a time instead of one, when the server has the memory for it. Uploads to a distant region were limited by the round trip, not the connection: one 3.2 GB backup took 51 minutes to reach Managed storage. A part that fails in a batch is sent again on its own with the usual retries.

3.2.833

  • FIXED: A site restored from a backup taken by 3.2.832 could start a full backup of itself a few minutes after the restore. The backup’s own “in progress” record travels inside its database, and the restored site took it for a backup of its own that had died. A run record is now used only by the site that wrote it, and never on a standby.
  • FIXED: A standby no longer runs a scheduled backup even when one is handed to it.
  • FIXED: Backup folders left behind by older versions of the plugin are no longer included in the uploads part of a backup. One site’s backup grew from 3 GB to 8 GB because of two old archives in such a folder.

3.2.832

  • FIXED: A scheduled backup that is killed part-way through its cloud upload (PHP restarted by a deploy or an update, a server reboot, an out-of-memory kill) is now noticed within five minutes and picked up again by itself. The archive is uploaded to the destinations that do not have it yet, and you are told both that it was interrupted and how it ended. Before, the run simply vanished: no alert, no retry, and no new backup in the cloud until the next night.
  • FIXED: The scheduled backup is now watched for the whole run, uploads included. A PHP error during the upload used to send nothing, because the safety net was switched off once the archive had been written.
  • FIXED: The cloud catch-up pass no longer stands down for six hours after a backup that died, and it now covers CloudScale Managed and OneDrive as well as S3, Google Drive and Dropbox.
  • FIXED: A scheduled backup killed while still building its archive is started again, once.
  • IMPROVED: A second scheduled backup cannot start while the previous one is still uploading.

3.2.830

  • FIXED: A large backup is no longer lost to one slow part of an Amazon S3 or CloudScale Managed upload. When S3 answers a part with a temporary error (a request timeout, or a 500, 502, 503 or 504), that part alone is now sent again, up to five times with waits of 2, 8, 30 and 60 seconds, instead of the whole upload failing. Before, a single timed-out part on a slow connection discarded a multi-gigabyte upload.
  • IMPROVED: The time allowed to send one part of a large S3 upload now follows the size of the part (up to 800 seconds for a full 50 MB part, 300 before), so an upload that is slow but still moving is allowed to finish.

3.2.819

  • CHANGED: The Restore button in the backup list now shows a box with an up arrow instead of a plain circular arrow, which read as “undo” or “refresh” rather than “restore from a backup”.
  • IMPROVED: When you choose your own site in “Bring a backup onto this server”, the list now says these are this site’s own backups and that restoring one replaces everything on this site with it. Copying it onto the server is still allowed, as it is how you recover a rebuilt server.

3.2.818

  • FIXED: A site can no longer be set up to restore itself from its own backups. Automatic restore replaces the whole site with the newest backup of another site, so pointed at its own backups it would undo everything written since the last one, every night. The source list now shows this site greyed out and unselectable, the save refuses it, and a schedule that already has it will not run. A standby copying its primary is unaffected.

3.2.817

  • FIXED: A restore now clears the site’s persistent object cache (Redis or Memcached). Before, the database was replaced but the cache kept serving the old settings, so a restored site could go on showing its previous theme, plugin list or site settings until the cache was cleared by hand, while the restore reported success. The cache is cleared as soon as the database has been restored, and also after an import that stops part-way.

3.2.816

  • FIXED: A restore no longer strands your backups in a folder the plugin has stopped looking in. The backup folder’s name carries a private token that was kept only in the database, so restoring a database that lacked it (a standby copying a primary, or a database taken from another site) made the plugin invent a new folder and leave the old one behind, unused, with the backups inside. The token is now also kept in a protected file outside the uploads folder, and the folder name stays the same after a restore. Sites that already have a folder keep it.

3.2.815

  • FIXED: Automatic Crash Recovery now takes its rollback copy when several plugins are updated at once. Before, it only did so for a single update, so “Update all” in the dashboard and wp plugin update --all left every plugin in the batch without a copy to roll back to, and the log said “No pre-update backup found”. Both now get a copy and the same post-update monitoring as a single update.

3.2.814

  • FIXED: Buying a one-off boost through PayPal could leave the order unpaid. The return link handed to PayPal had its parameters joined with &amp; instead of &, so when PayPal sent the buyer back the plugin could not find the order and quietly did nothing. The link is now built correctly and a return with a missing or expired security token is logged, with “Recover licence” as the way out.

3.2.813

  • FIXED: Automatic Crash Recovery no longer keeps copies of a plugin’s PHP files inside the uploads folder. Before each plugin update it copies the plugin so it can roll the update back, and those copies sat under uploads, where a security scanner reads any PHP as a possible compromise. Cyber DevTools’ file-integrity check reported 50 executable files on a standby after WordPress auto-updated one plugin. The copies now live under wp-content/csbr-state/, outside uploads, with deny rules. Rolling back works exactly as before, and copies taken by earlier versions are still used and are cleared by the same 72-hour sweep.

3.2.812

  • ADDED: Clone to a staging site. Restore any backup into a separate WordPress install on the same server, with its own directory and database and every URL rewritten, instead of over the live site. Set up targets on the new Clone Targets tab, run one with Clone Now (which names what it will overwrite and asks first) or refresh it after each scheduled backup on the days you pick.
  • ADDED: The clone refuses to run against this site’s own database or directory, or a directory that contains this site, and checks a target’s wp-config.php is writable before it deletes anything.
  • ADDED: csbr_clone_post_restore PHP action for steps to run after a clone. The clone runs no shell scripts.

3.2.809

  • FIXED: A restore now replaces files the web server cannot open for writing, such as files owned by another user after an SFTP upload, a control-panel edit or a host-side deploy. Those files were reported as “could not be written” and the stale copy was left in place, so the restore was partial while looking complete apart from a warning. The new file is written beside the old one and swapped in atomically, so a failure part way leaves the old file, never a gap. A file whose directory is not writable is still reported.
  • FIXED: The restore warning that lists files which could not be written printed “Array; Array; Array” instead of naming them. It now names the component, the reason and an example path, as the WP-CLI output already did.

3.2.806

  • FIXED: Backups failed in their first second on sites where the database is dumped by PHP, with “count(): Argument #1 must be of type Countable|array, null given”. A variable was released two lines before it was counted. Introduced in 3.2.799. If you installed 3.2.799 to 3.2.805, check that your scheduled backups have been running.
  • CHANGED: The Last recovery panel leaves out a phase that took no time, such as the copy from cloud storage when the backup was already on the server.

3.2.805

  • CHANGED: On the Recover a site tab, the “Cannot log in to wp-admin at all?” card has moved to the bottom, after the restore steps it used to interrupt. When Automatic Crash Recovery is already on it is now a single line saying so, and the full card appears only when it is off.

Older versions: see CHANGELOG.md in the plugin folder.