Veeam Package for vRealize OrchestratorDecember 7, 2015
Veeam is a popular backup product for virtualized environments but who wants to spend their days adding and removing machines to backup jobs?
Now available on github is a Veeam package for vRealize Orchestrator. This is my gift to you, just in time for the Hollow-days.
- Add a VM to an existing backup job
- Remove a VM from a backup job
- Start a backup job immediately
- Add a Build Profile to vRealize Automation
- Add a VM to a backup job from vRA
- Remove a VM from a backup job from vRA
Some additional functionality could easily be added to your environment using the existing worfklows such as start a backup as a Day 2 operation in vRA, or change backup jobs etc. The world is your oyster.
Disclaimer – Veeam had no involvement with the creation of the vRO workflows and does not officially support their use. This software is to be used at your own risk and tested in your own environment.
In order to use the package there are certain requirements that must be met before installation.
- A working Veeam Backup and Replication Server with at least one backup job configured – (Tested with v8)
- Veeam Backup Enterprise Manager (This provides the API)
- Working vRealize Orchestrator appliance
- Optional – vRealize Automation Solution
To begin, go to github.com and download the vRO Package. Once downloaded, open vRO and change to Design View. Select the Packages tab and then the import button. Select the package downloaded from github.
Next, the list of elements will be shown. You may import any you wish. Each of the elements is necessary for the package to fully work, but if you have existing elements already in your vRO appliance, you may choose not to import some of them. By default only the missing elements will be imported. Select “Import selected elements”.
Now that the package has been installed, navigate to your workflows and find the “Veeam” folder. Run the “Add_VeeamRestHost” workflow to add a REST endpoint. This should be your Veeam Enterprise Backup Server.
Run a Job
NOTE: the vCenter name must be identical to what is configured in Veeam Backup and Replication, including the case. As seen below from my lab.
If you want to leverage vRealize Automation to have your VMs automatically added to a backup job after provisioning and removed during deprovisioning, then go to the vRA_Setup folder and run “Veeam_CreateBuildProfile”.
Provide the vRA Host, the build profile name and description and then the vCenter Name and Backup job that you’d want to add VMs to. Feel free to add multiple profiles if you have more than one backup job, just be sure to change the profile name and job.
Once the job has been run, you can go into vRealize Automation and see the build profile and the settings that have been configured. Just add the build profile to your blueprint to use it.
Update for vRealize Automation 7
If you’re planning to use this package with vRealize Automation 7, there are two additional workflows available for use with “Property Groups” which are the replacement for the old vRA 6 “Build Profiles” and a workflow to be used with vRA 7 Event Subscriptions which are the replacement for the stubs found in vRA 6.
Once you run the “Veeam_CreatePropertyGroup” Workflow, you’ll have a new group listed in vRealize Automation 7. The screenshot below shows the results of the workflow.
From there, you can add the property group to any of your virtual machines in the design canvas. Be sure to set your vRO properties so that vRA is passing properties over to vRO during the machine provisioning events.
I hope that someone gets use out of this package. Automating your backup process can save a lot of time in dealing with mis-configurations or just forgetting to set a backup on a new machine. This package coupled with vRealize Automation should really save time for system administrators. This package is free for anyone to use and modify at your own risk. I won’t be responsible for the awesome stuff or bad stuff you may choose to do with it!