PluginsAppsPricingConsultingAboutBlog (opens andrewbaker.ninja in a new tab)Help Get in touch
👁28views

← CloudScale Plugin Help/CloudScale Backup & Restore, Free WordPress Backup Plugin with One-Click Restore & Cloud Sync

Cloud Backup Settings

CloudScale Backup & Restore, Free WordPress Backup Plugin with One-Click Restore & Cloud Sync, Cloud Backup Settings screenshot
On a phone
CloudScale Backup & Restore, Free WordPress Backup Plugin with One-Click Restore & Cloud Sync, Cloud Backup Settings screenshot, as it appears on a mobile screen
The same panel at 390px, showing how it reflows. Cropped to the first screens.

The Cloud Backup Settings card (blue) is the master control for all automated cloud syncing. It lives at the top of the Cloud Backups tab.

Cloud backup days, the days on which cloud sync runs. On each selected day the plugin runs providers in this fixed order: AMI snapshot → S3 → Google Drive → Dropbox → OneDrive → SFTP/FTP → WebDAV. Each provider is independent, a failure on one does not prevent the others from running.

Cloud Backup Delay, minutes after the local backup completes before cloud sync begins. Minimum 15 minutes. This ensures the local zip is fully written and closed before upload starts. The scheduled cloud sync time is shown when a schedule is configured.

Include in cloud backup, checkboxes to enable each provider individually:

  • AWS S3 (or the S3-compatible service chosen on its card), uploads the backup zip to your bucket through the S3 API (signed HTTPS requests from PHP, no AWS CLI needed).
  • Google Drive, uploads the backup zip to Google Drive through the Drive API. Requires a connected Google account.
  • Dropbox, uploads the backup zip to Dropbox through the Dropbox API. Requires a connected Dropbox app.
  • Microsoft OneDrive, uploads the backup zip to OneDrive through Microsoft Graph. Requires a connected Microsoft account.
  • SFTP / FTP, uploads the backup zip to your own server over SFTP, FTPS or FTP.
  • WebDAV, uploads the backup zip to a WebDAV folder such as Nextcloud, ownCloud or a NAS.
  • AWS EC2 AMI Snapshot, creates an Amazon Machine Image of the entire EC2 server.

Interrupted uploads are retried, not restarted. Large backups go up in chunks. If a chunk hits a dropped connection, a throttle (HTTP 429) or a server error (5xx), that chunk alone is sent again, up to 5 attempts, waiting 2, 8, 30 and 60 seconds (longer if the provider asks for longer). This applies to Google Drive, Dropbox, OneDrive and S3. OneDrive and Dropbox check what already arrived, so a chunk that arrived but got no reply is not sent twice. Dropbox also renews an access token that expires during a long upload. Each retry is written to the Activity Log. An upload fails only when the same chunk fails 5 times, or when the provider refuses it outright (for example a full drive or revoked access).

A failed upload keeps trying. If a scheduled upload still fails, for example during an internet outage, the plugin tries again every 30 minutes, up to 8 times over 4 hours, and only for the destinations that do not have the backup yet. It stops when a newer backup exists. You get one notice if it recovers and one alert if it gives up, not one for every attempt.

Providers that have not been configured in their cards below are greyed out and cannot be enabled here, and their cards start collapsed to the title bar with a Not set up chip; click the bar to open one. All of them can be active simultaneously, the backup zip is uploaded to each in turn.

Max Cloud Backups to Keep, the retention limit applied to each cloud destination independently. When this limit is exceeded after a sync, the oldest non-golden backup is deleted automatically. Applies to S3 objects, Google Drive, Dropbox and OneDrive files, files on your SFTP/FTP or WebDAV server, and AMI snapshots. Golden images are exempt from this limit.

If the local backup schedule is disabled while cloud sync is enabled, a warning banner appears at the top of the page, cloud sync will upload the most recent existing backup, but no new local backups will be created first.

← Back to all sections