Managed infrastructure for SMBs
WordPress and WooCommerce Backups and Uptime for Small Business
The short answer
A WordPress site or WooCommerce store survives bad days when three habits are in place: you back up the right things on a schedule, you keep at least one copy off the server, and you know a restore actually works because you have tested it. Uptime monitoring tells you the store is reachable before your customers do. None of that requires a huge IT team. It does require a clear checklist and someone who owns it.
This guide is for small business owners and operators who run WordPress or WooCommerce and want a practical backup and uptime plan. GlassHosting builds managed infrastructure for SMBs, including managed WooCommerce, so this is the same framing we use when we set expectations with customers.
What actually needs a backup
A WordPress or WooCommerce install is not one file. Treat these as separate pieces so a restore does not leave you with a half working store.
- The database. Posts, pages, products, orders, customers, settings, and most plugin data live here. If you lose the database, the storefront skin may still load while the business data is gone.
- WordPress core, themes, and plugins. The application files that make the site run. You can often reinstall core from wordpress.org, but custom themes and premium plugins are yours to keep.
- Uploads and media. Product images, PDFs, and the media library under
wp-content/uploads. These are easy to forget and painful to rebuild by hand. - Config and secrets, handled carefully.
wp-config.php, environment files, SSL material, and API keys. Back them up, store them separately from public copies, and never paste secrets into tickets or chat. - Custom code and mu-plugins. Anything your developer added outside the standard theme or plugin folders.
WooCommerce adds order history, product catalog data, and often payment or shipping plugin tables in the database. A file-only backup is not enough for a store that takes orders.
The off-server rule
A backup that lives only on the same VPS as the site fails when the disk dies, the account is locked, or ransomware encrypts the volume. Keep at least one recent copy somewhere else: object storage, another region, a separate host, or an encrypted download you control.
- Schedule. Daily is a common baseline for an active store. Quieter brochure sites can go less often. Peak seasons may need more frequent database dumps.
- Retention. Keep several generations (for example daily for a week plus a few weekly copies) so a problem you notice late does not sit only in yesterday's bad backup.
- Encryption in transit and at rest for copies that leave your primary host, especially if they include customer data.
- Access control. Limit who can download restore archives. Treat backup credentials like production credentials.
Test the restore, or it is not a plan
A backup you have never restored is a hope. Pick a quiet window, restore into a staging copy or a spare VPS, and confirm:
- The site loads over HTTPS with the right content.
- A sample product, page, and (for Woo) a recent order record look correct.
- Login still works, and critical plugins load without fatal errors.
- You know how long the restore took, so you can set real expectations for a real outage.
Write the steps down. When something breaks at 9pm, you want a short runbook, not a scavenger hunt. Our WooCommerce migration checklist uses the same discipline: inventory first, then move, then verify.
Uptime monitoring that matters for a store
Green ping checks are useful. They are not the whole story for WooCommerce.
- HTTPS reachability. Check the public homepage and a key interior URL (cart, product, or checkout landing) from outside your network.
- Alert someone who can act. A monitor that only emails an unread inbox wastes the night.
- Separate "site down" from "store broken." PHP fatals, a dead database, or a payment plugin failure can return an error page while the web server still answers. Spot checks of checkout after deploys catch that class of problem.
- Maintenance windows. Mute or expect alerts when you knowingly take the site offline for updates, so the team does not ignore real alerts later.
You do not need a wall of charts on day one. You need a reliable external check, a clear owner, and a habit of verifying the store path after changes.
Managed hosting vs doing it yourself
DIY on a VPS can work if someone on your team owns patching, backup jobs, off-server copies, restore drills, and monitoring. Many small businesses discover that person is also running sales, support, and inventory. That is when things slip.
Managed hosting means the platform side (updates where agreed, backups, monitoring posture, and help when the stack misbehaves) is part of what you buy. Managed vs unmanaged VPS spells out who does what. For stores specifically, see managed WooCommerce hosting.
If you stay DIY, keep the same bar: scheduled backups, off-server copies, a tested restore, and an uptime alert that reaches a human. The VPS type (KVM or LXC) matters less than those habits. When you choose infrastructure, KVM vs LXC explains the tradeoffs in plain words.
A simple weekly rhythm
- Confirm last night's backup finished and that an off-server copy exists.
- Glance at uptime history for surprises (flaps, long gaps, odd hours).
- After any plugin, theme, or core update, spot-check homepage, a product, cart, and checkout.
- Once a month, run a restore drill to staging or a spare host and note the time it took.
- After peak sales periods, keep an extra database snapshot until you are sure nothing needs a rollback.
How GlassHosting fits
- Managed WooCommerce: hosting shaped for WordPress and Woo stores, with the platform care small teams usually need. Start at managed WooCommerce hosting and our services overview.
- VPS when you want the keys: GlassVPS KVM and GlassCloud LXC when you prefer to run the stack yourself on solid infrastructure.
- MSP model: when you want an ongoing partner for the boring, load-bearing work, see how our MSP model works.
If you are unsure whether your current backups would survive a real failure, tell us what you run or email sales@glasshosting.com. We will help you map a practical backup and uptime plan for the store you have today.
Host with GlassHosting
Order a plan or browse the knowledgebase for deeper how-tos.