VMware Data Services Manager 2.2.1 and Aria Automation Enhancements

VMware Data Services Manager (DSM) 2.2.1 is now available with General Availability (GA) status and can be accessed directly from the Broadcom Product download Portal. One major new feature is the ability to now do Subnet Customisation during product installation, something many customers have been requesting. We have also included a number of security fixes, predominantly to address the critical security vulnerability CVE-2025-1094 to improve platform security. However, the purpose of this post is too look at another features which became available at the same time as DSM v2.2.1. This is the plugin for Aria Automation which allows the Service…

DSM 2.2: Disaster Recovery with Database Replication (Video)

This is the second in a series of videos related to Data Services Manager (DSM) version 2.2 from VMware by Broadcom. In this video, we examine how to configure replication between a primary and a secondary Postgres database. Whilst the video shows the replication being configured between a primary and secondary database managed by the same DSM provider, replication could also be configured between a primary and secondary database managed by different DSM providers. Thus, the primary database could reside on infrastructure managed by one vCenter server, and replicate to a secondary database on infrastructure managed by a completely different…

Introducing VMware Cloud Disaster Recovery

At VMworld 2019, I had the pleasure of presenting our business unit’s Spotlight session with our GM, John Gilmartin (you can watch the complete recording here). One of the topics that generated a lot of interest was a low-cost Disaster Recovery (DR) service. A lot has happened in the past year but most notably was the acquisition of Datrium. Merging the original goal of a low-cost DR as a Service (DRaaS) solution alongside the smarts acquired from Datrium, we are now almost at the point where we are ready to deliver a new VMware Cloud Disaster Recovery service to our…

Virtual Volumes (VVols) and Replication/DR

There have been a number of queries around Virtual Volumes (VVols) and replication, especially since the release of KB article 2112039 which details all the interoperability aspects of VVols. In Q1 of the KB, the question is asked “Which VMware Products are interoperable with Virtual Volumes (VVols)?” The response includes “VMware vSphere Replication 6.0.x”. In Q2 of the KB, the question is asked “Which VMware Products are currently NOT interoperable with Virtual Volumes (VVols)?” The response includes “VMware Site Recovery Manager (SRM) 5.x to 6.0.x” In Q4 of the KB, the question is asked “Which VMware vSphere 6.0.x features are…

DR of VMware vCenter Orchestrator

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…

DR of vCenter Operations – Method 2 (IP Customization)

Earlier this week I spoke about our efforts to failover vCenter Operations Manager (vCops) between two sites. In that article I stated that we used vApp containers at DR site, and added vApp variables to the Analytics and UI VMs at the recovery site. While this was painstaking to set up initially, it did provide us with the ability to failover vCops seamlessly to the DR site, with the vApp VMs inheriting their network settings via the vApp construct. At the end of that post, I mentioned a KB article, 2031891, which discusses the DR of vCops using IP Customization…

Disaster/Recovery (DR) of vCenter Operations Manager

I just spent a very useful week looking at how our customers might be able to protect vCenter Operations Manager (vCops) with VMware’s vSphere Replication (vR) and Site Recovery Manager (SRM) products. It was quite tricky to get this to work, if I’m perfectly honest, but that was the whole point of the exercise. What we learnt is being fed back to the various business units within VMware, to see if we can make this more intuitive and less complex to achieve, but if you are interested in knowing how to configure your DR infrastructure to protect vCops, please read…