Virtual Combat: Two VR vs SRM for disaster-tolerant design

From the beginning of this article, we will introduce a series of solutions for disaster tolerance. First explore the application scenarios, and then delve into the technical architecture.

Scenario One:

In a virtualized environment for a small company, run 100 virtual machines on 5 ESXi servers. Use NFS storage. There are 10 virtual machines that need to be recovered offsite. For offsite disaster recovery RPO requirements are 30 minutes and RTO is 1 hours. The Vspherestandard license has been used. Software purchase costs are limited.

Suggestions:

Adopt vsphere Replication (VR)

VR is free of charge for users who have already used vsphere essential license. VR can meet the requirements of RPO30 minutes.

Technical details:

VR is suitable for local recovery or offsite recovery. The offsite scenario is shown in the following illustration:

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/virtualization/

The full functions of VR are implemented by VR appliance. The VR appliance and the VRA communication installed on each ESXi, after the first data synchronization is completed (baselinesynchronization), transmits only the data that changes later to the offsite.

Factors to consider:

The following virtual machines are not suitable for using VR for disaster tolerance:

Ad,dns, LDAP and other virtual machines shared by two places

Vcenter

RPO Required <15 minutes

Physical RDM

Scenario Two:

A large company has a more complex virtualized environment, running 1500 virtual machines on 50 ESXi servers. With Sans. There are 100 virtual machines that need to be recovered offsite.  For off-site disaster recovery requirements RPO of 30 minutes. RTO is 20 minutes.

Suggestions:

Using VMware Site Recovery Manager (SRM)

Although VR can also meet the requirements for 30-minute RPO, it is harder to implement 100 virtual machines that are completely offsite in 20 minutes (rto=20 minutes). Because VR recovery is manual operation.

SRM is fully capable of implementing pre-set recovery workflows and testing them fully. Need is only one key to trigger the recovery, completely in the background automatically completed. Of course SRM requires an additional license to purchase. Note that VR and SRM can be used together.

Technical details:

SRM is a orchestrator that designs workflows and performs recovery actions. Data synchronization is dependent on the SRA of direct communication with the storage device

Factors to consider:

Design is relatively complex than VR

Storage device needs to support SRM

This article comes from the "Sit Watch Cloud up" blog, please be sure to keep this source http://frankfan.blog.51cto.com/6402282/1287774