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
n
You can run a cluster of MSCS virtual machines in the following possible configurations.
Cluster-in-a-box
The MSCS virtual machines in the cluster run on a single ESXi Server.
You can have a maximum of five MSCS nodes on one ESXi Server.
Cluster-across-boxes
You can spread the MSCS cluster across a maximum of five ESXi Server
instances. You can protect only one virtual machine node of any MSCS
cluster on a single ESXi Server instance. You can have multiple MSCS
node virtual machines running on an ESXi host, as long as they do not
participate in the same MSCS cluster. This configuration requires shared
storage on a Fibre Channel SAN for the quorum disk.
DRS Requirements for Protection of MSCS Virtual Machines
To use DRS on sites that contain MSCS virtual machines, you must configure the DRS rules to allow SRM to
protect the virtual machines. By following the guidelines, you can protect MSCS virtual machines on sites
that run DRS if the placeholder virtual machines are in either a cluster-across-boxes MSCS deployment or in
a cluster-in-a-box MSCS deployment.
n
Because vSphere does not support vSphere vMotion for MSCS virtual machines, you must set the VM to
Host DRS rule so that DRS does not perform vMotion on MSCS nodes. Set the VM to Host rule for the
virtual machines on the protected site and for the shadow virtual machines on the recovery site.
n
Set the DRS rules on the virtual machines on the protected site before you configure MSCS in the guest
operating systems. Set the DRS rules immediately after you deploy, configure, or power on the virtual
machines.
n
Set the DRS rules on the virtual machines on the recovery site immediately after you create a protection
group of MSCS nodes, as soon as the placeholder virtual machines appear on the recovery site.
n
DRS rules that you set on the protected site are not transferred to the recovery site after a recovery. For
this reason, you must set the DRS rules on the placeholder virtual machines on the recovery site.
n
Do not run a test recovery or a real recovery before you set the DRS rules on the recovery site.
If you do not follow the guidelines on either the protected site or on the recovery site, vSphere vMotion
might move MSCS virtual machines to a configuration that SRM does not support.
n
In a cluster-in-a-box deployment on either the protected or recovery site, vSphere vMotion might move
MSCS virtual machines to different ESXi hosts.
n
In a cluster-in-a-box deployment on either the protected or recovery site, vSphere vMotion might move
some or all of the MSCS virtual machines to a single ESXi host.
Create, Test, and Run a Recovery Plan
You perform several sets of tasks to create, test, and run a recovery plan.
Procedure
1 Create a Recovery Plan on page 43
You create a recovery plan to establish how SRM recovers virtual machines.
2 Edit a Recovery Plan on page 43
You can edit a recovery plan to change the properties that you specified when you created it. You can
edit recovery plans from the protected site or from the recovery site.
3 Suspend Virtual Machines When a Recovery Plan Runs on page 44
SRM can suspend virtual machines on the recovery site during a recovery and a test recovery.
Site Recovery Manager Administration
42 VMware, Inc.