VMware's disaster recovery solution is called SRM. SRM is mechanization programming that incorporates a hidden replication innovation to give strategy-based administration, non-problematic testing, and computerized coordination of recuperation designs. It gives accessibility to the VMs when disasters occur:

SRM uses vSphere Replication and supports a broad range of array-based replication solutions available from various VMware storage partners. SRM integrates tightly with VMware vSphere Web Client and vCenter Server, and it also takes advantage of software-defined datacenter (SDDC) by integrating NSX and vSAN.

As written, cross-site replication at the VM or storage level is just the first step for DR. You will then need an entire set of rules to define how to recover your VMs in the case of the primary site failure. SRM delivers several features and functions, including centralized recovery plans, non-disruptive testing, and automated orchestration, both for fail-over (in the case of DR) and fail-back (in case the original site has been recovered).

Adding extended stockpiling to a SRM sending on a very basic level diminishes recuperation times; on account of a catastrophe, recuperation is a lot quicker because the extended stockpiling design that empowers synchronous information composes and peruses on the two destinations.

Please note that the SRM model for active-active data centers is fundamentally different from the model used in the VMware vMSC. SRM uses two vCenter Server instances, one on each site, instead of stretching the vSphere cluster across sites.

Adding SRM to a stretched storage deployment allows users to benefit from key features of SRM that are not present in vMSC, such as centralized recovery plans, orchestrated recovery, and non-disruptive automated testing.