The vCenter Server, Platform Services Controller, and SRM versions must be the same on both sites.If the external deployment method is used ensure the vCenter at the failover site is able to connect to the Platform Services Controller (i.e. SRM supports both embedded and external Platform Services Controller deployments.
A vCenter Server must be in place at both the protected site and the recovery site.Each SRM installation requires its own database, this can be embedded for small deployments, or external for large deployments.The Windows server should have User Access Control (UAC) disabled (in the registry, not just set to never notify) as this interferes with the install.SRM requires an absolute minimum of 2vCPU, 2 GB RAM and 5 GB disk available, more is recommended for large environments and installations with an embedded database. SRM is installed on a Windows machine at the protected site and the recovery site.
#Srm compatibility matrix 6.0 upgrade#
Site Recovery Manager now has integration with the HTML5 vSphere client, see VMware Site Recovery Manager 8.x Upgrade Guide for more information. After a failover SRM can reverse the replication direction and protect virtual machines ready to fail back, all from within the vSphere web client. In the event of a site outage, or outage of components within a site meaning production virtual machines can no longer run there SRM brings online the replicated datastore and VMs in vSphere, with a whole bunch of automated customisation options such as assigning new IP addresses, boot orders, dependencies, running scripts, etc. SRM plugs into vCenter to protect virtual machines replicated to a failover site using array based replication or vSphere replication.
This post will walk through the installation of Site Recovery Manager (SRM) to protect virtual machines from site failure.