You set a nightly backup. You assume it runs. Three weeks later a plugin update bricks the site and the newest offsite archive is from last month. Nobody got an email. The cron job failed quietly after a host change. The “backup strategy” was optimism plus a green toggle you never verified.
Silent backups are not backups you can trust. Scheduled jobs need a finish signal and a fail signal that reach a human inbox. Otherwise you only discover gaps when you need a restore.
Snapshotify is the DaftPlug backup plugin. This post is about Backup Notifications: emailed when a scheduled run finishes or fails. Supporting context: scheduled backups daily, weekly, or monthly; cloud destinations Google Drive, Dropbox, and OneDrive; retention that only prunes automatic scheduled backups (manual and uploaded archives stay); full snapshot equals database SQL plus files as a standard ZIP. Not inventing Slack or webhook alerts. Not the focus: migration, upload ZIP restore, exclusions, or DB-only jobs (covered elsewhere). For why same-server copies fail you, read A WordPress backup on the same server is not a backup. For schedule plus cloud retention setup, keep Schedule WordPress backups to Google Drive with retention nearby.
What Snapshotify actually ships for backup email
Stay inside the real feature set:
- Backup Notifications: email when a scheduled backup finishes or fails
- Scheduled backups: daily, weekly, or monthly
- Cloud destinations: Google Drive, Dropbox, OneDrive
- Retention: only prunes automatic scheduled backups; manual and uploaded archives stay
- Full snapshot: database SQL + site files as a standard ZIP (readable without Snapshotify)
The contract is simple. Schedule real offsite snapshots. Get mail when a run succeeds or dies. Do not wait for a disaster to learn the job stopped.
Why finish and fail emails matter more than another dashboard badge
Dashboards lie when nobody opens them. Email still interrupts.
Finish emails confirm the job completed and, ideally, remind you that an archive exists where you expected it (local listing plus cloud if configured). They also create a paper trail when a client asks “are we actually backing up?”
Fail emails are the whole point. Disk full. Cloud auth expired. Cron disabled after a migrate. PHP timeout on a fat media library. Without a fail notice, the calendar icon stays comforting while the archives go stale.
Pair notifications with offsite storage. A success email for a backup that only lives next to wp-content on the same disk still fails the real test. Drive, Dropbox, or OneDrive should hold the ZIP+SQL snapshot. Retention can prune old automatic runs so the cloud folder does not grow forever. Manual and uploaded archives stay when retention runs, which is what you want for milestone copies.
How to turn on notifications in wp-admin
Assume Snapshotify is installed, a full snapshot type is selected (database SQL + files as ZIP), and you already know where archives should land. Notifications do not replace a schedule or a cloud destination. They report on them.
1. Confirm the schedule and destination first
In Snapshotify, set a schedule you will actually keep: daily for busy stores and frequently updated sites, weekly for quieter brochure sites, monthly only if you accept more data loss risk. Connect Google Drive, Dropbox, or OneDrive if offsite is the goal (it should be).
Run one manual full snapshot as a smoke test before you trust cron. Confirm the ZIP+SQL archive appears and, if configured, lands in the cloud folder you chose. Fix auth and disk issues now, not after a fail email storms your inbox every night.
2. Open Backup Notifications and set the email path
Find Backup Notifications in Snapshotify settings. Enable email for scheduled finishes and failures. Use an inbox someone monitors (founder inbox, ops alias, or a shared mailbox you actually read). A dead backup@ address that nobody checks is theatre.
Send yourself a test if the UI offers one, or trigger a small scheduled window in a staging-like check. Confirm the From path is allowed by your host or transactional setup so messages do not land in spam. WordPress site mail is flaky on many hosts. If mail never arrives, fix wp mail or SMTP before you blame Snapshotify.
3. Decide what “done” means for your team
Agree on a simple rule:
- Finish email arrives → glance at size/time; archive if you keep a runbook
- Fail email arrives → treat as a priority bug the same day
- No email on a day you expected a daily run → investigate (missing mail is itself a signal)
Do not invent Slack workflows this plugin does not ship. Email is the notification channel here. If you forward mail to Slack with your own filters, that is outside Snapshotify and fine, but do not document phantom webhook toggles.
4. Align retention so success stays meaningful
Turn on retention for automatic scheduled backups so old runs prune on purpose. Keep manual and uploaded archives out of that prune path (Snapshotify’s retention model already protects them). A finish email for a job that immediately deletes the only good copy because retention was mis-set is a bad night.
Name or note milestone manuals (pre-redesign, pre-migration) so humans know which archives are sacred. Notifications tell you the scheduler lived. Retention policy tells you how long automatic history remains.
5. Quarterly fire drill
Once a quarter, restore a recent archive to staging (or a throwaway environment). Confirm the ZIP+SQL snapshot opens without needing Snapshotify installed to read the formats. Confirm a fail email still arrives if you temporarily break cloud auth on staging and run a job. Then fix auth. The drill proves notifications and restores, not just green settings screens.
Exclusions, migration tools, and upload-ZIP flows are other articles. This post’s job is “tell a human when the scheduled run finished or failed.”
What good looks like
A finished setup feels boring in the best way:
- Scheduled backups run daily, weekly, or monthly on purpose.
- Full snapshots are SQL + files as standard ZIP.
- Cloud holds copies on Google Drive, Dropbox, or OneDrive.
- Retention prunes automatic runs only; manuals stay.
- Finish emails confirm success without you logging into wp-admin every morning.
- Fail emails page you the same day something breaks.
- Nobody discovers a month-old newest backup in the middle of an outage.
If finish emails stop arriving but the site is fine, check cron and mail delivery before you assume backups are healthy. Silence is not success.
Pitfalls (the ones that bite)
Notifications on, schedule off. Nothing to report. Enable both.
Success email, same-server only. Offsite still missing. Connect Drive, Dropbox, or OneDrive.
Inbox nobody reads. Fail mail to a black hole equals no notifications.
Broken site mail. WordPress cannot send. Fix SMTP or host mail.
Retention pruning manuals. Snapshotify’s retention targets automatic scheduled backups; keep manuals for milestones and do not “clean up” by deleting them blindly.
Ignoring fail mail as noise. One auth expiry ignored becomes three weeks of gap.
Inventing Slack or webhook alerts in your runbook. This feature is email. Document what exists.
Never testing restore. A finish email is not a restore test. Drill quarterly.
Practical checklist before you call it done
- Schedule daily, weekly, or monthly full snapshots (SQL + files ZIP).
- Connect Google Drive, Dropbox, or OneDrive for offsite copies.
- Enable Backup Notifications for finish and fail emails.
- Confirm mail arrives in an inbox a human reads.
- Set retention for automatic scheduled backups only; keep manuals.
- Run a manual smoke-test snapshot and verify the archive.
- Treat fail mail as same-day work.
- Quarterly: restore to staging and confirm formats open without the plugin.
- Keep same-server-only copies out of your definition of “backed up.”
Takeaway
A scheduled WordPress backup you never hear about is a hope, not a system. You need offsite snapshots and an email when a run finishes or fails. Dashboard badges do not wake anyone at 7am.
Snapshotify emails Backup Notifications for scheduled finish and fail events, beside daily, weekly, or monthly schedules, Drive / Dropbox / OneDrive destinations, retention that spares manual archives, and full ZIP+SQL snapshots you can read without the plugin. Turn notifications on after the schedule and cloud path work.
One Pro membership unlocks Snapshotify plus Progressify, Lightify, Generatify, and Rankify. New Pro plugins join existing memberships. Plans differ by site count only. See pricing when you want backups that speak up.
Enable the emails. Read the next fail. Fix it the same day. That is how scheduled backups stay real.