All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Lost my WordPress home page by accident. What backup setup would you use so it never happens again?
Hi everyone,
I recently lost the home page on one of my WordPress sites. It was deleted or changed and I had no recent backup, so I had to rebuild it. I want to set up a proper backup and recovery routine so this doesn’t happen again.
My setup:
WordPress site on shared hosting or a small VPS
Only me editing the site, no team
Small budget, so I prefer free or cheap tools
My questions:
Which free backup plugin do you trust most (UpdraftPlus, Duplicator, or something else)?
Where should I store backups? Google Drive, S3-compatible storage, or a separate VPS?
How often should a small site be backed up, daily or weekly?
Is there a way to recover a single deleted page without restoring the whole site? I’ve heard about post revisions and the trash, but I’m not sure how far back they go.
Do you test your restores, or only trust that backups work?
I’d also like to hear about any mistakes you’ve made with backups, so I can avoid them.
Thanks for any advice!
Comments
If you're on shared hosting, UpdraftPlus (free) or WPvivid are both solid picks since they support scheduled off-site uploads out of the box. Duplicator's free tier is great for manual point-in-time snapshots before big edits, though scheduled backups are locked behind Pro. If you're on a VPS with SSH access, a simple cron job running
wp db export(ormysqldump) +resticorborgis much lighter and avoids PHP timeout headaches.A quick breakdown for the rest of your setup:
wp-contentmostly changes when you upload media or update plugins. Also grab a manual snapshot right before doing major edits or updates.EMPTY_TRASH_DAYS), and Revisions keep earlier versions of edits you've saved (unless capped inwp-config.php). If it's already gone from Trash, you don't need to wipe your live site: restore the backup to a local setup (e.g., LocalWP or Docker) or a staging subdomain, then either copy-paste the page content or export just that page via Tools -> Export.wp-contentand a valid SQL dump.Common mistakes to watch out for:
1. Forgetting the database (or only backing up
wp-content) — WordPress pages live in the DB, not in files.2. No retention limit — leaving old daily archives piling up until the hosting disk hits 100% and MySQL crashes.
3. Keeping backups only on the same VPS/account — if the host suspends the account or the disk dies, the backups go with it.
On the Plesk side, we daily backups to a separate server, but for an end user, Google Drive is both cheap and practical. Also, handling it directly on the hosting side is usually way more stable since you get the full database + files intact. Plugins usually work fine, sure, but personally i feel like plugins can break after an update, or fail if wp-cron stops running properly, so solving backups at the hosting/panel level makes more sense to me. Then again, most of the sites we deal with arent WordPress anyway, so maybe im just biased because im used to manual/server-side backups.
If the site size isnt huge, taking a backup every night instead of weekly, or at least doing incremental backups is the smartest move. Something can always go wrong mid-week, and you don't want to roll back all the way to Monday. On the other hand, if its a static site that barely gets updated and doesnt hold dynamic data, weekly is probably fine too.
sure i'll do your homework ig
that doesn't makes sense, you never heard of wordpress staging before?. sure you can argue "Real Men Test In Production" but you already seen how it goes
wp db exportis the fastest backup method (if you only concerned about written data into database) and doesn't require complicated setup. most of shared hosting like cpanel/plesk/directadmin usually have thisnone of the plugin works properly imo. setting up a wp db export and rsync script is much more durable.
follow 3-2-1 rules, if you have $20000 budget in crypto i can tell you the best backup location
yes
you have to understand first that a "single page" is composed on several data inside your database. not just like uploading a single html file to fix it.
do both. archive integrity must be tested, and restore must be tested too. at bare minimum do it when you setting up the backup environment.
I trusted a backup system that being provided by provider without knowingly they're not encrypted, that ended with all of credentials inside the vps compromised because someone accessed the backed up data. had i stay strict with my own backup stack using encrypted borg backup, this wouldn't happen.
recommended to dive in if you're into that kind of thing wordpress https://io.bikegremlin.com/category/wordpress/
i havent touched wordpress since 2019 so YMMV
Google Drive and using a idle vps as backup should work just fine.
Thanks both, this is really helpful.
The point about plugins breaking after updates or when wp-cron stops running is something I hadn’t considered. I’d been thinking of plugins as the easy option, but a backup that silently fails is worse than no backup. Panel-level backups of the full database and files make more sense to me now.
On frequency, I agree. The site changes often right now, so I’ll go with nightly backups and keep a few days of history, so I’m not stuck rolling back a whole week.
I have two follow-up questions, if you don’t mind:
For the Plesk setup you described, how many days of backups do you usually keep on the separate server? Is 7 to 14 days a reasonable amount?
If I’m on a plain VPS without Plesk, would you recommend a simple script (mysqldump plus rsync to another server) or a panel like Plesk or cPanel just for backups?
Thanks again for taking the time to explain.