When recovering items in a consistency group, all items are restored to the same point in time. Recovery site: Site where protected virtual machines are recovered in the event of a failover. NOTE: It is possible for the same site to serve as a protected site and recovery site when replication is occurring in both directions and Site Recovery Manager is protecting virtual machines at both sites.
Datastore group: One or more datastores that are treated as a unit in Site Recovery Manager. A common example is a consistency group in an array replication solution. Site Recovery Manager 8. The Site Recovery Manager 8. It supports multiple versions of vCenter at either site. There must be one or more vSphere hosts running version 6.
Site Recovery Manager utilizes either vSphere Replication, array-based replication, Virtual Volume vVols replication, or stretched storage for transferring data between sites. Array-based replication and stretched storage must be licensed and configured and the appropriate storage replication adaptor must be installed on the Site Recovery Manager server at each site. Virtual Volume vVols replication must be licensed and configured as well, however, there is no requirement for a storage replication adaptor when using Virtual Volumes vVols.
For vSphere Replication, the vSphere Replication virtual appliance must be deployed and the virtual machines to be protected by Site Recovery Manager must be configured for replication. These must be in place at both the protected and recovery sites. Site Recovery Manager supports protection for up to 5, virtual machines and is able to simultaneously run up to 10 recovery plans containing up to 2, virtual machines.
Up to virtual machines can be included in a single protection group and Site Recovery Manager provides support for up to protection groups. Though the most obvious use case for Site Recovery Manager is disaster recovery from one site to another it can handle a number of different use cases.
Though the most obvious use case for Site Recovery Manager is disaster recovery from one site to another it can handle a number of different use cases and provide significant capability and flexibility to customers.
For all use cases and situations Site Recovery Manager supports non-disruptive testing of recovery plans in network and storage isolated environments. This provides for the ability to test disaster recovery, disaster avoidance, or planned migrations as frequently as desired to ensure confidence in the configuration and operation of recovery plans.
Disaster recovery or an unplanned failover is what Site Recovery Manager was specifically designed to accomplish. This is the most critical but least frequently used use case for Site Recovery Manager. Site Recovery Manager can help in this situation by automating and orchestrating the recovery of critical business systems for partial or full site failures ensuring the fastest RTO.
Preventive failover is another common use case for Site Recovery Manager. This can be anything from an oncoming storm to the threat of power issues. When utilized with a supported stretched storage solution, Site Recovery Manager can orchestrate the cross-vCenter vMotion of virtual machines allowing for zero-downtime disaster avoidance.
Without stretched storage, Site Recovery Manager allows for the graceful shutdown of virtual machines at the protected site, full replication of data, and ordered startup of virtual machines and applications at the recovery site ensuring app-consistency and zero data loss. The most common way Site Recovery Manager is used on a regular basis is for movement of virtual machines and applications between sites. This can be for datacenter relocation, global load balancing or planned site maintenance.
Site Recovery Manager has all the capabilities to ensure a smooth site migration. It supports full testing of the migration in a manner completely non-disruptive to production systems. It also supports using stretched storage for zero-downtime migrations. Additionally, in planned migration mode it will pause if any issues are discovered during the migration, providing an opportunity to correct them.
The Site Recovery Manager test environment provides a perfect location for conducting operating system and application upgrade and patch testing.
Test environments are complete copies of production environments configured in an isolated network segment which ensures that testing is as realistic as possible while at the same time not impacting production workloads or replication. Site Recovery Manager can be used in a number of different failover scenarios depending on customer requirements, constraints and objectives. All of these arrangements are supported and easily configured.
Additionally, Site Recovery Manager's integration with the vSphere Client makes multiple site topologies easy to manage. In the traditional active-passive scenario there is a production site running applications and services and a secondary or recovery site that is idle until needed for recovery. Site Recovery Manager can be used in a configuration where low-priority workloads such as test and development run at the recovery site and are powered off as part of the recovery plan.
This allows for the utilization of recovery site resources as well as sufficient capacity for critical systems in case of a disaster. In situations where production applications are operating at both sites Site Recovery Manager supports protecting virtual machines in both directions eg.
Site Recovery Manager supports using stretched storage, thereby combining the benefits of Site Recovery Manager with the advantages of stretched storage. As well as all of the pre-existing benefits of Site Recovery Manager, most of which are not available when using stretched storage by itself. VMware NSX is an excellent solution to this and provides a host of additional benefits as well. While Site Recovery Manager is designed for the most common protection use case, one site protected by another, it is also capable of supporting additional configurations.
These can be:. Any of these and other multi-site topologies are supported provided these limits are taken into account:. More details about Site Recovery Manager topologies and configurations are available in the documentation center.
The process of deploying and configuring Site Recovery Manager is simple and logical. This document will cover these steps at a high level. For detailed installation and configuration instructions please see the Site Recovery Manager Installation and Administration Guides.
Site pairing is the first step in configuring Site Recovery Manager. The most common configuration is pairing two sites, though as was outlined in the previous section on topologies, other arrangements are supported. There are multiple types of inventory mappings in Site Recovery Manager: Resource mappings, folder mappings, and network mappings. These mappings provide default settings for recovered virtual machines. Networks to be used during testing can also be configured in the same area.
For each protected virtual machine Site Recovery Manager creates a placeholder virtual machine at the recovery site. Placeholder virtual machines are contained in a datastore and registered with the vCenter Server at the recovery site.
Since placeholder virtual machines do not have virtual disks they consume a minimal amount of storage 1. The protected and recovery sites will each require that a small datastore that is accessible by all hosts at that site be created or allocated for use as the placeholder datastore. Each site requires at least one placeholder datastore to allow for failover as well as failback. Site Recovery Manager will automatically select the placeholder datastore if it isn't chosen by the administrator.
When utilizing Storage Policy-Based Protection Groups, placeholder datastores are not required and placeholder VMs are not created as they are not needed for this new type of protection group. As mentioned previously, Site Recovery Manager offers a choice of replication technologies. Virtual machines can be replicated with vSphere Replication, array-based replication, or Virtual Volumes replication and the same virtual machine cannot be protected by more than one replication type.
The virtual machine must be configured for replication before or as part of being protected by Site Recovery Manager. When using array-based replication, one or more storage arrays at the protected site replicate data to peer array s at the recovery site. A storage replication adaptor SRA is required for the specific array and replication solution to be used with Site Recovery Manager. Storage replication adaptors are software components that are created and supported by the array replication vendors using guidelines from VMware.
The storage replication adaptor is what Site Recovery Manager uses for communicating with the storage array. They are therefore installed on the Site Recovery Manager servers at both sites and are able to monitor and control array functions related to migrations, failovers, re-protections, failbacks, and tests. Replication Groups bringing more efficient, accurate, and responsive recovery of your virtual machines. A Replication Group is a group of replicated storage devices to provide atomic failover for an application.
In other words, a Replication Group is the minimum unit of failover. Replication Groups also define the set of vVols that are maintained in write-order fidelity where writes are replicated on the destination site in the exact same order they're generated at the source site to ensure at any time the destination site represents at least a crash-consistent version of the data on the source site. To use vSphere replication requires deployment and configuration of the vSphere Replication appliance.
This is done independently of Site Recovery Manager. For details about installing and configuring vSphere Replication see the vSphere Replication documentation. Protection groups are a way of grouping virtual machines that will be recovered together.
In many cases, a protection group will consist of the virtual machines that support a service or application such as email or an accounting system. For example, an application might consist of a two-server database cluster, three application servers, and four web servers.
In most cases, it would not be beneficial to failover part of this application, only two or three of the virtual machines in the example, so all nine virtual machines would be included in a single protection group.
Creating a protection group for each application or service has the benefit of selective testing. Having a protection group for each application enables non-disruptive, low-risk testing of individual applications allowing application owners to non-disruptively test disaster recovery plans as needed. A protection group contains virtual machines whose data has been replicated by array-based replication, Virtual Volumes or vSphere replication. Before a protection group can be created, replication must be configured.
A protection group cannot contain virtual machines replicated by more than one replication solution e. The virtual machines included in array-based replication protection groups are determined by the storage where the virtual machines are located.
If you choose Inline IP Pool , complete the fields. Click Submit. Click Submit on the Network Policy Information screen. You can view the collected inventory for SRM resource mappings, protection groups, and recovery plans. On the Compute page, choose the cloud. By default, the Unassigned Replicated VMs page appears. SRM protection groups let you group VMs to fail over from the protected site to the recovery site together as part of your recovery plan.
You can enable protection groups when creating a new SRM storage policy, or when editing an existing SRM storage policy. The available datastores that you can map to your SRM storage policy is filtered based on the selected protection group.
The recovery site VMs are provisioned on the selected protection group datastore. In the Protection Group field, click Select. Check the protection groups that you want to add to the storage policy, and click Select. On the System Disk Policy screen, if necessary, complete the required fields, and click Next. On the Additional Disk Policies screen, if necessary, configure a disk policy, and click Next. On the Hard Disk Policy screen, if necessary, specify the number of physical disks that you want to create during VM provisioning.
On the Add VDC screen, complete the fields, including:. If checked, all the policies for this account compute, storage and network that have SRM enabled are displayed here. In the User Action Policy drop-down list, choose the policy that is used for execution of orchestration workflow post-provisioning of the VMs.
In the Delete after Inactive VM days drop-down list, choose the number of days to wait before deleting an inactive VM. For more information, see Enabling Advanced Controls.
Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 2. Updated: November 12, Array-based replication ABR Replication of virtual machines that is managed and executed by the storage subsystem itself, rather than from inside the virtual machines, the vmkernel or the Service Console.
Failback Reversal of direction of replication, and automatic reprotection of protection groups. Failover Event that occurs when the recovery site takes over operation in place of the protected site after the declaration of a disaster.
Protection group A group of virtual machines that will be failed over together to the recovery site during testing or recovery. Protected site The primary site that contains the virtual machines to be protected. Recovery site The secondary site to which virtual machines will fail over.
Figure 1. Protection groups for the protected site have been created. Step 3 Click Add. Step 5 In the Cloud Name field, enter the name for the cloud. Note Either a datacenter within the credential policy or the VMware datacenter and VMware cluster can be selected. Step 8 Choose the converged infrastructure pod from the Pod drop-down list.
Step 9 Click Add. Step 4 On the Add Computing Policy screen, complete the fields, including the following: In the Policy Name field, enter the name of the policy. This name is used during catalog definition. Note You can narrow the scope of deployment by specifying whether to use all, include chosen, or exclude chosen options. Step 5 Click Submit. Step 4 On the Network Policy Information screen, complete the fields.
Note This option is not visible if the Copy Adapter from Template option is chosen. Step 8 Click Select to choose the port group name. Note All the port groups mapped in the protection site to the corresponding recovery site are displayed here.
Step 10 Click Submit. This is the first book on the market that provides an extensive disaster recovery solution using the latest vSphere Replication and vCenter Site Recovery Manager Master the skills of protecting your virtual machines by replicating and recovering them in seconds This practical, step-by-step guide will help you protect all your applications with Site Recovery Manager and Replication.
VMware vCenter Site Recovery manage is an orchestration tool used to automate disaster recovery in a manner that no other solution does. The book begins by talking about the architecture of SRM and guides you through the procedures involved in installing and configuring SRM to leverage array-based replication.
You will then learn how to protect your virtual machines by creating Protection Groups and validate their. All rights reserved.
How can I use SRM in my environment? This product is protected by U. VMware products are covered by one or more patents listed at. It is programmed to leverage array-based replication and VMwares proprietary vSphere Replication engine.
This book will familiarize you with the concepts of disaster recovery using vCenter Site Recovery Manager and vSphere Replication. You will learn how to deploy and confi gure vSphere Replication in the standalone mode to replicate virtual machines.
0コメント