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


The Getting Started tab is your home base. It shows the current state of your site’s protection at a glance and walks you through the three things that make a site safe: create a backup, copy it offsite, and set a schedule.
Step 1: Create a backup
Click Back Up Now to create a full local backup immediately. The most recent backup’s filename, size, and age are shown once one exists. You can download it directly from here with the Download button.
Step 2: Copy to the cloud
Choose where offsite copies go: CloudScale Managed (the recommended zero-config option; backups land in secure storage in the region nearest your site, or one you choose from ten, on six continents) or Your own cloud (AWS S3 or S3-compatible, Google Drive, Dropbox, OneDrive, SFTP/FTP or WebDAV, configured in the Cloud Backups tab).
Once a destination is selected, Copy Last Backup to Cloud pushes your most recent backup immediately with a live progress bar.
CloudScale Managed subscription: subscribe directly from this panel. Once active, the card shows your licence key, storage used, and a link to view all stored backups in the Restore tab.
Where Managed backups are stored: in one of ten AWS regions on six continents. Pick one from the Backup region list on the CloudScale Managed card, or leave it on Automatic (nearest this site).
- US East, N. Virginia (us-east-1)
- US West, Oregon (us-west-2)
- South America, São Paulo (sa-east-1)
- Europe, Ireland (eu-west-1)
- Europe, Frankfurt (eu-central-1)
- Africa, Cape Town (af-south-1)
- India, Mumbai (ap-south-1)
- Asia, Singapore (ap-southeast-1)
- Japan, Tokyo (ap-northeast-1)
- Australia, Sydney (ap-southeast-2)
On Automatic, the plugin times ten requests to each region on its first Managed backup and uses the fastest. Uploads are much faster to a nearby region: from Cape Town, a 3.2 GB backup took 51 minutes to reach Ireland and under 4 to reach Cape Town. Choose a region yourself when your data has to stay in one place, for example in Europe.
Fast copies both ways. Large backups upload up to four parts at a time. Downloads time one range against four and keep whichever is faster, so a distant region is not held back by the round trip, and a connection that is already full is not slowed by extra streams. Managed storage is Amazon S3 Glacier Instant Retrieval, so a restore starts straight away, with no wait for an archive to thaw.
Changing region moves nothing. New backups go to the new region. Backups already in the old region stop showing in the plugin and expire there within 90 days. To get one of them back, switch to the old region again and it is listed. The card and every backup alert say where your latest backup is, for example CloudScale Managed: OK, stored in Africa (Cape Town).
How long Managed backups are kept, and the storage limits:
- A time window you choose: Keep cloud backups for 1, 2 (the default) or 3 months. Nothing is kept longer than 90 days, even if your site stops backing up. A backup that was deleted, whether by you or by the window ending, stays recoverable through support for 30 more days and is then erased, so the last copy is gone by day 120. That limit is enforced in storage, not by the plugin, so it still applies to a site that is offline, broken or abandoned.
- Space that grows with the window: about 375 GB at 1 month, 750 GB at 2 months and 1,125 GB at 3 months. A single backup can be up to 5 GB.
- Where it is enforced: on CloudScale’s server, against your licence key. Changing plugin settings or the database on your site cannot raise a limit.
- What happens at the limit: before each upload the plugin deletes your oldest Managed backups to make room. If a backup still does not fit, or is over 5 GB, the upload is refused before it starts and the plugin tells you why. The backup on your own server is not affected. There is no overage billing: you never pay more than $5 a month.
So 90 days is a ceiling, not a guarantee of how long a backup stays available to restore. If you need longer retention, use Your own cloud, where you control the bucket’s lifecycle rules.
Step 3: Set a schedule
Enable Automatic backups and choose a frequency. The schedule runs via WordPress cron. For production sites, replace WP-Cron with a real server cron for reliability (see the Backup Schedule card on the Local Backups tab for setup instructions).
Optionally enable Email reminders. If no backup has been created within the reminder interval you’ll receive a nudge email to the admin address.
The plugin does not run on WordPress multisite. See Backup Signing and Security for why.