5.0
Table Of Contents
- Site Recovery Manager Administration Guide
- Contents
- About This Book
- Administering VMware vCenter Site Recovery Manager
- Installing and Updating Site Recovery Manager
- Configuring the SRM Database
- About the vSphere Replication Management Database
- Install the SRM Server
- Upgrading SRM
- Install Storage Replication Adapters
- Install the SRM Client Plug-In
- Connect the Sites
- Revert to a Previous Release
- Repair or Modify the Installation of a Site Recovery Manager Server
- Install the SRM License Key
- Establishing Inventory Mappings and Placeholder Datastores
- Configuring Array-Based Protection
- Installing vSphere Replication Servers
- Creating Protection Groups and Replicating Virtual Machines
- Limitations to Protection and Recovery of Virtual Machines
- Create Array-Based Protection Groups
- Create vSphere Replication Protection Groups
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines Using Physical Couriering
- Move a Virtual Machine to a New vSphere Replication Server
- Apply Inventory Mappings to All Members of a Protection Group
- Recovery Plans and Reprotection
- Customizing Site Recovery Manager
- Customizing a Recovery Plan
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Configure SRM Alarms
- Working with Advanced Settings
- Troubleshooting SRM
- Index
Before replicating multiple machines, configure datastore mappings in the SRM user interface. For more
information, see “Configure Datastore Mappings for vSphere Replication Management,” on page 44. You
configure the mappings so that information is available to SRM regarding the target datastore destinations for
replication.
Procedure
1 On the vSphere Client Home page, click VMs and Templates.
2 Select a folder or datacenter in the left pane and click the Virtual Machines tab.
A list of virtual machines appears in the right pane.
3 On the right pane, right-click the virtual machines to be replicated and click vSphere Replication
4 On the Replication Settings page, configure general replication settings.
a Use the Recovery Point Objective (RPO) slider or enter a value.
The RPO value determines the maximum amount of data that can be lost during the recovery. The
available range is from 15 minutes to 24 hours.
NOTE Every time that a virutal machine reaches its RPO target, SRM records approximately 3800
bytes of data in the vCenter Server events database. If you set a low RPO period, this can quickly
create a large volume of data in the database. To avoid creating large volumes of data in the vCenter
Server events database, you should limit the number of days that vCenter Server retains event data.
See Configure Database Retention Policy in the vCenter Server and Host Management Guide.
Alternatively, set a higher RPO value.
b Select the Guest OS Quiescing method.
c Choose whether to enable Initial copies of .vmdk files have been placed on the target datastore.
This option searches the replicated datastore. If candidate files are found, confirm whether to use the
found files as initial copies.
5 On the VRS page, accept the automatic assignment of a VRS or select a particular server.
6 Review the settings and click Finish to establish replication.
Replicate Virtual Machines Using Physical Couriering
Initial replication of .vmdk files can be made more efficient by physically couriering files on a storage device.
This may also be known as sneakernet replication. Physical couriering may be required if it's not practical to
copy the files over the network because the amount of data is large, the bandwidth available is small, or some
combination of the two.
When replicating virtual machines, it is best to ensure that virtual machines are replicated to subdirectories
within datastores. Copying disks are expected to work, as long as the method preserves the identity information
stored inside the .vmdk file.
Prerequisites
To replicate a virtual machine using vSphere Replication (VR), you must establish the VR infrastructure at both
sites. A minimal VR infrastructure requires one vSphere Replication Management Servers (VRMS) at both sites
and at least one VR server on the recovery site. SRM servers at each site must be paired, and VRMS must be
paired as well. If a virtual machine is powered off, replication begins when the virtual machine is powered on.
Procedure
1 Use the vSphere Client to connect to a vCenter Server that can manage the virtual machines to be physically
couriered.
Site Recovery Manager Administration Guide
64 VMware, Inc.