VMware Site Recovery Manager 6.5 is an exciting release for VMware. We’ve added a number of cool features that make it easier to use and monitor SRM. We’ve also done a number of things to allow SRM to interoperate more and better with other VMware products. All of these improvements enhance what is already the premier virtualization BC/DR solution and provide additional value, time savings, security and risk reduction to customers.
vSphere 6.5 Compatibility
First off, SRM 6.5 is compatible with vSphere 6.5 including:
- Full integration with the new vCenter HA feature. SRM will continue working normally if vCenter HA fails over
- Full support for Windows vCenter to VCSA migration. If a customer uses the migration tool to upgrade and migrate their environment from vCenter 6.0 on Windows to vCenter 6.5 on the VCSA, from an SRM standpoint this is just seen as an upgrade and is fully compatible with a standard SRM upgrade
- SRM supports protecting VMs that are using VM encryption when using Storage Policy-Based Protection Groups (SPPGs)
- There is now support for Two-factor authentication such as RSA SecurID with SRM 6.5
Integration with the new vSphere Guest Operations API. This means that changes to VM IP addresses and scripts running on VMs will now be even more secure
vSAN 6.5 Compatibility
SRM 6.5 is fully supported and compatible with vSAN 6.5, as well as all previous vSAN versions, using vSphere Replication. SRM and vSAN make a great pair for a number of different use cases. They have and continue to work well together to provide low cost, easy to use vSphere integrated storage and disaster recovery.
SRM and VVOLs interoperability
In addition to all the new cool features that are part of Virtual Volumes (VVOLs) 2.0, SRM 6.5 now supports protection of VMs located on VVOLs using vSphere Replication. If you are using storage other than vSAN you owe it to yourself to take a look at VVOLs and see what you can get out of using them.
API and vRO plug-in enhancements – Scripted/Unattended install and upgrade
There have been a number of enhancements to the programmatic interaction with SRM 6.5. These take a few forms, primarily: exposure of a number of new options in the SRM API and significant enhancements to the vRealize Orchestrator (vRO) plug-in for SRM to take advantage of these. The new functions available through the API and vRO plug-in are listed below. Follow these links for details on the existing API and vRO plug-in.
- Add a Test Network Mapping
- Get Test Network Mappings
- Remove a Test Network Mapping
- Remove Folder Mapping
- Remove Network Mapping
- Remove Resource Mapping
- Remove Protection Group
- Remove Replicated VM From VR Group
- Unprotect Virtual Machines
- Add Test Network Mapping to Recovery Plan
- Create Recovery Plan
- Delete Recovery Plan
- Initiate Planned Migration Recovery Plan
- Remove Protection Group From Recovery Plan
- Remove Test Network Mapping From Recovery Plan
- Discover Replicated Devices
These functions along with the functions previously exposed provide programmatic access to almost the full range of SRM functionality. This makes it that much easier to manage and maintain SRM programmatically, saving time and improving accuracy and efficiency. Additionally, SRM 6.5 now fully supports unattended/silent installation and upgrades. This makes the deployment of SRM much faster and easier, saving you time and money.
vSphere Replication RPO
Another exciting new enhancement for SRM is actually part of a related solution, vSphere Replication. vSphere Replication now supports VM RPOs of as low as a 5 min on most VMware compatible storage. Look for the specific details in the release notes and documentation. This takes the RPO available with vSphere Replication to the point where it covers most use cases. And remember that vSphere Replication is included in vSphere Essentials Plus licensing and above.
vROps SRM Management Pack
Last but definitely not least, SRM 6.5 marks the first time that vROps has a management pack for monitoring SRM. This will allow for monitoring of the SRM server, Protection Group and Recovery Plan status from within vROps. This makes it easier to monitor, manage and troubleshoot SRM.
I hope you enjoy all these new features and capabilities, put them to good use and tell us about it.
23 comments have been added so far
Wow, VMware has done a really great job , finally they have released SRM 6.5 with some new features and these features are easy to use . This is really awesome that SRM 6.5 is compatible with vSphere 6.5 and SRM 6.5 is fully supported and compatible with vSAN 6.5, as well as all previous vSAN versions. All the new features of SRM will be very beneficial for any virtualization infrastructure . Thanks for this information . The way you explained each and everything about new features of SRM 6.5 is really great . Thanks once again.
Great recap of the new features! Does SRM 6.5 require installation on a Windows platform as in the past, or can it be used on a Linux virtual appliance (either the VCSA itself, or a separate Linux-based virtual appliance)?
Yes, SRM still requires installation on a Windows platform.
Is VVOL Replication supported in SRM 6.5?
SRM 6.5 supports protecting VMs that are located on VVOLs and replicated with VR. It doesn’t support VVOL array based replication.
Does it still have the 256 OS device limit, counting R2s and test clones?
Is it backwards compatible with SRM 6.0?
Are the SAN array’s SRA web based plugins available?
When creating the Recover Plans does it allow you to single click and map the network mappings to all VMs, or is it one at a time?
If I have an existing recovery plan and create another one with the same protection group and additional ones does it still effect the original VMs in the original recovery plan if I make changes?
Does it still have the 256 OS device limit, counting R2s and test clones? – That is a vSphere limit that I believe will increase in the next release.
Is it backwards compatible with SRM 6.0? – No, SRM 6.5 will require vCenter 6.5, and SRM 6.5 at both sites.
Are the SAN array’s SRA web based plugins available? – They will be available on the product GA date.
When creating the Recover Plans does it allow you to single click and map the network mappings to all VMs, or is it one at a time? – SRM 5.8 and higher support auto mapping of networks. Network mapping is done at the site level not within RPs. 5.8 and higher also support IP subnet mapping.
If I have an existing recovery plan and create another one with the same protection group and additional ones does it still effect the original VMs in the original recovery plan if I make changes? – Yes, this is expected behavior and hasn’t changed in the upcoming release.
Is SRM 6.5 compatible/supported on Windows Server 2016?
Well, looks like SRM 6.5 is still a Windows based application. My WIndows 2008 R2 server has all VMware stuff under one roof, vCenter, Update Manager and SRM. I have waited and waited, and happy to know that VUM is now supported with the new vcenter server virtual appliance. But SRM is left off and once I migrated to VCSA, I still need to maintain a dedicated WIndows box just for SRM! This is annoying!! Hopefully VMware can fix this soon.
Can I pair a SRM 6.1 / Windows vCenter 6.0U2 (Protected Site) with a SRM 6.5 / VCSA 6.5 (Recovery Site) ?
See this for interop details: http://www.vmware.com/resources/compatibility/sim/interop_matrix.php#interop&7=&2=
Yes. See: https://www.vmware.com/support/srm/srm-compat-matrix-6-5.html#hostOS
So that is a no then 🙁
SRM 6.5 is only compatible with vCenter Server 6.5 and vCenter Server 6.5 is not compatible with SRM 6.1.1. This creates a problems since you cannot upgrade vCenter Server due to SRM 6.1.1 plugin compatibility and you cannot upgrade SRM due to the vCenter Server compatibility. What are customers to do, manually delete the plugin with MOB before vCenter server upgrade?
The steps for upgrading to SRM 6.5 are documented here: http://pubs.vmware.com/srm-65/index.jsp?topic=%2Fcom.vmware.srm.install_config.doc%2FGUID-B3A49FFF-E3B9-45E3-AD35-093D896596A0.html&__utma=207178772.223010927.1464162749.1485806341.1486401617.25&__utmb=2071787126.96.36.1996401617&__utmc=207178772&__utmx=-&__utmz=207178772.1486401617.25.21.utmcsr=google|utmccn=(organic)|utmcmd=organic|utmctr=(not%20provided)&__utmv=-&__utmk=74101777
Can here to say this. I agree it is annoying.
How does this new encryption feature will work in VSPhere 6.5 , as i have seen some comments which is a new feature in the product.