# Backup WordPress Site: Three Layers You Can Restore > A reliable backup WordPress site owners can recover from includes both files and the database, with copies outside the hosting account and a tested restore. Use three layers: a WordPress backup tool, server backups and independent storage you own. That gives your business a recovery path when an update fails, a server disappears or access to the hosting account is lost. Canonical: https://fer.marketing/wordpress-backups Author: Fernando Marcano, Fer Marketing Updated: 2026-10-17 - **Protection:** WordPress + server + external storage - **Contents:** Matching files and database - **Ownership:** An off-site account you control - **Proof:** Quarterly restore to staging ## Backup WordPress site: what you need to save Your website is more than its visible pages: it may hold orders, inquiries, bookings and the settings that send them to your team. A backup should let you recover those business functions, not just display an old homepage. Start by listing what changes and where each record lives. - **Files.** Save uploads, themes, plugins, custom code and configuration needed to rebuild the site. Include files outside the usual folders if your developer has added custom integrations or private documents. - **Database.** Save content, settings, users and all relevant plugin tables. WooCommerce orders and many stored form entries live here, so copying the uploads folder alone will not recover them. - **Recovery notes.** Record hosting requirements, DNS access, external services and the restore method. Keep credentials in a secure password manager, with recovery access available if WordPress itself is down. The [WordPress backup handbook](https://developer.wordpress.org/advanced-administration/security/backup/) confirms that a complete recovery needs files and database. Check the actual backup contents, including exclusions, rather than assuming a job labeled full includes every dependency. > **Some records live somewhere else:** A WordPress backup does not automatically back up your email inbox, CRM or Google Calendar. Map those systems separately, and check whether your contact plugin stores submissions at all; a message that only existed in email cannot be recovered from the website database. ## WordPress backups in three independent layers Layer one creates a portable site backup inside the WordPress workflow and sends it off the server. Layer two captures the hosting environment independently of the plugin. Layer three keeps recoverable copies in a separate storage account owned by your business, such as Google Drive, Dropbox, Amazon S3 or Backblaze B2. *Diagram: WordPress creates site copies, the server provides another recovery route, and independent storage preserves access beyond the host. Verify which copies share credentials or infrastructure.* | Layer | Protects against | Restore speed | Control | | --- | --- | --- | --- | | WordPress | Bad edits or updates | Often direct | Your team | | Server | Site or server faults | Host-dependent | Host or VPS admin | | External | Host or account loss | Download + rebuild | Your business | The [3-2-1 rule explained by Backblaze](https://www.backblaze.com/blog/the-3-2-1-backup-strategy/) calls for three copies, including the live original, on two media, with one off-site. Three folders on the same disk do not meet that goal. Our three layers describe responsibilities; count actual copies and storage locations separately. > **Separate the failure points:** A plugin sending to independent storage plus a host snapshot can provide distinct recovery options. Confirm where the snapshot lives, who can delete each copy and whether you can recover if the hosting account becomes inaccessible. ## Why host-only WordPress backups fall short Hosting backups are valuable, but they are still part of a commercial account you may lose access to. Account suspension, a provider closing, a billing dispute or a compromised administrator can leave you unable to reach both the site and its copies. Ransomware may also reach backups accessible with the same credentials. - **Recovery may involve a queue.** Ask whether you can restore yourself or must open a support request. A backup can exist while your booking page stays offline waiting for someone with permission to use it. - **Retention may be too short.** A problem discovered late can outlive the oldest available clean copy. Ask for the actual recovery dates and retention policy, not just a promise that backups run daily. - **Access may be shared.** A snapshot under the same account is useful for rollback but may share the account's risks. Keep an independent copy and recovery credentials outside the host's control. On cPanel hosting, a provider may offer a tool such as [JetBackup](https://docs.jetbackup.com/); a VPS may use snapshots and scheduled database exports. Confirm what your plan actually includes, where copies are stored and whether database consistency is handled. A running server snapshot is not automatically proof of a working store restore. > **Ask for an export you can use elsewhere:** Your escape route should include downloadable files, database and recovery instructions. Test access to the independent destination without logging into the hosting control panel, then confirm a replacement host could use those copies. ## Set your limits for data loss and downtime Backup frequency is a business decision before it is a plugin setting. A brochure site edited occasionally has different needs from a store accepting orders throughout the day. Choose two recovery targets and ask your provider how the proposed system will support them. - **RPO: how much recent work can you lose?.** This is your acceptable gap between the last usable backup and the failure. For example, if losing an hour of orders is unacceptable, a nightly database backup leaves too large a gap. - **RTO: how long can the site be down?.** This is your target for restoring service. Include noticing the outage, obtaining access, downloading data, rebuilding and checking the site, not just the restore button's processing time. Keep several recovery dates, with daily and longer-term points chosen around your business and data retention needs. Take a fresh matching backup before risky changes as well. Schedule heavy jobs away from peak traffic and avoid overlapping exports that strain a small hosting account. > **A store needs more than frequent file copies:** Back up every relevant order table, including tables used by extensions and the store's configured order storage. Rolling back the database can erase newer orders even when the payment provider still shows successful charges; plan reconciliation before replacing live data. Backups support recovery, but they do not prevent every outage. Pair this plan with [safe WordPress updates](https://fer.marketing/wordpress-updates), the [WordPress security checklist](https://fer.marketing/wordpress-security-checklist) and the business priorities in our [WordPress web design hub](https://fer.marketing/wordpress-web-design). An unavailable form cannot collect a lead, and an unavailable page cannot be crawled normally by Google. ## Backup WordPress site: set up the three layers Use this setup sequence with your host or technical team. Agree on what successful recovery means before choosing tools, then validate each layer rather than installing several plugins that all depend on WordPress working. 1. **Map the site and agree on recovery targets.** List files, database, orders, forms and external systems. Write down acceptable data loss, downtime, backup retention and the person responsible for recovery. 2. **Create storage in an account you own.** Choose an independent destination, enable two-factor authentication and arrange secure recovery access. Give the maintenance team only the access it needs, with encryption keys stored separately and recoverably. 3. **Configure the WordPress backup layer.** Choose a maintained backup plugin, include files and database, and connect the off-server destination. Run an initial backup and inspect the remote files and timestamps rather than stopping at a connection success message. 4. **Add a separate server recovery route.** Ask the host to configure snapshots or account backups with documented retention. On a VPS, arrange server-side scheduling and consistent database exports; record how recovery works if the WordPress dashboard is unavailable. 5. **Set schedules, retention and failure alerts.** Match database frequency to new transactions and file frequency to site changes. Keep multiple recovery dates, monitor missing as well as failed jobs, and send alerts to someone who will act. 6. **Restore an independent copy to staging.** Download a matching backup set and rebuild on a private test site. Disable live integrations before running tests, then measure the total recovery time and verify the visitor actions your business relies on. 7. **Document and schedule the next drill.** Save the tested procedure, access owners, backup date and unresolved gaps. Put a quarterly restore test on the calendar and repeat after major changes to hosting, backup tools or the site's business functions. > **Want three-layer backups you can actually restore?** We configure the WordPress, server and independent storage layers, then test a restore and document the result. Send your site and hosting details for a fixed written maintenance quote. https://fer.marketing/services/wordpress-maintenance ## Best WP backup plugin: choose by recovery needs The best WP backup plugin for your business is one your team can restore from under your hosting limits. Check supported storage destinations, archive size limits, scheduling, encryption options and recovery without dashboard access. Confirm which features belong to the edition you will actually use. ### A practical starting point for backup on WordPress [UpdraftPlus on WordPress.org](https://wordpress.org/plugins/updraftplus/) documents scheduled backups and destinations including Google Drive, Dropbox and Amazon S3. It is one option for the WordPress layer, not a substitute for server backups or independent ownership. Test it against your actual site before committing to a recovery plan. ### Google Drive and other independent destinations Google Drive or Dropbox can suit a business that wants familiar account management; Amazon S3 or Backblaze B2 may suit a team managing storage policies. Choose the destination around access, capacity, recovery and retention. Connecting cloud storage does not automatically provide encryption you control, immutable copies or a separate deletion policy. **Verify before you choose** - [ ] The backup fits and completes.: Check disk space, execution limits, storage quota and a complete run with the real media library. - [ ] The restore route is documented.: Confirm how to recover onto another server if the current site and dashboard are gone. - [ ] Ownership survives a supplier change.: Keep storage billing, recovery codes and access ownership with your business; review permissions when a provider leaves. ## Keep WordPress backups private and recoverable **Do** - Send copies off the server to an account you control. - Keep archives outside public web folders and restrict access. - Encrypt sensitive backups and retain recovery keys securely. - Preserve dated recovery points with a deletion policy. **Don't** - Keep your only backup inside /wp-content. - Expose SQL files or archives through a public download URL. - Copy files but forget the database and WooCommerce orders. - Treat cloud sync or a green badge as a tested recovery plan. For a VPS, a technical team can automate database exports with [WP-CLI](https://developer.wordpress.org/cli/commands/db/export/) and send them to [Google Drive through rclone](https://rclone.org/drive/). The example below assumes an already configured encrypted remote named gdrive-crypt, using [rclone crypt](https://rclone.org/crypt/) over a Google Drive destination. It illustrates the database part only. **Database export to encrypted Google Drive storage** ``` set -eu umask 077 cd /srv/www/example backup_dir=/srv/private/wp-backups stamp=$(date -u +%Y%m%dT%H%M%SZ) job_dir="$backup_dir/$stamp" mkdir -p "$job_dir" wp db export "$job_dir/database.sql" rclone copy "$job_dir" "gdrive-crypt:example/$stamp" ``` Illustration for your technical team, not a complete backup script. Adapt private paths, confirm database consistency and add matching file backups, transfer verification, retention and failure alerts. > **Encryption also needs a recovery plan:** Protect the rclone configuration and keep the crypt password and any custom salt in a secure recovery record outside the server. The local SQL export remains unencrypted, so restrict its access and set a cleanup policy; encryption of the upload does not make the local file public-safe. Separate storage credentials reduce shared risk, but a compromised server may still misuse its upload credentials. Review deletion permissions and consider protected retention or an offline copy where appropriate. Encryption protects confidentiality; it does not stop an attacker from deleting an accessible backup. ## Restore WordPress from backup on staging first Test a restore quarterly and after significant platform changes. Use an isolated staging site, a private copy where mistakes will not overwrite live orders or send customer messages. Restore from the independent destination so the exercise proves you can recover without the original host. **A useful restore test proves these things** - [ ] You can obtain and open the backup.: Record the recovery date, files and database included; verify download, decryption and a compatible environment. - [ ] Staging is isolated before tests run.: Password-protect it, block indexing and disable live payments, customer mail, webhooks and scheduled integrations; route test mail to a controlled inbox. - [ ] Content and navigation work.: Check login, images, menus, important landing pages, redirects and links after adjusting the test site's address. - [ ] Revenue and inquiry paths work.: Submit labeled test forms and verify delivery; inspect stored entries and sample orders, and test checkout only with sandbox settings. - [ ] New live records have a preservation plan.: Compare the backup time with later orders or inquiries and define reconciliation before any production database replacement. - [ ] Recovery time and gaps are recorded.: Measure from obtaining access through final checks, assign fixes and delete staging data when the exercise is complete. > **A hacked site's newest backup may already be infected:** Preserve evidence and identify a trustworthy recovery point before restoring. Contain the incident, fix the entry point and rotate affected credentials; restoring yesterday's files without addressing the cause can put the same problem back online. **Recovery record, fill in actual results** ```text Backup date and independent destination: Files and database restored: Access and decryption verified: Forms, pages and order checks: Total recovery time and blockers: Owner, next action and next test date: ``` ## What a WordPress backup service should deliver Ask for evidence you can understand: the last independent backup, available recovery dates, who receives failure alerts and the last successful restore test. A service should name who acts when a backup stops arriving. Owning a subscription is different from having someone responsible for recovery. - **A written scope.** Specify included sites, data, schedules, retention and restore responsibilities. Record storage or licensing costs and any recovery work outside the agreed scope before work starts. - **Checks with follow-through.** Review completion, independent copies and alerts, then investigate failures. The quarterly restore record should show working business functions and unresolved issues, not only an archive's size. - **A clean agency handoff.** Keep the client's storage ownership clear and document agency access. Use staging on the agency domain and a report your team can pass on under its own brand. Our [WordPress maintenance service](https://fer.marketing/services/wordpress-maintenance) starts at $250 per month per site, with a fixed written quote before work. We set up and test the three-layer plan within the agreed scope; agencies can use [white-label WordPress support](https://fer.marketing/white-label/wordpress), with NDA and non-solicitation available. Use our [maintenance checklist](https://fer.marketing/guides/wordpress-maintenance-checklist) to connect backups with updates, security and visitor checks. If your site sells online, also review [WooCommerce optimization](https://fer.marketing/woocommerce-optimization) so order handling, checkout and recovery are planned together. Send us your site address, hosting provider and current backup arrangement; those details let us identify the gaps before quoting. ## Want us to set up and test your backups? We configure a three-layer recovery plan around your site and hosting, then prove the restore on staging. Maintenance plans start at $250 per month per site, with a fixed written quote before work. - WordPress files and database backups with an agreed schedule. - A separate server backup route with documented retention. - Independent storage you own, with protected access. - Failure alerts and a named person responsible for review. - A staging restore test and written recovery instructions. https://fer.marketing/services/wordpress-maintenance ## FAQ ### How do I back up a WordPress site completely? Save the site's files and database as a matching recovery set, including custom files and plugin tables. Keep copies outside the hosting account, retain several recovery dates and test a restore on private staging. Record external systems that need their own backup arrangements. ### How often should WordPress backups run? Choose frequency around how much new work you can afford to lose. A store taking orders all day needs more frequent database protection than a rarely edited brochure site. Add a fresh backup before risky changes and verify that scheduled copies reach independent storage. ### How do I restore WordPress from backup? Identify matching files and database from a suitable recovery date, prepare a compatible environment and test the restore on isolated staging. Check pages, login, forms and commerce functions. Before replacing production data, preserve newer orders and inquiries and agree on how to reconcile them. ### Are my hosting provider's backups enough? They are useful but should not be your only recovery route. Access, retention and restore requests depend on the provider, and some failures affect the entire hosting account. Keep an independent copy in storage your business controls and test recovery without the original host. ### What is the best WP backup plugin for a business site? Choose a maintained tool that handles your actual files and database, works within your hosting limits and supports your chosen destination. UpdraftPlus is one option. Confirm the features in your chosen edition and test a complete restore rather than choosing by a feature list alone. ### Can I keep WordPress backups in Google Drive? Yes, through a compatible backup tool or a configured transfer process. Use an account owned by your business, restrict access and check that transfers complete. Keep multiple recovery dates and arrange encryption and recovery keys as needed; a connected folder alone does not prove recoverability. ### Will a WordPress backup include WooCommerce orders? A complete database backup should include the relevant order tables and extension data, but you must verify scope and exclusions. Orders created after the backup are outside that recovery point. Replacing the database without reconciliation can erase them while leaving their payments recorded elsewhere. ### Can Fer Marketing set up and test backups for my agency? Yes. We configure WordPress, server and independent storage backups and test restores within an agreed scope. Maintenance starts at $250 per month per site, with a fixed written quote before work. White-label delivery, agency-domain staging, NDA and non-solicitation are available. Send your site to fer@fer.marketing or WhatsApp for a fixed written maintenance quote from $250 per month per site, with same-business-day replies from 9 AM to 9 PM ET and white-label delivery for agencies.