Find the latest version here.
My Veeam Report v1.2 has arrived! With it comes a couple of minor tweaks and the addition of successfully backed up VMs. For those backing up hundreds (or thousands) of VMs, this option can be disabled within the User Variables section. In smaller scenarios it’s nice to see at a glance which VMs got backed up last night.
This will most likely be the last update prior to Veeam rolling out v8. We’ll have to wait and see if any changes are needed for it to continue to work properly.
For those that were too busy on Tuesday looking at the shiny Apple, VMware released updates for a few of their products including PowerCLI. Following in the footsteps of the vCloud Suite, the latest version of PowerCLI is now 5.8.
VMware has published a new KB (2082132) article outlining the latest versions of PowerCLI that contain fixes for the infamous OpenSSL bugs.
I’ve gotten some great feedback from my original PowerShell/PowerCLI script to deploy multiple VMs asynchronously via a CSV file found here. I decided a minor update was needed to employ these new ideas along with a few I had myself.
One of those ideas was to require the usage of the new PowerCLI 5.5 R2 features which allows the script to run without the need for a 32bit PowerShell console.
- Cleaned up code / Minor bug fixes
- Added CSV field descriptions to notes section
- Removed requirement for 32bit PowerShell
- Added requirement for PowerCLI 5.5 R2 or later
- Added Boot parameter to determine whether or not to power on new VMs
- Added OS Customization Spec to CSV (previously was hard coded in user variables)
- Fixed logic for vSS vs vDS – Added parameter to CSV
- Added ability to use DHCP instead of just static IPs
- Renamed a few CSV fields to better describe parameter
- Added progress bar to indicate status
VMware has rolled out a few updates this week with the release of vSphere 5.5 Update 1. The majority of the products involved all got some sort of bump/patch as well as the addition of VSAN. Not to be outdone, Alan and his team also released PowerCli 5.5 R2 (Build 1649237). It is wonderful to see grand improvements in a product I use everyday.
A full rundown of the new features and download link can be found here.
It just may be time to give a serious look at updating to PowerShell 4.0 as with this update, PowerCli is fully compatible. Time to start looking at other plugins as well and determine what dependencies might have issues.
Another one of the new features that caught my eye was this:
64 bit Support
The New/Set-OSCustomizationSpec cmdlets have been updated to work in 64-bit PowerShell and no longer require running in a 32-bit PowerShell environment.
This will help my VM Deployment script as you will now longer have to run in 32bit mode. I’ll be checking this out and updating shortly.
A few posts back I described how you can document your Veeam backup job settings. This gives a great overview, especially if you have many jobs to keep track of. As I mentioned, I had found a few inconsistencies across jobs and in this post I’ll show how to update all jobs via a small script. You can imagine the time saved by not having to open each and every job, check the settings and update if needed.
A few months back I came across this article from Luca Dell’Oca – Check multiple job settings in Veeam Backup & Replication with Powershell. As he describes, this is a great way to get a good view of your backup jobs. When you have a few hands in the mix, over time with lots of jobs, human error is going to happen. A missed check box here, incorrect setting there. You’ll be surprised what you may find the first time you look. So I decided to finally take his advice and create a quick report that dumps the job details to a csv file.
Find the latest version here.
Here’s another case of taking a script that someone has shared and putting your personal tweaks into it.
If there was an area in which I wish Veeam would improve, it would be reporting. Though their answer is VeeamOne, it’s a bit much if you just want the additional backup reports. Fortunately this can be overcome with some creative Powershell. I started with a report called vPowerCLI v6 Army Report which can be found here. I had used this report for quite a while until v7 came along and broke a few items. I decided to take the opportunity to not only fix the issues (where I could) but also add some information to the report. I had also been looking at the SAMReports found here and decided to combine a few bits. Lastly, Tom Sightler had a post here that added the ability to report back VMs that had not been backed up within the given time frame – very nice. I can’t say enough about the original authors, without which, I never could have come up with such a report in the end.