5.5
Table Of Contents
- Site Recovery Manager Administration
- Contents
- About VMware vCenter Site Recovery Manager Administration
- SRM Privileges, Roles, and Permissions
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Replicate Virtual Machines By Using Replication Seeds
- Reconfigure Replications
- Stop Replicating a Virtual Machine
- Creating Protection Groups
- Creating, Testing, and Running Recovery Plans
- Testing a Recovery Plan
- Performing a Planned Migration or Disaster Recovery By Running a Recovery Plan
- Differences Between Testing and Running a Recovery Plan
- How SRM Interacts with DPM and DRS During Recovery
- How SRM Interacts with Storage DRS or Storage vMotion
- How SRM Interacts with vSphere High Availability
- Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines
- Create, Test, and Run a Recovery Plan
- Export Recovery Plan Steps
- View and Export Recovery Plan History
- Cancel a Test or Recovery
- Delete a Recovery Plan
- Reprotecting Virtual Machines After a Recovery
- Restoring the Pre-Recovery Site Configuration By Performing Failback
- Customizing a Recovery Plan
- Recovery Plan Steps
- Specify the Recovery Priority of a Virtual Machine
- Creating Custom Recovery Steps
- Types of Custom Recovery Steps
- How SRM Handles Custom Recovery Steps
- Create Top-Level Command Steps
- Create Top-Level Message Prompt Steps
- Create Command Steps for Individual Virtual Machines
- Create Message Prompt Steps for Individual Virtual Machines
- Guidelines for Writing Command Steps
- Environment Variables for Command Steps
- Customize the Recovery of an Individual Virtual Machine
- Customizing IP Properties for Virtual Machines
- Advanced SRM Configuration
- Configure Protection for a Virtual Machine or Template
- Configure Resource Mappings for a Virtual Machine
- Specify a Nonreplicated Datastore for Swap Files
- Recovering Virtual Machines Across Multiple Hosts on the Recovery Site
- Resize Virtual Machine Disk Files During Replication Using Replication Seeds
- Resize Virtual Machine Disk Files During Replication Without Using Replication Seeds
- Reconfigure SRM Settings
- Change Local Site Settings
- Change Logging Settings
- Change Recovery Settings
- Change Remote Site Settings
- Change the Timeout for the Creation of Placeholder Virtual Machines
- Change Storage Settings
- Change Storage Provider Settings
- Change vSphere Replication Settings
- Modify Settings to Run Large SRM Environments
- Troubleshooting SRM Administration
- Limitations to Protection and Recovery of Virtual Machines
- SRM Events and Alarms
- vSphere Replication Events and Alarms
- Collecting SRM Log Files
- Access the vSphere Replication Logs
- Resolve SRM Operational Issues
- SRM Doubles the Number of Backslashes in the Command Line When Running Callouts
- Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors
- LVM.enableResignature=1 Remains Set After a SRM Test Failover
- Adding Virtual Machines to a Protection Group Fails with an Unresolved Devices Error
- Configuring Protection fails with Placeholder Creation Error
- Planned Migration Fails Because Host is in an Incorrect State
- Recovery Fails with a Timeout Error During Network Customization for Some Virtual Machines
- Recovery Fails with Unavailable Host and Datastore Error
- Reprotect Fails with a vSphere Replication Timeout Error
- Recovery Plan Times Out While Waiting for VMware Tools
- Reprotect Fails After Restarting vCenter Server
- Rescanning Datastores Fails Because Storage Devices are Not Ready
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Reconfigure Replication on Virtual Machines with No Datastore Mapping
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication RPO Violations
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Generating Support Bundles Disrupts vSphere Replication Recovery
- Recovery Plan Times Out While Waiting for VMware Tools
- Index
3 In the left pane, browse to the datastore that contains the files for the virtual machine, select the
datastore, and in the right pane, click Browse this datastore.
4 Select the folders for all virtual machines to be physically moved, right-click the selection, and click
Download.
5 Select a destination to which to copy the files and click OK.
6 Click Yes.
7 After the download finishes, transfer the files to a location on the paired site to upload them.
8 On the vSphere Client Home page at the paired site, click Datastores.
9 In the left pane, browse to the datastore to contain the files for the virtual machine, select the datastore,
and in the right pane, click Browse this datastore.
10 Select the folder to contain the copies of the virtual machines, right-click the selection, and click Upload
Folder.
11 Select the folder containing the virtual machines, and click OK.
12 On the protected site, right-click the virtual machine to replicate and select vSphere Replication.
13 Set the recovery point objective and target file location as normal and click Next.
14 Click Browse in the Target Disk File Location panel.
15 Select the target datastore, select the Specify datastore folder check box, and click Browse.
16 Select the target datastore and click Open.
17 Select the datastore folder that contains the seed files, change the file type to All Files, select the VMDK
file to use as a replication seed, and click OK.
18 Click Yes to confirm that you want to use this file as an initial copy.
19 Follow the prompts to select a vSphere Replication server and click Finish to complete the
configuration.
Reconfigure Replications
You can reconfigure the replication to enable or disable a virtual machine disk file for replication, modify
replication options, such as RPO or the quiescing method. You can also specify a different target datastore
for replica configuration and disk files and move the virtual machine to a different vSphere Replication
server.
Prerequisites
You configured vSphere Replication on one or more virtual machines.
Procedure
1 Select the vSphere Replication view of the SRM interface.
2 Select a vSphere Replication server and click the Virtual Machines tab.
3 Select a virtual machine or use the Ctrl or Shift keys to select multiple virtual machines, right-click and
select Configure Replication.
4 (Optional) Use the RPO slider or enter a value to reconfigure the maximum amount of data that can be
lost in the case of a site failure.
The available RPO range is from 15 minutes to 24 hours.
5 (Optional) Change the Guest OS Quiescing configuration, if applicable to the virtual machine guest
operating system
Site Recovery Manager Administration
26 VMware, Inc.