-
- Service Provider
- Posts: 128
- Liked: 11 times
- Joined: May 15, 2012 9:06 am
- Full Name: Martin Broaders
- Contact:
Report on newly added/removed servers in backup jobs
We have a site that uses VMWare tags to add servers to jobs. Running the Veeam change audit report doesn't pick up on servers added and removed to the jobs presumably because the job configuration isn't changing. Is there a way to report on newly added/removed servers to the backup jobs in Veeam any other way?
-
- Veeam Software
- Posts: 745
- Liked: 191 times
- Joined: Nov 01, 2016 11:26 am
- Contact:
Re: Report on newly added/removed servers in backup jobs
Hello Martin,
You can find workloads, for example in the Job History report drill down
Please let me know if that is what you are looking for.
Thanks
You can find workloads, for example in the Job History report drill down
Please let me know if that is what you are looking for.
Thanks
-
- Service Provider
- Posts: 128
- Liked: 11 times
- Joined: May 15, 2012 9:06 am
- Full Name: Martin Broaders
- Contact:
Re: Report on newly added/removed servers in backup jobs
Not really. I was hoping for a report that would just show newly added/removed servers to jobs. Its the kind of thing that would be picked up by the Veeam Infrastructure Audit Job logs if the change occurred there but as the VMs are added/removed via a tag they don't. The Job History report requires comparing reports and would be time consuming.
-
- Veeam Software
- Posts: 745
- Liked: 191 times
- Joined: Nov 01, 2016 11:26 am
- Contact:
Re: Report on newly added/removed servers in backup jobs
Hello Martin,
Currently, only Job History has this data.
Your idea is Interesting, but there are a few possible issues.
VBR created a list of tag-based VMs only when the job started. Therefore, we would be able to track newly added/removed VMs at this time only.
As you probably noticed, the Audit report is event-based. We are able to create an event and compare the previous and latest backup sessions. But what would happen when >100 VMs would be added to the job(or 10 jobs with +10 new VMs)? It would be impossible to read the Audit report.
It seems to me that something like "%JobName% finished: X new VMs were added, Y removed, Z backed up" would work as an audit event but would it be helpful without names?
Thanks
Currently, only Job History has this data.
Your idea is Interesting, but there are a few possible issues.
VBR created a list of tag-based VMs only when the job started. Therefore, we would be able to track newly added/removed VMs at this time only.
As you probably noticed, the Audit report is event-based. We are able to create an event and compare the previous and latest backup sessions. But what would happen when >100 VMs would be added to the job(or 10 jobs with +10 new VMs)? It would be impossible to read the Audit report.
It seems to me that something like "%JobName% finished: X new VMs were added, Y removed, Z backed up" would work as an audit event but would it be helpful without names?
Thanks
Who is online
Users browsing this forum: No registered users and 140 guests