Most people running several WordPress sites have a different backup plugin on each one, and trust none of them. The schedules drifted, two of them silently stopped running months ago, and nobody has ever tested a restore. That is not a backup strategy. It is a hypothesis.
What makes a WordPress backup trustworthy?
Three things, and most setups miss at least one:
- It actually ran. You can see, without logging into the site, when the last backup completed and how big it was.
- It restores. Not "the file exists" but "we put it back and the site came up".
- It is portable. If the tool that made it disappears tomorrow, the backup is still worth something.
A plugin sitting inside the site it is protecting struggles with all three. It reports to itself, it restores into its own assumptions, and its archive format usually only means something to that same plugin.
How Vibery handles it
Backups are a property of the platform, not a plugin you install per site. Every site you host with us gets the same mechanism, so "which backups ran last night" has one answer across every site.
Restores are point-in-time. You pick a restore point and the site goes back to it, rather than choosing between one nightly snapshot and nothing.
And the artifact is a portable bundle you can download. The bundle carries the whole site: database, uploads, themes, plugins, and any custom or must-use plugin code. We use the same bundle format for exporting a site off Vibery entirely, which is the honest test of whether it is really portable: if our own migration path uses it, it works.
Can I get my site out?
Yes, at any time, without asking us. Export produces a bundle you can restore elsewhere.
This matters more than it sounds. A backup that only restores into the vendor that made it is a lock-in mechanism wearing a safety vest. Being able to leave is what makes it safe to arrive.
Making backups something you stop thinking about
The workflow that works in practice is to stop scheduling backups as a separate chore and attach them to the risky moments instead:
- "Back up this site, then update the plugins." The restore point exists before the risk does.
- "Schedule nightly backups on all my hosted sites." One rule, not one plugin per site.
- "Restore the staging site to yesterday morning." A sentence, not a support ticket.
The point is not that backups become automatic. It is that taking one stops being expensive enough to skip.
No comments yet