Six months after releasing 1.0 of the Veeam cookbook, I am happy to announce that there is a brand new version and even more bells and whistles.  The timing of this release corresponds with the VeeamOn conference starts this week.  In order to be fully prepared, I took some time to perform a very substantial overhaul and include some great new features.  When we initially launched the cookbook, the solution supported the foundational requirements to get Veeam Backup and Replication server off the ground.  We provided both dedicated recipes for building standalone or distributed enviroments.  The cookbook went one step further by providing direct custom resource integration to allow you to integrate Veeam into your own cookbook.

Today, I am pleased to announce the latest enhancements.  This list is also documented in the official Release Notes for the Veeam Cookbook version 2.0.

• New resource – Veeam Proxy: Allows for the registration of Windows Servers as new Backup Proxies and includes the feature to remove a currently registered Proxy.  This feature opens a very big opportunity to dynamically and ephemerally deploy Veeam Backup Proxies on a job by job basis.
• New resource – Veeam Upgrade: New resource that gives the server the ability to initiate an on-demand or automatic upgrade.  Simply set the desire build version or provide the update_url link to initiate the upgrade on the next chef-client run.
• Code refactor – Veeam::Helper:  We have gone back to the existing resources and completely overhauled the libraries to consolidate and remove a large amount of duplicated code.  This refactoring will make the overall process much easier to manage the code moving forward.

Interested in seeing this cookbook in action and attending VeeamOn?  Come to our session, where Michael Cade and I will talk about Cooking up some Veeam deployment with CHEF automation on Wednesday, May 16th @12:15pm

Official Github Repository for the Veeam Chef Cookbook