WordPress backups are insurance you hope you never need. They are also one of the most consistently mishandled parts of running a WordPress site for Idaho small businesses. A backup that lives on the same server as your site is not a backup. It’s a copy of your site that disappears when the server does. A backup nobody has tested restoring is a hope, not a backup. Here’s how to do this right for an Idaho business that can’t afford to lose its website to a hack, a server failure, or a botched update.
The 3-2-1 rule for WordPress backups
Three copies of your data, two different media types, one off-site. For WordPress that means: the live site itself, a recent backup on your hosting account, and a third copy stored off-server (cloud storage, a different host, a physical drive somewhere safe). If you can’t list those three locations for your site right now, you don’t have a real backup strategy.
What needs to be backed up
- WordPress files: themes, plugins, mu-plugins, uploads (images, PDFs, anything in /wp-content/uploads/)
- WordPress database: every post, page, comment, setting, user, custom field
- Server config: .htaccess, wp-config.php (with sensitive keys), any custom NGINX or Apache rules
- Email forwarders and DNS: separately, since these often live outside the WordPress backup
Frequency by site type
Static brochure site: weekly backups are fine. The content doesn’t change much.
Blog or content site: daily backups. New posts and edits happen frequently enough that a week of lost work is painful.
WooCommerce or e-commerce: hourly or every 6 hours, with database snapshots at least daily. Lost orders are lost money.
Membership or user-driven site: daily minimum. User account loss damages trust.
The tools that actually work
- Host-level backups: SiteGround, WP Engine, Kinsta, and most managed hosts include daily backups. Verify the retention policy.
- UpdraftPlus, Solid Backups, or BlogVault: WordPress plugins that push backups to S3, Google Drive, Dropbox, or dedicated backup storage.
- WP-CLI and rsync: for businesses with technical staff, scriptable backups to external storage.
The part everyone skips: testing restores
A backup you have never restored is a backup that may not work. Quarterly, do a test restore to a staging environment. Confirm the database imports cleanly, files restore correctly, and the site comes up functional. The hour you spend testing each quarter is the cheapest insurance you’ll ever buy.
Backups in maintenance plans
Backups follow the hosting account, so nobody pays for them twice. If your site is on my managed hosting, daily off-server backups with verified restore capability come with the hosting itself. If you hold your own hosting account, backups are covered by the care plan instead, because that means reaching into an account I do not control to make sure the copies exist and actually restore. Either way it is handled, and it is the part most “set it and forget it” backup plugins skip. Book a 30-minute call to audit your current backup situation. Most Idaho businesses I audit find at least one gap they didn’t know they had.
Thinking About a Project?
Free quote, scope and price locked up front, fully owned at launch.