This post was originally published on this site
One of the issues that Veeam Backup & Replication users, actually those of any application aware backup solution, is that the various VSS writers are typically very finicky to say the least. Often you will get warnings about the services only to do a “vssadmin list writers” and see either writers in a failed state or not there at all. In most of these cases a reboot of either the service or the target system itself is an easy quick fix.
But do you really want to rely on yourself to remember to do this every day? I know I don’t and going with the mantra of “When in doubt, automate” here’s a script that will help out. The Reboot-VSS.ps1 script assumes that you are using vSphere tags to dynamically identify VMs to be included in backup jobs, looks at the services in the given services array and if they are present on the VM will restart them.
# Name: Restart-VSS.ps1 # Description: Restarts list of services in an array on VMs with a given vSphere tag. Helpful for Veeam B&R processing # For more info on Veeam VSS services that may cause failure see https://www.veeam.com/kb2041 Import-Module VMware.PowerCLI $vcenter = “vcenter.domain.com”
Want to learn more? Read the source post!
Previous Post
Next Post