Today Veeam released Veeam Reporter 4.0. This release is significant for many reasons but one that I’d like to focus on here is the new tracking and auditing capability. We introduced change tracking with Reporter 3.5 but we were missing one critical piece…who made the changes? With Reporter 4.0 we now pull in the vCenter audit logs and correlate every change back to the person (or system) that made the change. Another feature that’s not available from the vSphere client is the ability to not only see the new value, but the previous value as well.
Let’s take a look at an example.
You come into work on Monday morning and you’ve got an inbox full of emails about a particular virtual machine. On Friday everything was working fine but on Monday it won’t respond, even though you can see it’s powered on and you can access the console through the vSphere client.
After a reboot doesn’t fix the issue, you now need to determine what changed. Using the vSphere client, you can see that doug.hazelman changed a custom attribute:
The screenshot above shows that the Custom Attribute “TEEAM_FUNCTION” was changed to PROD for the VM “XPViewTemp”. This is slightly helpful in that you know you have an automated process that reconfigures VM’s based on custom attribute values. Setting “TEEAM_FUNCTION” to PROD kicked off a script that moved it to the production network which is why people who could access it on Friday can’t access it today. The easy fix it to change “TEEAM_FUNCTION” back to the previous value…but what was it? The proper setting determines how this VM works, you need a quick resolution. Veeam Reporter to the rescue! All you need to do is run the infrastructure changes report showing all changes for that VM over the weekend. Clicking the name of the VM in the report, you can easily see that the old value was DEV:
Now all you have to do is change the attribute back to the correct value, let your automated script reconfigure the VM and you’re good to go!
The above example is a bit of a stretch (who automates VM configuration based on attributes?) but was meant to show how quickly and easily it is to get this data from Reporter 4. While the scenario above shows a change made in a relatively short time frame, what if the change had been made 2 months ago? How would use us the vSphere Client (or even PowerShell) to find who changed it as well as what the previous value was? Reporter 4 can give you that audit data for any time frame, you choose a date and Reporter shows you the configuration as it was on that date. If you want to see how an object has changed over a period of time (including WHO changed it), just select a time “window” for your report to get the detail.
There are a lot of powerful, new features in Reporter 4. I did the voice for this quick overview video, check it out and then download Reporter 4 to see what YOU can do with it.