How to Back Up Your WordPress Site Before 11.11 and 12.12

The last thing any Philippine online store owner wants during 11.11 or 12.12 is a website that fails at peak traffic. A failed plugin update, a server overload, or a targeted hack at the wrong moment can mean hours of lost sales and frustrated customers.

Why Backing Up Before 11.11 Matters

11.11 and 12.12 are among the biggest online shopping events in the Philippines. During peak hours, your site handles far more simultaneous visitors, and an overloaded server is more likely to crash or time out.

Last-minute changes before a sale, such as plugin updates or theme adjustments, can also introduce a conflict that breaks your site.

Without a recent backup, recovering from a crashed site means:

• Contacting your hosting provider and waiting for their restore process, which may take several hours
• Potentially losing recent orders, updated product content, and customer records
• Missing a major sales window with no clear timeline for recovery

A recent, tested backup gives you a much better chance of recovering quickly with minimal data loss. Backups aid recovery but do not fix server capacity problems or the root cause of a compromise; resolve overload or clean up a hacked site separately.

What a WordPress Backup Includes

A complete recovery strategy has two core parts, and you need both to restore your site fully.

Database: This contains your posts, pages, WooCommerce orders, customer information, plugin settings, and your site's core configuration.

Files: This includes your themes, plugins, and the wp-content/uploads folder where your product images, blog images, and media files are stored.

A database-only backup cannot restore your site's appearance, and a files-only backup cannot restore your orders or customers.

It also helps to separate a complete recovery strategy from what one plugin covers. According to the UpdraftPlus Free vs Premium comparison, the free version backs up the WordPress database (tables using your site's configured table prefix, with wp_ only the default example) and the wp-content directory, including plugins, themes, uploads, and other wp-content files. It does not protect wp-config.php, core customizations, custom directories outside the standard WordPress structure, or unrelated tables outside that configured prefix. Sites with a custom prefix can still be backed up. If your site relies on any of the uncovered items, ask your host about full-account or file-level backups, or keep a separate secure copy, such as a private download of wp-config.php stored where only authorized people can reach it.

How to Back Up Your WordPress Site with UpdraftPlus

UpdraftPlus offers a free version in the WordPress plugin directory. Here is the setup process for the free version:

1. Install and activate UpdraftPlus. In your WordPress dashboard, go to Plugins → Add New, search for "UpdraftPlus WordPress Backup Plugin," click Install Now, then Activate.
2. Open Settings → UpdraftPlus Backups, then click the Settings tab at the top of the UpdraftPlus page.
3. Set your backup schedule. Under "Files backup schedule" and "Database backup schedule," choose intervals using the guidance in the schedule section below. Set the number of stored backups to retain to at least 3.
4. Connect cloud storage. Choose Google Drive or Dropbox, both available in the free version, and follow the authentication prompt to link your account.
5. Save your settings by clicking Save Changes at the bottom of the Settings page.
6. Run an immediate backup. Go to the Backup/Restore tab and click Backup Now. Confirm that both database and files are selected. Verify that the files appear in your cloud storage folder.

How to Test Your Backup Before 11.11

A backup you have never tested is a backup you cannot trust.

Test on a separate staging copy of your site, never on your live store. Staging availability depends on your host and plan, so ask your provider; otherwise use a separate test installation. Restoring an older production database can overwrite newer orders and customers, and you should never push the test database back to the live store.

To run a restore test with UpdraftPlus, following the official restoration guide:

1. Open the staging WordPress dashboard, not production.
2. Isolate staging first. Restrict access (for example, password protection), disable outbound customer emails, set payment gateways to test mode or disable them, and turn off production integrations and webhooks as appropriate. Prefer host- or environment-level isolation that survives a database restore, because plugin or dashboard settings stored in the database may not.
3. Make the complete backup set available. Install UpdraftPlus on staging and go to Settings → UpdraftPlus Backups → Existing Backups. If the set is not listed, connect the same Google Drive or Dropbox account, save settings, and click "Rescan remote storage." Alternatively, download the set and use "Upload backup files" under More tasks, or upload it by FTP to wp-content/updraft and click "Rescan local folder for new backup sets."
4. Click Restore beside the backup set and select the components to restore: Database, Plugins, Themes, Uploads, and Others. Review the guide's notes on database options, then click Restore again when prompted and wait for completion. Restoring a production database can replace staging settings with production values.
5. Re-verify isolation before browsing checkout or placing a test order. Confirm the staging URL and access restrictions still apply, outbound customer emails are still blocked, payment gateways are in test mode with sandbox credentials (or disabled), and production webhooks and integrations are disabled.
6. Verify the result. Check that pages load and product images display. Place a test order through cart and checkout using test payments, and confirm orders appear as expected.

The official guide covers restoring to the same address; a staging site with a different URL may need extra steps, so check the documentation or your host. Staging sync tools can also overwrite newer live orders, as WordPress.com's staging sync guide warns for WooCommerce stores.

Where to Store Your WordPress Backups

Never store your only backup on the same server as your live site. If the server fails or is compromised, a backup stored on the same machine is often lost at the same time.

Storage options for Philippine site owners:

• Google Drive — Easy to set up with UpdraftPlus and available in the free version
• Dropbox — Reliable and available in the free version
• OneDrive — Requires UpdraftPlus Premium, regardless of any Microsoft 365 subscription
• External hard drive — Useful as a secondary local copy downloaded from UpdraftPlus

Keep at least two independent copies: one in cloud storage (automated through UpdraftPlus) and one downloaded locally from your dashboard. Backups contain customer data, so restrict access to the storage account, enable multi-factor authentication, avoid public sharing links, and protect local copies on encrypted or access-controlled devices.

Your Backup Schedule Before 11.11

There is no single correct schedule. Choose database frequency by order volume and how much data you can afford to lose, and choose file frequency by how often your content, themes, or plugins change.

• Now: Run a full manual backup and confirm it appears in cloud storage.
• Database: A daily backup can leave roughly 24 hours of orders and customer changes at risk. UpdraftPlus Free also supports 2-, 4-, 8-, and 12-hour intervals, but frequent backups use server resources, so confirm the load is acceptable with your host. Stores needing a shorter recovery point may need a different backup solution; no schedule guarantees zero data loss.
• Files: Match the schedule to how often you add products, media, or plugin and theme changes. Weekly may suffice if little changes; daily suits frequent updates.
• Before updates and after final pre-sale changes: Run a manual backup after prices, banners, and plugins are final, and before any update.
• After 12.12: Review your schedule against actual order volume and server load, and adjust only if your acceptable data-loss window allows.

Common Backup Mistakes to Avoid

Frequently Asked Questions