[Virtualization practice] Design Method for Disaster Tolerance Design

Author: Fan Jun Frank Fan) Sina Weibo: @ frankfan7

There must be a clear idea in Disaster Tolerance Design to help us consider both the overall situation and the details. Taking business needs as the leading factor is necessary, rather than talking about the specific functions of a product as soon as possible. I have summarized the following three steps:

1. gain an in-depth understanding of business needs

650) this. width = 650; "src =" http://www.bkjia.com/uploads/allimg/131228/003HRX7-0.png "title =" dr1 (Mobile).png "/>

Some Business Parameters are listed. From this article.

We will focus on the following elements:

RTORecovery time objective): After a disaster occurs, applications must be restored within this time.

RPORecoverypoint objective): the time period in which data loss can be tolerated after a disaster occurs.

In theory, of course, the smaller the RTO and RPO supported by the disaster recovery solution, the better, but it is not necessary to simply pursue the minimum value, resulting in unnecessary high costs, that is, OverEngineering. Good architects should provide solutions to meet their needs from the perspective of customers.

When communicating with the customer, we must break the sandpot and ask the question to the end, how does the RTO and RPO come from? Many times, no one can make it clear. This requires starting from the application. For example, some applications have achieved high availability, such as MSCluster and LVS. Disaster Tolerance does not have to be overly considered for the Infrastructure that supports the application. In many cases, the Hypervisor can satisfy its own HA requirements.

Risk

From the Severity) and likelihood likehood. For example, financial institutions have very high requirements for this. One of my customers cannot accept the huge losses caused by system downtime. Therefore, they require ZeroRTO and Zero RPO after risk assessment.

Ii. Factors affecting key Architecture DesignArchitecture Decisions)

Site:

Local: some disaster recovery solutions can be implemented locally to meet customer needs.

Dedicated DR Sites: whether a Dedicated DRSite is required depends on the company's IT strategy and sustainable development. Of course, the cost is greatly affected.

Shared DR Site: Shared DR Site is out of Disaster Tolerance and may be of other use.

Cloud Based Recovery: You can consider the Disaster Tolerance solution of Cloud service providers. For example, VMware hybrid cloud vCHS has recently released a Disaster Tolerance solution.

StorageReplication

Software: the Software is fully used for data synchronization and does not rely on SANReplication.

SAN-based: most high-end storage devices support SANBased Replication. If you have special requirements, you can also use software to implement advanced SANReplication. For example, EMC Recovery Point.

Networks between data centers

DR dedicated: completely proprietary to DR

MPLS: public.

Determine whether the disaster recovery solution meets RTO and RPO requirements based on the bandwidth and synchronized data volume.

3. Evaluate appropriate productsProduct Mapping)

There are many Disaster Tolerance products and solutions on the market. We need to ask ourselves a series of questions, list the Feature that needs to be met, and then evaluate the indicators for each product.

Method 1: Evaluate several major aspects

Such as RTO, RPO, Cost, Flexibility, and Managability.

Method 2: careful evaluation

	Product 1	Product 2
Requirement 1	Y	Y
Requirement 2	N	Y

Refer:

Disaster Prevention and Recovery Architecture from RMI

DRBC Design-Disaster Recovery and Business Continuity Fundamentals

This article from "sit up and watch the cloud" blog, please be sure to keep this source http://frankfan.blog.51cto.com/6402282/1288884