Never wonder whether last night's backup ran. MokoSuiteBackup sends per-profile success and failure alerts over email and ntfy push, targeting individual addresses or whole Joomla user groups — with rich run details and, on failure, the tail of the backup log to help you diagnose fast.
Overview
MokoSuiteBackup can send notifications when backups complete or fail, over both email and ntfy push. Notifications are configured per profile, giving you fine-grained control over who gets notified and when. Component-level defaults fill in any field a profile leaves blank.
Configuration
Open a backup profile and go to the Notifications tab:
| Field | Description |
|---|---|
| Notification Email | Comma-separated email addresses to receive notifications |
| Notify User Groups | Select Joomla user groups — all members will receive notifications |
| Notify on Success | Send when a backup completes successfully (default: No) |
| Notify on Failure | Send when a backup fails (default: Yes) |
| ntfy Topic / Server / Token | Optional ntfy push: topic, server (default https://ntfy.mokoconsulting.tech), and access token |
Email addresses and user group members are combined. Duplicate addresses are automatically filtered.
Global Defaults and Inheritance
Component-wide defaults live in Components → Backup → Options, on the Notifications tab — which now also contains the ntfy push settings (server, topic, token) that previously had their own section. You can set a default notification email, notify-on-success and notify-on-failure, and ntfy server, topic, and token there.
These defaults are applied per field: when a profile leaves a notification or ntfy field blank, it inherits the component-level value; when a profile sets its own value, that value is used instead. Inheritance applies to both backup-completion notifications and restore/snapshot notifications.
Email Content
Subject Line
[MokoSuiteBackup] SUCCESS: Daily Full Backup — My Joomla Site
[MokoSuiteBackup] FAILED: Daily Full Backup — My Joomla SiteEmail Body Includes
- Site name and URL
- Backup status (success/failure)
- Profile name and backup type
- Backup description and origin (backend, CLI, scheduled, web cron)
- Archive filename and total size
- Duration, start time, and end time
- Remote filename (if uploaded to SFTP/FTP/S3/Google Drive)
- File count and table count
On failure, the last 30 lines of the backup log are appended to help diagnose the issue.
Tips
- For critical production sites, enable Notify on Failure and add the site admin's email or an ntfy topic
- Use user group notifications to automatically include new team members
- Set a notification email and ntfy topic once in the component Options and leave those fields blank on individual profiles to have every profile inherit the same recipients
- Notification errors are logged but never block the backup process — a failed email won't cause a backup failure