Have you ever restored a website (in wp) because for some reason it’s needed ?
If yes,
how did the process go ?
Any “I wish I had known this before” moment ??
What tools you used ?
Do you track code files with Git also ?
—
Curiosly asking, I have never been in the situation to have to do this.
I need to decide a somehow definitive system to use as a backup strategy and we have a lot of options:
– backup at hosting level
– backup as WordPress plugin that save the artifacts in a remote storage (S3, Google Drive,…)
– cron-job script handcrafted (rsync, mysql dump, …)
– …
Thanks
Always backup to a remote server using whatever method works best for you.
There are a lot of.different solutions for that.
You can backup your site manualy (get the database and files and put it somewhere safe).
You can use a wordpress plugin like updraft (I dont like this method but it’s easy).
you can pay a service like wpumbrella. It will back up everything every day and you can update your websites by bulk.
There are also companies that offer this kind of services and it’s pretty cheap. We use lms backup cloud dor our plesk websites for example.
Yes. Super easy. I always use daily hosting backups, make a one-time backup before doing anything major, like upgrading core or major plugins like woocommerce.
I recommend using host-level backups, even IF you do plugin-based backups.
Plenty of times. Sometimes a major plugin update will break a site and the simplest solution is to roll the site back.
I prefer hosts that offer backups, even if I have to do them manually. For everything else, I use All in One Migration and save it to my computer.
Yes, through several ways, and all worked fine: Updraft, GoDaddy’s backup, BlueHost’s backup, and AIO WP Migration.
>backup at hosting level
We use this method on our SiteGround hosting, for free (for the 30 days)
>backup as WordPress plugin that saves the artifacts in a remote storage (S3, Google Drive,…)
We use this approach as well: All in one WP migration plugin + 2.5 TB pCloud scheduled offsite backups.
We also use SaaS backups via BlogVault platform.
WP Vivid, updraft, or All-In-One Migration for WordPress. Plesk, and cPanel both have migration tools that should help if you have access. Make sure you have a solid back up before any changes. Back up locally, and off site to your local PC S3 type of storage, One Drive, Dropbox. etc.
I work for a managed WP host. Multiple times a day, every day, we have folks contacting support asking for help reverting to a backup.
I’d suggest you check with your host about their backup availability first since those take zero effort on your end and don’t use up your own storage.
I don’t think you can have too many backup solutions. So I…
* Use a backup plugin every time before working on a site (Solid Backups, a.k.a. BackupBuddy.) I store these basically forever (some of my client archives go back to 2010!)
* Use hosting backups if available (usually good only for 14 or 30 days, but usually the easiest to restore.)
* Use automated scheduled weekly backups of all client sites with my maintenance suite (InfiniteWP) that’s stored off site (S3) for up to three years (156 weeks.)
* Use InfiniteWP to make daily backups of all client sites, stored on S3 for 14 days.
I’ll occasionally make intermediate database-only backups when making potentially risky/experimental changes like search and replace or trying out a replacement plugin that affects data only.
Most basic thing ever: no matter what backup tool you use, make sure you can restore with it.