Monitoring Iperius Backup by email

1. Turn on email notifications in the job

In Iperius notifications are set per backup job, in the email notifications panel.

• Create an email account with sender, SMTP server, credentials and secure connection. You can reuse it in every job.
• Turn on the notification at the end of the backup and, as recipient, enter the mailbox Mail Monitor will read: ideally a dedicated one, such as [email protected].
• Choose to send the email every time, not only on errors: the missing success email is what triggers the alert.
• In the subject use Iperius’s special variables to insert the computer name, the job name and the result: they are what your rules will look for.

2. Sending conditions

Iperius can also send the email only in some cases: errors, a backup larger than a threshold, no files copied. For the Mail Monitor check keep it sending on every run: Mail Monitor checks the conditions on the emails that arrive.

3. Create the check in Mail Monitor

One check per job: if one goes missing, you know which.

• Connect the mailbox over IMAP. We always open it read-only: nothing is moved or deleted.
• Sender: the address of the email account set up in Iperius. Subject contains: the computer or job name.
• The result wording depends on how you wrote the subject, on the version and on the language: test the rules on the last 50 emails and pick the words that really appear in yours.
• Expected: the job’s own schedule (daily, Mon–Fri, every N hours, or a cron expression on the Premium plan) with a cut-off time and a tolerance.

4. What happens when something goes wrong

• The backup ends with errors: the email arrives and the check turns ERROR, with the rule that triggered it.
• Nothing arrives by the cut-off time: the check turns MISSING. This is the case Iperius’s own notifications cannot cover.
• Either way an alert goes out: to you, right away or in the daily digest, and if you want to your customer, from your SMTP and with your logo.

5. Beyond email

On the Premium plan you can add a threshold on a number written in the email, such as the backup size, and an API check: in the job step for other processes, run a call to the check URL after the backup. If the job does not run, the call never arrives and the check turns MISSING even when email is down.

curl.exe -fsS -m 10 --retry 3 <check-URL>