Site Recovery Manager Administration Guide vCenter Site Recovery Manager 5.0 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 Guide 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–2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About This Book 7 1 Administering VMware vCenter Site Recovery Manager 9 SRM Deployment 10 Protected Sites and Recovery Sites 11 Array-Based Replication 11 vSphere Replication 12 About Protection Groups and Recovery Plans 13 Testing and Running a Recovery Plan 14 About Reprotect 16 About Failback 16 About the Site Recovery Manager Database 16 SRM and VMware vCenter Server 17 SRM Licensing 18 SRM Authentication 18 Requirements When Using Public Key Certificates Understanding Roles and Permissions
Site Recovery Manager Administration Guide Install the SRM License Key 42 3 Establishing Inventory Mappings and Placeholder Datastores 43 Understanding Placeholder Datastores 43 Configure a Placeholder Datastore 44 Configure Datastore Mappings for vSphere Replication Management Select Inventory Mappings 44 44 4 Configuring Array-Based Protection 47 Configure Array Managers 47 Rescan Arrays to Detect Configuration Changes Edit Array Managers 48 48 5 Installing vSphere Replication Servers 51 Deploy a
Contents 8 Customizing Site Recovery Manager 75 Customizing a Recovery Plan 75 Recovery Plan Steps 75 Customize Recovery Plan Steps 77 Customize the Recovery of an Individual Virtual Machine 80 Customize IP Properties For an Individual Virtual Machine 80 Report IP Address Mappings for a Protection Group 82 Understanding Customizing IP Properties for Multiple Virtual Machines 82 Configure Protection for a Virtual Machine or Template 86 Configure Resource Mappings for a Virtual Machine 87 Configure SRM Alar
Site Recovery Manager Administration Guide 6 VMware, Inc.
About This Book ® VMware vCenter Site Recovery Manager (SRM) is an extension to VMware vCenter that delivers a business continuity and disaster recovery solution that helps you plan, test, and execute the recovery of vCenter virtual machines. SRM can discover and manage replicated datastores, and automate migration of inventory from one vCenter to another.
Site Recovery Manager Administration Guide Technical Support and Education Resources The following technical support resources are available to you. To access the current version of this book and other books, go to http://www.vmware.com/support/pubs. Online and Telephone Support To use online support to submit technical support requests, view your product and contract information, and register your products, go to http://www.vmware.com/support.
Administering VMware vCenter Site Recovery Manager 1 VMware vCenter Site Recovery Manager (SRM) is a business continuity and disaster recovery solution that helps you plan, test, and execute the recovery of vCenter virtual machines between one site (the protected site) and another site (the recovery site). You can configure SRM to work with several third-party disk replication mechanisms (array based replication) or with VMware vSphere Replication. Two types of recovery are available.
Site Recovery Manager Administration Guide n “Understanding Roles and Permissions,” on page 20 n “SRM Network Ports,” on page 23 n “Connecting to SRM,” on page 24 n “Operational Limits of Site Recovery Manager,” on page 24 SRM Deployment You must complete several groups of tasks to configure SRM. You complete some tasks in all cases, and you complete some tasks only for vSphere Replication (VR) or for array based replication.
Chapter 1 Administering VMware vCenter Site Recovery Manager Protected Sites and Recovery Sites In a typical SRM installation, the protected site provides business-critical datacenter services. The recovery site is an alternative facility to which these services can be migrated. The protected site can be any site where vCenter supports a critical business need. The recovery site can be located thousands of miles away.
Site Recovery Manager Administration Guide How Site Recovery Manager Computes Datastore Groups The composition of a datastore group is determined by the set of virtual machines that have files on the datastores in the group, and by the devices on which those datastores are stored. When you use array-based replication, each storage array supports a set of replicated devices.
Chapter 1 Administering VMware vCenter Site Recovery Manager About Protection Groups and Recovery Plans A protection group is a collection of virtual machines and templates. A recovery plan specifies how the virtual machines in a specified set of protection groups are recovered. In the case of virtual machines replicated using array-based replication, protection groups are composed of virtual machines that use the same replicated datastore group.
Site Recovery Manager Administration Guide About Placeholder Virtual Machines and Inventory Mapping For each virtual machine that you add to a protection group, SRM creates a placeholder at the recovery site. These placeholders are added to, and can be managed as part of, the recovery site's inventory.
Chapter 1 Administering VMware vCenter Site Recovery Manager Table 1-1. Differences Between Testing and Running a Recovery Plan (Continued) Test a Recovery Plan Run a Recovery Plan Effect on virtual machines at recovery site Local virtual machines are suspended if required by the plan. Suspended virtual machines are restarted after the test is cleaned up. Local virtual machines are suspended if required by the plan.
Site Recovery Manager Administration Guide About Reprotect With reprotect, you can protect recovered virtual machines after a recovery back to the original protected site, including reversing the direction of replication. Reprotect uses the protection information that was established before a recovery to reverse the direction of protection. You can complete the Reprotect process after a recovery is finished.
Chapter 1 Administering VMware vCenter Site Recovery Manager User Name and Password This authentication information is required so that SRM can use the database. Connection Count The initial connection pool size. If all connections are in use and a new one is needed, a connection is created as long as it does not exceed the maximum number of connections allowed. It is faster for SRM to use a connection from the pool than to create a new one. In most cases, it is not necessary to change this setting.
Site Recovery Manager Administration Guide SRM and Other vCenter Server Solutions You can run other VMware solutions such as vCenter Update Manager, vCenter Server Heartbeat, VMware Fault Tolerance, and vCenter CapacityIQ in deployments that you protect using SRM. However, use caution before connecting other VMware solutions to the vCenter Server instance to which the SRM server is connected.
Chapter 1 Administering VMware vCenter Site Recovery Manager Certificate-Based Authentication If you have or can acquire a PKCS#12 certificate signed by a trusted authority, use certificate-based authentication. Public key certificates signed by a trusted authority streamline many SRM operations and provide the highest level of security. Certificates used by SRM have special requirements. See “Requirements When Using Public Key Certificates,” on page 19.
Site Recovery Manager Administration Guide n The certificate used by each member of an SRM server pair must include an extendedKeyUsage or enhancedKeyUsage attribute whose value is serverAuth, clientAuth. If you are using an openssl CA, modify the openssl configuration file to include a line like the following: extendedKeyUsage = serverAuth, clientAuth n The SRM certificate password must not exceed 31 characters.
Chapter 1 Administering VMware vCenter Site Recovery Manager Assign Roles and Permissions Permission assignments apply on a per-site basis. After installation only vCenter Administrators can log into SRM. To allow other users access, vCenter Administrators must grant them permissions in the SRM UI. You must add corresponding permission on both sites. SRM requires permissions on vCenter objects as well as SRM objects.
Site Recovery Manager Administration Guide Table 1-2.
Chapter 1 Administering VMware vCenter Site Recovery Manager Table 1-2.
Site Recovery Manager Administration Guide Table 1-4. How VRMS Uses Network Ports Default Port Protocol or Description 80 Endpoints or Consumers All traffic to SRM servers through the vCenter Server proxy. 8043 SOAP VRM and the vCenter Server proxy. 8080 VAMI Web UI Administrator's web browser. Table 1-5. How VR Servers Use Network Ports Default Port Protocol or Description Endpoints or Consumers 8123 SOAP Management traffic used by VRMS to manage the VR Servers.
Chapter 1 Administering VMware vCenter Site Recovery Manager Table 1-6. SRM Protection Limits for Array Based Protection Item Maximum Protected virtual machines per protection group 500 Protected virtual machines 1000 Protection groups per recovery plan 150 Datastore groups 150 Concurrent recoveries 10 Table 1-7.
Site Recovery Manager Administration Guide 26 VMware, Inc.
Installing and Updating Site Recovery Manager 2 You must install an SRM server at the protected site and also at the recovery site. After the SRM servers are installed, you can download the SRM client plug-in from either SRM server using the Manage Plugins menu from your vSphere Client. You use the SRM client plug-in to configure and manage SRM at each site. Prerequisites SRM requires that a vCenter Server be installed at each site prior to installing SRM.
Site Recovery Manager Administration Guide Configuring the SRM Database Each SRM server requires its own database to store recovery plans, inventory information, and similar data. Before installing the SRM server, you must configure and initialize the SRM database. If you are updating SRM to a new release, you can use the existing database. Before attempting an SRM environment upgrade, ensure both SRM server databases are backed up. This helps ensure you can revert after the upgrade, if required.
Chapter 2 Installing and Updating Site Recovery Manager n create session DB2 Server Configuration A DB2 Server configuration must meet specific requirements to support SRM. DB2 Server has the following configuration requirements when used as the SRM database: n When creating the database instance, specify utf-8 encoding. n Because DB2 uses Windows authentication, specify the database owner as a domain account.
Site Recovery Manager Administration Guide Microsoft SQL Server Configuration A Microsoft SQL Server configuration must meet specific requirements to support VRM. You must configure these requirements in Microsoft SQL Server. n You can use either a named instance or the default instance of SQL Server. n Enable TCP on the database instance. n Use a static TCP port, for example set to the default of 1433. Alternatively, to use dynamic TCP ports, you must perform additional configuration.
Chapter 2 Installing and Updating Site Recovery Manager DB2 Server Configuration A DB2 Server configuration must meet specific requirements to support VRM. DB2 Server has the following configuration requirements when used as the VRM database. n When creating the database instance, specify utf-8 encoding. n DB2 uses Windows authentication, so you must specify the database owner as a domain account.
Site Recovery Manager Administration Guide 6 Select the folder in which to install SRM and click Next. The default installation folder for a new installation of SRM is C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager. If you use a different folder, the pathname cannot be longer than 240 characters and cannot include non-ASCII characters. 7 (Optional) Select whether or not to install vSphere Replication functions. Installing vSphere Replication enables additional functions.
Chapter 2 Installing and Updating Site Recovery Manager 11 Type the SRM database configuration information and click Next. Option Action Database Client Select a database client type from the drop-down menu. Data Source Name Select an existing DSN from the drop-down menu,. You can also click ODBC DSN Setup to view existing DSNs or create a system DSN. Username A user ID valid for the specified database. Password Password for the specified user ID. Connection Count Initial connection pool size.
Site Recovery Manager Administration Guide n SRM object permissions in vSphere n Custom alarms and alarm actions n Test plan histories n Security certificates n Mass IP customization files (CSVs) New Behavior for 5.0 Because of the significant changes introduce in SRM 5.0, including modifications to the database schemas, an upgrade while the system is running is not possible.
Chapter 2 Installing and Updating Site Recovery Manager Table 2-1. vCenter Upgrade Paths for SRM Upgrade Type Description Supported In-place upgrade The simplest upgrade path. This path involve upgrading those vCenter Servers associated with SRM before upgrading SRM. Yes Upgrade with migration If you need to migrate an SRM server to a different host or virtual machine as part of the SRM upgrade, VMware recommends that you first uninstall the existing SRM 4.
Site Recovery Manager Administration Guide 2 Download the SRM installation file to a folder on the host, or open a folder on the network that contains this file. For faster starting and installing, copy the installation file to a local temporary folder. 3 Double-click the SRM installer icon to begin installation. 4 When prompted to verify that you want to update the existing installation, click Yes. 5 Click Next. 6 Click Yes to confirm that you backed up the database.
Chapter 2 Installing and Updating Site Recovery Manager Procedure 1 Use the vSphere Client to pair the SRM servers. 2 Configure SRM storage. Use the storage report generated by the installer for required information. a Refresh SRAs on both the local and remote site. SRM 5.0 requires different versions of SRAs from previous versions such as SRM 4.1. 3 b Create array managers for the SRAs. c Enable replicated array pairs. d Verify datastores are replicated as expected. Use the srm-migration.
Site Recovery Manager Administration Guide Install Storage Replication Adapters If you are using array-based replication, you must install a Storage Replication Adapter (SRA). An SRA is a program provided by an array vendor that enables SRM to work with a specific kind of array. You must install an appropriate SRA on the SRM server hosts at the protected and recovery sites. If you are using vSphere Replication (VR), an SRA is not required.
Chapter 2 Installing and Updating Site Recovery Manager Procedure 1 Start the vSphere Client and connect to vCenter Server at the protected or recovery site. 2 Select Plugins > Manage Plugins. 3 In the Available Plug-ins area , right-click the VMware vCenter Site Recovery plug-in and click Download and Install. 4 After the download finishes, click Next to start the wizard. 5 Click I accept the terms in the license agreement, and click Next. 6 Click Install.
Site Recovery Manager Administration Guide Revert to a Previous Release To revert to a previous release, uninstall the current SRM server release from the protected and recovery sites, uninstall the SRM plug-in, and restore the SRM database from the backup you made before you updated the SRM server. You can then install the previous release and use the restored database. Prerequisites Verify that that the current installation of vCenter supports that release.
Chapter 2 Installing and Updating Site Recovery Manager Procedure 1 Log in to the SRM server host. 2 Open the Windows Add or Remove Software tool. 3 Navigate to the entry for VMware vCenter Site Recovery Manager and click Change to start the installer in repair mode. 4 Click Next. 5 Select Modify or Repair and click Next. 6 Option Description Repair Fixes issues in the SRM Server installation. Selecting Repair runs the installer in repair mode without any user input. Go to Step 10.
Site Recovery Manager Administration Guide 11 When the repair operation is finished and the SRM server restarts, log in to the SRM interface in the vSphere client to check the status of the connection between the protected site and the recovery site. 12 (Optional) If the connection between the protected site and the recovery site is broken, reconfigure the connection, starting from the SRM server that you updated. Install the SRM License Key The SRM server requires a license key to operate.
Establishing Inventory Mappings and Placeholder Datastores 3 The protection provided by SRM is supported by placeholder datastores, datastore mappings, and inventory mappings.
Site Recovery Manager Administration Guide Configure a Placeholder Datastore Specify a placeholder datastore for SRM to use for the storage of placeholder virtual machines. Prerequisites Verify that sites are connected and paired. Procedure 1 Click Sites in the left pane, and select a site 2 Click the Placeholder Datastores tab. 3 Click Configure Placeholder Datastore. 4 Expand the folders to find a datastore to designate as the location for placeholder datastores, click the datastore, and click OK.
Chapter 3 Establishing Inventory Mappings and Placeholder Datastores machine cannot be protected unless it has some form of valid inventory mappings for networks, folders, and compute resources. Inventory mappings can be created at both protection and recovery site. After having established mappings at the protected site when configuring protection, you should also configure inventory mappings at the recovery site.
Site Recovery Manager Administration Guide 46 VMware, Inc.
Configuring Array-Based Protection 4 After you pair the protected and recovery sites, you must configure protection for virtual machines. If you are using array-based replication, configure storage replication adapters (SRAs) at each site, and then configure SRM at each site. If you are using only vSphere Replication, array managers are not required, and you can go to Chapter 5, “Installing vSphere Replication Servers,” on page 51.
Site Recovery Manager Administration Guide 3 Provide an SRA name and select an adapter type. a Type a name for the array in the Display Name text box. Use a descriptive name that makes it easy for you to identify the storage associated with this array manager. b Ensure that the array manager type that you want SRM to use appears in the SRA Type field. If more than one SRA has been installed on the SRM server host, click the drop-down arrow and select a manager type.
Chapter 4 Configuring Array-Based Protection 3 Modify the name for the array in the Display Name field. Use a descriptive name that makes it easy for you to identify the storage associated with this array manager. The array manager type cannot be modified. 4 Modify the adapter information. These fields are created by the SRA. 5 VMware, Inc. Click Finish to complete the modification of the array manager.
Site Recovery Manager Administration Guide 50 VMware, Inc.
Installing vSphere Replication Servers 5 vSphere Replication (VR) uses replication technologies included in ESX Servers with the assistance of virtual appliances to replicate virtual machines between sites. VR is provided by vSphere Replication Servers (VR Servers or VRS). VR Servers are managed by the vSphere Replication Management Server (VRMS). Both VRMS and VR Servers are virtual appliances. To use VR you must deploy exactly one VRMS server at each site and at least one VR Server at the recovery site.
Site Recovery Manager Administration Guide Deploy a vSphere Replication Management Server Before using vSphere Replication (VR), you need to deploy a vSphere Replication Management Server (VRMS) from the SRM UI, thereby creating the framework to support VR. VR requires that VRMS be deployed at each site. Prerequisites n Verify that you have a static IP address. n Verify that the SRM database has been set up. n Verify that you enabled the VR option during SRM installation.
Chapter 5 Installing vSphere Replication Servers Procedure 1 Connect to the VRMS Web interface. 2 Provide the user name and password for the server. The user name is root and the password is configured during the OVF deployment of the VRMS. 3 Click the VRMS tab and click Configuration. 4 In Configuration mode, select manual configuration to specify a configuration or select Configure from an Existing VRMS Database to use a previously established configuration.
Site Recovery Manager Administration Guide 5 Review the current SSL information. Configure VRMS Network Settings You can review current network settings and change address and proxy settings for the VRMS Server. You might makes these changes to match network reconfigurations. Procedure 1 In the SRM interface, click the Getting Started tab, and click Configure VRMS Server to connect to the VRMS server.
Chapter 5 Installing vSphere Replication Servers 5 Click the Information button. For this server virtual appliance, you can review information about: n Appliance vendor n Appliance name n Appliance version n Hostname n Appliance operating system and version. a Click View for information about the OVF environment. b Click Reboot to reboot the virtual appliance. c Click Shutdown to shutdown the virtual appliance.
Site Recovery Manager Administration Guide The VRS, which is a virtual appliance, is stored with the SRM server. VRS servers should be deployed at a site after a VRMS server is deployed and configured for that site. If problems occur when deploying the VRS using the SRM interface, the VRS OVF file can be found in the SRM installation directory. This file can be used to manually deploy the appliance from the vSphere Client by selecting Deploy OVF Template from the File menu.
Chapter 5 Installing vSphere Replication Servers Register a vSphere Replication Server You must register the vSphere Replication Server (VRS) with the vSphere Replication Management Server (VRMS) to enable vSphere Replication (VR). Prerequisites n Configure a VRMS as described in “Configure vSphere Replication Server Settings,” on page 56. n Verify that the VRMS is paired as described in “Configure vSphere Replication Management Connections,” on page 55.
Site Recovery Manager Administration Guide 58 VMware, Inc.
Creating Protection Groups and Replicating Virtual Machines 6 After you configure a replication solution, you create protection groups. You can also customize the configuration of virtual machine replication and protection.
Site Recovery Manager Administration Guide n If a virtual machine is attached to a Raw Disk Mapping (RDM) disk device, you must store the mapping file in the same folder as the VMX file. RDM snapshots are only available if you create the RDM mapping using Virtual Compatibility Mode. If you are running a ESX or ESXi Server 4.1 or later, these limitations do not apply. vSphere Replication supports the protection of virtual machines with snapshots, but you can only recover the latest snapshot.
Chapter 6 Creating Protection Groups and Replicating Virtual Machines SRM creates a protection groups that you can use to protect virtual machines. After protection is established, placeholders are created and inventory mappings applied for each virtual machine in the group. If a virtual machine cannot be mapped to a folder, network, and resource pool on the recovery site, it is listed with a status of Mapping Missing, and a placeholder is not created for it.
Site Recovery Manager Administration Guide What to do next Next create a recovery plan with which to associate your protection groups. This process is described in “Create a Recovery Plan,” on page 67. Edit vSphere Replication Protection Groups You can change the name of a vSphere Replication (VR) protection group and the virtual machines that are protected in the group. Procedure 1 Click Protection Groups in the left pane and right-click a protection group. 2 Select Edit Protection Group.
Chapter 6 Creating Protection Groups and Replicating Virtual Machines 4 Configure general replication settings. a Use the Recovery Point Objective (RPO) slider or enter a value to configure the maximum amount of data that can be lost in the case of a site failure. The available range is from 15 minutes to 24 hours. For example, a recovery point objective of one hour seeks to ensure that the virtual machine loses no more than one hour of data during the recovery.
Site Recovery Manager Administration Guide Before replicating multiple machines, configure datastore mappings in the SRM user interface. For more information, see “Configure Datastore Mappings for vSphere Replication Management,” on page 44. You configure the mappings so that information is available to SRM regarding the target datastore destinations for replication. Procedure 1 On the vSphere Client Home page, click VMs and Templates.
Chapter 6 Creating Protection Groups and Replicating Virtual Machines 2 Click Datastores. In the left pane, browse to the datastore that contains the files for the virtual machine, select the datastore, and in the right pane, click Browse this datastore. 3 Select the folders for all virtual machines to be couriered, right-click the selection, and click Download... 4 Select a destination to which to copy the files and click OK. 5 Click Yes.
Site Recovery Manager Administration Guide Move a Virtual Machine to a New vSphere Replication Server After establishing vSphere Replication (VR), you can move the virtual machines being replicated to other VR Servers. You might do this to complete maintenance tasks on existing VR servers or to balance the load on VR servers in the event that one server becomes overloaded with virtual machines. Procedure 1 Click vSphere Replication, and select a site. 2 Click the Virtual Machines tab.
Recovery Plans and Reprotection 7 After you have configured SRM at the protected and recovery sites, you can create and test a recovery plan without affecting services at either site. You can also perform planned migrations or disaster recoveries by running a recovery plan, and, if necessary, reverse the role of your two sites by performing a reprotect. The test does not disrupt replication or any ongoing activities at the protected site.
Site Recovery Manager Administration Guide 4 Select a recovery site network to which recovered virtual machines connect during recovery plan tests, and click Next. 5 Type a name for the plan in the Recovery Plan Name text box and add an optional description. 6 Click Next. 7 Review the summary information and click Finish to create the recovery plan.
Chapter 7 Recovery Plans and Reprotection Procedure 1 Click Recovery Plans in the left pane. 2 Click the recovery plan to test, and click Test. 3 Determine whether to enable Replicate recent changes to recovery site. Enabling this option ensures that the recovery site has the latest copy of protected virtual machines, but the synchronization might take additional time. 4 Click Next. 5 Review the confirmation window and click Finish. The wizard closes and the recovery plan test begins.
Site Recovery Manager Administration Guide Run a Recovery Plan When you run a recovery plan, all virtual machines in the recovery plan are migrated to the recovery site. The corresponding virtual machines in the protected site are shut down. When you perform a planned migration, SRM attempts to replicate all virtual machines and gracefully shut down the protected machines. If errors occur during a planned migration, the plan pauses so that users can resolve errors.
Chapter 7 Recovery Plans and Reprotection 3 Review the information in the confirmation prompt, and select I understand that this process will permanently alter the virtual machines and infrastructure of both the protect and recovery datacenters. 4 (Optional) If you enabled the forced failover function, you can select the Forced Failover - recovery site operations only check box. 5 Click Next. 6 Click Start to run the recovery plan. 7 Click the Recovery Steps tab.
Site Recovery Manager Administration Guide Reprotection of MCSC and Fault Tolerant Virtual Machines To use reprotection with Microsoft Cluster Server (MSCS) and fault tolerant virtual machines, the 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 Servers. n You can run a cluster of MCSC virtual machines in the following possible configurations.
Chapter 7 Recovery Plans and Reprotection Reprotection State Reference As the process of reprotection proceeds, there are several states that can be observed in the recovery plan in the vSphere client SRM plug-in in the vSphere Client. Table 7-1. Reprotection States State Description Reprotect In Progress SRM is attempting to complete the process of reprotection. If reprotection fails, the result is the state "Reprotect Interrupted".
Site Recovery Manager Administration Guide 74 VMware, Inc.
Customizing Site Recovery Manager 8 In its default configuration, SRM enables a number of simple recovery scenarios. Advanced users can customize SRM to support a broader range of site recovery requirements. The default protection and recovery capabilities of SRM can be appropriate for sites that have simple configurations or recovery objectives.
Site Recovery Manager Administration Guide n Some steps are always skipped during test recoveries. Understanding the steps, their order, and the context in which they run is important when you customize a recovery plan. NOTE When you run a recovery plan, it starts by powering off the virtual machines at the protected site. Machines are powered off in reverse priority order (high-priority machines are powered off last). This step is omitted when you test a recovery plan.
Chapter 8 Customizing Site Recovery Manager n Batch files or commands that produce output that contains characters with ASCII values greater than 127 must use UTF-8 encoding. Only the final 4KB of script output is captured in log files and recovery history. Scripts that produce more output can redirect the output to a file rather than sending it to the standard output to be logged.
Site Recovery Manager Administration Guide Specify Virtual Machine Recovery Priority By default, all virtual machines in a new recovery plan are members of the level 3 priority group. Members of this group are recovered in the order that they were created on the protected datastore. You can move a virtual machine to a different priority group or to a different priority within a group. Procedure 1 Open the Recovery Steps page for the plan, as described in “Customize Recovery Plan Steps,” on page 77.
Chapter 8 Customizing Site Recovery Manager During the reprotect for a recovery plan, all custom recovery steps are preserved in the recovery plan. However, if a recovery or test is done for the recovery plan after a reprotect, these custom recovery steps are executed on the new recovery site (the original protected site). Typically, you can use prompt custom recovery steps directly without any modifications.
Site Recovery Manager Administration Guide 3 Select a virtual machine and click Configure. 4 Select Pre-Power On Steps or Post Power On Steps in the left pane, and click Add, Edit, or Remove. 5 If you click Add or Edit, configure the step. a Select the type of Step to be completed: a step on the SRM server, a step on the virtual machine, or a prompt. Complete pre-power on steps on the SRM server. b In the Name field, type a name for the step.
Chapter 8 Customizing Site Recovery Manager n Different IP customizations for each site. n DHCP, Static IPv4, or Static IPv6 addressing. n Address customization for Windows and Linux virtual machines. n Customizing multiple NICs for each virtual machine. You can also apply IP customizations to multiple virtual machines. SRM includes the ability for the vSwitches to be DVS based and, therefore, span hosts.
Site Recovery Manager Administration Guide 8 Click the WINS tab to enter primary and secondary WINS addresses. The WINS tab is available only when configuring DHCP or IPv4 addresses for Windows virtual machines. 9 Repeat Step 5 through Step 8 to configure recovery or protection settings, if required. For example, if you configured IP settings for the protected site, you might want to configure settings for the recovery site.
Chapter 8 Customizing Site Recovery Manager Customize IP Properties for Multiple Virtual Machines Use the dr-ip-customizer.exe tool on a computer with access to vCenter Servers in your environment to specify IP properties for any or all of the virtual machines in a recovery plan by editing a file that the tool generates. Configure IP settings for both protected and recovery sites so failback operations are easier to configure. Procedure 1 Open a command shell on the SRM server host.
Site Recovery Manager Administration Guide n --cmd arg Command to execute: n apply Applies the network customization settings from the input CSV file to the recovery plans on the SRM servers. n generate Generates a basic CSV file for the all virtual machines in the recovery plans on the SRM servers. n drop Removes virtual machine recovery settings from virtual machines specified by the input CSV file. n --csv arg Path to the CSV file. Read as input for the apply and drop commands.
Chapter 8 Customizing Site Recovery Manager Guidelines Follow these guidelines. n You can export protected virtual machine information to use as a template, rather than author a new CSV file manually. The generated file can provide a structure that you can modify to suit the needs of your environment. n Some restrictions exist on the ways in which DNS settings are applied.
Site Recovery Manager Administration Guide Table 8-3. Sample CSV File Contents vCen ter Serv er Seco ndar y Wins VM ID protect edvm-10 301 exam plevm-3 -win vc04. eng.e xamp le.co m 0 examp le.com protect edvm-10 301 exam plevm-3 -win vc04. eng.e xamp le.co m 0 eng.ex ample. com protect edvm-10 301 exam plevm-3 -win vc04. eng.e xamp le.co m 1 protect edvm-10 301 exam plevm-3 -win vc04. eng.e xamp le.co m 1 protect edvm-10 301 exam plevm-3 -win vc04. eng.e xamp le.
Chapter 8 Customizing Site Recovery Manager n If you use Storage VMotion to move a virtual machine to a nonreplicated datastore, or to a replicated datastore on an array that SRM has not been configured to manage (through an SRA), the virtual machine's protection is invalidated. You can use Storage VMotion to move a virtual machine to datastore that is part of another protection group, though.
Site Recovery Manager Administration Guide Configure SRM Alarms SRM adds feature-specific alarms to the ones supported by vCenter. You can configure SRM alarms to send an email notification, send an SNMP trap, or run a script on the machine that contains the vCenter Server. vCenter provides a comprehensive and flexible alarm facility. As a vCenter extension, SRM can add its own alarms to the ones provided by vCenter.
Chapter 8 Customizing Site Recovery Manager Change Recovery Site Settings Use the Advanced Settings Recovery page to adjust default values for time-outs that occur when you test or run a recovery plan. You might do this if tasks were failing to complete due to insufficient time. Several types of time-outs can occur during the execution of recovery plan steps. These time-outs cause the plan to pause for a specified interval to give the step time to finish.
Site Recovery Manager Administration Guide Procedure 1 Click Sites in the left pane, and right-click the site whose settings you want to change. 2 Click Advanced Settings. 3 Click storageProvider. 4 Modify the SAN provider settings. n To force removal, upon successful completion of a recovery, of the snap-xx prefix applied to recovered datastore names, select the storageProvider.fixRecoveredDatastoreNames check box.
Chapter 8 Customizing Site Recovery Manager Change Remote Site Settings Use the Advanced Settings remoteSiteStatus page to modify default values that the SRM server at the site to which the vSphere Client is currently connected uses to determine whether the SRM server at the remote site is available SRM monitors the connection between the members of an SRM site pair (a protected site and its recovery site) and, by default, raises alarms when this connection is interrupted.
Site Recovery Manager Administration Guide Change Replication Setting You can adjust replication settings to modify how long SRM waits for virtual machine placeholder creation to complete. Procedure 1 Click Sites, and right-click the site whose settings you want to change. 2 Click Advanced Settings. 3 Click replication. 4 Change the replication.placeholderVmCreationTimeout setting to modify the number of seconds to wait when creating a placeholder virtual machine. 5 Click OK to save your changes.
Troubleshooting SRM 9 If you have problems with replication, site pairing, or guest customization, you can troubleshoot the problem. To help identify the cause, you might need to collect SRM server or client log files to review or send to VMware Support. Errors encountered during SRM operations appear in error dialog boxes or appear in the Recent Tasks window. Most errors also generate an entry in an SRM log files. Check the recent tasks and log files for the recovery site and the protected site.
Site Recovery Manager Administration Guide Connection Monitor Algorithm Connection related events are produced according to this algorithm: 1 When administrative connection between two paired SRM servers is established SRM server that initiated the connection raises RemoteSiteUpEvent. 2 When SRM detects that a monitored connection is down it starts a periodic connection check. Time interval for these pings is configurable through the remoteSiteStatus.pingInterval advanced setting.
Chapter 9 Troubleshooting SRM Table 9-2. Protection Group Replication Informational Events Event Key Event Description Cause ProtectionGroup > CreatedEvent Created protection group. Posted on both vCenter Servers in the completion of the Commit phase of creating a protection group. ProtectionGroup > RemovedEvent Removed protection group. Posted on both vCenter Servers in the completion of the Commit phase of removing a protection group.
Site Recovery Manager Administration Guide Table 9-4. Protection Group Replication Error Events Event Key Event Description Cause ProductionVmDeletedEvent Virtual machine in group: The production virtual machine has been removed from the virtual machineware vCenter Server inventory. Posted when we detect that the protected virtual machine’s production virtual machine has been deleted or removed from the vCenter inventory.
Chapter 9 Troubleshooting SRM Table 9-5. Recovery Events (Continued) Event Key Event Description Cause RecoveryPlanExecuteReprotectBegin Recovery Plan has begun a reprotect operation. Signaled on the recovery site when a reprotect is initiated. RecoveryPlanExecuteReprotectEnd Recovery Plan has completed a reprotect operation. Signaled on the recovery site when a reprotect has completed. If an error occurred it is available as described.
Site Recovery Manager Administration Guide Table 9-6. SNMP Traps (Continued) Type Description Content RecoveryPlanExecuteReprotectBeginTr ap This trap is sent when SRM starts the reprotect workflow for a Recovery Plan. SRM site name, recovery plan name, recovery type, execution state. RecoveryPlanExecuteReprotectEndTra p This trap is sent when SRM has finished the reprotect workflow for a Recovery Plan. SRM site name, recovery plan name, recovery type, execution state, result status.
Chapter 9 Troubleshooting SRM Table 9-8. Array Manager Events Type Description Content StorageArrayManagerAdded Created the specified array manager using the specified SRA. User added an Array Manager. StorageArrayManagerRemoved Deleted the specified array manager. User removed an Array Manager. StorageArrayManagerReconfigured Reconfigured the specified array manager. User edited Array Manager properties. StorageArrayManagerPingOk Ping for the specified array manager succeeded.
Site Recovery Manager Administration Guide Table 9-11. Protection Events (Continued) 100 Type Description Content StorageProviderDatastoreProtectionMi ssing Replicated datastore needs to be included in specified protection group. See description. StorageProviderDatastoreProtectionCo nflict Replicated datastore needs to be included in specified protection group but is included in an alternate protection group. See description.
Chapter 9 Troubleshooting SRM Licensing Events Licensing events provide information about changes in SRM licensing status. Table 9-12. Licensing Events Type Description Content LicenseExpiringEvent The SRM 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.
Site Recovery Manager Administration Guide Collecting SRM Log Files SRM creates several log files that contain information that can help VMware Support diagnose problems. You can use the SRM log collector to simplify log file collection. The SRM server and client use different log files. The SRM server log files contain information about the server configuration and messages related to server operations.
Chapter 9 Troubleshooting SRM n To initiate the collection of SRM server log files from the Windows command line: a Start a Windows command shell on the SRM server host. b Change directory to C:\Program Files (x86)\VMware\VMware vCenter Site Recovery Manager\bin. c Run the following command. cscript srm-support.wsf The individual log files are collected in a file named srm-support-MM-DD-YYYY-HH-MM.
Site Recovery Manager Administration Guide Solution 1 Use a file management tool to connect to the VRMS appliance. For example, you might use SCP or WinSCP. Connect using the root account, which is the same account used to connect to VAMI. 2 Delete any files you find in /opt/vmware/vrms/logs. 3 Connect to VAMI and attempt to save the VRMS configuration. This action recreates the SQL error. 4 Connect to the VRMS appliance again and find the hms.log file which is in /opt/vmware/vrms/logs.
Index A administration, overview of 9 advanced setting dialog box, vSphere replication 92 advanced setting dialog boxes replication 92 storage 91 advanced settings dialog box, recovery site 89 advanced settings dialog boxes guest customization 88 local site 90 remote site 91 SAN provider 89 Advanced Settings dialog boxes 88 alarms, SRM-specific 88 array based protection group, edit 61 array based recovery plan, create 67 array managers and storage replication adapters 47 edit 48 replicated device discovery
Site Recovery Manager Administration Guide to repair 40 updating to a new release 35 inventory mappings about 14 and placeholders 14 to apply 66 to create 44 to override 86, 87 IP address mappings to customize 83 to report 82 IP properties, customizing 80 L license key, to install 42 licensing about 18 events 101 license key 42 linked clones, limitations on recovery of 59 log files collecting 102 SRM server 102 logs, downloading 102 M managing 24 N network, test 14 network settings, vrms 54 O OVF, cann
Index site protected 11 recovery 11 site pairing 39 Site Recovery Manager, and other vCenter Server Solutions 17 site status, events 94 snapshots, limitations on recovery of 59 sneakernet, replication 64 SNMP traps 97 SRA, See storage replication adapter SRM migration utility 37 srm roles 21 srm upgrade, preparation 34 steps, recovery 78 storage, events 98 storage provider, events 98 storage replication adapter and array managers 47 to download 38 to install 38 support 7 suspended virtual machines, limitat
Site Recovery Manager Administration Guide 108 VMware, Inc.
