Guest Post by Bob Lanning, Sr. Infrastructure Engineer at Premier, Inc.
At Premier, we are currently protecting and managing hundreds of VMs and TBs of storage – and the environment is only growing. Automation is becoming more and more important to us to ensure we are able to effectively manage the environment. With Zerto’s Virtual Replication we are able to execute a complete failover of our environment in the event of a disaster in just a few clicks with all the automation built into the product. In Zerto Virtual Replication 4.5 and the growing library of REST APIs, I am very excited with the prospects we have to automate more processes within our environment.
We have been automating via scripts with some of the standard command line tools available from the Zerto cmdlets as well as some of the testing APIs that were present in previous version. We are now seeing that as we add more and more virtual machines to our production environment, we need to further automate the inclusion into Zerto VPGs. The new APIs included in 4.5 that will allow us to fully manipulate VPGs as part of our normal orchestration (we use VMware Orchestrator for Production), are going to make it super easy to automate and allow more administrators to build critical Production servers and have them automatically placed in the appropriate VPG. Of course the hard part will be to make sure we have a really good knowledge of what VPG a new server should be in. This will be hopefully handle by our ticketing system, where the requestor will fill out the appropriate Application information that we will use to either build a new VPG or add to existing.
Now I am a former Windows administrator so this scripting and automation is kind of new to me. When we were building servers at a rate of 4-5 per month, using Templates in VMware was more than enough. And we typically just added the virtual machines to Zerto VPGs when we got a list for the next Quarterly Failover Testing cycle. Not super-efficient or fault tolerant, but it worked. Now we build 10 plus virtual machines per week it seems and adding many new critical applications from our never ending acquisition schedule. So automation is a must. Our Unix/Linux team built out much of our Orchestrator infrastructure (thanks Matt), so I just got to edit and learn.
Excited to see how we can use the new REST API’s to pretty much soup to nuts our Production BC/DR strategy.
Some of the new API capabilities we are planning to deploy are:
I think that by fully automating our Production server build process to include Zerto protection, we will always been in a state of utmost recoverability. If we make sure that every Production system is not only built similarly, but with all appropriate protection (anti-virus, backups, system configurations and most importantly BC/DR) we can truly say that our infrastructure is protected. And, by having a fully automated solution, we can scale our offerings out quickly and easily with the same protection as when we did things one at a time!