Site Recovery Manager Administration vCenter Site Recovery Manager 5.8 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 vCenter 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 Mach
Site Recovery Manager Administration Edit a Recovery Plan 47 Test a Recovery Plan 48 Clean Up After Testing a Recovery Plan 48 Run a Recovery Plan 49 Recover a Point-in-Time Snapshot of a Virtual Machine 50 Cancel a Test or Recovery 51 Export Recovery Plan Steps 51 View and Export a Recovery Plan History 51 Delete a Recovery Plan 52 Recovery Plan Status Reference 52 5 Configuring a Recovery Plan 55 Recovery Plan Steps 56 Creating Custom Recovery Steps 56 Types of Custom Recovery Steps 57 How Site Reco
Contents Using Site Recovery Manager with vSphere Replication on Sites with Storage DRS or Storage vMotion 94 How Site Recovery Manager Interacts with vSphere High Availability 94 Site Recovery Manager and vSphere PowerCLI 95 Site Recovery Manager and vCenter Orchestrator 95 Automated Operations That the vCenter Orchestrator Plug-In for Site Recovery Manager Provides 95 Protecting Microsoft Cluster Server and Fault Tolerant Virtual Machines 96 Limitations to Protection and Recovery of Virtual Machines 97
Site Recovery Manager Administration Recovery Plan Times Out While Waiting for VMware Tools 141 Synchronization Fails for vSphere Replication Protection Groups 141 Reprotect Fails After Restarting vCenter Server 142 Rescanning Datastores Fails Because Storage Devices are Not Ready 142 Index 145 6 VMware, Inc.
About VMware vCenter Site Recovery Manager Administration VMware vCenter Site Recovery Manager (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-001400-02 n n n n EN-001400-01 n n n EN-001400-00 VMware, Inc. Corrected the path to SRA downloads on myvmware.com and clarified that you can download certified SRAs from third party sites in “Install Storage Replication Adapters,” on page 22.
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 Site Recovery Manager to use with 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 Site Recovery Manager to use with 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 4 Select a role from the Assigned Role drop-down menu to assign to the user or user group that you selected in Step 3. The Assigned Role drop-down menu includes all of the roles that vCenter Server and its plug-ins make available. Site Recovery Manager adds several roles to vCenter Server. Option Action Allow a user or user group to perform all Site Recovery Manager configuration and administration operations. Assign the SRM Administrator role.
Chapter 1 Site Recovery Manager Privileges, Roles, and Permissions Site Recovery Manager Roles Reference Site Recovery Manager includes a set of roles. Each role includes a set of privileges, which allow users with those roles to complete different actions. Roles can have overlapping sets of privileges and actions. For example, the Site Recovery Manager Administrator role and the Site Recovery Manager Protection Groups Administrator have the Create privilege for protection groups.
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 n Modify protection groups. n Add virtual machines to protection groups. n Delete protection groups. n Configure protection on virtual machines. n Remove protection from 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 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. n Configure custom command steps on virtual machines.
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 dropdown menu. 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.
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 Using vSphere Replication with Site Recovery Manager Site Recovery Manager can use vSphere Replication to replicate data to servers at the recovery site. Previous versions of Site Recovery Manager included the vSphere Replication appliance. In previous releases you could configure vSphere Replication in the Site Recovery Manager interface.
Chapter 2 Replicating Virtual Machines Using vSphere Replication and VMware Virtual SAN Storage with Site Recovery Manager You can use VMware Virtual SAN storage with vSphere Replication and Site Recovery Manager. Replicating a Virtual Machine and Enabling Multiple Point in Time Instances You can recover virtual machines at specific points in time (PIT) such as the last known consistent state.
Site Recovery Manager Administration n Deploy vSphere Replication appliances on both sites and configure the connection between the appliances. n Configure virtual machines for replication using either array-based replication or vSphere Replication, as appropriate. NOTE Do not attempt to configure vSphere Replication on a virtual machine that resides on a datastore that you replicate by using array-based replication.
Creating and Managing Protection Groups 3 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 Apply Inventory Mappings to All Members of a Protection Group on page 35 If the status of a protection group is Not Configured, you can configure protection for all of the unconfigured virtual machines by using existing site-wide inventory mappings, in one step. n Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group on page 36 You can configure the mappings for the virtual machines in a protection group individually.
Chapter 3 Creating and Managing Protection Groups replicated storage devices, one datastore is the replication source and the other is the replication target. Data written to the source datastore is replicated to the target datastore on a schedule controlled by the replication software of the array. When you configure Site Recovery Manager to work with a storage replication adapter (SRA), the replication source is at the protected site and the replication target is at the recovery site.
Site Recovery Manager Administration About vSphere Replication Protection Groups You can include virtual machines that you configured for vSphere Replication in vSphere Replication protection groups. Virtual machines in the vCenter Server inventory that are configured for vSphere Replication are available for selection when you create or edit a vSphere Replication protection group.
Chapter 3 Creating and Managing Protection Groups 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.
Site Recovery Manager Administration n To apply inventory mappings to each virtual machine in the protection group individually, see “Configure Inventory Mappings for an Individual Virtual Machine in a Protection Group,” on page 36. 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 protection group, or add or remove virtual machines in a vSphere Replication protection group.
Chapter 3 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 5 (Optional) If the status of the virtual machines is Not Configured or Mapping Missing, check the inventory mappings and click Configure All again. 6 (Optional) If the status of the virtual machines is Placeholder VM creation error, check the placeholder datastore mapping and try to recreate the placeholder virtual machines. n To recreate the placeholder for an individual virtual machine, right-click a virtual machine and select Recreate Placeholder.
Chapter 3 Creating and Managing Protection Groups 9 (Optional) If the status of the virtual machine Placeholder VM creation error, check the placeholder datastore mapping at the site level, right-click the virtual machine, and select Recreate Placeholder. Modifying the Settings of a Protected Virtual Machine You can edit the settings of a virtual machine in a protection group.
Site Recovery Manager Administration Remove Protection from a Virtual Machine You can temporarily remove protection from a replicated virtual machine without removing it from its protection group. Removing protection deletes the placeholder virtual machine on the recovery site. If you remove protection from a virtual machine, the states of the virtual machine and the protection group are set to Not Configured.
Chapter 3 Creating and Managing Protection Groups Table 3‑1. Protection Group States (Continued) State Description Cleaning Up Group is used in a plan that is cleaning up after a test. You cannot edit the group. Group returns to the OK or Not Configured state when cleanup is successful. If cleanup fails, the group goes to the Testing state. Recovering Group is used in a plan that is running a recovery. You cannot edit the group. If recovery succeeds, the group goes to Recovered state.
Site Recovery Manager Administration Table 3‑2. Virtual Machine Protection States (Continued) 40 State Description Device not found: device name You added an unreplicated disk or device to a protected virtual machine. You must edit the replication of the virtual machine either include or remove the device from protection. Mapping missing: Folder name; Network name ; Resource pool name Folder, resource pool, or network mappings are not configured for this VM.
Creating, Testing, and Running Recovery Plans 4 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 51 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 51 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 52 You can delete a recovery plan if you do not need it.
Chapter 4 Creating, Testing, and Running 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 4 Creating, Testing, and Running Recovery Plans Differences Between Testing and Running a Recovery Plan Testing a recovery plan has no lasting effects on either the protected site or the recovery site, but running a recovery plan has significant effects on both sites. You need different privileges when testing and running a recovery plan. Table 4‑1.
Site Recovery Manager Administration machines to communicate, establish and select DVS switches or VLANs. With an isolated VLAN that connects all hosts to each other but not to a production network, you can more realistically test a recovery. To achieve connectivity among recovery hosts, but maintain isolation from the production network, follow these recommendations: n Create DVS switches that are connected to an isolated VLAN that is private.
Chapter 4 Creating, Testing, and Running Recovery Plans 2 On the Related Objects > Recovery Plans tab, click the icon to create a recovery plan. 3 Enter a name for the plan, select a location, then click Next. 4 Select the recovery site and click Next. 5 Select one or more protection groups for the plan to recover, and click Next. 6 Select a test network for the virtual machines whose configured recovery network is the selected recovery network identified by the datacenter and recovery network.
Site Recovery Manager Administration Test a Recovery Plan When you test a recovery plan, Site Recovery Manager runs the virtual machines of the recovery plan on a test network and on a temporary snapshot of replicated data at the recovery site. Site Recovery Manager does not disrupt operations at the protected site.
Chapter 4 Creating, Testing, and Running Recovery Plans Procedure 1 In the vSphere Web Client, select Site Recovery > Recovery Plans, and select a recovery plan. 2 Right-click the recovery plan and select Cleanup. You can also run cleanup from the Recovery Steps tab. 3 Review the cleanup information and click Next. 4 Click Finish. 5 After the cleanup finishes, if it reports errors, run the cleanup again, selecting the Force Cleanup option.
Site Recovery Manager Administration 8 Click the Monitor tab and click Recovery Steps. The Recovery Steps tab displays the progress of individual steps. The Recent Tasks area reports the progress of the overall plan. Recover a Point-in-Time Snapshot of a Virtual Machine 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.
Chapter 4 Creating, Testing, and Running Recovery Plans Cancel a Test or Recovery You can cancel a recovery plan test whenever the status is test in progress or failover in progress. When you cancel a test or recovery, Site Recovery Manager does not start processes, and uses certain rules to stop processes that are in progress. Canceling a failover requires you to re-run the failover.
Site Recovery Manager Administration Prerequisites You ran or tested a recovery plan, or cleaned up after a test. Procedure 1 In the vSphere Web Client, select Site Recovery > Recovery Plans, and select a recovery plan. 2 On the Monitor tab, click History. 3 (Optional) Click the Export icon for the recovery plan history for a specific time period, recovery plan run, test, or cleanup operation. You can save the recovery plan history as HTML, XML, CSV, or MS Excel or Word document.
Chapter 4 Creating, Testing, and Running Recovery Plans Table 4‑2. Recovery States (Continued) State Description Disaster recovery complete During recovery at the protected site, VM shutdown enountered errors, possibly because the sites were not connected, the step before split brain. System prompt warns of split brain and to run recovery again when sites reconnect.
Site Recovery Manager Administration Table 4‑2. Recovery States (Continued) State Description Protection groups in use Plan contains groups that are being used for a test by another plan. This state also occurs when the other plan has completed a Test operation on the groups, but has not run Cleanup. Wait for the other plan to complete the test or cleanup or edit the plan to remove the groups. Direction error Groups are in a mixed state, which is an invalid state.
Configuring a Recovery Plan 5 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, 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 Recovery Plan Steps A recovery plan runs a series of steps that must be performed in a specific order for a given workflow such as a planned migration or reprotect. You cannot change the order or purpose of the steps, but you can insert your own steps that display messages and run commands. Site Recovery Manager runs different recovery plan steps in different ways. n Some steps run during all recoveries. n Some steps run only during test recoveries.
Chapter 5 Configuring a Recovery Plan n How Site Recovery Manager Handles Custom Recovery Step Failures on page 58 Site Recovery Manager handles custom recovery step failures differently based on the type of recovery step. n Create Top-Level Message Prompts or Command Steps on page 58 You can add top-level recovery steps anywhere in the recovery plan. Top-level command steps are commands or scripts that you run on Site Recovery Manager Server during a recovery.
Site Recovery Manager Administration How Site Recovery Manager Handles Custom Recovery Step Failures Site Recovery Manager handles custom recovery step failures differently based on the type of recovery step. Site Recovery Manager attempts to complete all custom recovery steps, but some command recovery steps might fail to finish. Command Recovery Steps By default, Site Recovery Manager waits for 5 minutes for command recovery steps to finish. You can configure the timeout for each command.
Chapter 5 Configuring a Recovery Plan 5 Select Command on SRM Server or Prompt. 6 In the Name text box, enter a name for the step. The step name appears in the list of steps in the Recovery Steps view. 7 8 In the Content text box, enter the commands for the step to run. n If you selected Command on SRM Server, enter the command or script to run. n If you selected Prompt, enter the text of the message to display during the recovery plan run.
Site Recovery Manager Administration 8 9 In the Content text box, enter the commands for the step to run. n If you selected Command on SRM Server or Command on Recovered VM, enter the command or script to run. n If you selected Prompt, enter the text of the message to display during the recovery plan run. (Optional) Modify the Timeout setting for the command to run on Site Recovery Manager Server. This option is not available if you create a prompt step.
Chapter 5 Configuring a Recovery Plan Table 5‑2. Environment Variables Available to Per-Virtual Machine Command Steps Name Value Example VMware_VM_Uuid UUID used by vCenter to uniquely identify this virtual machine. 4212145a-eeae-a02c-e525-ebba70b0d4f3 VMware_VM_Name Name of this virtual machine, as set at the protected site. My New Virtual Machine VMware_VM_Ref Managed object ID of the virtual machine. vm-1199 VMware_VM_GuestName Name of the guest OS as defined by the VIM API.
Site Recovery Manager Administration 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 and select All Priority Actions. 4 Select a new priority for the virtual machine. The highest priority is 1. The lowest priority is 5. 5 Click Yes to confirm the change of priority.
Chapter 5 Configuring a Recovery Plan 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.
Site Recovery Manager Administration 64 VMware, Inc.
Customizing IP Properties for Virtual Machines 6 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 After the IP customization process finishes, virtual machines power on according to the priority groups and any dependencies that you set. The power on process happens immediately before the Wait for VMTools process for each virtual machine. NOTE To customize the IP properties of a virtual machine, you must install VMware Tools or the VMware Operating System Specific Packages (OSP) on the virtual machine. See http://www.vmware.com/download/packages.html.
Chapter 6 Customizing IP Properties for Virtual Machines 10 Repeat Step 6 through Step 9 to configure recovery site or protected site settings, if required. For example, if you configured IP settings for the protected site, you might want to configure settings for the recovery site. 11 Repeat the configuration process for other NICs, as required.
Site Recovery Manager Administration n Report IP Address Mappings for Recovery Plans on page 68 The IP address map reporter generates an XML document describing the IP properties of protected virtual machines and their placeholders, grouped by site and recovery plan. This information can help you understand the network requirements of a recovery plan.
Chapter 6 Customizing IP Properties for Virtual Machines Syntax of the DR IP Customizer Tool The DR IP Customizer tool includes options that you can use to gather networking information about the virtual machines that Site Recovery Manager protects. You can also use the options to apply customizations to virtual machines when they start up on the recovery site.
Site Recovery Manager Administration Table 6‑1. DR IP Customizer Options (Continued) Option Description Mandatory --cmd arg You specify different commands to run DR IP Customizer in different modes. Yes n The apply command applies the network customization settings from an existing CSV file to the recovery plans on the Site Recovery Manager Server instances. n The generate command generates a basic CSV file for all virtual machines that Site Recovery Manager protects for a vCenter Server instance.
Chapter 6 Customizing IP Properties for Virtual Machines Configuring IP settings for both sites is optional. You can provide settings for only the protected site, or settings for only the recovery site, or settings for both sites. You can configure each site to use a different set of network adapters in a completely different way. Certain fields in the CSV file must be completed for every row. Other fields can be left blank if no customized setting is required. Table 6‑2.
Site Recovery Manager Administration Table 6‑2. Columns of the DR IP Customizer CSV File (Continued) 72 Column Description Customization Rules Net BIOS Select whether to activate NetBIOS on this adapter. Customizable. Can be left blank. If not left empty, this column must contain one of the following strings: disableNetBIOS, enableNetBIOS, or enableNetBIOSViaDhcp.
Chapter 6 Customizing IP Properties for Virtual Machines Table 6‑2. Columns of the DR IP Customizer CSV File (Continued) Column Description Customization Rules DNS Server(s) Address of the DNS server or servers. Customizable. Can be left blank. If you enter this setting in an Adapter ID 0 row, it is treated as a global setting. On Windows virtual machines, this setting applies for each adapter if you set it in the Adapter ID rows other than Adapter ID 0.
Site Recovery Manager Administration n To specify an IP address for a network adapter on each of the protected and recovery sites, or to specify multiple DNS server addresses, add a new row for each address. Copy the VM ID, VM Name, and Adapter ID values to each row. Examples of DR IP Customizer CSV Files You obtain a CSV file that contains the networking information for the protected virtual machines on the vCenter Server by running dr-ip-customizer.exe with the --cmd generate command.
Chapter 6 Customizing IP Properties for Virtual Machines Table 6‑3. Setting Static 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 Subnet Mask Gatewa y(s) DNS Server(s ) protecte dvm-1030 1 vcenter serversite-B 1 2.2.3.4 2.2.3.5 192.168.1 .21 255.255.2 55.0 192.168.1 .1 1.1.1.1 protecte dvm-1030 1 vcenter serversite-B 2 2.2.3.4 2.2.3.5 192.168.1 .22 255.255.2 55.0 192.168.1 .1 1.1.1.
Site Recovery Manager Administration Table 6‑4. Setting Static and DHCP IPv4 Addresses in a Modified CSV File VM ID VM Name vCent er Server Adapt er ID Primar y WINS Secon dary WINS IP Address Subnet Mask Gatewa y(s) DNS Server(s ) DNS Suffix(es) protecte dvm-1030 1 vm-3win vcenter serversite-B 0 example.c om protecte dvm-1030 1 vm-3win vcenter serversite-B 0 eng.exam ple.com protecte dvm-1030 1 vcenter serversite-B 1 2.2.3.4 2.2.3.
Chapter 6 Customizing IP Properties for Virtual Machines Example: Setting Static and DHCP IPv4 and IPv6 Addresses You can modify the generated CSV file to assign multiple NICs to vm-3-win, one of the virtual machines. The NICs can use a combination of static and DHCP IPv4 and IPv6 addresses. The settings can be different on both the protected site and the recovery site. For readability, the example CSV file in the following table omits empty columns. The DNS Domain and NetBIOS columns are omitted.
Site Recovery Manager Administration Table 6‑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. 5 192.16 8.0.22 255.
Chapter 6 Customizing IP Properties for Virtual Machines 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. dr-ip-customizer.exe --cfg ..\config\vmware-dr.xml --cmd generate --out "path_to_CSV_file.
Site Recovery Manager Administration Customize IP Properties for Multiple Virtual Machines by Defining IP Customization Rules You can specify a single subnet-level IP mapping rule for a selected configured virtual network mapping on the protected and recovery sites. Subnet-level mapping eliminates the need to define exact adapter-level IP mapping. Instead, you specify an IP customization rule that Site Recovery Manager applies to relevant adapters.
Chapter 6 Customizing IP Properties for Virtual Machines If you set the advanced setting option recovery.useIpMapperAutomatically to True and configure the IP mapping rule for virtual networks, then Site Recovery Manager evaluates the subnet IP mapping rules during recovery to customize the virtual machines. If you set this option to False, Site Recovery Manager does not evaluate the IP mapping rules during recovery.
Site Recovery Manager Administration 82 VMware, Inc.
Reprotecting Virtual Machines After a Recovery 7 After a recovery, the recovery site becomes the new protected site, but it is 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 7‑1.
Chapter 7 Reprotecting Virtual Machines After a Recovery Forcing synchronization of data from the new protection site to the new recovery site ensures that the recovery site has a current copy of the protected virtual machines running at the protection site. Forcing this synchronization ensures that recovery is possible immediately after the reprotect process finishes.
Site Recovery Manager Administration Procedure 1 In the vSphere Web Client, select Site Recovery > Recovery Plans. 2 Right-click a recovery plan and select Reprotect. 3 Select the check box to confirm that you understand that the reprotect operation is irreversible. 4 (Optional) Select the Force Cleanup check box to ignore errors during the cleanup operation on the recovery site, and click Next.
Restoring the Pre-Recovery Site Configuration By Performing Failback 8 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 8‑1. Site Recovery Manager Failback Process 2. Reprotect–Recovery site becomes protected site 1.
Chapter 8 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 90 VMware, Inc.
Interoperability of Site Recovery Manager with Other Software 9 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, vSphere Storage DRS, and vCenter CapacityIQ in deployments that you protect using Site Recovery Manager.
Site Recovery Manager Administration How Changes to vCenter Server Inventory Affect Site Recovery Manager Because Site Recovery Manager protection groups apply to a subset of the vCenter Server inventory, changes to the protected inventory made by vCenter Server administrators and users can affect the integrity of Site Recovery Manager protection and recovery.
Chapter 9 Interoperability of Site Recovery Manager with Other Software If DRS is enabled and in fully automatic mode, DRS might move other virtual machines to further balance the load across the cluster while Site Recovery Manager is powering on the recovered virtual machines. DRS continues to balance all virtual machines across the cluster after Site Recovery Manager has powered on the recovered virtual machines.
Site Recovery Manager Administration n Moving a protected disk to a different consistency group results in the same problems as for moving an entire virtual machine. These problems occur if you move a disk to a different consistency group within the same protection group or if you move it into a different protection group. Site Recovery Manager does not prevent you from doing this, but if a disk has moved to a different consistency group, powering on the virtual machine fails after the move.
Chapter 9 Interoperability of Site Recovery Manager with Other Software Site Recovery Manager and vSphere PowerCLI VMware vSphere PowerCLI provides a Windows PowerShell interface for command-line access to Site Recovery Manager tasks. vSphere PowerCLI exposes the Site Recovery Manager APIs. You can use vSphere PowerCLI to administrate Site Recovery Manager or to create scripts that automate Site Recovery Manager tasks.
Site Recovery Manager Administration Because of the significant effect that running a recovery has on the protected and recovery sites, you cannot use the vCenter Orchestrator plug-in for vCenter Site Recovery Manager to automate test recovery, planned migration, or disaster recovery. Recovery is too sensitive to automate and always requires human intervention.
Chapter 9 Interoperability of Site Recovery Manager with Other Software ESXi Host Requirements for Protection of MSCS Virtual Machines To protect MSCS or fault tolerant virtual machines, the ESXi host machines on which the virtual machines run must meet certain criteria. n You must run a fault tolerant virtual machine and its shadow on two separate ESXi Server instances. n You can run a cluster of MSCS virtual machines in the following possible configurations.
Site Recovery Manager Administration Protection and Recovery of Virtual Machines with Snapshots Array-based replication supports the protection and recovery of virtual machines with snapshots, but with limitations. You can specify a custom location for storing snapshot delta files by setting the workingDir parameter in VMX files. Site Recovery Manager does not support the use of the workingDir parameter. Limitations also apply if you are running versions of ESX or ESXi Server older than version 4.1.
Chapter 9 Interoperability of Site Recovery Manager with Other Software Protection and Recovery of Virtual Machines Attached to RDM Disk Devices The 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. n Array-based replication supports RDM devices in physical compatibility mode and in virtual compatibility mode.
Site Recovery Manager Administration The location of the VMX file of a virtual machine determines which array pair a virtual machine belongs to. A virtual machine cannot belong to two array pairs, so if it has more than one disk and if one of those disks is in an array that is not part of the array pair to which the virtual machine belongs, Site Recovery Manager cannot protect the whole virtual machine.
Advanced Site Recovery Manager Configuration 10 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 Procedure 1 In the vSphere Web Client, click Site Recovery > Sites, and select a site. 2 On the Manage tab, click Advanced Settings. 3 Select Export History and click Edit. 4 Change the value for exportHistory.numReports as needed. You can enter a value from 0 to 50. The default value is 5. 5 To choose not to export reports, change the value to zero (0). 6 Click OK to save your changes.
Chapter 10 Advanced Site Recovery Manager Configuration Change Logging Settings You can change the levels of logging that Site Recovery Manager provides for the Site Recovery Manager Server components. Site Recovery Manager Server operates log rotation. When you restart Site Recovery Manager Server, or when a log file becomes large, Site Recovery Manager Server creates a new log file and writes subsequent log messages to the new log file.
Site Recovery Manager Administration 4 Click Edit to modify the logging settings. By default, all components record verbose level logs, unless stated otherwise in the description of the logging level. 5 Option Description Set logging level for all components that do not have an entry in logManager. The default is verbose. Select a logging level from the logManager.Default drop-down menu. Set logging level for the external API module. The default is verbose.
Chapter 10 Advanced Site Recovery Manager Configuration Change Recovery Settings You can adjust default values for timeouts that occur when you test or run a recovery plan. You might adjust default values if tasks fail to finish because of timeouts. Several types of timeouts can occur when recovery plan steps run. These timeouts cause the plan to pause for a specified interval to give the step time to finish.
Site Recovery Manager Administration 5 Option Action Change the delay after powering on a virtual machine before starting dependent tasks. The default value is 0. Enter a new value in the recovery.powerOnDelay text box. The new value applies to power-on tasks for virtual machines at the recovery site. Change the timeout to wait for VMware Tools when powering on virtual machines. The default value is 300 seconds. Enter a new value in the recovery.powerOnTimeout text box.
Chapter 10 Advanced Site Recovery Manager Configuration Procedure 1 In the vSphere Web Client, click Site Recovery > Sites, and select a site. 2 On the Manage tab, click Advanced Settings. 3 Click Remote Site Status. 4 Click Edit to modify the settings. 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 remoteSiteStatus.panicDelay text box.
Site Recovery Manager Administration 4 5 Click Edit to modify the storage settings. Option Action Change timeout in seconds for executing an SRA command. The default value is 300 seconds. Enter a new value in the storage.commandTimeout text box. Change the maximum number of concurrent SRA operations. The default value is 5. Enter a new value in the storage.maxConcurrentCommandCnt text box. Change the minimum amount of time in seconds between datastore group computations. The default value is 0.
Chapter 10 Advanced Site Recovery Manager Configuration VMware, Inc. Option Action Change the timeout in seconds to wait for Batch Attach LUN operation to complete on each ESXi host. The default value is 3600 seconds. Enter a value in the storageProvider.batchAttachTimeoutSec text box. Change the timeout in seconds to wait for Batch Detach LUN operation to complete on each ESXi host. The default value is 3600 seconds. Enter a value in thestorageProvider.batchDetachTimeoutSec text box.
Site Recovery Manager Administration 5 Option Action Identify VMX file paths that Site Recovery Manager should not consider as potential VMX file candidates after Storage vMotion. The default value is .snapshot, Some arrays create VMX file paths that the storageProvider.storageVmotionVmxSearch search algorithm should ignore. Enter a comma-separated list of strings in the storageProvider.storageVmotionVmxFilePathsToSkip text box to identify VMX file paths to ignore after Storage vMotion.
Chapter 10 Advanced Site Recovery Manager Configuration 5 Option Description Change the timeout period for reverse replication during reprotect operations. The default value is 3600. Enter a new value in the reverseReplicationTimeout text box. Change this value if you experience timeout errors when vSphere Replication reverses replication during reprotect operations. Change the timeout period for vSphere Replication synchronization operations. The default value is 7200.
Site Recovery Manager Administration 7 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 Recovery Manager\config folder. 8 Change the defaultMaxBootAndShutdownOpsPerCluster and defaultMaxBootAndShutdownOpsPerHost settings in the vmware-dr.xml file: ... 24 4 ...
Chapter 10 Advanced Site Recovery Manager Configuration Table 10‑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 Modify Settings for Long-Running Tasks If you run tasks that take a long time to complete, the default timeout period on the remote site might elapse before the task completes. You can configure additional timeouts to allow long-running tasks to finish. A long-running task might be the test recovery or cleanup of a large virtual machine. If a virtual machine has large disks, it can take a long time to perform a test recovery or to perform a full recovery.
Chapter 10 Advanced Site Recovery Manager Configuration 5 Add a element inside the tags. The must be at least 1/100th of the period. If you set a period that is less than 1/100th of the period, Site Recovery Manager silently adjusts the timeout.
Site Recovery Manager Administration 116 VMware, Inc.
Site Recovery Manager Events and Alarms 11 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 in the Manage of the vSphere Web Client lists all of the Site Recovery Manager alarms.
Chapter 11 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 11‑1.
Site Recovery Manager Administration Table 11‑1. Site Status Events (Continued) Event Description Cause LocalQsConnectionUpEvent The connection to the local inventory service is restored 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 nu mber of seconds in the vmware-dr.xml configuration file.
Chapter 11 Site Recovery Manager Events and Alarms Table 11‑2. Protection Group Replication Informational Events (Continued) Event Description Cause ProtectedVmReconfiguredRecoveryLocationS ettingsEvent 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 Recovery Events Recovery events provide information about actions and status related to the Site Recovery Manager recovery processes. Table 11‑5. Recovery Events 122 Event Description Cause RecoveryVmBegin Recovery plan has begun recovering the specified virtual machine. Signaled when the recovery virtual machine was successfully created. If some error occurred before the virtual machine ID is known the event is not fired.
Chapter 11 Site Recovery Manager Events and Alarms Table 11‑5. Recovery Events (Continued) Event Description Cause PlanServerCommandBegin Recovery plan has started to run a command on the Site Recovery Manager Server machine. Signaled on the recovery site when Site Recovery Manager has started to run a callout command on the Site Recovery Manager Server machine. PlanServerCommandEnd Recovery plan has completed executing a command on the Site Recovery Manager Server machine.
Site Recovery Manager Administration Table 11‑8. Array Pair Events Event Description Cause SAPairDiscoveredEvent Discovered replicated array pair with Array Manager. User created Array Manager which discovered replicated array pairs. SAPairEnabledEvent Enabled replicated array pair with Array Manager. User enabled an Array Pair. SAPairDisabledEvent Disabled replicated array pair with Array Manager. User disabled an Array Pair. SAPairPingOkEvent Ping for replicated array pair succeeded.
Chapter 11 Site Recovery Manager Events and Alarms Table 11‑10. Protection Events (Continued) Event Description Cause SPGroupProtRestoredEvent Protection has been restored for specified protection group. The previous (non-empty) issues of a protection group are cleared. SPVmDsProtMissingEvent Datastore used by virtual machine needs to be included in specified protection group.
Site Recovery Manager Administration Licensing Events Licensing events provide information about changes in Site Recovery Manager licensing status. Table 11‑11. Licensing Events Event Description Cause LicenseExpiringEvent The Site Recovery Manager License at the specified site expires in the specified number of days. Every 24 hours, non-evaluation, expiring licenses are checked for the number of days left. This event is posted with the results.
Chapter 11 Site Recovery Manager Events and Alarms SNMP Traps Site Recovery Manager sends SNMP traps to community targets defined in vCenter Server. You can configure them using the vSphere Web Client. When you enter localhost or 127.0.0.1 as a target host for SNMP traps, Site Recovery Manager uses the IP address or host name of the vSphere server as configured by the Site Recovery Manager installer. SNMP traps for Site Recovery Manager 5.x are backward compatible with Site Recovery Manager 4.
Site Recovery Manager Administration Table 11‑13. SNMP Traps (Continued) 128 Event Description Cause RecoveryPlanVmCommandBeginTrap This trap is sent when a recovery plan starts the execution of a command callout on a recovered virtual machine. Site Recovery Manager site name, recovery plan name, recovery type, execution state, command name, virtual machine name, virtual machine UUID.
Collecting Site Recovery Manager Log Files 12 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 12 Collecting Site Recovery Manager Log Files 4 Set the maximum size in megabytes of the logs to retain. You set the maximum log size by adding a section to the section. The default is 5 MB. 5 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 10 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. The possible logging levels are error, warning, info, trivia, and verbose.
Chapter 12 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 134 VMware, Inc.
Troubleshooting Site Recovery Manager 13 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 13 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 13 Troubleshooting Site Recovery Manager 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 the Timeout for the Creation of Placeholder Virtual Machines,” on page 107. You do not need to restart Site Recovery Manager Server after changing this setting.
Site Recovery Manager Administration 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. n The cluster on the recovery site is experiencing heavy resource use while trying to simultaneously recover multiple virtual machines. In this case you can increase certain timeout settings to allow more time for tasks to complete. See “Change Recovery Settings,” on page 105.
Chapter 13 Troubleshooting Site Recovery Manager . Cause When you run reprotect, Site Recovery Manager performs an online sync for the vSphere Replication protection group, which might cause the operation to timeout. The default timeout value is 2 hours. Solution Increase the synchronizationTimeout timeout value in Advanced Settings. See “Change vSphere Replication Settings,” on page 110.
Site Recovery Manager Administration 3 Add a element to the vmware-dr.xml file. You can add the element anywhere at the top level in the tags. Set the value of to at least 300 seconds. If you set the logging level to trivia, set to 1000 seconds. 1000 4 Save and close the vmware-dr.xml file.
Chapter 13 Troubleshooting Site Recovery Manager Solution To delay the start of storage rescans until the storage devices are available on the ESXi hosts, increase the storageProvider.hostRescanDelaySec setting to a value between 20 and 180 seconds. See “Change Storage Provider Settings,” on page 108. NOTE In Site Recovery Manager 5.1 and earlier, you might have used the storageProvider.hostRescanRepeatCnt parameter to introduce a delay in recoveries. Use the storageProvider.
Site Recovery Manager Administration 144 VMware, Inc.
Index A Active Directory domain controllers, limits on protection 97 Admission Control clusters, using with SRM 97 Advanced Settings, vSphere Replication 110 advanced settings local site 102 logging 103 long-running tasks 114 recovery 105 remote site 106 replication 107 storage 107 Advanced Settings dialog boxes 101 affinity rules, limits on recovery 97 alarms, Site Recovery Manager-specific 118 all paths down (APD) 49 all paths down, recovery plans 43 apply IP customization rule to a virtual machine 80 ar
Site Recovery Manager Administration forced recovery 44, 49 G generate manually 130 H High Availability, and SRM 94 host-based replication 26 I installation, of storage replication adapter 22 interoperability 91 inventory mappings, apply to all virtual machines in a protection group 35 IP customization DR IP Customizer 67 multiple virtual machines 67 subnet-level IP customization rules 67 IP properties, customizing 65, 66 IP address mappings, to report 68 IP customization, subnet IP mapping rules 80 IP
Index command steps 60 configure VM dependencies 62 create 46 customizing 55 deleting 52 differences between testing and running 45 disaster recovery 43 export history 51 export steps 51 force cleanup 48 forced recovery 44, 49 planned migration 43 privileges 45 run 41, 46 running 43, 45, 49 steps 56 suspend virtual machines 61 test, create 41 testing 42, 45, 48 time-outs 56 to change properties of 47 to report IP address mappings used by 68 view history 51 virtual machine recovery priority 56 VM shutdown o
Site Recovery Manager Administration troubleshooting recovery 139 recovery times out 139 U updated information 9 V vCenter, and Site Recovery Manager 91 vCenter Orchestrator list of operations 95 SRM plug-in 95 vCenter Server, administrator role 13 vCenter Server administrator 13 vCenter Server Appliance, and SRM 91 vCO list of operations 95 SRM plug-in 95 virtual machines, dependency 62 Virtual SAN 26, 48 virtual machine customize IP properties 78 recovery priority 56, 61 suspend during recovery 61 virt
