chall wrote:I've configured a new rule using "Job duration exceeded the allowed timeout period" and configured a custom duration but then I am prompted to choose a VM.
As I have a lot of VM's it would be easier if it was possible to do this for all VM's with a wildcard or something? This would also cover any new backup/replication jobs I create in the future.
chall wrote:But I see it only triggers the alarm once for the first job - so if subsequent jobs run past the specified time I won't receive another alert until I have manually resolved the first one.
Vitaliy S. wrote:Chris,chall wrote:But I see it only triggers the alarm once for the first job - so if subsequent jobs run past the specified time I won't receive another alert until I have manually resolved the first one.
No exactly, you should receive email notification on the breached threshold for other jobs too, however only one combined alarm will be visible in the backup console, it is by design. If you need to review all jobs that has exceeded their max duration, please double-click on the alarms history to review all jobs. Anyway, I will verify the behavior you describe with our QC team.
The major use case for this alarm is to track individual job duration. I believe you would agree that jobs duration can vary a lot depending on the number of VMs being processed, thus it's hard to set a single threshold for all jobs, that is why you should be using separate alarms for different jobs.
BTW - how many jobs you have in your environment?
chall wrote:This week we had a problem with our core switches which had a massive impact on Veeam's performance. I was seeing very low throughput (approx. 100Kb/s instead of 100+Mb/s) but because the jobs weren't failing I wasn't aware for several days until I logged on to the Veeam B&R server by chance!
chall wrote:who already have Veeam B&R but aren't using Veeam One.
Users browsing this forum: No registered users and 3 guests