VMware SRM Review

SRM - standard disaster recovery for VMware

Most VMware administrators have heard of Site Recovery Manager (SRM). SRM has been the standard in disaster recovery for some time. It plays into VMware’s parent company’s (EMC) product line, traditionally leveraging storage based replication. This architecture leverages write journaling technology we spoke of in our first article in the series, so Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs) could be very aggressive.

The down side to this architecture is that the customer has to have similar storage arrays at both the production and disaster recovery site. If for example the customer had a fiber channel array on the production side, and a lower grade NFS array from a different vendor on the other side SRM was not compatible Bummer…

VMware however released vSphere replication in the vSphere 5 family suite and allowed administrators to replicate their virtual machines without common storage subsystems. What this means is that you could have your traditional fibre channel SAN on the production side, and NFS, or internal storage on your disaster recovery site. The underlying storage type is completely irrelevant as long as the workload is supported. This is a gift for DR budgets everywhere. Additionally you can recover to previous points in time using snapshots at the recovery site much the same as you would use a traditional snapshot.

SRM in thie configuration sits on top of the vSphere replication instead of RPAs that are common in array to array based architectures. These replication appliances are Linux virtual machines that are deployed in the VMware environment. I will give VMware a large amount of credit here, where some competing technologies are cumbersome to install, vSphere replication installation takes only a few mouse clicks. Your vSphere replication appliances are functional in just a few minutes. Replication can be configured through the VMware fat client or the web client.

So what’s the catch? vSphere replication would fall into the snap and replicate category. This means that RTOs and RPOs wont be as aggressive as with array to array based replciation, or hypervisor technologies that use write journaling. The current RTOs and RPOs that can be achieved by vSphere replication with SRM over vSphere replication is 15 minutes. There are rumors that this will be coming down to 5 minutes in the future, but it’s only a rumor at this point. Also if you are trying to move to the web client then you will dismayed to learn that SRM can still only be managed through the VMware fat client. I don’t know to many administrators that are excited about the web client, but it’s a relevant piece of information for your day to day work.

So what about the licensing and additional costs? There are pros and cons to the vSphere replication / SRM model.

The virtual appliances are Linux based – pro

This means there aren’t additional Windows licenses required to operate the environment. Some of the other products use Windows based virtual appliances. When you have to stand up more Windows servers you have to patch and manage them, this adds to the cost of the solution. SRM can generally be installed on your Windows system that vCenter runs on. If you’re using the Linux based vCenter appliance SRM isn’t compatable. I would expect this to be resolved soon as VMware is trying to eliminate the need for Windows systems in the environment.

The base vSphere replication is free – pro

Yes you heard that correct, vSphere replication is free. If you have lower priority virtual machines you don’t have to buy SRM licenses. This means you can save money and buy only the SRM licenses (sold in packs of 25) for your mission critical VMs.

SRM is the orchestration tool on top of vSpherer replication – nutural

SRM and all of it’s power can be scoped down to only the systems you need it for. I personally like the flexability and choice, most companies don’t need to replicate all of their virtual machines with very tight RTOs and RPOs. If you are trying to replicate your entire VMware environment, you maybe better off with a solution that licenses by socket as it maybe more cost effective.

Snap and replicate technology – con

At the end of the day snap and replicate technologies are limited. Because the recovered virtual machine ends up with snapshots scalability can be an issue. Let’s look at an example.

VMware recommends that you only have 21 snapshots at a maximum using vSphere replication. More snapshots than this can lead to snapshot consolidation issues. If you wanted to have a recovery point every hour, you wouldn’t be able to recover your virtual machine to a point further back than 21 hours. This a limitation of any snaphost based replication technology not a defiency with in SRM or vSphere replication.

Scalability – neutral

The upper limit to SRM with vSphere replication is 1000 virtual machines. This will suit most enterprises; however, for very large scale deployments this may not be enough. SRM with storage array replication for example can support up to 1500 vitual machines. This limit is roughly about what you would get with any other snap and replication technology. In my personal experience Veeam starts to have problems after 300 virtual machines in a single instance.

Speaking of Veeam this is the next technology that we will discuss. Veeam is a good product that not only provides DR capabilities, but also a very mature backup solution. Join us for our next article in the series.

Originally published here: https://simplecontinuity.com/dr-for-vmware-srm-on-vsphere-replication/

**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More VMware SRM reviews from users
...who work at a Manufacturing Company
...who compared it with Zerto
Learn what your peers think about VMware SRM. Get advice and tips from experienced pros sharing their opinions. Updated: July 2021.
523,431 professionals have used our research since 2012.
Add a Comment
ITCS user

author avatarit_user280458 (Technical Lead at a non-profit with 501-1,000 employees)

Nice article but just to let readers know that you don't have to have similar storage arrays at your protected and recovery sites.

When we first rolled out SRM we had an EVA at our protected site replicating to a Hitachi AMS at our DR site. The magic that allowed this to happen was Falconstor NSS. It's effectively a vendor agnostic SAN controller that sits between you SAN and VMWare. It has its own VMWare SRA so plugs seamlessly into SRM.

If, like us at the time, you're serious about BCP but your budget doesn't stretch to two, similar enterprise SANs and associated replication license costs, then it's worth a look.

Falconstor brings other tools to the table such as LUN mirroring, useful for moving data between SANs. There's also CDP for physical hosts mirroring their local disk to SAN storage, which can then be replicated to your DR site, recovered to a blank VM and converted to a full blown VM using VMWare Converter - useful for recovering your physical SQL servers into a lab environment as well.

author avatarRoger Nurse
Top 5LeaderboardReal User

Nice article - I recently have been looking at Vsan as a viable option for lab POC. Some DRaaS customers have a need to replicate/recover specific workloads outside of the SRM protected groups so they can control failover testing. In real world I do not see many customers using vsphere native replication in conjunction with SRA San layer replication. Vsan requires 3 host Minimum and works with vsphere replication.

Vsphere replication nice free to use pro for sure. Limited use cases as far as enterprise production recovery. Perhaps vsphere replication and vsan combination is low cost future of DRaaS?