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


Clicking Restore next to any backup opens a unified restore modal. Choose how you want to restore before confirming:
Full restore puts back everything the backup holds: its files, then its database. The restore runs on the server, so you can close the page. The plugin activates Maintenance Mode for the duration, serving HTTP 503 to frontend visitors while wp-admin stays accessible to administrators.
- An encrypted backup is checked against this site’s backup password first. Without the right password the restore is refused before anything is touched.
- Maintenance mode activated,
wp-content/.maintenancewritten to disk. - Files first: uploads, plugins, themes, mu-plugins, languages, drop-ins,
.htaccess, core and root files, whichever the backup includes. Files go first because the database refers to them.wp-config.phpis never restored: it holds this server’s own database credentials. - Then the database: the
.sqldump is imported, replacing the tables it contains. The object cache is flushed afterwards. A database-only backup skips the files step, and a files-only backup leaves the database alone. - Every restored file is checked against the backup for presence and size.
- Maintenance mode deactivated,
.maintenancedeleted. - Health check: a drop-in (for example
object-cache.php) that would crash this server is renamed out of the way and named in the result. - The result is recorded in the activity log, and a success or failure alert goes to your notification channels.
Specific tables only, restores only the tables you select. The plugin lists every table found in the backup; tick the ones you want. Only those tables are dropped and recreated, all others remain untouched. No maintenance mode is used.
This site was hacked, a tick shown for a full restore. It turns on Protected Mode after the restore, because a plain restore brings back the hole the attacker used and leaves stolen logins working.
Both modes require you to tick a confirmation checkbox before Restore Now activates. Take an EC2 AMI or hosting snapshot first, if anything goes wrong you can roll back instantly.
Important: a full restore is irreversible. Any changes made after the backup date are permanently lost.
If a full restore fails mid-way, the plugin takes the site out of maintenance mode, records the failure and sends an alert. A database that rejected part of the dump is reported as failed, not as a success. Restore again from a known-good backup. If PHP itself dies during the restore, the next admin page load removes the stale .maintenance file and records which phase it died in. If the site is still stuck, delete wp-content/.maintenance via SFTP or SSH and inspect wp-content/debug.log.
From a shell, wp csbr restore <file> --yes runs exactly the same restore as the Restore button, with the same checks and alerts. It takes a database safety backup first unless you pass --no-safety-backup. It can be narrowed with --db-only, --files-only or --components=uploads,themes. wp csbr sync-from-cloud --yes copies the newest S3 backup here and restores it the same way. Both exit non-zero on failure and refuse to start while another restore is running.
Which tables to choose for a partial restore
The Specific tables only mode is useful when you only need to recover one piece of the site without reverting everything else. The table names below assume the default wp_ prefix, if your install uses a different prefix (e.g. abc_), substitute it accordingly.
Posts, pages, and custom post types
wp_posts, every post, page, revision, menu item, and custom post type record.wp_postmeta, all post metadata (custom fields, featured image IDs, ACF data, etc.). Always restore this together withwp_posts.
Comments
wp_comments, all comment records including spam, pending, and approved.wp_commentmeta, comment metadata. Always restore together withwp_comments.
Users and login data
wp_users, usernames, email addresses, and hashed passwords.wp_usermeta, user roles, preferences, and metadata. Always restore together withwp_users.
Site settings and plugin configuration
wp_options, site URL, theme settings, plugin configuration, widget data, and transient cache. Restoring this table rolls back all plugin settings to the backup date, not just one plugin. If you only need to recover a single plugin’s settings, a full database restore is usually safer.
WooCommerce orders and customers
wp_posts+wp_postmeta, WooCommerce stores legacy orders as a custom post type. Restore both tables.wp_wc_orders+wp_wc_order_items+wp_wc_order_operational_data+wp_wc_order_addresses+wp_wc_order_stats, if HPOS (High-Performance Order Storage) is enabled, WooCommerce uses these dedicated order tables instead. Restore all of them together.
Email logs (Contact Form 7, Gravity Forms, Fluent Forms, newsletters)
These plugins store form submissions and email logs in their own tables. Look for tables with the plugin name in them, for example wp_cf7_* for Contact Form 7 add-ons, wp_gf_* for Gravity Forms, wp_fluentform_* for Fluent Forms, or wp_newsletter_* for newsletter plugins. Select all tables belonging to the plugin you want to recover. Because these tables are self-contained, restoring them does not affect posts, users, or any other part of the site.
The safest approach, before doing any partial restore on a live site, take a fresh backup first. That way if the partial restore causes unexpected problems, you can immediately do a full restore back to the moment before you started.