Get Email When a Scheduled WordPress Backup Finishes or Fails
A backup schedule you never look at is theatre. The job “ran” in some cron sense. The ZIP never reached Google Drive. Nobody knew until the host ate the site on a Sunday.
Snapshotify emails you when a scheduled backup finishes or fails. Pair that with daily, weekly, or monthly schedules, cloud destinations on Google Drive, Dropbox, or OneDrive, retention that prunes automatic backups only (manual and uploaded copies are never auto-deleted), reconnects and retries on failed cloud uploads, one-click restore, and standard ZIP plus SQL you can open without the plugin.
This post is about notifications and the schedule habits around them. For why same-server copies are not enough, see a WordPress backup on the same server is not a backup. For slim pre-update safety, see database-only WordPress backup before a plugin update.
The problem: silent failure
Backup plugins fail quietly for boring reasons:
- Cloud OAuth token expired after a password change
- Disk quota on Drive or Dropbox filled during a big media month
- Host killed the PHP process mid-run
- Cron stopped after a migration
- Someone “cleaned up” the local backup folder and assumed the cloud still had copies
Without email on finish and fail, you discover the gap during the restore you needed yesterday. Notifications are not a nice-to-have. They are how you know the safety net still exists.
What Snapshotify actually ships here
Backup notifications by email when a scheduled run finishes or fails. Success and failure both matter. Success proves the pipeline. Failure tells you to fix it before the next incident.
Scheduled daily, weekly, or monthly. Match frequency to how often the site changes, not to anxiety.
Cloud to Google Drive, Dropbox, or OneDrive. Off-server copies beat “backup” folders on the same VPS.
Retention prunes automatic backups only. Manual and uploaded backups are never auto-deleted. You can keep a golden pre-relaunch ZIP without fighting the pruner.
Reconnects and retries failed cloud uploads. Transient network blips should not equal a missing remote copy.
One-click restore. When the bad day comes, you need a restore path, not an archaeology project.
Standard ZIP plus SQL. Readable without Snapshotify installed. That is insurance against lock-in.
Set notifications before you trust the schedule
- Connect a cloud destination (Google Drive, Dropbox, or OneDrive) and run one manual backup to prove auth works.
- Turn on email notifications for scheduled finishes and failures. Use an inbox you actually read, or a shared ops alias.
- Pick a schedule: daily for busy stores and membership sites, weekly for brochure sites, monthly only for near-static properties (and even then, weekly is safer).
- Set retention for automatic backups so Drive does not fill forever. Leave manual and uploaded backups alone; Snapshotify will not auto-delete those.
- Force a test failure once on staging (revoke token or use a tiny quota) and confirm the failure email arrives.
If the failure mail never shows up, fix mail delivery before you celebrate green success messages.
How to read the emails without noise fatigue
Success mail: Glance at timestamp and destination. If success stops arriving on a daily site, treat silence like failure.
Failure mail: Act the same day. Common fixes: reconnect cloud auth, free quota, raise host timeout for large sites, confirm cron is running.
Filter Snapshotify mail into a dedicated folder or Slack-via-email bridge if your team lives in chat. Do not mute the failures.
Retention and manuals: keep the lifeboats
Automatic retention is for the routine stream of scheduled ZIPs. Before a redesign, host move, or risky commerce change, take a manual backup (or upload a known-good archive). Snapshotify’s retention prunes automatic backups only, so those manuals stay until you delete them on purpose.
That split stops the classic accident: “retention kept the last seven dailies and deleted the only pre-migration copy.”
Cloud retries and restore confidence
Failed cloud uploads happen. Snapshotify reconnects and retries rather than assuming one failed PUT is final. Still verify in the cloud UI after you change OAuth apps or rotate passwords.
When you need to restore, use one-click restore for the usual path. Keep the ZIP plus SQL habit in mind for emergencies where WordPress itself will not boot: standard archives open with ordinary tools, no plugin required.
Pitfalls
- Scheduling daily with no failure email. You will not notice a week of misses.
- Cloud on the same Google account that is already full of videos. Watch quota.
- Only local backups. Re-read the same-server article linked above.
- Assuming success email means off-site forever. Retention and manual deletes still apply in the cloud UI.
- Never testing restore. A backup you have not restored is a hypothesis. Test on staging.
How this fits DaftPlug Pro
Snapshotify is one of five Pro plugins on a single membership. One licence unlocks Progressify (PWA), Lightify (performance), Generatify (AI), Rankify (SEO and GEO), and Snapshotify (backups). Plans differ by site count only: Pro $37.99/year (1 site), Pro Plus $74.99 (5), Pro Max $138.99 (100). Features are identical across plans. Checkout is Freemius, with a 14-day money-back guarantee. See pricing.
Takeaway
Schedules without alerts are hope. Turn on email when a scheduled WordPress backup finishes or fails, send automatic copies to Google Drive, Dropbox, or OneDrive, keep retention off your manual lifeboats, and confirm retries after cloud blips. Snapshotify is built for that loop: know the job ran, know when it did not, restore without drama.