Incremental encrypted copies stored off-site, a restore point before every update, and scheduled restore testing that boots the backup and confirms it works. Recovery is one click, and you can prove the copy is good before the day you need it.
Included on every plan. No add-on pricing.
Almost every WordPress site has a backup plugin installed. A much smaller number have a backup that would actually restore. The failure modes are boring and common: the plugin hit a PHP timeout partway through a large database, the destination filled up, credentials expired, the schedule silently stopped after a plugin conflict, or the backup has been running perfectly for two years to a folder on the same server that just got wiped.
None of these produce an alert, because the plugin believes it succeeded. You discover the truth during an incident, which is the worst possible moment to learn something new about your infrastructure.
After the first full copy, only what changed is transferred. Backups complete in seconds rather than hours, do not hammer the host, and do not time out on large databases. Sites with large media libraries stay practical to back up daily or better.
AES-256 encryption at rest, TLS 1.3 in transit, stored in a region you choose and never on the same infrastructure as the site. You can bring your own S3-compatible bucket if backups must live inside your own account.
Any update, bulk action or migration takes a fresh snapshot first. Rollback never depends on last night's scheduled run, which may be nineteen hours old and missing the orders that came in this morning.
WooCommerce sites can back up order and customer data continuously rather than on a schedule, so a restore does not lose the transactions that arrived between backups.
On a cadence you set, WPCentrify restores a backup into an isolated sandbox, boots WordPress, checks the database imports, confirms the home page and admin respond, and records a pass or fail.
Each test produces a dated record. "Backup verified 3 September, restore completed in 2 minutes 14 seconds" is a much better answer to a nervous client than "backups are running".
Restore a whole site, a single file, a plugin folder, or an individual database table. You do not have to roll the entire site back to fix one broken thing.
Because tests measure real restore duration, you know your actual recovery time objective per site instead of guessing at it.
What people ask before they turn this on.
In encrypted object storage in the region you select, never on the same infrastructure as the site being protected. You can supply your own S3-compatible bucket so backups sit inside your own account.
It depends on site size, but restore testing measures it for you. A typical 3GB site restores in two to four minutes. Because the test runs on a schedule, you always know your real recovery time rather than estimating it.
Yes. Restore a full site, files only, database only, a single table, or an individual file. Selective restore is usually the right tool when one plugin has corrupted its own settings.
You can download everything before you go, and there is a grace period after cancellation during which exports remain available. Backups are never held to encourage you to stay.
It can, and it is usually better because it is off-site, tested and granular. Many people keep both. Host backups tend to be full-server snapshots with coarse restore options and no verification.
Connect a site in under two minutes and see this working against something real. Free during early access.
Free during early access. Keep your data, export any time.