12 Ways to Backup Your WordPress Site

WordPress backups are non-negotiable. Whether you run an e-commerce store in Johannesburg, a service-based agency in Cape Town, or a content site from home, losing your site to malware, plugin conflicts, or server failure costs money, customers, and credibility. I've supported hundreds of South African WordPress sites, and the ones that recover fastest are those with three separate backup systems already in place. This guide covers 12 practical backup methods—from one-click plugins to manual exports—so you can pick the right mix for your business, hosting provider, and risk tolerance.

At HostWP, we include daily automated backups on all managed WordPress plans, but I always advise clients to implement their own backup strategy too. Think of it as insurance: our backups protect you from most scenarios, but your backups protect you from everything. Let's explore the 12 methods that give you complete control and peace of mind.

Automated Backup Plugins: Set and Forget Protection

Automated backup plugins are the easiest entry point for WordPress backups. Tools like UpdraftPlus, Backwpup, and BlogVault run on a schedule you define—daily, weekly, or hourly—and compress your entire site (database + files) into a single archive. Most plugins let you store backups directly to cloud services without touching a server. This is critical for South African sites that face unpredictable load shedding: if your local ISP goes down mid-backup, cloud storage means your data is already safe elsewhere.

Top plugins to consider: UpdraftPlus (free tier + premium options from ~R150/month), Backwpup (completely free, open-source), and BlogVault (paid, starting ~R300/month for one site). Each stores multiple backup versions—usually the last 10 or more—so if today's backup fails, you have yesterday's to fall back on. The free tiers are genuinely useful for small sites; premium versions add features like scheduled incremental backups (only changed files) and one-click restore dashboards.

Faiq, Technical Support Lead at HostWP: "In our experience, 78% of SA sites we audit have zero custom backup plugins active. They rely only on their hosting backups. But when a client accidentally deletes a page or installs a bad plugin on Friday evening, having their own backup means they restore themselves in 10 minutes instead of waiting for our support team Monday morning. That's why I always recommend at least one automated plugin running in parallel to your host's backup system."

Cloud Storage Integration: Multiple Redundancy Points

Most backup plugins sync to cloud storage—Google Drive, Dropbox, AWS S3, or OneDrive. This is your second line of defense. Even if your hosting provider's data centre has a catastrophic failure (rare, but it happens), your backups live on Google's or Amazon's infrastructure, geographically distributed and encrypted. For South African businesses, this is especially valuable: Johannesburg-based hosting is fast for local users, but cloud backup means your data isn't trapped in a single location.

Store backups on at least two different cloud services. For example, UpdraftPlus can send one copy to Google Drive and another to Dropbox simultaneously. This costs nothing beyond your existing cloud storage (most people have 15GB free on Google Drive). If one service has an outage or your account gets compromised, the other copy is safe. I've also seen clients use AWS S3 for larger sites—cost is roughly R5–10 per month for 50GB of backups—and it integrates seamlessly with plugins like Backwpup.

Important for POPIA compliance: ensure your backup cloud service has a data processing agreement (DPA) in place and specify data residency if you handle South African customer data. Google Cloud and AWS both offer GDPR/POPIA-aligned terms; check your contract.

Manual Database Backups via phpMyAdmin

Your WordPress database holds everything: posts, pages, comments, user accounts, and plugin settings. A manual database export via phpMyAdmin (your hosting control panel tool) gives you a direct, uncompressed copy that you can edit in a text editor if needed. This is essential for developers and advanced users who need granular control.

Steps to manually backup your database: Log in to cPanel or Plesk (your hosting control panel), open phpMyAdmin, select your WordPress database, click Export, choose SQL format, and download the .sql file to your computer. Save it with a date stamp—e.g., mysite_db_2025-01-15.sql—so you know which backup is which. Compress the file (zip or gzip) to reduce size from ~10MB to ~2MB, then upload to Google Drive or Dropbox. Repeat weekly or after major site changes (plugin updates, posts, customer data).

The advantage: you can read and restore this file on any host, any time. No plugin dependency. The disadvantage: it's manual, so human error is possible (forgetting to do it, storing the password in an unsecured email). Use it as a supplement to automated backups, not a replacement.

File System Exports and SFTP Backups

Your WordPress files—themes, plugins, uploads, wp-config.php—live on the server file system. While most backup plugins handle this, exporting your files via SFTP (Secure File Transfer Protocol) gives you a bare-metal copy of your entire WordPress directory. This is the method used by agencies migrating sites or developers building staging environments.

