Site Recovery Manager Administration Site Recovery Manager 6.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
Site Recovery Manager Administration You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2008–2015 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents About VMware Site Recovery Manager Administration 7 Updated Information 9 1 Site Recovery Manager Privileges, Roles, and Permissions 11 How Site Recovery Manager Handles Permissions 12 Site Recovery Manager and the vCenter Server Administrator Role 13 Site Recovery Manager and vSphere Replication Roles 13 Managing Permissions in a Shared Recovery Site Configuration 14 Assign Site Recovery Manager Roles and Permissions 15 Site Recovery Manager Roles Reference 17 2 Replicating Virtual Machines 23
Site Recovery Manager Administration Storage Policy Protection Groups and Nonprotected Virtual Machines 52 Create Protection Groups 53 Organize Protection Groups in Folders 55 Add or Remove Datastore Groups or Virtual Machines to or from a Protection Group 56 Apply Inventory Mappings to All Members of a Protection Group 57 Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group 58 Modifying the Settings of a Protected Virtual Machine 59 Remove Protection from a Virtual Machin
Contents 8 Customizing IP Properties for Virtual Machines 93 Manually Customize IP Properties For an Individual Virtual Machine 94 Customizing IP Properties for Multiple Virtual Machines 95 Customizing IP Properties for Multiple Virtual Machines By Using the DR IP Customizer Tool 95 Customize IP Properties for Multiple Virtual Machines by Defining IP Customization Rules 109 9 Reprotecting Virtual Machines After a Recovery 111 How Site Recovery Manager Reprotects Virtual Machines with Array Based Replica
Site Recovery Manager Administration Change Replication Settings 141 Change SSO Setting 142 Change Storage Settings 142 Change ABR Storage Policy Setting 143 Change Storage Provider Settings 144 Change vSphere Replication Settings 146 Modify Settings to Run Large Site Recovery Manager Environments Settings for Large Site Recovery Manager Environments 148 13 Site Recovery Manager Events and Alarms 151 How Site Recovery Manager Monitors Connections Between Sites Configure Site Recovery Manager Alarms 152
About VMware Site Recovery Manager Administration VMware Site Recovery Manager is an extension to VMware vCenter Server that delivers a business continuity and disaster recovery solution that helps you plan, test, and run the recovery of vCenter Server virtual machines. Site Recovery Manager can discover and manage replicated datastores, and automate migration of inventory from one vCenter Server instance to another.
Site Recovery Manager Administration 8 VMware, Inc.
Updated Information Site Recovery Manager Administration is updated with each release of the product or when necessary. This table provides the update history of Site Recovery Manager Administration. Revision Description EN-001772-01 n n n n n n n n n n EN-001772-00 VMware, Inc. Revised and expanded the information in “Inventory Mappings for Storage Policy Protection Groups,” on page 34.
Site Recovery Manager Administration 10 VMware, Inc.
Site Recovery Manager Privileges, Roles, and Permissions 1 Site Recovery Manager provides disaster recovery by performing operations for users. These operations involve managing objects, such as recovery plans or protection groups, and performing operations, such as replicating or powering off virtual machines. Site Recovery Manager uses roles and permissions so that only users with the correct roles and permissions can perform operations.
Site Recovery Manager Administration n Managing Permissions in a Shared Recovery Site Configuration on page 14 You can configure permissions on Site Recovery Manager to use a shared recovery site. The vCenter Server administrator on the shared recovery site must manage permissions so that each user has sufficient privileges to configure and use Site Recovery Manager, but no user has access to resources that belong to another user.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions Site Recovery Manager and the vCenter Server Administrator Role If a user or user group has the vCenter Server administrator role on a vCenter Server instance when you install Site Recovery Manager, that user or user group obtains all Site Recovery Manager privileges.
Site Recovery Manager Administration Managing Permissions in a Shared Recovery Site Configuration You can configure permissions on Site Recovery Manager to use a shared recovery site. The vCenter Server administrator on the shared recovery site must manage permissions so that each user has sufficient privileges to configure and use Site Recovery Manager, but no user has access to resources that belong to another user.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions n n Place all of the user's placeholder virtual machines in this folder, so that they can inherit its permissions. n Do not assign permissions to access this folder to other users. Assign dedicated resource pools, datastores, and networks to each user, and configure the permissions in the same way as for folders. CAUTION A deployment in which you isolate user resources still assumes trust between the vSphere sites.
Site Recovery Manager Administration Option Description Assign permissions to a protection group folder Click Site Recovery, expand Inventory Trees, click Protection Groups and select a protection group folder. You can assign permissions to the root folder or to a subfolder. Assign permissions to an individual recovery plan Click Site Recovery, expand Inventories, click Recovery Plans, and select a recovery plan.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions 5 Select Propagate to Children to apply the selected role to all of the child objects of the inventory objects that this role can affect. For example, if a role contains privileges to modify folders, selecting this option extends the privileges to all the virtual machines in a folder. You might deselect this option to create a more complex hierarchy of permissions.
Site Recovery Manager Administration Table 1‑1. Site Recovery Manager Roles Role Site Recovery Manager Administrator Site Recovery Manager Protection Groups Administrator 18 Actions that this Role Permits Privileges that this Role Includes The Site Recovery Manager Administrator grants permission to perform all Site Recovery Manager configuration and administration operations. n Configure advanced settings. n Configure connections. n Configure inventory preferences.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions Table 1‑1. Site Recovery Manager Roles (Continued) Role Site Recovery Manager Recovery Administrator VMware, Inc. Actions that this Role Permits Privileges that this Role Includes Objects in vCenter Server Inventory that this Role Can Access n Create protection groups. n Modify protection groups. n Add virtual machines to protection groups. n Delete protection groups. n Configure protection on virtual machines.
Site Recovery Manager Administration Table 1‑1. Site Recovery Manager Roles (Continued) Role Site Recovery Manager Recovery Plans Administrator Site Recovery Manager Test Administrator 20 Actions that this Role Permits Privileges that this Role Includes The Site Recovery Manager Recovery Plans Administrator role allows users to create and test recovery plans. n Add protection groups to recovery plans. n Remove protection groups from recovery plans.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions Table 1‑1. Site Recovery Manager Roles (Continued) Role Actions that this Role Permits Privileges that this Role Includes Objects in vCenter Server Inventory that this Role Can Access protection groups or recovery plans, or perform recoveries or reprotect operations. VMware, Inc.
Site Recovery Manager Administration 22 VMware, Inc.
Replicating Virtual Machines 2 Before you create protection groups, you must configure replication on the virtual machines to protect. You can replicate virtual machines by using either array-based replication, vSphere Replication, or a combination of both.
Site Recovery Manager Administration Figure 2‑1.
Chapter 2 Replicating Virtual Machines n Download the SRA by going to https://my.vmware.com/web/vmware/downloads, selecting VMware vCenter Site Recovery Manager > Download Product, then selecting Drivers & Tools > Storage Replication Adapters > Go to Downloads. n If you obtain an SRA from a different vendor site, verify that it has been certified for the Site Recovery Manager release you are using by checking the VMware Compatibility Guide for Site Recovery Manager at http://www.vmware.
Site Recovery Manager Administration 4 Select a site or pair of sites for the array manager and click Next. 5 Select the array manager type that you want Site Recovery Manager to use from the SRA Type table and click Next. If no manager type appears, rescan for SRAs or check that you have installed an SRA on the Site Recovery Manager Server host. 6 Enter a name for the array in the Display Name text box and click Next..
Chapter 2 Replicating Virtual Machines Edit Array Managers Use the Edit Array Manager wizard to modify an array manager's name or other settings, such as the IP address or user name and password. For more information about how to fill in the adapter fields, see the documentation that your SRA vendor provides. While fields vary among SRAs, common fields include IP address, protocol information, mapping between array names and IP addresses, and user names and passwords.
Site Recovery Manager Administration Isolating Devices For Stretched Storage During Disaster Recovery In a disaster recovery with stretched storage, the failover command must isolate devices at the recovery site. If some hosts at the protected site are still operational and continue running virtual machines when you initiate a disaster recovery, Site Recovery Manager cannot power on the corresponding virtual machines at the recovery site due to file locks.
Chapter 2 Replicating Virtual Machines Figure 2‑2.
Site Recovery Manager Administration Figure 2‑3. Recovering a Virtual Machine at Points in Time (PIT) Source Site Target Site vSphere Web Client vSphere Web Client Replication VR Appliance VM VR Appliance t0 t1 t2 t3 VM VM VM VM Using Array-Based Replication and vSphere Replication with Site Recovery Manager You can use a combination of array-based replication and vSphere Replication in your Site Recovery Manager deployment.
Chapter 2 Replicating Virtual Machines Figure 2‑4. Site Recovery Manager Architecture with Array-Based Replication and vSphere Replication Protected Site Recovery Site vSphere Web Client vSphere Web Client SRM plug-in SRM plug-in SRA SRA SRM Server vCenter Server vCenter Server SRM Server VR Appliance VR Appliance Additional VR Server ESXi Server ESXi Server ESXi Server VR Agent VR Agent VR Agent Storage VMFS VMware, Inc.
Site Recovery Manager Administration 32 VMware, Inc.
Configuring Mappings 3 Mappings allow you to specify how Site Recovery Manager maps virtual machine resources on the protected site to resources on the recovery site. You can configure site-wide mappings to map objects in the vCenter Server inventory on the protected site to corresponding objects in the vCenter Server inventory on the recovery site.
Site Recovery Manager Administration Inventory Mappings for Array-Based Replication Protection Groups and vSphere Replication Protection Groups For array-based protection and vSphere Replication protection, Site Recovery Manager applies inventory mappings to all virtual machines in a protection group when you create that group. Site Recovery Manager creates a placeholder virtual machine when you create an array-based or vSphere Replication protection group.
Chapter 3 Configuring Mappings Because Site Recovery Manager applies inventory mappings for storage policy protection groups when you run a recovery plan, you cannot configure individual mappings on virtual machines in storage policy protection groups. Site Recovery Manager always uses the site-wide inventory mappings when you run a recovery with storage policy protection.
Site Recovery Manager Administration If a recovery plan that contains a storage policy protection group fails due to missing mappings and the protected site is unavailable, you cannot configure the missing mappings normally. To allow the recovery to succeed, you must complete the temporary placeholder mappings that Site Recovery Manager creates when a recovery plan fails due to missing mappings. Prerequisites n The protected site is unavailable.
Chapter 3 Configuring Mappings Users Gain Access to Virtual Machines After Configuring Temporary Placeholder Mappings Users who complete temporary placeholder mappings when the protected site is unavailable might gain access to virtual machines that they should not. Problem The protected site is unavailable during a disaster recovery and Site Recovery Manager creates temporary placeholder mappings. The user who runs the recovery plan completes the temporary placeholder mappings and reruns the plan.
Site Recovery Manager Administration 2 On the Manage tab, select the type of resource to configure. Option Action Network Mappings Map networks on the protected site to networks on the recovery site. Folder Mappings Map datacenters or virtual machine folders on the protected site to datacenters or virtual machine folders on the recovery site.
Chapter 3 Configuring Mappings 8 (Optional) If you are configuring network mappings, in the Select test networks page, click the network in the Test Network column and use the drop-down menu to select the network to use when you test recovery plans. You can configure Site Recovery Manager to create an isolated network on the recovery site for when you test a recovery plan.
Site Recovery Manager Administration 4 5 Select whether to create the mapping automatically or manually and click Next. Option Description Automatically Site Recovery Manager automatically maps storage policies on the protected site to storage policies on the recovery site that have the same name. Manually To map specific storage policies on the protected site to specific storage policies on the recovery site.
About Placeholder Virtual Machines 4 When you create an array-based replication protection group that contains datastore groups or a vSphere Replication protection group that contains individual virtual machines, Site Recovery Manager creates a placeholder virtual machine at the recovery site for each of the virtual machines in the protection group. A placeholder virtual machine is a subset of virtual machine files.
Site Recovery Manager Administration About Placeholder Datastores If you use array-based replication to protect datastore groups, or if you use vSphere Replication to protect individual virtual machines, you must identify a datastore on the recovery site in which Site Recovery Manager can store the placeholder virtual machine files. NOTE Site Recovery Manager does not create placeholder virtual machines for storage policy protection groups.
Chapter 4 About Placeholder Virtual Machines 4 5 When you run a recovery plan, Site Recovery Manager shuts down the virtual machines on the protected site, and activates the virtual machines on the recovery site according to the type of replication that you use. n For datastore-based replication, Site Recovery Manager surfaces the raw storage on the recovery site that contains the replicated virtual machines as a vCenter Server datastore.
Site Recovery Manager Administration 44 5 Select the other site in the pair. 6 Repeat Step 2 to Step 4 to configure a placeholder datastore on the other site. VMware, Inc.
Creating and Managing Protection Groups 5 After you configure a replication solution, you can create protection groups. A protection group is a collection of virtual machines that Site Recovery Manager protects together. You can include one or more protection groups in a recovery plan. A recovery plan specifies how Site Recovery Manager recovers the virtual machines in the protection groups that it contains.
Site Recovery Manager Administration n “Add or Remove Datastore Groups or Virtual Machines to or from a Protection Group,” on page 56 n “Apply Inventory Mappings to All Members of a Protection Group,” on page 57 n “Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group,” on page 58 n “Modifying the Settings of a Protected Virtual Machine,” on page 59 n “Remove Protection from a Virtual Machine,” on page 60 n “Protection Group Status Reference,” on page 61 n “Virtu
Chapter 5 Creating and Managing Protection Groups A datastore provides storage for virtual machine files. By hiding the details of physical storage devices, datastores simplify the allocation of storage capacity and provide a uniform model for meeting the storage needs of virtual machines. Because any datastore can span multiple devices, Site Recovery Manager must ensure that all devices backing the datastore are replicated before it can protect the virtual machines that use that datastore.
Site Recovery Manager Administration You select a target location on a datastore on the remote site when you configure vSphere Replication on a virtual machine. When you include a virtual machine with vSphere Replication in a protection group, Site Recovery Manager creates a placeholder virtual machine for recovery.
Chapter 5 Creating and Managing Protection Groups n Associates the storage policies that you select with the storage policy protection group. Site Recovery Manager protects all compliant storage policies that you include in the storage policy protection group. n The local storage policy protection group actively protects the appropriate vSphere entities on the local vCenter Server instance and determines the compliance of the storage policies that it contains.
Site Recovery Manager Administration For information about how to create storage policies, see Virtual Machine Storage Policies in the VMware vSphere ESXi and vCenter Server 6.0 Documentation. For information about how to create inventory mappings, see “Configure Inventory Mappings,” on page 37. For information about temporary placeholder mappings, see “Inventory Mappings for Storage Policy Protection Groups,” on page 34.
Chapter 5 Creating and Managing Protection Groups Changing Array States Between Recovery and Reprotect After running a recovery plan but before running reprotect, if you change the state of an array device, for example to fix issues with reversal of replication, and you initiate a rescan of the storage devices, Site Recovery Manager can stop unexpectedly. If this occurs, you must recreate the corresponding protection groups and recovery plans.
Site Recovery Manager Administration Storage Policy Protection Groups and Periodic Polling Storage policy protection groups attempt to protect virtual machines associated with storage policies only during policy association when Site Recovery Manager Server starts. Site Recovery Manager does not attempt to periodically protect virtual machines that are already associated with a storage policy.
Chapter 5 Creating and Managing Protection Groups Nonprotected virtual machines can appear in storage policy protection groups for reasons other than the non-association of virtual machines with the correct storage policy. For descriptions of other circumstances in which nonprotected virtual machines can appear in storage policy protection groups, see “Limitations of Storage Policy Protection Groups,” on page 50.
Site Recovery Manager Administration When you create protection groups, wait to ensure that the operations finish as expected. Make sure that Site Recovery Manager creates the protection group and that the protection of the virtual machines in the group is successful.
Chapter 5 Creating and Managing Protection Groups n For array-based replication and vSphere Replication protection groups, if you did not configure inventory mappings, or if Site Recovery Manager was unable to apply them, the protection status of the protection group is Not Configured. n For storage policy protection groups, if Site Recovery Manager could not protect all of the virtual machines associated with the storage policy, the protection status of the protection group is Not Configured.
Site Recovery Manager Administration Add or Remove Datastore Groups or Virtual Machines to or from a Protection Group You can add or remove datastore groups in an array-based replication protection group, or add or remove virtual machines in a vSphere Replication protection group. You can also change the name and description of an array-based or vSphere Replication protection group. NOTE You cannot edit storage policy protection groups after their initial creation.
Chapter 5 Creating and Managing Protection Groups What to do next If the status of the protection group is Not Configured and the status for the new virtual machines is Mapping Missing, apply inventory mappings to the virtual machines: n To apply site-wide inventory mappings, or to check that inventory mappings that you have already set are valid, see Select Inventory Mappings in Site Recovery Manager Installation and Configuration.
Site Recovery Manager Administration 4 Click Yes to confirm that you want to apply inventory mappings to all unconfigured virtual machines. n If Site Recovery Manager successfully applied inventory mappings to the virtual machines, the status of the protection group is OK. n If Site Recovery Manager was unable to apply some or all of the inventory mappings, the status of the virtual machines is Not Configured or Mapping Missing.
Chapter 5 Creating and Managing Protection Groups 6 (Optional) To apply these mappings to all protected virtual machines on the site, select the Save as Inventory Mapping check box for each resource. If you do not select the check box, the mapping is only applied to this virtual machine. 7 Click OK. n If Site Recovery Manager successfully applied inventory mappings to the virtual machine, the status of the virtual machine is OK.
Site Recovery Manager Administration Remove Protection from a Virtual Machine You can temporarily remove protection from a replicated virtual machine in an array-based replication or vSphere Replication protection group without removing it from its protection group. NOTE You cannot temporarily remove protection from virtual machines in storage policy protection groups. Removing protection deletes the placeholder virtual machine on the recovery site.
Chapter 5 Creating and Managing Protection Groups 3 Right-click a virtual machine and select Remove Protection. 4 Click Yes to confirm the removal of protection from the virtual machine. Protection Group Status Reference You can monitor the status of a protection group and determine the operation that is allowed in each state. Table 5‑1. Protection Group States State Description Loading Appears briefly while the interface is loading until the protection group status appears. OK Group is idle.
Site Recovery Manager Administration Virtual Machine Protection Status Reference You can monitor the status of a virtual machine in a protection group and determine the operation that is allowed in each state. Table 5‑2. Virtual Machine Protection States 62 State Description Placeholder VM Not Found You deleted the placeholder virtual machine. The Restore Placeholder icon is enabled.
Chapter 5 Creating and Managing Protection Groups Table 5‑2. Virtual Machine Protection States (Continued) State Description Replication Error vSphere Replication reports an error about the virtual machine. Replication Warning vSphere Replication reports a warning about the virtual machine. VMware, Inc.
Site Recovery Manager Administration 64 VMware, Inc.
Creating, Testing, and Running Site Recovery Manager Recovery Plans 6 After you configure Site Recovery Manager at the protected and recovery sites, you can create, test, and run a recovery plan. A recovery plan is like an automated run book. It controls every step of the recovery process, including the order in which Site Recovery Manager powers on and powers off virtual machines, the network addresses that recovered virtual machines use, and so on. Recovery plans are flexible and customizable.
Site Recovery Manager Administration n Export Recovery Plan Steps on page 76 You can export the steps of a recovery plan in various formats for future reference, or to keep a hard copy backup of your plans. n View and Export a Recovery Plan History on page 77 You can view and export reports about each run of a recovery plan, test of a recovery plan, or test cleanup. n Delete a Recovery Plan on page 77 You can delete a recovery plan if you do not need it.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans Test Networks and Datacenter Networks When you test a recovery plan, Site Recovery Manager can create a test network that it uses to connect recovered virtual machines. Creating a test network allows the test to run without potentially disrupting virtual machines in the production environment.
Site Recovery Manager Administration Site Recovery Manager uses VMware Tools heartbeat to discover when a virtual machine is running on the recovery site. In this way, Site Recovery Manager can ensure that all virtual machines are running on the recovery site. For this reason, VMware recommends that you install VMware Tools on protected virtual machines.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans After the forced recovery completes and you have verified the mirroring of the storage arrays, you can resolve the issue that necessitated the forced recovery. After you resolve the underlying issue, run planned migration on the recovery plan again, resolve any problems that occur, and rerun the plan until it finishes successfully.
Site Recovery Manager Administration Performing Test Recovery of Virtual Machines Across Multiple Hosts on the Recovery Site You can create recovery plans that recover virtual machines across multiple recovery site hosts in a quarantined test network. With Site Recovery Manager, the vSwitches can be DVS based and span hosts. If you accept the default test network configured as Auto, then virtual machines that are recovered across hosts are placed in their own test network during recovery plan tests.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans 7 Recover a Point-in-Time Snapshot of a Virtual Machine on page 75 With vSphere Replication, you can retain point-in-time snapshots of a virtual machine. You can configure Site Recovery Manager to recover a number of point-in-time (PIT) snapshots of a virtual machine when you run a recovery plan.
Site Recovery Manager Administration 5 6 Add new or existing recovery plans to the folder. Option Description Create a new recovery plan Right-click the folder and select Create Recovery Plan. Add an existing recovery plan Drag and drop recovery plans from the inventory tree into the folder. (Optional) To rename or delete a folder, right-click the folder and select Rename Folder or Delete Folder. You can only delete a folder if it is empty.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans 2 Right-click the plan and select Test. You can also run a test by clicking the Test recovery plan icon in the Recovery Steps view in the Monitor tab. 3 (Optional) Select Replicate recent changes to recovery site. Selecting this option ensures that the recovery site has the latest copy of protected virtual machines, but means that the synchronization might take more time. 4 Click Next.
Site Recovery Manager Administration Run a Recovery Plan When you run a recovery plan, Site Recovery Manager migrates all virtual machines in the recovery plan to the recovery site. Site Recovery Manager attempts to shut down the corresponding virtual machines on the protected site. CAUTION A recovery plan makes significant alterations in the configurations of the protected and recovery sites and it stops replication. Do not run any recovery plan that you have not tested.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans 7 Review the recovery information and click Finish. When you run planned migration of a recovery plan that contains a storage policy protection group, Site Recovery Manager checks that the protection groups are synchronized on both of the protected and recovery sites before it runs the recovery plan. This check happens when you click Finish. If the protection group is synchronized on both sites, the planned migration begins.
Site Recovery Manager Administration 7 Select one of the PIT snapshots of this virtual machine and click Go to. The recovered virtual machine reverts to the PIT snapshot that you selected. 8 (Optional) If you have configured the virtual machine for IP customization, and if you select an older PIT snapshot than the most recent one, manually configure the IP settings on the recovered virtual machine.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans View and Export a Recovery Plan History You can view and export reports about each run of a recovery plan, test of a recovery plan, or test cleanup. Recovery plan histories provide information about each run, test, or cleanup of a recovery plan. The history contains information about the result and the start and end times for the whole plan and for each step in the plan.
Site Recovery Manager Administration Table 6‑2. Recovery States (Continued) 78 State Description Test complete Test completed with or without errors. If a failure occurs during the test, plan goes to Test Interrupted state. Test interrupted Server failed while a test was running. Cleanup in progress After successful cleanup, plan state goes to Ready. If cleanup is incomplete, state goes to Cleanup Incomplete. If you set the Force Cleanup option, state goes to Ready after an error.
Chapter 6 Creating, Testing, and Running Site Recovery Manager Recovery Plans Table 6‑2. Recovery States (Continued) State Description Incomplete recovery Canceled recovery or datastore error. Run recovery again. You need to either resolve errors and rerun recovery, or remove protection for VMs in error. The plan detects the resolution of errors in either of these ways and updates state to Recovery Complete. Partial recovery Some but not all protection groups are recovered by an overlapping plan.
Site Recovery Manager Administration Table 6‑2. Recovery States (Continued) 80 State Description Plan out of sync This state can occur under different circumstances: n Between a successful test recovery and a cleanup operation. You cannot edit the plan when it is in this state. Run cleanup to return the plan to the Ready state. If the plan remains in the Plan Out of Sync state, edit the plan. n During regular operation You can edit the plan.
Configuring a Recovery Plan 7 You can configure a recovery plan to run commands on Site Recovery Manager Server or on a virtual machine, display messages that require a response when the plan runs on the Site Recovery Manager Server or in the guest OS, suspend non-essential virtual machines during recovery, configure dependencies between virtual machines, customize virtual machine network settings, and change the recovery priority of protected virtual machines.
Site Recovery Manager Administration n Some steps are always skipped during test recoveries. n Some steps run only with stretched storage. Understanding recovery steps, their order, and the context in which they run is important when you customize a recovery plan. Recovery Order When you run a recovery plan, it starts by powering off the virtual machines at the protected site.
Chapter 7 Configuring a Recovery Plan After reprotect, you can usually use custom recovery steps that show messages directly without modifications. You might need to modify some custom recovery steps after a reprotect, if these steps run commands that contain site-specific information, such as network configurations. You can configure commands and prompts in recovery plan steps that signify completion of a particular operation. You cannot add commands and prompts before the Configure Test networks step.
Site Recovery Manager Administration For array-based replication protection groups and vSphere Replication protection groups, the first command or prompt (or custom) step added between Create Writeable Storage Snapshot and the first nonempty VM priority group starts in parallel with the step Create Writeable Storage Snapshot to address restart failure scenarios.
Chapter 7 Configuring a Recovery Plan 3 Use the View drop-down menu to select the type of recovery plan run to which to add a step. Option Description Test Steps Add a step to run when you test a recovery plan. Recovery Steps Add a step to run when you perform planned migration or disaster recovery You cannot add steps in the cleanup or reprotect operations. 4 To add a step before a step, right click the step and select Add Step Before.
Site Recovery Manager Administration 6 7 Select the type of step to create. Option Description Prompt Prompts users to perform a task or to provide information that the user must acknowledge before the plan continues to the next step. This option is available for both pre-power on steps and post-power on steps. Command on SRM Server Runs a command on Site Recovery Manager Server. This option is available for both pre-power on steps and post-power on steps.
Chapter 7 Configuring a Recovery Plan Table 7‑1. Environment Variables Available to All Command Steps Name Value Example VMware_RecoveryName Name of the recovery plan that is running. Plan A VMware_RecoveryMode Recovery mode. Test or recovery VMware_VC_Host Host name of the vCenter Server at the recovery site. vc_hostname.example.com VMware_VC_Port Network port used to contact vCenter Server.
Site Recovery Manager Administration Specify the Recovery Priority of a Virtual Machine By default, Site Recovery Manager sets all virtual machines in a new recovery plan to recovery priority level 3. You can increase or decrease the recovery priority of a virtual machine. The recovery priority specifies the shutdown and power on order of virtual machines. If you change the priority of a virtual machine, Site Recovery Manager applies the new priority to all recovery plans that contain this virtual machine.
Chapter 7 Configuring a Recovery Plan n Verify that the virtual machine with the dependency and the virtual machine that it depends on are in the same recovery priority group. Procedure 1 In the vSphere Web Client, select Site Recovery > Recovery Plans, and select a recovery plan. 2 On the Related Objects tab, click Virtual Machines. 3 Right-click a virtual machine that depends on one or more other virtual machines and select Configure Recovery. 4 Expand VM Dependencies.
Site Recovery Manager Administration Configure Virtual Machine Startup and Shutdown Options You can configure how a virtual machine starts up and shuts down on the recovery site during a recovery. You can configure whether to shut down the guest operating system of a virtual machine before it powers off on the protected site. You can configure whether to power on a virtual machine on the recovery site.
Chapter 7 Configuring a Recovery Plan Limitations to Protection and Recovery of Virtual Machines The protection and recovery by Site Recovery Manager of virtual machines is subject to limitations. Protection and Recovery of Suspended Virtual Machines When you suspend a virtual machine, vSphere creates and saves its memory state.
Site Recovery Manager Administration Protection and Recovery of Virtual Machines with Reservations, Affinity Rules, or Limits When Site Recovery Manager recovers a virtual machine to the recovery site, it does not preserve any reservations, affinity rules, or limits that you have placed on the virtual machine. Site Recovery Manager does not preserve reservations, affinity rules, and limits on the recovery site because the recovery site might have different resource requirements to the protected site.
Customizing IP Properties for Virtual Machines 8 You can customize IP settings for virtual machines for the protected site and the recovery site. Customizing the IP properties of a virtual machine overrides the default IP settings when the recovered virtual machine starts at the destination site. If you do not customize the IP properties of a virtual machine, Site Recovery Manager uses the IP settings for the recovery site during a recovery or a test from the protection site to the recovery site.
Site Recovery Manager Administration If you configure IP customization on virtual machines, Site Recovery Manager adds recovery steps to those virtual machines. Guest OS Startup The Guest Startup process happens in parallel for all virtual machines for which you configure IP customization. Customize IP Site Recovery Manager pushes the IP customizations to the virtual machine.
Chapter 8 Customizing IP Properties for Virtual Machines 9 Click the DNS tab to configure DNS settings. a Choose how DNS servers are found. You can use DHCP to find DNS servers or you can specify primary and alternate DNS servers. b Enter a DNS suffix and click Add or select an existing DNS suffix and click Remove, Move Up, or Move Down. Alternately, if the virtual machine is powered on and has VMware Tools installed, you can click Retrieve to import current settings configured on the virtual machine.
Site Recovery Manager Administration Rather than manually creating a CSV file, you can use the DR IP Customizer tool to export a CSV file that contains information about the networking configurations of the protected virtual machines. You can use this file as a template for the CSV file to apply on the recovery site by customizing the values in the file. 1 Run DR IP Customizer to generate a CSV file that contains the networking information for the protected virtual machines.
Chapter 8 Customizing IP Properties for Virtual Machines 2 Change to the C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin directory. 3 Run the dr-ip-reporter.exe command. n If you have a Platform Services Controller with a single vCenter Server instance, run the following command: dr-ip-reporter.exe --cfg ..\config\vmware-dr.xml --out path_to_report_file.xml --uri https://Platform_Services_Controller_address[:port]/lookupservice/sdk This example points dr-ip-reporter.
Site Recovery Manager Administration --vcid UUID [--ignore-thumbprint] [--extra-dns-columns] [--verbose] You can run the DR IP Customizer tool on either the protected site or on the recovery site. Virtual machine IDs for protected virtual machines are different at each site, so whichever site you use when you run the DR IP Customizer tool to generate the CSV file, you must use the same site when you run DR IP Customizer again to apply the settings.
Chapter 8 Customizing IP Properties for Virtual Machines Table 8‑1. DR IP Customizer Options (Continued) Option Description Mandatory --vcid arg The primary sitevCenter Server instance UUID. Optional, unless the primary site infrastructure contains more than one vCenter Server instance. -i [ --ignore-thumbprint ] Ignore the vCenter Server thumbprint confirmation prompt. No -e [ --extra-dns-columns ] Must be specified if the input CSV file contains extra columns for DNS information.
Site Recovery Manager Administration Table 8‑2. Columns of the DR IP Customizer CSV File 100 Column Description Customization Rules VM ID Unique identifier that DR IP Customizer uses to collect information from multiple rows for application to a single virtual machine. This ID is internal to DR IP Customizer and is not the same as the virtual machine ID that vCenter Server uses. Not customizable. Cannot be blank.
Chapter 8 Customizing IP Properties for Virtual Machines Table 8‑2. Columns of the DR IP Customizer CSV File (Continued) Column Description Customization Rules Secondary WINS DR IP Customizer validates that WINS settings are applied only to Windows virtual machines, but it does not validate NetBIOS settings. Customizable. Can be left blank. IP Address IPv4 address for this virtual machine. Customizable. Cannot be blank. Virtual machines can have multiple virtual network adapters.
Site Recovery Manager Administration Modifying the DR IP Customizer CSV File You modify the DR IP Customizer comma-separated value (CSV) file to apply customized networking settings to virtual machines when they start on the recovery site. NOTE This release of Site Recovery Manager allows you to define subnet-level IP mapping rules to customize IP settings on virtual machines, as well as by using the DR IP Customizer tool. You can use subnet-level IP mapping rules in combination with DR IP Customizer.
Chapter 8 Customizing IP Properties for Virtual Machines Example: A Generated DR IP Customizer CSV File For a simple setup with only two protected virtual machines, the generated CSV file might contain only the virtual machine ID, the virtual machine name, the names of the vCenter Server instances on both sites, and a single adapter.
Site Recovery Manager Administration Table 8‑3. Setting Static IPv4 Addresses in a Modified CSV File (Continued) VM ID VM Name vCent er Server Adapt er ID protecte dvm-1030 1 vcenter serversite-A 1 protecte dvm-1030 1 vcenter serversite-A 2 Primar y WINS 1.2.3.4 Secon dary WINS 1.2.3.5 IP Address Subnet Mask Gatewa y(s) 192.168.0 .21 255.255.2 55.0 192.168.0 .1 192.168.0 .22 255.255.2 55.0 192.168.0 .
Chapter 8 Customizing IP Properties for Virtual Machines Table 8‑4. Setting Static and DHCP IPv4 Addresses in a Modified CSV File (Continued) VM ID VM Name vCent er Server Adapt er ID Primar y WINS Secon dary WINS IP Address protecte dvm-1030 1 vcenter serversite-B 1 2.2.3.4 2.2.3.5 dhcp protecte dvm-1030 1 vcenter serversite-B 2 2.2.3.4 2.2.3.5 192.168.1 .22 Subnet Mask Gatewa y(s) DNS Server(s ) DNS Suffix(es) 1.1.1.1 255.255.2 55.0 192.168.1 .1 1.1.1.
Site Recovery Manager Administration Table 8‑5. Setting Static and DHCP IPv4 and IPv6 Addresses in a Modified CSV File VM ID vCe nter Serv er Ada pter ID Prim ary WIN S IP Addr ess Subn et Mask Gate way(s ) IPv6 Addr ess IPv6 Subn et Prefix lengt h IPv6 Gate way(s ) DNS Serve r(s) DNS Suffix( es) protec tedvm-10 301 vm3win vcen terserv ersiteB 0 exampl e.com protec tedvm-10 301 vm3win vcen terserv ersiteB 0 eng.exa mple.co m protec tedvm-10 301 vcen terserv ersiteB 1 2.2.3. 4 2.
Chapter 8 Customizing IP Properties for Virtual Machines Table 8‑5. Setting Static and DHCP IPv4 and IPv6 Addresses in a Modified CSV File (Continued) VM ID VM Nam e vCe nter Serv er Ada pter ID protec tedvm-10 301 vcen terserv ersiteA 1 protec tedvm-10 301 vcen terserv ersiteA 2 Prim ary WIN S Sec ond ary WIN S IP Addr ess Subn et Mask Gate way(s ) IPv6 Addr ess IPv6 Subn et Prefix lengt h IPv6 Gate way(s ) DNS Serve r(s) DNS Suffix( es) ::ffff: 192.16 8.0.25 1 1.2.3. 4 1.2.3.
Site Recovery Manager Administration n The user account that you use to run the DR IP Customizer tool requires at least the Site Recovery Manager Recovery Plans Administrator role. Procedure 1 Open a command shell on the Site Recovery Manager Server host. 2 Change directory to C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin. 3 Run the dr-ip-customizer.exe command to generate a comma-separated value (CSV) file that contains information about the protected virtual machines.
Chapter 8 Customizing IP Properties for Virtual Machines This example points dr-ip-customizer.exe to the vmware-dr.xml file of the Site Recovery Manager Server and applies the customizations in the CSV file to the vCenter Server that is associated with the Platform Services Controller at https://Platform_Services_Controller_address. n If you have a Platform Services Controller that includes multiple vCenter Server instances, you must specify the vCenter Server ID in the --vcid parameter. dr-ip-customizer.
Site Recovery Manager Administration Site Recovery Manager applies DNS and other parameters as specified. DHCP-enabled NICs are not subject to customization as their network configuration remains unchanged during recovery. Procedure 1 In the vSphere Web Client, click Site Recovery > Sites, and select a site. 2 On the Manage tab, select Network Mappings. 3 Select a network mapping for which to define a customization rule. 4 To define a rule, click Add IP Customization Rule.
Reprotecting Virtual Machines After a Recovery 9 After a recovery, the recovery site becomes the primary site, but the virtual machines are not protected yet. If the original protected site is operational, you can reverse the direction of protection to use the original protected site as a new recovery site to protect the new protected site. Manually reestablishing protection in the opposite direction by recreating all protection groups and recovery plans is time consuming and prone to errors.
Site Recovery Manager Administration Figure 9‑1.
Chapter 9 Reprotecting Virtual Machines After a Recovery When creating placeholder virtual machines on the new protected site, Site Recovery Manager uses the location of the original protected virtual machine to determine where to create the placeholder virtual machine. Site Recovery Manager uses the identity of the original protected virtual machine to create the placeholder.
Site Recovery Manager Administration If the storage arrays fail to reverse replication for any consistency groups in the protection group, the recovery plan goes into the Incomplete Reprotect state. In this state, you must resolve the storage issues and run reprotect again. Rerunning reprotect on a storage policy protection group only affects the direction of replication of consistency groups for which a previous reprotect operation did not complete successfully.
Chapter 9 Reprotecting Virtual Machines After a Recovery Reprotect Virtual Machines Reprotect results in the reconfiguration of Site Recovery Manager protection groups and recovery plans to work in the opposite direction. After a reprotect operation, you can recover virtual machines back to the original site using a planned migration workflow. Prerequisites See “Preconditions for Performing Reprotect,” on page 114. Procedure 1 In the vSphere Web Client, select Site Recovery > Recovery Plans.
Site Recovery Manager Administration Table 9‑1. Reprotect States (Continued) State Description Remedial Action Incomplete Reprotect Occurs because of failures during reprotect. For example, this state might occur because of a failure to synchronize storage or a failure to create placeholder virtual machines. n n Reprotect Interrupted 116 Occurs if one of the Site Recovery Manager Servers stops unexpectedly during the reprotect process.
Restoring the Pre-Recovery Site Configuration By Performing Failback 10 To restore the original configuration of the protected and recovery sites after a recovery, you can perform a sequence of optional procedures known as failback. After a planned migration or a disaster recovery, the former recovery site becomes the protected site. Immediately after the recovery, the new protected site has no recovery site to which to recover.
Site Recovery Manager Administration Figure 10‑1. Site Recovery Manager Failback Process 2. Reprotect–Recovery site becomes protected site 1.
Chapter 10 Restoring the Pre-Recovery Site Configuration By Performing Failback 4 Determine whether to enable Force Cleanup and click Next. This option is only available after you have run reprotect once and errors occured. Enabling this option forces the removal of virtual machines, ignoring errors, and returns the recovery plan to the ready state. 5 Review the reprotect information and click Finish. 6 In the Monitor tab, click Recovery Steps to monitor the reprotect operation until it finishes.
Site Recovery Manager Administration 120 VMware, Inc.
Interoperability of Site Recovery Manager with Other Software 11 Site Recovery Manager Server operates as an extension to the vCenter Server at a site. Site Recovery Manager is compatible with other VMware solutions, and with third-party software. You can run other VMware solutions such as vCenter Update Manager, vCenter Server Heartbeat, VMware Fault Tolerance, vSphere Storage vMotion, and vSphere Storage DRS in deployments that you protect using Site Recovery Manager.
Site Recovery Manager Administration Site Recovery Manager and vCenter Server Site Recovery Manager takes advantage of vCenter Server services, such as storage management, authentication, authorization, and guest customization. Site Recovery Manager also uses the standard set of vSphere administrative tools to manage these services.
Chapter 11 Interoperability of Site Recovery Manager with Other Software How Site Recovery Manager Interacts with DPM and DRS During Recovery Distributed Power Management (DPM) and Distributed Resource Scheduler (DRS) are not mandatory, but Site Recovery Manager supports both services and enabling them provides certain benefits when you use Site Recovery Manager. DPM is a VMware feature that manages power consumption by ESX hosts.
Site Recovery Manager Administration n Site Recovery Manager supports Storage DRS clusters containing datastores from different consistency groups. If you migrate a virtual machine to a datastore that is not part of a protection group, then you have to reconfigure the protection group to include that datastore. n Site Recovery Manager supports Storage vMotion without limitation between non-replicated datastores and between replicated datastores in the same consistency group.
Chapter 11 Interoperability of Site Recovery Manager with Other Software n A full sync causes Storage DRS to trigger Storage vMotion only if you set the Storage DRS rules to be very aggressive, or if a large number of virtual machines perform a full sync at the same time. The default I/O latency threshold for Storage DRS is 15ms. By default, Storage DRS performs loading balancing operations every 8 hours.
Site Recovery Manager Administration Protection Groups IMPORTANT Protection groups for stretched storage must be created as storage policy protection groups. You must create and use storage profiles to protect and recover stretched storage devices. n Protection groups with stretched devices must have a preferred direction from the protected site to the recovery site. The preferred direction must match the site preference that the array maintains for the corresponding devices.
Chapter 11 Interoperability of Site Recovery Manager with Other Software n Currently connected network interface cannot use network , because the type of the destination network is not supported for vMotion based on the source network type. Cross vCenter Server vMotion does not work in these situations.
Site Recovery Manager Administration Site Recovery Manager and vRealize Orchestrator The vRealize Orchestrator plug-in for Site Recovery Manager allows you to automate certain Site Recovery Manager operations by including them in vRealize Orchestrator workflows. The vRealize Orchestrator plug-in for Site Recovery Manager includes actions and workflows that run Site Recovery Manager operations.
Chapter 11 Interoperability of Site Recovery Manager with Other Software n n n The plug-in provides actions and workflows that protect virtual machines: n Protect a virtual machine by using an existing array-based replication protection group n Protect a virtual machine by using an existing vSphere Replication protection group The plug-in provides actions and workflows that configure recovery settings on virtual machines: n Set the recovery priority n Configure virtual machine recovery settings
Site Recovery Manager Administration Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines You can use Site Recovery Manager to protect Microsoft Cluster Server (MSCS) and fault tolerant virtual machines, with certain limitations. To use Site Recovery Manager to protect MSCS and fault tolerant virtual machines, you might need to change your environment.
Chapter 11 Interoperability of Site Recovery Manager with Other Software 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.
Site Recovery Manager Administration Site Recovery Manager and Virtual Machines Attached to RDM Disk Devices Protection and recovery of virtual machines that are attached to a raw disk mapping (RDM) disk device is subject to different support depending on whether you use array-based replication or vSphere Replication. NOTE Site Recovery Manager does not support the protection of virtual machines attached to RDM devices in storage policy protection groups.
Advanced Site Recovery Manager Configuration 12 The Site Recovery Manager default configuration enables some simple recovery scenarios. Advanced users can customize Site Recovery Manager to support a broader range of site recovery requirements.
Site Recovery Manager Administration 5 Option Action Change the number of failed pings before raising a site down event. The default value is 5. Enter a new value in the connections.qsPanicDelay text box. Change the number of status checks (pings) to try before declaring the check a failure. The default value is 2. Enter a new value in the connections.qsPingFailedDelay text box. Change the timeout value for the VIX service connection to the virtual machine. The default value is 120 seconds.
Chapter 12 Advanced Site Recovery Manager Configuration 2 On the Manage tab, click Advanced Settings. 3 Click Local Site Status. 4 Click Edit to change the settings. 5 Option Action Change the time difference at which Site Recovery Manager checks the CPU usage, disk space, and free memory at the local site. The default value is 60 seconds. Enter a new value in the localSiteStatus.checkInterval text box.
Site Recovery Manager Administration panic Records only panic log entries. Panic messages occur in cases of complete failure. error Records panic and error log entries. Error messages occur in cases of problems that might or might not result in a failure. warning Records panic, error, and warning log entries. Warning messages occur for behavior that is undesirable but that might be part of the expected course of operation. info Records panic, error, warning, and information log entries.
Chapter 12 Advanced Site Recovery Manager Configuration 5 Option Description Set logging level for recovery configuration operations. The default is verbose. Select a logging level from the logManager.RecoveryConfig drop-down menu. Set logging level for array-based replication operations. The default is verbose. Select a logging level from the logManager.Replication drop-down menu. Set logging level for authorization issues between Site Recovery Manager Server and vCenter Server.
Site Recovery Manager Administration settings for site B. When recovering from site B to site A Site Recovery Manager applies the local recovery settings for site A. This condition exists until you explicitly edit and save individual virtual machine recovery settings from the recovery plan Virtual Machines tab. Recovery settings for the affected virtual machine synchronize and become identical on both Site Recovery Manager sites.
Chapter 12 Advanced Site Recovery Manager Configuration 5 Option Action Enable or disable skipping the shutdown of the guest OS. The default value is false. Select or deselect the recovery.skipGuestShutdown check box. If skipGuestShutdown=true, Site Recovery Manager does not attempt guest OS shutdown on protection site VMs, but directly powers them off instead. In this case, the value set for recovery.powerOffTimeout has no effect together with this setting.
Site Recovery Manager Administration Apply Recovery Settings to Virtual Machines in a Protection Group If you change advanced recovery settings for protected virtual machines, the new settings do not take effect until the virtual machines are reconfigured. You can more conveniently update recovery settings by using the Protection Groups feature when you apply settings to multiple virtual machines, although it can be used for a single virtual machine.
Chapter 12 Advanced Site Recovery Manager Configuration Option Action Configure the maximum time to wait for cancelled tasks to stop. The default value is 300 seconds. Enter a value for remoteManager.taskCancelDefaultTimeout. Configure an additional timeout period for tasks to complete on the remote site. The default value is 900 seconds. Enter a value for remoteManager.taskDefaultTimeout. Configure the number of seconds to wait for a timed out task to report progress.
Site Recovery Manager Administration 4 5 Click Edit to change the settings. Option Action Skip the check for non-protected replica virtual machines while deactivating the protection site during Planned Migration. The default value is false. Select the checkbox to enable the value replication.disablePiggybackVmsCheckDuringDeactivate. Change the timeout in seconds to wait when creating a placeholder virtual machine. The default value is 300 seconds. Enter a new value in the replication.
Chapter 12 Advanced Site Recovery Manager Configuration 5 Option Action Allow Site Recovery Manager to automatically create tag categories and the Replicated tag that Storage DRS compatibility requires. The default value is true. Select the storage.enableSdrsStandardTagCategoryCreation check box. Allow Site Recovery Manager to automatically create and attach tags to replicated or protected datastores for Storage DRS compatibility. The default value is true. Select the storage.
Site Recovery Manager Administration Change Storage Provider Settings For array-based replication, the SAN provider is the interface between Site Recovery Manager and your storage replication adapter (SRA). Some SRAs require you to change default SAN provider values. You can change the default timeout values and other behaviors of the Site Recovery Manager SAN provider. You can change settings for resignaturing, fixing datastore names, host rescan counts, and timeouts in seconds.
Chapter 12 Advanced Site Recovery Manager Configuration VMware, Inc. Option Action Change the time that Site Recovery Manager waits before removing the snap-xx prefix applied to recovered datastore names. The default value is 0 seconds. Enter a new value in the storageProvider.fixRecoveredDatastoreNamesDelaySec text box. Delay host scans during testing and recovery. The default value is 0 seconds.
Site Recovery Manager Administration 5 Option Action Enable Site Recovery Manager to wait to discover datastores after recovery. Select the storageProvider.waitForDeviceRediscovery check box. Set the timeout in seconds to wait for the Virtual Center to report newly discovered datastores. The default value is 30 seconds. Enter the new value in the storageProvider.waitForRecoveredDatastoreTimeoutSec text box.
Chapter 12 Advanced Site Recovery Manager Configuration Modify Settings to Run Large Site Recovery Manager Environments If you use Site Recovery Manager to test or recover a large number of virtual machines, you might need to modify the default Site Recovery Manager settings to achieve the best possible recovery times in your environment or to avoid timeouts. In large environments, Site Recovery Manager might simultaneously power on or power off large numbers of virtual machines.
Site Recovery Manager Administration If these elements do not already exist in the vmware-dr.xml file, you can add them anywhere in the section. If you set the value to 24, the next guest starts booting or shutting down as soon as one of the first batch of 24 has finished, namely VMs 1 to 24 all start together, then VM 25 starts once one of the first batch has finished, VM 26 starts when the second one of the first batch has finished, and so on.
Chapter 12 Advanced Site Recovery Manager Configuration Table 12‑1. Settings that Modify the Number of Simultaneous Power On or Power Off Operations Option Description srmMaxBootShutdownOps Specifies the maximum number of concurrent power-on operations for any given cluster. Guest shutdowns, but not forced power offs, are throttled according to this value. Guest shutdowns occur during primary site shutdowns (planned failover) and IP customization workflows.
Site Recovery Manager Administration 150 VMware, Inc.
Site Recovery Manager Events and Alarms 13 Site Recovery Manager supports event logging. Each event includes a corresponding alarm that Site Recovery Manager can trigger if the event occurs. This provides a way to track the health of your system and to resolve potential issues before they affect the protection that Site Recovery Manager provides.
Site Recovery Manager Administration Configure Site Recovery Manager Alarms Site Recovery Manager adds alarms to the alarms that vCenter Server supports. You can configure Site Recovery Manager alarms to send an email notification, send an SNMP trap, or to run a script on the vCenter Server host. The Alarm Definitions tab lists all of the Site Recovery Manager alarms. You can edit the settings for each alarm to specify the action for Site Recovery Manager to take when an event triggers the alarm.
Chapter 13 Site Recovery Manager Events and Alarms Site Recovery Manager Events Reference Site Recovery Manager monitors different types of events. Site Status Events Site status events provide information about the status of the protected and recovery sites and the connection between them. Table 13‑1.
Site Recovery Manager Administration Table 13‑1. Site Status Events (Continued) Categor y Event Name Event Type Event Description The connection to the local inventory service is restored LocalQsConnectionUpEven t Connection to the local inventory server is successful. You can specify the interval between pings from Site Recovery Manager to the inventory service by adding number of seconds in the vmware-dr.xml configuration file.
Chapter 13 Site Recovery Manager Events and Alarms Table 13‑2. Protection Group Replication Events (Continued) Catego ry Event Description Cause ProtectedVmReconfiguredR ecoveryLocationSettingsE vent Reconfigured recovery location settings for virtual machine. Posted on the protected site vCenter Server only on the successful completion of reconfiguring the recovery location settings for a protected virtual machine.
Site Recovery Manager Administration Table 13‑3. Recovery Events (Continued) 156 Event Name Event Type Event Description Category Recovery Plan [data.Plan] failed registering virtual machine [data.Vm]. RecoveryVmRegisterFa iled Signaled in the case of SPPGs after a recovered VM has failed registration with the recovery site VC. If the plan is run against the local VC, then [data.local] will be true. Info Recovery plan hostnamehas been created. PlanCreated Signaled when a new plan is created.
Chapter 13 Site Recovery Manager Events and Alarms Table 13‑3. Recovery Events (Continued) Event Name Event Type Event Description Category Recovery plan has completed executing a command on the Site Recovery Manager Server machine. PlanServerCommandEnd Signaled on the recovery site when Site Recovery Manager has finished running a callout command on the Site Recovery Manager Server machine. Info Recovery plan has started to run a command on a recovered virtual machine.
Site Recovery Manager Administration Table 13‑6. Array Pair Events Categ ory Event Description Cause SAPairDiscoveredEvent Discovered replicated array pair with Array Manager. User created Array Manager which discovered replicated array pairs. Info SAPairEnabledEvent Enabled replicated array pair with Array Manager. User enabled an Array Pair. Info SAPairDisabledEvent Disabled replicated array pair with Array Manager. User disabled an Array Pair.
Chapter 13 Site Recovery Manager Events and Alarms Table 13‑8. Protection Events (Continued) Catego ry Event Description Cause SPDsProtMissingE vent Replicated datastore needs to be included in specified protection group but is included in an alternate protection group. This is raised if you have a datastore that needs to be merged and is still not protected. At the conflict event, the datastore is already protected.
Site Recovery Manager Administration Table 13‑8. Protection Events (Continued) Event Description Cause Catego ry Event Target SPCgDsMissingPro tEvent Datastore from specified consistency group needs to be included in specified protection group. See description. Error Datastore SPDsSpansConsist GroupsEvent Datastore spans devices from different consistency groups. This is raised if you have a datastore on top of multiple LUNs but these LUNs do not belong to the same consistency group.
Chapter 13 Site Recovery Manager Events and Alarms Table 13‑9. Licensing Events (Continued) Event Description Cause UnlicensedFeatureEvent The Site Recovery Manager license at the specified site is overallocated by the specified number of licenses. Every 24 hours and upon the protection or unprotection of a virtual machine, this event will be posted if the total number of licenses exceeds the capacity in the license.
Site Recovery Manager Administration Table 13‑11. SNMP Traps (Continued) 162 Event Description Cause RecoveryPlanExecuteBeginTrap This trap is sent when a recovery plan starts a recovery. Site Recovery Manager site name, recovery plan name, recovery type, execution state. RecoveryPlanExecuteEndTrap This trap is sent when a recovery plan ends a recovery. Site Recovery Manager site name, recovery plan name, recovery type, execution state, result status.
Collecting Site Recovery Manager Log Files 14 To help identify the cause of any problems you encounter during the day-to-day running of Site Recovery Manager, you might need to collect Site Recovery Manager log files to review or send to VMware Support. Site Recovery Manager creates several log files that contain information that can help VMware Support diagnose problems. You can use the Site Recovery Manager log collector to simplify log file collection.
Site Recovery Manager Administration Procedure 1 In the vSphere Web Client, click Site Recovery > Sites, and select a site. 2 From the Actions menu, and select Export SRM Log. You can also right-click the site and select Export SRM Log. 3 In the Export SRM Log wizard, click Generate Log and wait for the operation to complete. 4 Click Download Log to download the logs.
Chapter 14 Collecting Site Recovery Manager Log Files 4 Set the maximum size in bytes of the logs to retain. You set the maximum log size by adding a section to the section. The default is 10485760 bytes. 10485760 5 Set the maximum number of log files to retain. You set the maximum number of logs by adding a section to the section. The default is 20 log files.
Site Recovery Manager Administration 10 (Optional) Set the level of logging for storage replication adapters. Setting the Site Recovery Manager logging level does not set the logging level for SRAs. You change the SRA logging level by adding a section to vmware-dr.xml to set the SRA logging level. SraCommand trivia 11 Restart the Site Recovery Manager Server service for changes to take effect.
Chapter 14 Collecting Site Recovery Manager Log Files 5 To modify the maximum number of core dump files, add a row to the section. max files If unspecified, the default value is 4. This value specifies the maximum number of core dump files that are retained in the core dump directory.
Site Recovery Manager Administration 168 VMware, Inc.
Troubleshooting Site Recovery Manager 15 If you encounter problems with creating protection groups and recovery plans, recovery, or guest customization, you can troubleshoot the problem. When searching for the cause of a problem, also check the VMware knowledge base at http://kb.vmware.com/.
Site Recovery Manager Administration Site Recovery Manager Doubles the Number of Backslashes in the Command Line When Running Callouts When a backslash is a part of the callout command line, Site Recovery Manager doubles all backslashes. Problem The command-line system interpreter treats double backslashes as a single backslash only in file paths.
Chapter 15 Troubleshooting Site Recovery Manager Powering on Many Virtual Machines Simultaneously on the Recovery Site Can Lead to Errors When many virtual machines perform boot operations at the same time, you might see errors during arraybased and vSphere Replication recovery. Problem When powering on many virtual machines simultaneously on the recovery site, you might see these errors in the recovery history reports: n The command 'echo "Starting IP customization on Windows ...
Site Recovery Manager Administration Cause Site Recovery Manager does not check how snapshot volumes are presented to ESXi hosts. Site Recovery Manager does not support setting the LVM.enableResignature flag to 0. If you set the flag from 1 to 0, a virtual machine outage might occur each time you perform a test recovery or an actual recovery occurs. Setting the LVM.enableResignature flag on ESXi hosts is a host-wide operation.
Chapter 15 Troubleshooting Site Recovery Manager n You use the Site Recovery Manager API to protect a large number of virtual machines manually. Cause The infrastructure on the recovery site is unable to handle the volume of concurrent creations of placeholder virtual machines. Solution Increase the replication.placeholderVmCreationTimeout setting from the default of 300 seconds. See “Change Replication Settings,” on page 141.
Site Recovery Manager Administration Recovery Fails with a Timeout Error During Network Customization for Some Virtual Machines During a recovery some virtual machines do not recover and show a timeout error during network customization. Problem During recovery some virtual machines do not recover within the default timeout period of 120 seconds. Cause This problem can occur for one of the following reasons. n The VMware Tools package is not installed on the virtual machine that you are recovering.
Chapter 15 Troubleshooting Site Recovery Manager Reprotect Fails with a vSphere Replication Timeout Error When you run reprotect on a recovery plan that contains vSphere Replication protection groups, the operation times out with an error. Problem Reprotect operations on recovery plans that contain vSphere Replication protection groups fail with the error Operation timed out: 7200 seconds VR synchronization failed for VRM group . Operation timed out: 7200 seconds .
Site Recovery Manager Administration Cause Excessive I/O traffic on one or more of the virtual machines in the protection group causes the synchronization to time out before it can finish. This can be because of heavy traffic. For example, setting the logging level to trivia mode can generate heavy I/O traffic. Solution 1 Log in to the Site Recovery Manager Server host. 2 Open the vmware-dr.xml file in a text editor. You find the vmware-dr.xml file in the C:\Program Files\VMware\VMware vCenter Site Reco
Chapter 15 Troubleshooting Site Recovery Manager Recovery Sticks at 36% During Planned Migration If you stop the Site Recovery Manager service on the protected site during a planned migration, the operation sticks at 36%. Problem During a planned migration, if you stop the Site Recovery Manager service on the protected site, when the workflow proceeds to step 15 Unmount protected site storage, it might not fail gracefully, but instead remains at 36%.
Site Recovery Manager Administration 178 VMware, Inc.
Index A Active Directory domain controllers, limits on protection 132 Admission Control clusters, using with SRM 131 Advanced Settings, vSphere Replication 146 advanced settings local site 134 logging 135 long-running tasks 140 recovery 137, 139, 140 remote site 141 replication 141 storage 142 Advanced Settings dialog boxes 133 affinity rules, limits on recovery 91 alarms, Site Recovery Manager-specific 152 all paths down (APD) 74 all paths down, recovery plans 67 apply IP customization rule to a virtual m
Site Recovery Manager Administration F M failback diagram 117 perform 118 failover, effects of 74 fault tolerant virtual machines protection 130 reprotect 130 Flash Read Cache 23 forced recovery 68, 74 many-to-one configuration 14 mappings datastore protection groups 33 storage policy 39 storage policy protection groups 33 vSphere Replication protection groups 33 monitoring connection 151 MPIT, and IP customization 75 MSCS and vMotion 130 DRS requirements 130 ESXi host requirements 130 protection 130 re
Index add devices to a protected VM 59 add virtual machines 56 apply inventory mappings 57 array-based 46 array-based replication 53 Configure All 57 Configure Protection 58 configure mappings on an individual VM 58 create 53 create folders 55 delete folders 55 disabling replication 59 edit 56 events 154 folder permissions 55 reconfigure protection after modifying a VM 59 Recreate Placeholder 57, 58 relation to recovery plan 45 remove protection from a VM 60 rename folder 55 Restore Placeholder VMs 57 stor
Site Recovery Manager Administration S settings for large environments 147, 148 shared recovery site events 14 isolate user resources 14 permissions 14 share user resources 14 tasks 14 SIOC disaster recovery 131 planned migration 131 reprotect 131 site status, events 153 Site Recovery Manager, and other vCenter Server Solutions 122 Site Recovery Manager History Reports 134 snapshots, limitations on recovery of 91 SNMP traps 161 SRA, See storage replication adapter SRM administrator 13 SRM administration 7
Index synchronization 146 synchronization error 175 vSphere Replication server, role 28 vSphere Replication administrator 13 vSphere Replication management server, role 28 VMware, Inc.
Site Recovery Manager Administration 184 VMware, Inc.
