Manual backups fail the week you are busiest. A plugin update goes wrong on Friday night. The host snapshot is older than you thought. Someone asks for yesterday’s database and you have a ZIP on a laptop that left the building. Snapshotify’s scheduled automatic backups run in the background on a daily, weekly, or monthly cadence, copy archives to Google Drive, Dropbox, or OneDrive, and use retention that prunes old automatic runs while keeping manual copies. The point is a boring, off-site rhythm you do not have to remember.
Snapshotify is the DaftPlug backup and restore plugin. This post stays on scheduled automatic backups only. Not a one-click manual-only deep dive, not migrate-with-URL-rewrite as the main topic, not database-only-only backups as the focus, not chunked upload of an external ZIP, not a smart-exclusions deep dive, not email notifications as the headline feature (you may notice notices briefly while verifying schedules). Those are siblings on the same backup list. A related enablement may already cover how retention keeps manual copies while pruning automatics. This article is schedule-and-cloud-cadence-only.
What Snapshotify actually ships here
Stay inside the real feature set:
- Scheduled automatic backups on daily, weekly, or monthly cadence
- Jobs that run in the background so you are not babysitting a browser tab for every run
- Cloud copies to Google Drive, Dropbox, or OneDrive
- Retention that prunes old automatic runs but keeps manual backups
- A WordPress-native scheduler so backup policy lives next to the rest of your site ops, without a separate cron SaaS for the basic cadence
This post does not invent undocumented multi-region orchestration dashboards, immutable WORM vaults, or promises that every host’s PHP timeout will love multi-gigabyte sites without normal operational care. The product promise is scheduled automatic backups to cloud storage with retention that protects manuals. Stay there. Manual-only deep dives, migration URL rewrite, DB-only-only focus, external ZIP chunked upload, smart exclusions deep dive, and email-notification-as-main-topic are parallel stories, not this article’s job.
Why scheduled automatic cloud backups matter on WordPress
Humans forget. The sites that survive incidents had a backup from before the incident, not a good intention from after it.
On-server copies are not enough. If the VPS dies, the malware encrypts the disk, or the host account is suspended, a backup that lived only on the same machine is gone too. Cloud destinations (Google Drive, Dropbox, OneDrive) put a copy outside that blast radius.
Cadence should match change rate. Daily fits stores and busy publishers. Weekly can fit quieter brochure sites. Monthly is a floor, not a flex, for anything that takes payments or publishes often. Snapshotify’s daily/weekly/monthly choices exist so the policy matches reality.
Retention must not eat your intentional restore points. Automatic runs should rotate. Manual runs often mark “before the redesign” or “before the migration.” Pruning automatics while keeping manuals is the difference between tidy storage and accidental deletion of the only good restore point.
Sibling backup features solve different jobs. Manual one-click is for deliberate checkpoints. Migration URL rewrite is for moving hosts or domains. Exclusions tune what enters the archive. Scheduling is the always-on cadence. Shipping all of them in one untested hour makes regression hunting painful. Enable the schedule, verify a cloud landing, then tune exclusions or migration drills on their own day.
How to enable scheduled automatic backups in wp-admin
Assume Snapshotify is installed, you can connect a cloud destination, and you have enough cloud quota for at least a few full runs. You will verify with a real scheduled or triggered automatic run and a file visible in Drive, Dropbox, or OneDrive, not only with a green checkbox in settings.
1. Pick the cadence that matches how often the site changes
Ask honestly:
- Daily: WooCommerce, membership, high-publish editorial
- Weekly: modest marketing sites with occasional edits
- Monthly: near-static brochure properties (and accept more data loss risk)
Write the choice in the runbook with the business reason. Do not enable every Snapshotify tool in the same hour.
2. Connect Google Drive, Dropbox, or OneDrive
In wp-admin, open Snapshotify. Connect the cloud destination you actually intend to use for automatic copies. Confirm the account is the team’s ops account (or a shared drive the team controls), not a personal sandbox you will lose when someone leaves. Spot-check that Snapshotify can see the destination folder it will use.
3. Open scheduled automatic backups and set the cadence
Locate scheduled automatic backups among Snapshotify’s backup features. Enable the schedule. Choose daily, weekly, or monthly. Leave migration URL rewrite drills, external ZIP upload experiments, and deep exclusion redesigns alone until the schedule lands a known-good cloud copy.
4. Confirm retention keeps manuals while pruning automatics
Review retention settings with the product behavior in mind: old automatic runs prune; manual copies stay. If you rely on named manual checkpoints before risky deploys, take one manual backup now and confirm it is labeled in a way your team will recognize later. Related reading on retention behavior lives in the manual copies retained guide when you want that sibling topic expanded.
5. Smoke-test an automatic run end to end
- Note the next scheduled time, or use whatever safe “run now”/test path Snapshotify provides for verifying the automatic pipeline without waiting a full day if available.
- Confirm the job runs in the background (you are not stuck watching a single browser request for the whole archive on a large site).
- Confirm a new backup appears in Snapshotify’s list as an automatic run.
- Confirm the archive (or the product’s cloud object) appears in Google Drive, Dropbox, or OneDrive as configured.
- Spot-check size sanity (not a tiny empty stub unless the site truly is tiny).
- Confirm a pre-existing manual backup was not pruned by automatic retention.
If the cloud never receives a file, confirm OAuth/connection health, confirm destination quota, confirm the schedule is actually enabled, and check host cron/loopback conditions WordPress schedules depend on. Do not invent undocumented Snapshotify “bypass all host cron forever” switches that are not on the product page.
6. Align WordPress cron reality with the host
Scheduled tasks need a reliable trigger. On some hosts, traffic-based WP-Cron is enough. On quiet sites, a real system cron hitting wp-cron.php is safer. Note what your host uses in the runbook so a “weekly backup never ran” ticket has a first place to look.
7. Document the enablement for the next teammate
Write one line in your internal runbook: “Snapshotify scheduled backups enabled on [date]. Cadence: [daily/weekly/monthly]. Cloud: [Drive/Dropbox/OneDrive account]. Retention prunes automatics, keeps manuals. Verified cloud object: [name/date]. Migration and exclusions are separate.” Schedules get blamed when someone disconnects the cloud account and assumes WordPress will still magically store off-site copies.
Who this is for
WooCommerce and membership sites that cannot afford a week-old restore point after a bad update.
Agencies that need client sites on an automatic off-site cadence without babysitting each dashboard every Monday.
Publishers with frequent content changes who want daily cloud copies without remembering a manual click.
Solo founders who are the entire ops team and know manual discipline fails during launches.
Anyone who already takes careful manual backups before deploys and still needs automatic rotation for the days nobody ships.
This is less urgent for disposable staging sites you can rebuild from git in minutes, or for hosts that already provide immutable, tested off-site snapshots you have personally restored. Even then, an application-level schedule to Drive, Dropbox, or OneDrive is useful portable insurance when host tooling changes.
What good looks like
- A scheduled automatic backup completes in the background on the cadence you chose.
- A copy lands in Google Drive, Dropbox, or OneDrive without a manual download step.
- Retention removes aging automatic runs according to policy.
- Manual backups remain available after automatic pruning.
- You can name the cloud account and folder in the runbook.
- Schedule enablement did not require a migration drill or exclusions redesign in the same window.
- You did not invent infinite retention or claim email alerts are the backup strategy.
- The next incident starts with “restore from [date] in [cloud],” not “does anyone have a ZIP?”
If schedules never fire, confirm WordPress cron health, confirm the schedule toggle, confirm cloud auth, and re-run a verification pass.
Pitfalls (the ones that bite)
Confusing scheduled automatics with manual-only discipline. Manual checkpoints are still valuable before risky changes. Scheduling is the always-on baseline. You want both mental models, not one pretending to be the other.
Storing only on the same server. If the cloud connection never completed, you may have local comfort and no off-site copy. Verify the destination UI, not only the WordPress success toast.
Retention that surprises the team. If someone expected every automatic forever, storage fills or costs spike. If someone expected manuals to rotate away, restore points vanish. Snapshotify’s “prune automatics, keep manuals” behavior should be written in plain language for non-engineers.
Ignoring quota. A growing media library can outpace a free cloud tier. Watch quota before the first failed upload becomes an outage discovery.
Enabling every Snapshotify feature with the schedule. If schedule, exclusions redesign, and migration tools all change together, you cannot tell which change broke a run. Enable schedule, verify cloud landing, then add the next piece.
Quiet sites with sleepy WP-Cron. Low traffic can delay schedules. Confirm host cron if the site is quiet.
Forgetting to re-test after reconnecting OAuth. Cloud tokens expire or get revoked when passwords change. A schedule that worked last quarter can fail silently until you look.
Practical checklist before you call it done
- Confirm Snapshotify is installed and you know which cloud account will hold copies.
- Choose daily, weekly, or monthly based on real change rate; write the reason down.
- Connect Google Drive, Dropbox, or OneDrive; confirm the team controls that account.
- In Snapshotify, enable scheduled automatic backups only for this pass.
- Leave migration URL rewrite drills, external ZIP upload experiments, and deep exclusion redesigns alone if they are not already stable.
- Confirm retention prunes old automatics and keeps manuals; take one labeled manual checkpoint if needed.
- Run or wait for an automatic job; confirm background completion and cloud object presence.
- Confirm a manual backup still exists after retention logic applies.
- Verify WordPress cron reliability on this host (system cron if the site is quiet).
- Check cloud quota headroom for the next few runs.
- Re-test after OAuth reconnects, host changes, or major media library growth.
- Write the enablement date, cadence, cloud destination, and verified object name in the team runbook.
Takeaway
Backups that depend on memory fail under stress. Snapshotify’s scheduled automatic backups run daily, weekly, or monthly in the background, copy to Google Drive, Dropbox, or OneDrive, and retain manuals while pruning old automatic runs. It is not a migration guide, not an exclusions essay, and not an email-notification product pitch. It is the off-site cadence WordPress sites actually need.
Snapshotify handles scheduled cloud backups alongside the rest of the backup and restore stack, without asking you to babysit a browser upload every night. Enable it once. Verify a real automatic object in cloud storage. Keep sibling backup features as separate enablement work. For how retention treats intentional checkpoints after the schedule is stable, use the related retention keeps manual copies guide when you are ready.
One Pro membership unlocks Snapshotify plus Progressify, Lightify, Generatify, and Rankify. New Pro plugins join existing memberships. Plans differ by site count only (Pro $37.99 for 1 site, Pro Plus $74.99 for 5, Pro Max $138.99 for 100), with a 14-day money-back guarantee. See pricing when automatic WordPress backups should land in cloud storage on a schedule you can defend.
Turn the schedule on. Connect the cloud account the team owns. When the next automatic archive appears off-site without anyone clicking Backup, restore planning finally starts from a position of strength.