https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IxMTIxIiwiaGFzaCI6IjBkMzFhNzYzLTY2MDktNGM0ZC1iZWVkLTgzOGE2YzQxZTNkNyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Duplicate e-mail notifications sent when a backup or replication job is completed.

Challenge

When a backup or replication job is completed, 2 identical e-mail notifications are sent to inform on the session result.

Cause

The e-mail notification address was specified both in the general settings of Veeam Backup & Replication and in the job settings.

Solution

The problem occurs if you have enabled the Send e-mail notifications to the following recipients option in the advanced settings of the job and at the same time specified your e-mail address in the general e-mail notification settings (Tools > Options > E-Mail Settings).

To avoid receiving duplicate e-mail messages, disable the Send e-mail notifications to the following recipients option in the job settings (Backup Destination > Advanced > Notifications).
You can also set alternative e-mail addresses in the general Veeam Backup & Replication notification settings (Tools > Options > E-Mail Settings).

KB ID:
1121
Product:
Veeam Backup & Replication
Version:
All
Published:
2011-08-01
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later