Last week I wrote about the new vSAN management pack for vRealize Operations. This week sees another nice new storage feature/solution released. This time it is a solution to integrate vRealize Automation and Storage Policy Based Management (SPBM). For those of you who saw the VMworld 2016 keynotes, you may remember Yanbing Li demonstrating the ability to have a VM move to a completely new datacenter, based on storage policy compliance. In essence, if a VM exits compliance with its storage policy (for whatever reason), vRealize Automation SPBM integration can initiate a migration of this VM to a completely different…
Over the past month or so, I’ve been looking at disaster recovery of some of the vCloud Suite components. My experiences of using vSphere Replication and Site Recovery Manager to protect and recover vCenter Operations Manager in the event of a disaster can be found here and here. Now it was time to look at vCenter Orchestrator (vCO) to see if that could be protected and recovered. In this configuration, I deployed vCO in HA mode, meaning that there were two vCenter Orchestrator servers, one running and one in standby mode. The database for vCO was an external SQL Server…
I’ve recently been looking at VCO, our VMware vCenter Orchestrator product, more from a High Availability and Disaster Recovery point of view rather than a usability perspective. I admit I have little or no orchestration skills whatsoever, but there are plenty of other blogs and educational web sites out there to help you get started with VCO. Anyhow, whilst getting the product up and running, I hit a couple of snags that I thought would be interesting to share.