Tag Archives: Scripts

My Veeam Report v1.2

6 Replies

VeeamReport-v1_2Find 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.

Continue reading →

Deploying multiple VMs via PowerCLI – Updated v1.2

92 Replies

DeployVMv1.2

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.

Changes include:

  • 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

Continue reading →

Veeam – Updating job settings with PowerShell

1 Reply

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.

Continue reading →

Updating Remote Passwords with PowerShell

Leave a reply

Changing passwords is always one of those fun tasks for any admin. It becomes even more challenging when your a Windows admin over hundreds of individual servers that are not part of the same domain.  Here’s my take on a PowerShell script to change the password of a local user on a remote system (or many remote systems), regardless of domain status.

Continue reading →

Documenting Veeam Backup Job Settings

9 Replies

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.

Continue reading →

Deploying multiple VMs via PowerCLI

6 Replies

Find the latest version here.

Here’s a PowerCLI script I have been playing with for a while that helps with deploying multiple VMs.

Highlights include deploying both Windows and Linux VMs via Customization Specification enabling the setting of hostname, IP address, etc. The script uses help from LucD to deploy using -RunAsync which speeds things up tremendously.

It’s a bit lengthy, with a rudimentary level of logging and error catching but has served me well.

Continue reading →

My Veeam Report

56 Replies

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.

Continue reading →

Veeam v7 – Backing up a single VM within a job

5 Replies

Find the latest version here.

One of the best things about Powershell and the community is the ability to easily find what others have done and improve upon it or tweak it for your own needs. This was the case with a script I found in the Veeam forums a few months back to backup a single VM using Powershell. It worked great (with a minor issue described below) but unfortunately was broken after upgrading to v7.  I was able to identify the issues causing it to fail but was not able to rectify them all. Back to the forums I went and with a little help from the folks at Veeam we were back in business.

Continue reading →

Searching through all those script files: Find-Script

Leave a reply

If you are like me, you have built up a good amount of scripts over time and haven’t yet made it to the point of creating modules or other ways to handle all of them. I needed a way to be able to search through all these scripts to find the little gems that hide within.

I came up with this short and sweet script I can run quickly to find the tidbits I am looking for. The script will prompt for a keyword and then search recursively the path specified showing the output via Out-GridView.

Not a perfect solution but works very well. It could also be tweaked to search files other than *.ps1 easily enough.

Continue reading →