November 19, 2017 1
Table of Contents 1. Disaster Recovery 1.1.Overview 1.2.vSAN Stretched Clusters and Site Recovery Manager 1.3.vSAN Performance 1.4.Summary 2
1. Disaster Recovery According to the United States Department of Homeland Security, roughly 40 to 60 percent of small businesses never reopen their doors following a disaster. 3
1.1 Overview Lowering the Risk and Cost of Disaster Recovery According to the United States Department of Homeland Security, roughly 40 to 60 percent of small businesses never reopen their doors following a disaster - www.fema.gov Large organizations are also susceptible to significant losses from a disaster as shown in numerous online news articles. The expense of a disaster recovery site is cost prohibitive for many organizations. As a result, a number of businesses have an inadequate or no disaster recovery plan, which introduces considerable risk. One of the more significant costs of a disaster recovery site is the IT systems infrastructure including server hardware, storage, and replication software. It was common for organizations to deploy similar systems at both the production site and the disaster recovery site. This costly approach was done to help prevent failure in recovering applications and data due to differences in the infrastructure. Virtualization removes the need to have the same infrastructure hardware at both the production and disaster recovery sites by abstracting the physical hardware from the applications. Furthermore, a virtual machine s configuration, operating system, applications, and data are stored as files making it much easier to copy a virtual machine from one site to another. The virtual machine can be reliably powered on and used at the disaster recovery site even if the underlying physical hardware is different from the production site. However, storage is needed just the same at a disaster recovery site to hold the virtual machine files. Many of these files can be quite large ranging from just a few gigabytes (GB) in size up to hundreds of GB or even a few terabytes (TB). Storage capacity requirements can add up quickly depending on the number and size of the applications and databases that need to be protected. Performance is also a factor that must be considered as it has a direct impact on the reliability of a recovery and the recovery time. It is possible that an organization will have to run business-critical applications at a disaster recovery site for several days or weeks. Storage that does not meet ongoing business demands can impact productivity and revenue. In summary, storage provisioned at the disaster recovery site must meet capacity and performance requirements at a reasonable cost. Why vsan for Disaster Recovery? VMware vsan is VMware s radically simple storage solution for hyper-converged infrastructure (HCI). vsan and VMware vsphere provide a complete, natively integrated platform consisting of compute, network, and storage resources for a wide variety of use cases including disaster recovery. Deploy on inexpensive industry-standard x86 server components to remove large, upfront investments. Since disks internal to the vsphere hosts are used to create a vsan datastore, there is no dependency on external shared storage hardware. This helps reduce the total cost of the solution while providing sufficient capacity, reliability, and performance. 4
vsan is built on an optimized I/O data path in the vsphere hypervisor for exceptional performance. It is managed as a core component of a vsphere environment meaning separate administration tools and connections are not required. This simplifies management particularly in locations that have little or no local IT staff such as a disaster recovery site. VMware vsphere Replication provides asynchronous virtual machine replication with recovery point objectives (RPOs) as low as five minutes. Replication is configured on a per-virtual machine basis enabling precise control over which workloads are protected. This approach avoids the need to provide excess capacity at a disaster recovery site to accommodate an all-or-nothing replication solution. Furthermore, there is no requirement to have the same type of storage at both sites enabling more deployment options. As an example, consider four 200GB virtual machines on a single LUN at the production site. Disaster recovery protection is needed only for two of the virtual machines. With array replication, the entire LUN (all virtual machine data) is replicated. vsphere Replication can replicate just the two virtual machines needing protection, which reduces capacity requirements at the disaster recovery site and wide area network (WAN) bandwidth consumption. Virtual machine-centric storage policies can be created and assigned for various workload types. Policies are based on the availability and performance services provided by vsan. These policies can be modified and reassigned, as needed, with no downtime. vsphere Replication supports storage policies. When configuring replication, a storage policy is selected and the configured storage policy is automatically assigned to the virtual machine when it is recovered. 5
The use of local disks without vsan introduces risk to application uptime. For example, only one copy of a virtual machine s files is stored on a local disk. If that disk fails, the virtual machine files must be restored from backup media, which is time-consuming and, in some cases, unreliable. It is possible to create a second copy of virtual machine files on another disk, but the process is not automatic and must be performed frequently to minimize data loss. The recovery of a second copy would also be a manual process in further increasing risk and recovery time. vsan addresses these challenges by aggregating local disks into a shared datastore distributed across hosts in the cluster. vsan features a storage policy rule called Primary Level of Failures to Tolerate or PFTT, which defines the number of copies of a virtual machine s files to distribute across the physical nodes in the cluster. The formula for determining the minimum number of hosts required to support a PFTT rule is 2n+1. For example, five hosts are required for PFTT=2. Services such as VMware vsphere vmotion, VMware vsphere High Availability (vsphere HA), and VMware vsphere Fault Tolerance ( vsphere FT) can be utilized at the disaster recovery site to protect workloads failed over from the production site. This is especially important if an organization needs to run production workloads for an extended period of time at a disaster recovery site as these services help minimize planned and unplanned downtime. A variety of data protection solutions are available to back up and recover virtual machines and applications in a vsan cluster. Many of these solutions include the capability to replicate backup data to a disaster recovery site. Having the backup data at the production and disaster recovery sites facilitates recovery from a variety of downtime scenarios. Backup and recovery solutions can be used in the same environment as vsphere Replication. Depending on business requirements, some virtual machines could be protected from disaster by 6
vsphere Replication and others by replicating backup data to a remote site. This approach provides flexibility in recovery times and capacity consumption at the disaster recovery site. For example, Tier-1 workloads can be replicated with vsphere Replication, which offers faster recovery times than restore from backup, but consumes more capacity at the disaster recovery site. Tier-2 workloads can be backed up locally and the backup data replicated to the disaster recovery site. It will take longer to restore a virtual machine from backup data, but the backup data will likely consume less storage capacity due to various deduplication and compression features that are built into some data protection solutions. As a footnote, the capacity consumed by vsphere Replication replicas can be reduced using vsan deduplication and compression in all-flash configurations. Automation with Site Recovery Manager VMware Site Recovery Manager can be utilized with vsan and vsphere Replication to orchestrate the recovery of multiple virtual machines. Automation further reduces recovery times and minimizes risk by eliminating manual, error-prone processes. Site Recovery Manager includes the ability to precisely control the startup order of virtual machines and it automates IP address changes when virtual machines are failed over. Testing recovery plans with Site Recovery Manager is non-disruptive, which enables frequent testing. Frequent testing leads to higher levels of confidence that recovery will work as planned when needed. History reports are generated with every test and failover event providing documentation to satisfy organization and regulatory requirements. 7
1.2 vsan Stretched Clusters and Site Recovery Manager For higher levels of resiliency across three sites, consider the use of a vsan stretched cluster with Site Recovery Manager. For example, two production locations 100 kilometers apart could each house one half of a stretched cluster to protect against the failure of either location. A third location farther away hosts a second vsan cluster to supply compute, storage, and network resources for recovered virtual machines, as well as, any workloads that run on a regular basis at the disaster recovery site. 8
A vsan stretched cluster requires a witness host, which is vsphere running on a virtual machine. The witness host serves as a tie-breaker in certain situations such as loss of network connectivity between the two locations that make up a stretched cluster. The witness host cannot be located within the same site as the stretched cluster so the disaster recovery site is the natural place to host this virtual machine appliance. Other workloads running at a disaster recovery site might include test and development, virtual desktops, email, directory services, and DNS. Since stretched clusters essentially utilize synchronous replication between the two locations, an RPO of zero is achieved. That means no loss of data if one of the locations in the stretched cluster is offline. vsphere HA automates the recovery of virtual machines affected by an outage at either location in the stretched cluster. Recovery time for these virtual machines is typically measured in minutes. Replication from the stretched cluster to the disaster recovery site is facilitated by vsphere Replication. As mentioned previously, per-virtual machine RPOs for replication between two vsan datastores can be as low as five minutes. Site Recovery Manager automates the failover and fail-back processes between the stretched cluster and the disaster recovery site. 1.3 vsan Performance vsan is uniquely embedded in the vsphere hypervisor kernel. It is able to deliver the highest levels of performance without taxing the CPU or consuming high amounts of memory resources, as compared to other solutions requiring storage virtual machine appliances that run separately on top of the hypervisor. An all-flash vsan configuration will naturally provide the highest performance, which translates to lower recovery times. This video demonstration shows a 4-node all-flash vsan cluster recovering 1000 virtual machines in just under 30 minutes: Recover 1000 VMs in 26 mins with SRM & VR on vsan 1.4 Summary VMware vcenter Server, vsphere, and vsan collectively create the best platform for running and managing virtual machine workloads requiring predictable performance and rapid recovery in the 9
event of a disaster. The integration of vsan with vsphere simplifies administration through storage policy-based management. Business-critical workloads such as websites, e-commerce applications, databases, employee remote access, and communications can benefit from shared storage without the cost and complexity of dedicated storage hardware. vsphere includes availability features such as vsphere HA, vsphere Replication, and vsphere Data Protection to minimize unplanned downtime. Site Recovery Manager can automate virtual machine migration and disaster recovery through tight integration with vsphere Replication. This includes precise virtual machine startup orders, IP address changes, and the generation of history report documentation for testing, failover, and failback operations. The health and performance levels of a vsan datastore are constantly monitored to lower risk before, during, and after a disaster recovery. If more capacity is needed, it is simple to add using a scale up or scale out approach without incurring downtime. Learn More vsan Stretched Cluster with SRM Demo Video Virtual Blocks Blog Customer Stories 10