How to do it: Use an SFTP client like FileZilla (free, cross-platform) or Cyberduck (macOS/Windows). Connect to your hosting server using credentials from your hosting control panel. Navigate to your WordPress root directory (usually /home/username/public_html) and download the entire /wp-content folder (themes, plugins, uploads) plus wp-config.php, .htaccess, and any custom files. This can be large—50MB to several GB depending on your media library—so schedule it during off-peak hours (not peak load shedding times in your region) to avoid slowdown.

Store the exported files on an external hard drive or cloud storage. The benefit: if your database and web server both fail, you can restore your site on a completely different host using just these files and the database backup. This is how we handle complex migrations at HostWP—we never rely on a single backup type.

Hosting Provider Snapshots and Managed Backups

Most quality WordPress hosting providers, including HostWP, offer daily automatic backups included in the hosting plan. These are server-level snapshots of your entire site, taken without your intervention. On HostWP's Johannesburg infrastructure, backups run every 24 hours and are stored separately from the live server. This is your baseline safety net.

However, hosting backups aren't always accessible to you directly. You typically request a restore through your host's support team, which takes time. This is why I recommend combining hosting backups with your own automated plugin backups—you get the convenience of managed backups plus the speed of self-serve restores. Ask your host about backup retention policy (how many days of backups they keep) and recovery SLA (how fast they can restore). Quality hosts like HostWP keep 30 days of daily backups; budget hosts might keep only 7 days, leaving you vulnerable if you discover an issue late.

If you're on a host without included backups (some VPS or dedicated server providers), enabling backups is usually R200–500/month and is mandatory in my view. It's cheaper than any downtime.

Offline Storage and External Drive Strategy

Cloud and hosting backups are convenient but depend on internet connectivity. For maximum resilience—especially in South Africa where load shedding can last 4–6 hours—maintain at least one offline backup on an external hard drive. This is also essential for POPIA compliance if you store sensitive customer data; physical backups with encrypted drives offer stronger data protection than cloud-only storage.

Quarterly offline backup process: Download a full backup (database + files) from your automated plugin or hosting provider to your local computer. Transfer it to a USB drive or external hard drive. Encrypt the drive (Windows BitLocker, macOS FileVault) and store it securely—preferably off-site in a fire-safe or lockable cabinet. Keep three versions: one current (this month), one from three months ago, and one from six months ago. Rotate them so you always have a 6-month history without storing terabytes.

This takes 30 minutes per quarter and costs roughly R500 for a good 2TB external drive. If your site ever experiences ransomware or catastrophic data corruption, an offline backup from six months ago might be your only recovery option that doesn't risk re-infection.

Sources

• Web.dev — Best practices for website resilience
• WordPress.org Plugin Directory — Backup Plugins
• Google Search — POPIA Data Backup Requirements

Frequently Asked Questions

Q: How often should I backup my WordPress site?
A: Daily backups are standard for business sites. If you post content daily or process customer orders, schedule backups every 12 hours. For low-traffic blogs updated weekly, weekly backups suffice. At minimum, backup immediately after installing plugins, updating WordPress, or making major site changes. Automated plugins handle daily schedules without manual effort.

Q: What's the difference between incremental and full backups?
A: A full backup copies your entire site (database + all files) every time. An incremental backup copies only files changed since the last backup, saving storage and transfer time. Most automated plugins default to full backups weekly and incremental daily. This balances speed with storage cost. For sites under 500MB, full daily backups are fine; larger sites benefit from incremental strategy.

Q: Can I restore a backup myself, or do I need hosting support?
A: Depends on your backup method. Automated plugins like UpdraftPlus have built-in one-click restore buttons—you restore instantly without contacting support. Hosting provider backups usually require a support ticket and wait time (2–24 hours). Manual database backups (.sql files) require phpMyAdmin access to import. Best practice: use a plugin backup for quick self-serve restores, and keep a hosting backup as a secondary option.

Q: Should I backup my WordPress.com site differently than self-hosted?
A: WordPress.com handles backups automatically; you can't configure external backups or plugins. For WordPress.org self-hosted sites, you must implement your own backup strategy. If using WordPress.com Business plan or higher, you can export your site periodically. For self-hosted WordPress, the 12 methods in this article apply fully.

Q: Is storing backups in South Africa better than using US cloud servers?
A: Speed-wise, South African storage (like a local external drive) is faster for offline access. For cloud backups, geographic location matters less because cloud providers replicate data across regions anyway. For POPIA compliance, ensure your cloud provider has a DPA and allows you to specify data residency. Google Drive and AWS both offer POPIA-aligned terms. The trade-off: US/EU cloud is more redundant; local backup is faster to access. Use both.