內容簡介
CloudScale Backup & Restore 是一款專為大型網站設計的備份與還原外掛，能夠同時備份至五個目的地，並提供一鍵還原功能。無論是伺服器故障或外掛更新問題，這款外掛都能快速恢復網站，確保資料安全。
【主要功能】
• 同時備份至五個目的地
• 一鍵全站還原，無需維護模式
• 自動恢復至新網站的功能
• 支援自我修復的備份
• 自動回滾不良外掛更新
• 提供失敗備份的即時警報
外掛標籤
開發者團隊
② 後台搜尋「CloudScale Backup & Restore」→ 直接安裝（推薦）
📦 歷史版本下載
原文外掛簡介
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.
Seven kinds of destination at once. Amazon S3 or any S3-compatible store (R2, B2, Wasabi and more), Google Drive, Dropbox, OneDrive, your own server over SFTP or FTP, or WebDAV (Nextcloud, a NAS), plus CloudScale Managed Cloud.
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.
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.
Alerts that reach you. Email and Telegram alerts for failed backups, restores and recoveries, including PHP fatal errors.
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
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
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
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
This plugin optionally connects to third-party services when those features are configured by the site administrator. No data is sent to any external service unless the administrator has explicitly enabled the relevant integration.
Telegram Bot API (optional notifications)
Service: Telegram Messenger, https://telegram.org/
When a Telegram bot token and chat ID are entered, the plugin sends backup,
restore, rollback and error alerts to that chat. A message holds the site name,
event status and, for errors, the PHP error, file and line. No visitor data,
post content or backup data is sent.
API endpoint contacted: the sendMessage method on api.telegram.org, addressed with
the administrator’s own bot token.
Terms of Service: https://telegram.org/tos
Privacy Policy: https://telegram.org/privacy
Telegram Bot API documentation: https://core.telegram.org/bots/api
Amazon S3 (optional cloud backup)
Service: Amazon Web Services, https://aws.amazon.com/
When S3 settings are configured, the plugin uploads backup zips to the
administrator’s own S3 bucket via the S3 REST API. Only the backup zip is sent.
The credentials are stored on the site and sent only to the AWS S3 endpoint.
API endpoint contacted: the Amazon S3 host for the bucket’s own AWS region, for
example s3.eu-west-1.amazonaws.com.
Terms of Service: https://aws.amazon.com/service-terms/
Privacy Policy: https://aws.amazon.com/privacy/
S3-compatible storage (optional cloud backup)
Services: Cloudflare R2, Backblaze B2, Wasabi, DigitalOcean Spaces, Google
Cloud Storage, Hetzner Object Storage, or another S3-compatible service the
administrator names.
When one is chosen on the S3 card, backup zips go to the administrator’s own
bucket there through the S3 API, as for Amazon S3. Access keys go only to the
endpoint the administrator entered.
API endpoint contacted: the endpoint shown in the S3 card.
Cloudflare: Terms https://www.cloudflare.com/terms/ Privacy https://www.cloudflare.com/privacypolicy/
Backblaze: 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: Terms https://www.digitalocean.com/legal/terms-of-service-agreement Privacy https://www.digitalocean.com/legal/privacy-policy
Google Cloud: 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/
Your own SFTP, FTP or WebDAV server (optional cloud backup)
When the administrator enters a server on the SFTP / FTP or WebDAV card, backup
zips are uploaded to it, and listed, downloaded and deleted there. The sign-in
details go only to that server. No other party is contacted; the server owner’s
terms apply.
Google Drive (optional cloud backup)
Service: Google, https://workspace.google.com/products/drive/
When Google Drive settings are configured, the plugin transfers backup zip files
to the administrator’s own Google Drive account using the Google Drive v3 REST
API and OAuth 2.0. No data is sent unless the administrator has completed the
OAuth authorisation flow (entered a Client ID and Client Secret from Google
Cloud Console and clicked “Connect to Google Drive”). Only the backup zip file
is uploaded. OAuth tokens (access token and refresh token) are stored in the
WordPress options table.
API endpoints contacted: www.googleapis.com (Drive v3) and oauth2.googleapis.com
(OAuth 2.0 tokens).
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
Dropbox (optional cloud backup)
Service: Dropbox, https://www.dropbox.com/
When Dropbox settings are configured, the plugin transfers backup zip files to
the administrator’s own Dropbox account using the Dropbox v2 REST API and
OAuth 2.0. No data is sent unless the administrator has completed the OAuth
authorisation flow (entered an App Key and App Secret from the Dropbox App
Console and clicked “Connect to Dropbox”). Only the backup zip file is
uploaded. OAuth tokens are stored in the WordPress options table.
API endpoints contacted: api.dropboxapi.com and content.dropboxapi.com (Dropbox v2
REST API).
Terms of Service: https://www.dropbox.com/terms
Privacy Policy: https://www.dropbox.com/privacy
Microsoft OneDrive (optional cloud backup)
Service: Microsoft, https://learn.microsoft.com/en-us/onedrive/
When OneDrive settings are configured, the plugin transfers backup zip files to
the administrator’s own Microsoft OneDrive account using the Microsoft Graph
REST API and OAuth 2.0. No data is sent unless the administrator has completed
the OAuth authorisation flow (entered an Azure App Client ID and Client Secret
and clicked “Connect to OneDrive”). Only the backup zip file is uploaded.
OAuth tokens are stored in the WordPress options table.
API endpoint contacted: https://graph.microsoft.com/ and https://login.microsoftonline.com/
Terms of Service: https://www.microsoft.com/en-us/servicesagreement/
Privacy Policy: https://www.microsoft.com/en-us/privacy/privacystatement
CloudScale Managed Cloud Backup (optional, paid service)
Service: CloudScale Consulting, https://cloudscale.consulting/
When subscribed, the plugin asks the CloudScale broker for a short-lived,
prefix-scoped Amazon S3 token, then uploads backup zips straight to CloudScale’s
S3 storage; backup bytes never pass through the broker. It times ten HEAD requests per storage
region and sends the averages, to pick the nearest region. Nothing is sent until
a licence key is entered. Storage is encrypted at rest. For extra security, Encrypt
backups adds AES-256 encryption with the site owner’s own password before upload. Leave us a message sends the typed email and
message, hostname and licence key on Send. Clicking the PayPal button sends the
product name, hostname and the optional email typed above it to /checkout-start,
so a failed checkout can be followed up.
API endpoints contacted (broker): 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.
Storage and timing requests go to CloudScale’s Amazon S3 storage in its ten
regions: af-south-1, eu-west-1, us-east-1, ap-southeast-2, ap-southeast-1,
ap-south-1, sa-east-1, us-west-2, eu-central-1 and ap-northeast-1.
Terms of Service: https://cloudscale.consulting/terms/
Privacy Policy: https://cloudscale.consulting/privacy/
PayPal (optional, payment for Managed Cloud Backup)
Service: PayPal, https://www.paypal.com/us/home
Subscription payments for the optional CloudScale Managed Cloud Backup service are
processed by PayPal on its own hosted checkout; card details never reach this plugin
or the site. When the administrator starts a subscription, the subscriber’s email and
the order amount ($5.00 USD) are sent from the WordPress server to the PayPal REST API
(api-m.paypal.com) to create a checkout session. Nothing is sent unless the
administrator chooses to subscribe.
API endpoint contacted: api-m.paypal.com (live) or api-m.sandbox.paypal.com
(sandbox testing), the PayPal REST API: https://developer.paypal.com/api/rest
Browser-loaded script: PayPal’s JavaScript SDK from www.paypal.com/sdk/js, loaded
into the plugin’s admin screen only after an administrator opens the subscription
checkout. PayPal requires the SDK be served from its own origin so a compromised build
can be revoked, so it cannot be bundled with the plugin.
Terms of Service: https://www.paypal.com/us/legalhub/paypal/useragreement-full
Privacy Policy: https://www.paypal.com/us/legalhub/paypal/privacy-full
AWS EC2 / AMI snapshots (optional, AMI snapshot feature only)
Service: Amazon Web Services, https://aws.amazon.com/
When the AMI snapshot feature is used, the plugin reads instance metadata
(instance ID and region) from the local EC2 Instance Metadata Service at the
link-local address 169.254.169.254. This address is only reachable from within an EC2
instance and no data leaves the server at this step. AMI creation, status poll,
deregister, and snapshot delete requests are then issued directly to the AWS
EC2 REST API (no external tools required). The same AWS credentials
(access key ID and secret key) used for S3 are used; if none are configured
the plugin attempts to use the EC2 instance role via IMDS.
API endpoint contacted: the Amazon EC2 host for the instance’s own AWS region, for
example ec2.eu-west-1.amazonaws.com.
Terms of Service: https://aws.amazon.com/service-terms/
Privacy Policy: https://aws.amazon.com/privacy/
Automatic Crash Recovery: health check probe (optional)
When Automatic Crash Recovery is enabled, the plugin periodically sends an HTTP
request to the administrator-configured health check URL to verify the site is
responding. The URL defaults to the site’s own home URL. No personal data is
transmitted. The request is a plain GET with no authentication payload. The
same probe is made when the administrator clicks “Test Health Check” in the
plugin settings. If a system-cron watchdog script is installed on the server,
that script also probes this URL independently via curl. The health check URL
is set by the administrator and is never shared with any third party.
No Terms of Service or Privacy Policy apply (the request goes to a URL you own).
Gmail SMTP port check (only when sending a test email)
Service: Google, https://workspace.google.com/gmail/
When the administrator clicks Send Test in the Notifications card, the plugin opens
a TCP connection to smtp.gmail.com on ports 587, 465 and 25 and closes it at once,
to tell whether this server can reach an outside mail server at all. No email,
login or data of any kind is sent; only the connection is attempted. Nothing
happens until the button is clicked.
Terms of Service: https://policies.google.com/terms
Privacy Policy: https://policies.google.com/privacy
Help documentation link
The plugin’s header links to its help pages on help.cloudscale.consulting. It is
an ordinary link the administrator may choose to open; the plugin itself never
requests that host and sends it no data.
Privacy Policy
CloudScale Backup & Restore does not collect, transmit, or store any personal data. All backups are stored locally in the cloudscale-backups/ folder inside your WordPress uploads directory. No telemetry or analytics are sent by this plugin. Optional cloud backup features (S3, Google Drive, Dropbox, OneDrive, AMI snapshots, CloudScale Managed) transmit data only when explicitly configured by the site administrator. CloudScale Managed backups are encrypted at rest; Encrypt backups adds the site owner’s own password. See the External services section above.
