hi,
In Veeam ONE we use the alarm 'Backup job state'. For vmware backups, it waits for all the retries to complete, then sends one alarm informing about all vm's that failed the backups.
For Nutanix backups the logic seems to be different. It sends one alarm/notification for each vm before the job completes doing the retries.
I much prefer the logic as it is for vmware. But the very least that it would be the same for both.
We have VBR 13.0.1.1071 and Veeam ONE 13.0.1.6168. AHV 9 and Nutanix Prism 7.3.1.1.
Is this by design?
Regards,
Jóhannes
-
johannesk
- Expert
- Posts: 181
- Liked: 38 times
- Joined: Jan 19, 2016 1:28 pm
- Full Name: Jóhannes Karl Karlsson
- Contact:
-
RomanK
- Veeam Software
- Posts: 846
- Liked: 231 times
- Joined: Nov 01, 2016 11:26 am
- Contact:
Re: Backup job state: Veeam ONE alarm on nutanix backup
Hello Jóhannes,
VBR does not allow distinguishing a retry session from the main session for the Proxmox, oVirt, and Nutanix platforms, so we decided to slightly adjust the alarm logic for these platforms.
For these platforms, the alarm should not be re-triggered if a newly appeared session has the same status as the previous one. In addition, child sessions should not trigger the alarm at all.
So this is a design. As soon as we learn to distinguish between sessions, we’ll be able to implement the same behavior as for VMware.
Thanks
VBR does not allow distinguishing a retry session from the main session for the Proxmox, oVirt, and Nutanix platforms, so we decided to slightly adjust the alarm logic for these platforms.
For these platforms, the alarm should not be re-triggered if a newly appeared session has the same status as the previous one. In addition, child sessions should not trigger the alarm at all.
So this is a design. As soon as we learn to distinguish between sessions, we’ll be able to implement the same behavior as for VMware.
Thanks
Who is online
Users browsing this forum: No registered users and 2 guests