Site Recovery Manager Installation and Configuration vCenter Site Recovery Manager 5.5 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 Installation and Configuration 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–2013 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and intellectual property laws.
Contents About Site Recovery Manager Installation and Configuration 7 1 Overview of VMware vCenter Site Recovery Manager 9 About Protected Sites and Recovery Sites 10 Using Array-Based Replication with SRM 12 Using vSphere Replication with SRM 13 Using Array-Based Replication and vSphere Replication with SRM 17 SRM and vCenter Server 18 2 Site Recovery Manager System Requirements 21 SRM Licensing 21 SRM Network Ports 22 Operational Limits of SRM 22 3 Creating the SRM Database 23 Configure Microsoft
Site Recovery Manager Installation and Configuration Rescan Arrays to Detect Configuration Changes Edit Array Managers 51 51 8 Installing vSphere Replication 53 Deploy the vSphere Replication Virtual Appliance 54 Configure vSphere Replication Connections 55 Reconfigure the vSphere Replication Appliance 56 Deploy an Additional vSphere Replication Server 67 Register an Additional vSphere Replication Server 68 Reconfigure vSphere Replication Server Settings 68 Unregister and Remove a vSphere Replication S
Contents Index VMware, Inc.
Site Recovery Manager Installation and Configuration 6 VMware, Inc.
About Site Recovery Manager Installation and Configuration Site Recovery Manager Installation and Configuration provides information about how to install, upgrade, and configure VMware vCenter Site Recovery Manager. This information also provides a general overview of Site Recovery Manager. For information about how to perform day-to-day administration of Site Recovery Manager, see Site Recovery Manager Administration.
Site Recovery Manager Installation and Configuration 8 VMware, Inc.
Overview of VMware vCenter Site Recovery Manager 1 VMware vCenter Site Recovery Manager (SRM) is a business continuity and disaster recovery solution that helps you to plan, test, and run the recovery of virtual machines between a protected vCenter Server site and a recovery vCenter Server site. You can configure SRM to work with several third-party disk replication mechanisms by configuring arraybased replication.
Site Recovery Manager Installation and Configuration n Using vSphere Replication with SRM on page 13 SRM can use vSphere Replication to replicate data to servers at the recovery site. n Using Array-Based Replication and vSphere Replication with SRM on page 17 You can use a combination of array-based replication and vSphere Replication in your SRM deployment. n SRM and vCenter Server on page 18 SRM Server operates as an extension to the vCenter Server at a site.
Chapter 1 Overview of VMware vCenter Site Recovery Manager Figure 1‑1. SRM Site Pairing and Recovery Process Site A Site B Protection group Protected site goes offline apps apps apps OS OS OS apps OS apps apps apps apps OS OS OS OS apps apps apps apps OS OS OS OS Replica virtual machines power on Virtual machines replicate from site A to site B Bidirectional Protection You can use a single set of paired SRM sites to protect virtual machines in both directions.
Site Recovery Manager Installation and Configuration Table 1‑1. Heterogeneity of SRM Components Between Sites (Continued) Component Heterogeneous or Identical Installations Storage arrays for array-based replication Can be different on each site. You can use different versions of the same type of storage array on each site, or different types of storage array.
Chapter 1 Overview of VMware vCenter Site Recovery Manager Storage Replication Adapters Storage replication adapters are not part of an SRM release. Your array vendor develops and supports them. You can download storage replication adapters by going to https://my.vmware.com/web/vmware/downloads and selecting VMware vCenter Site Recovery Manager > View Components > Go to Downloads. VMware does not support SRAs that you download from other sites.
Site Recovery Manager Installation and Configuration For information about the loads that a vSphere Replication management server and a vSphere Replication server can support, see http://kb.vmware.com/kb/2034768. vSphere Replication does not require storage arrays. The vSphere Replication storage replication source and target can be any storage device, including, but not limited to, storage arrays. You can use Virtual SAN (VSAN) storage with vSphere Replication. NOTE vSphere 5.
Chapter 1 Overview of VMware vCenter Site Recovery Manager How vSphere Replication Works With vSphere Replication, you can configure replication of a virtual machine from a source site to a target site, monitor and manage the status of the replication, and recover the virtual machine at the target site.
Site Recovery Manager Installation and Configuration Table 1‑2. Compatibility of vSphere Replication with Other vSphere Features (Continued) vSphere Feature Compatible with vSphere Replication Description vSphere Fault Tolerance No vSphere Replication cannot replicate virtual machines that have fault tolerance enabled. You cannot protect the vSphere Replication appliance itself with FT. vSphere DRS Yes Replication continues at the defined RPO after resource redistribution is finished.
Chapter 1 Overview of VMware vCenter Site Recovery Manager Configuring Replications by Using Replication Seeds When copying replication seed files to the target datastore, you can use the vSphere Web Client to create a new root folder on a virtual SAN datastore, or place the files in an existing folder. When you configure replications that use replication seeds, you must select the folder by using its UUID name. Selecting the user-friendly folder names is not supported.
Site Recovery Manager Installation and Configuration Figure 1‑4.
Chapter 1 Overview of VMware vCenter Site Recovery Manager SRM can tolerate certain changes at the recovery site without disruption. n Moving placeholder virtual machines to a different folder or resource pool. n Deleting an object for which an inventory map exists. SRM and the vCenter Server Database If you update the vCenter Server installation that SRM extends, do not reinitialize the vCenter Server database during the update.
Site Recovery Manager Installation and Configuration 20 VMware, Inc.
Site Recovery Manager System Requirements 2 The system on which you install vCenter Site Recovery Manager must meet specific hardware requirements. Table 2‑1. SRM System Requirements Component Requirement Processor 2.0GHz or higher Intel or AMD x86 processor Memory 2GB minimum Disk Storage 5GB minimum Networking 1 Gigabit recommended for communication between SRM sites. Use a trusted network for the management of ESXi hosts.
Site Recovery Manager Installation and Configuration SRM License Keys and vCenter Server Instances in Linked Mode If your vCenter Server instances are connected with vCenter Server instances in linked mode, you install the same SRM license on both vCenter Server instances. SRM License Keys and Protected and Recovery Sites SRM requires a license key that specifies the number of virtual machines that you can protect at a site. n Install SRM license keys at one site to enable recovery.
Creating the SRM Database 3 The SRM Server requires its own database, which it uses to store data such as recovery plans and inventory information. The SRM database is a critical part of an SRM installation. You must create the SRM database and establish a database connection before you can install SRM. SRM cannot use the vCenter Server database because it has different database schema requirements. You can use the vCenter Server database server to create and support the SRM database.
Site Recovery Manager Installation and Configuration If you install SQL Server on a different machine to SRM Server, both of the SRM Server and SQL Server machines must belong to the same domain. You then create a domain user that has the SQL Server login and that also has access to SRM Server. For information about database sizing, see the Sizing calculator for vCenter Site Recovery Manager databases MSSQL at http://www.vmware.com/products/site-recovery-manager/resource.html.
Chapter 3 Creating the SRM Database Alternatively, you can create an ODBC system DSN by running the Windows ODBC Administrator tool during the SRM installation process. Prerequisites You created the database instance to connect to SRM. Procedure 1 Double-click the Odbcad32.exe file at C:\Windows\System32 to open the 64-bit ODBC Administrator tool. IMPORTANT Do not confuse the 64-bit Windows ODBC Administrator tool with the 32-bit ODBC Administrator tool located in C:\Windows\SysWoW64.
Site Recovery Manager Installation and Configuration 26 VMware, Inc.
SRM Authentication 4 All communications between SRM and vCenter Server instances take place over SSL connections and are authenticated by public key certificates or stored credentials. When you install an SRM Server, you must choose either credential-based authentication or custom certificate-based authentication. By default, SRM uses credential-based authentication, but custom certificate-based authentication can alternatively be selected.
Site Recovery Manager Installation and Configuration Requirements When Using Public Key Certificates with SRM If you installed SSL certificates issued by a trusted certificate authority (CA) on the vCenter Server that supports SRM, the certificates you create for use by SRM must meet specific criteria. While SRM uses standard PKCS#12 certificate for authentication, it places a few specific requirements on the contents of certain fields of those certificates.
Installing SRM 5 You must install an SRM Server at the protected site and also at the recovery site. SRM requires a vCenter Server instance of the equivelent version at each site before you install SRM Server. The SRM installer must be able to connect with this vCenter Server instance during installation. After you install the SRM Server instances, you can download the SRM client plug-in from the SRM Server instance by using the Manage Plug-ins menu from your vSphere Client.
Site Recovery Manager Installation and Configuration For environments with a small number of virtual machines to protect, you can run SRM Server and vCenter Server on the same system. For environments that approach the maximum limits of SRM and vCenter Server, install SRM Server on a system that is different from the system on which vCenter Server is installed.
Chapter 5 Installing SRM 5 6 Type information about the vCenter Server instance at the site where you are installing SRM and click Next. Option Action vCenter Server Address Type the host name or IP address of vCenter Server. Enter the host name in lowercase letters. After installation is complete and you are configuring the connection between the protected and recovery sites, supply this host name or IP address exactly as you enter it here, because it is subject to case-sensitive comparisons.
Site Recovery Manager Installation and Configuration Option Description Local Host Name or IP address of the local host. This value is obtained by the SRM installer and needs to be changed only if it is incorrect. For example, the local host might have more than one network interface and the one detected by the SRM installer is not the interface you want to use. If you use certificate-based authentication, the Local Host value must be the same as the SAN value of the supplied certificate.
Chapter 5 Installing SRM 2 Select Plugins > Manage Plug-ins. 3 Under Available Plug-ins, locate VMware vCenter Site Recovery Manager Extension and click Download and Install. 4 Review and accept the certificate. This step only occurs if you use certificate-based authentication. 5 After the download finishes, click Run to start the installation wizard, select the installation language, and click OK. 6 Click Next to start the installation, then click Next again at the VMware Patents page.
Site Recovery Manager Installation and Configuration Prerequisites n Verify that you installed SRM Server instances at the protected and recovery sites. n Verify that you installed the SRM client plug-in in the vSphere Client. Procedure 1 In the vSphere Client, connect to the SRM Server on the protected site. 2 Click Sites in the left pane and click Configure Connection on either the Summary tab or the Getting Started tab.
Chapter 5 Installing SRM 11 Click Finish to confirm the license changes. What to do next Repeat the process to assign SRM license keys to all appropriate vCenter Server instances. Modify the Installation of an SRM Server To change the information that you supplied when you installed the SRM Server, you can run the SRM installer in modify mode.
Site Recovery Manager Installation and Configuration 7 Select an authentication method and click Next. Option Description Leave the current authentication method unchanged Select Use existing certificate. If the installed certificate is not valid, this option is unavailable. Use credential-based authentication Select Automatically generate certificate to generate a new certificate. Use certificate-based authentication Select Use a PKCS #12 certificate file to upload a new certificate.
Chapter 5 Installing SRM 3 Select the entry for VMware vCenter Site Recovery Manager and click Change. 4 Click Next. 5 Select Repair and click Next. 6 (Optional) If you did not install vSphere Replication when you installed SRM, select whether to install it now. If you already installed vSphere Replication, this option does not appear. 7 Click Install to repair the installation and optionally install vSphere Replication.
Site Recovery Manager Installation and Configuration 38 VMware, Inc.
Upgrading SRM 6 You can upgrade existing SRM installations. The SRM upgrade process preserves existing information about SRM configurations. You must upgrade versions of SRM earlier than 5.0 to SRM 5.0 or 5.0.1 before you can upgrade to SRM 5.5. IMPORTANT Upgrading vCenter Server directly from 4.1.x to 5.5 is a supported upgrade path. However, upgrading SRM directly from 4.1.x to 5.5 is not a supported upgrade path. When upgrading a vCenter Server 4.1.
Site Recovery Manager Installation and Configuration n Protection groups n Inventory mappings n Recovery plans n IP customizations for individual virtual machines n Custom roles and their memberships 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) IMPORTANT During an upgrade, SRM preserves only protection groups and recovery plans that are in a valid state.
Chapter 6 Upgrading SRM Upgrade the components on the protected site before you upgrade the components on the recovery site. Upgrading the protected site first allows you to perform a disaster recovery on the recovery site if you encounter problems during the upgrade that render the protected site unusable. The exception is the ESXi hosts, which you can upgrade after you finish upgrading the other components on the protected and recovery sites.
Site Recovery Manager Installation and Configuration 3 Upgrade the SRM Server with Migration on page 44 You can upgrade SRM and migrate the SRM Server to a different host than the previous SRM Server installation. 4 Upgrade the SRM Client Plug-In on page 46 You must upgrade the SRM client plug-in for all vSphere Client instances that you use to manage SRM. 5 Configure the Upgraded SRM Installation on page 47 You must configure the upgraded components to establish a working SRM installation.
Chapter 6 Upgrading SRM An upgrade without migration provides a quick way to upgrade the SRM Server to a new release without changing any of the information that you provided for the current installation. To change any installation information, for example, database connections, the authentication method, certificate location, or administrator credentials, you must run the installer in modify mode after you upgrade an existing SRM Server.
Site Recovery Manager Installation and Configuration 9 Select an authentication method and click Next. Option Description Use credential-based authentication a b Select Automatically generate certificate and click Next. Type text values for your organization and organization unit, typically your company name and the name of your group in the company. Use certificate-based authentication a b Select Use a PKCS #12 certificate file and click Next. Type the path to the certificate file.
Chapter 6 Upgrading SRM 3 Follow the prompts and accept the license agreement. 4 Click Change to change the folder in which to install SRM, select a target volume, and click Next. The default installation folder for SRM is C:\Program Files\VMware\VMware vCenter Site Recovery Manager. If you use a different folder, the pathname cannot be longer than 170 characters including the end slash, and cannot include non-ASCII characters. 5 Select whether to install vSphere Replication and click Next.
Site Recovery Manager Installation and Configuration Option Description Additional E-mail An optional email address of another SRM administrator, for potential use by vCenter Server. Local Host Name or IP address of the local host. This value is obtained by the SRM installer and needs to be changed only if it is incorrect. For example, the local host might have more than one network interface and the one detected by the SRM installer is not the interface you want to use.
Chapter 6 Upgrading SRM 3 Under Available Plug-ins, locate VMware vCenter Site Recovery Manager Extension and click Download and Install. 4 Review and accept the certificate. This step only occurs if you use certificate-based authentication. 5 After the download finishes, click Run to start the installation wizard, select the installation language, and click OK. If you did not uninstall the previous version of the SRM client plug-in, the installer prompts you to do so and stops the installation.
Site Recovery Manager Installation and Configuration n Verify that you made a backup of the SRM database before you upgraded SRM from a previous release to this release. Procedure 1 Use the Windows Control Panel options to uninstall SRM at the protected and recovery sites. If you connected the SRM Server instances at the protected and recovery sites, you must uninstall SRM at both sites.
Configuring Array-Based Protection 7 After you pair the protected and recovery sites, you must configure protection for virtual machines. If you are using array-based replication, you must configure storage replication adapters (SRAs) at each site. If you are using only vSphere Replication, you do not require an SRA. See Chapter 8, “Installing vSphere Replication,” on page 53.
Site Recovery Manager Installation and Configuration If you are using vSphere Replication, you do not require an SRA. Prerequisites n Download the SRA by going to https://my.vmware.com/web/vmware/downloads and selecting VMware vCenter Site Recovery Manager > Download Product > Go to Downloads > Go to Downloads. VMware does not support storage replication adapters downloaded from other sites. n Read the documentation provided with your SRA. SRAs do not support all features that storage arrays support.
Chapter 7 Configuring Array-Based Protection 4 Select the array manager type that you want SRM to use from the SRA Type drop-down menu. If no manager type appears, rescan for SRAs or check that you have installed an SRA on the SRM Server host. 5 Provide the required information for the type of SRA you selected. The SRA creates these text boxes. For more information about how to fill in these text boxes, see the documentation that your SRA vendor provides.
Site Recovery Manager Installation and Configuration 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. You cannot modify the array manager type. 4 Modify the adapter information. These fields are created by the SRA. 5 52 Click Finish to complete the modification of the array manager. VMware, Inc.
Installing vSphere Replication 8 vSphere Replication uses the replication technologies included in ESXi with the assistance of virtual appliances to replicate virtual machines between source and target sites. The vSphere Replication appliance registers with the corresponding vCenter Server instance. For example, on the source site, the vSphere Replication appliance registers with the vCenter Server instance on the source site.
Site Recovery Manager Installation and Configuration 5 Register an Additional vSphere Replication Server on page 68 If you deploy additional vSphere Replication servers, you must register these servers with the vSphere Replication appliance to enable them as traffic handlers at the recovery site. 6 Reconfigure vSphere Replication Server Settings on page 68 The vSphere Replication appliance contains a vSphere Replication server.
Chapter 8 Installing vSphere Replication 8 Set the appliance properties, and click Next. Option Description Password Type and confirm a root password for the appliance. Initial Configuration Use the embedded vSphere Replication database. If you use the embedded database, you can use vSphere Replication immediately after deployment. Deselect the checkbox to use vSphere Replication with an external database.
Site Recovery Manager Installation and Configuration Reconfigure the vSphere Replication Appliance If necessary, you can reconfigure the vSphere Replication appliance settings by using the virtual appliance management interface (VAMI). You provide the settings for the vSphere Replication appliance in the Deploy OVF wizard when you deploy the appliance.
Chapter 8 Installing vSphere Replication For example, you can reconfigure the address of the vSphere Replication appliance if you did not specify a fixed IP address when you deployed the appliance, and DHCP changes the address after deployment. Similarly, you can update the address of the vCenter Server instance if the address changes after deployment. Prerequisites n Verify that the vSphere Replication appliance is powered on.
Site Recovery Manager Installation and Configuration Procedure 1 Connect to the VAMI of the vSphere Replication appliance in a Web browser. The URL for the VAMI is https://vr-appliance-address:5480. You can also access the VAMI by clicking Configure VR Appliance in the Summary tab in the vSphere Replication view of the SRM interface. 2 Type the root user name and password for the appliance. You configured the root password during the OVF deployment of the vSphere Replication appliance.
Chapter 8 Installing vSphere Replication vSphere Replication can trust remote server certificates either by verifying the validity of the certificate and its thumbprint or by verifying the thumbprint only. The default is to verify by thumbprint only.
Site Recovery Manager Installation and Configuration n vSphere Replication accepts MD5 and SHA1 signatures, but VMware recommends that you use SHA256 signatures. n vSphere Replication does not accept RSA or DSA certificates with 512-bit keys. vSphere Replication requires at least 1024-bit keys. VMware recommends using 2048-bit public keys. vSphere Replication shows a warning if you use a 1024-bit key.
Chapter 8 Installing vSphere Replication 2 Obtain the current hms-keystore password. # /opt/vmware/hms/hms-configtool -cmd list | grep keystore Example of the output hms-keystore-password = old_password 3 Change the hms-keystore password. # /usr/java/default/bin/keytool -storepasswd -storepass old_password -new new_password keystore /opt/vmware/hms/security/hms-keystore.jks 4 Change the vSphere Replication appliance private key password.
Site Recovery Manager Installation and Configuration 2 Type the root user name and password for the appliance. You configured the root password during the OVF deployment of the vSphere Replication appliance. 3 Click the Network tab. 4 Click Status to review current network settings. 5 Click Address to review or modify IPv4 and IPv6 address settings. 6 IP Address Type Option Description IPv4 DHCP DHCP is not recommended if the IP address of the appliance might change if it reboots.
Chapter 8 Installing vSphere Replication 3 Click the System tab. 4 Click Information. You can review information about vSphere Replication, and reboot or shutdown the appliance.
Site Recovery Manager Installation and Configuration n You must create and configure the external database before you connect it to vSphere Replication. See “Databases that vSphere Replication Supports,” on page 64 for the configuration requirements for each supported type of database. Procedure 1 Connect to the VAMI of the vSphere Replication appliance in a Web browser. The URL for the VAMI is https://vr-appliance-address:5480.
Chapter 8 Installing vSphere Replication Configure Microsoft SQL Server for vSphere Replication When you create a Microsoft SQL Server database, you must configure it correctly to support vSphere Replication. You use SQL Server Management Studio to create and configure an SQL Server database for vSphere Replication. This information provides the general steps that you must perform to configure an SQL Server database for vSphere Replication.
Site Recovery Manager Installation and Configuration This information provides the general steps that you must perform to configure an Oracle Server database for vSphere Replication. For instructions about how to perform the relevant steps, see the Oracle documentation. Procedure 1 When creating the database instance, specify UTF-8 encoding. 2 Create the vSphere Replication database user account. 3 If they are not selected already, select the CONNECT and RESOURCE roles.
Chapter 8 Installing vSphere Replication Deploy an Additional vSphere Replication Server The vSphere Replication appliance includes a vSphere Replication server. However, you might need to deploy multiple vSphere Replication servers to meet your load balancing needs. vSphere Replication server is distributed as an OVF virtual appliance. SRM deploys the OVF file from the vCenter Server instance that SRM extends. The vSphere Replication server OVF file is also available at C:\Program Files\VMware\VMware vCen
Site Recovery Manager Installation and Configuration 10 Click Finish. What to do next When the OVF file has deployed, register the vSphere Replication server with the vSphere Replication appliance. Register an Additional vSphere Replication Server If you deploy additional vSphere Replication servers, you must register these servers with the vSphere Replication appliance to enable them as traffic handlers at the recovery site.
Chapter 8 Installing vSphere Replication 5 6 (Optional) Click Configuration to generate or upload a new certificate. Option Action Generate and install a self-signed certificate Click Generate and Install. Upload an existing SSL certificate Click Browse next to the Upload PKCS#12 (*.pfx) file text box to browse for an existing certificate, and click Upload and Install. (Optional) Click Security to change the Super User password for the vSphere Replication server. root is the Super User.
Site Recovery Manager Installation and Configuration 5 In the Hosts and Clusters view, power off and delete the vSphere Replication server virtual machine. Uninstall vSphere Replication You uninstall vSphere Replication by unregistering the appliance from vCenter Server and removing it from your environment. Prerequisites n Verify that the vSphere Replication virtual appliance is powered on. n Stop all existing outgoing or incoming replications to the site.
Chapter 8 Installing vSphere Replication What to do next Deploy a new vSphere Replication appliance and perform any optional configuration. VMware, Inc.
Site Recovery Manager Installation and Configuration 72 VMware, Inc.
Upgrading vSphere Replication 9 If you installed vSphere Replication as part of a previous SRM installation, you must upgrade vSphere Replication after you upgrade SRM. If you upgrade SRM, vSphere Replication is not upgraded automatically. You must upgrade vSphere Replication as a separate process from upgrading SRM. The quickest way to upgrade vSphere Replication is to use vSphere Update Manager.
Site Recovery Manager Installation and Configuration Using Standalone vSphere Replication with SRM vSphere Replication 5.1 and later is available as a standalone extension of vCenter Server, that is independent of SRM. If you installed a standalone version of vSphere Replication and then install SRM, all existing pairings and replications are immediately accessible through the SRM user interface, except for pairings and replications in a single vCenter Server.
Chapter 9 Upgrading vSphere Replication Prerequisites n You upgraded vCenter Server, the vSphere Client, SRM, and the SRM client to version 5.5. n For the list of vSphere Replication appliances, vSphere Replication management servers, and vSphere Replication servers to upgrade, consult the vSphere Replication upgrade report that the SRM installer generated at the end of the SRM upgrade. n Verify that you installed Update Manager 5.
Site Recovery Manager Installation and Configuration 14 Repeat Step 11 to Step 13 for all vSphere Replication servers. What to do next If you configured vSphere Replication to accept only certificates that are signed by a trusted certificate authority, after an upgrade you must reconnect the vSphere Replication appliances.
Chapter 9 Upgrading vSphere Replication What to do next If you configured vSphere Replication to accept only certificates that are signed by a trusted certificate authority, after an upgrade you must reconnect the vSphere Replication appliances. If your SRM 5.1.x infrastructure uses more than one vSphere Replication server, or if you are upgrading from SRM 5.0.x, upgrade the vSphere Replication server appliances.
Site Recovery Manager Installation and Configuration 7 Repeat the procedure to upgrade other vSphere Replication server instances that you deployed with the previous version. Upgrade vSphere Replication Without Internet Access In environments where you do not have access to the Internet, you can upgrade the vSphere Replication appliance and the vSphere Replication server by using a downloaded ISO image. Prerequisites n Upgrade the vCenter Server instance that vSphere Replication extends.
Creating SRM Placeholders and Mappings 10 When you use SRM to configure the protection for virtual machines, you reserve resources on the recovery site by creating placeholders. You map the resources of the protected virtual machines to resources on the recovery site. n About Placeholder Virtual Machines on page 79 When you add a virtual machine or template to a protection group, SRM creates a placeholder virtual machine at the recovery site.
Site Recovery Manager Installation and Configuration About Placeholder Virtual Machine Templates When you protect a template on the protected site, SRM creates the placeholder template by creating a virtual machine in the default resource pool of a compute resource and then by marking that virtual machine as a template.
Chapter 10 Creating SRM Placeholders and Mappings How SRM Applies Mappings During Reprotect During reprotect, SRM converts the virtual machines from the original protected site into placeholders, to protect the recovered virtual machines that were formerly the placeholder virtual machines on the recovery site. In most cases, the previously protected virtual machines and their devices are used during reprotect.
Site Recovery Manager Installation and Configuration n You cannot select replicated datastores as placeholder datastores. Configure a Placeholder Datastore You can specify a placeholder datastore for SRM to use for the storage of placeholder virtual machines. Prerequisites Verify that you connected and paired the protected and recovery sites. Procedure 1 Select Sites in the left pane of the SRM interface, and select a site. 2 Click the Placeholder Datastores tab.
Installing SRM to Use with a Shared Recovery Site 11 With SRM, you can connect multiple protected sites to a single recovery site. The virtual machines on the protected sites all recover to the same recovery site. This configuration is known as a shared recovery site, a many-to-one, or an N:1 configuration. In the standard one-to-one SRM configuration, you use SRM to protect a specific instance of vCenter Server by pairing it with another vCenter Server instance.
Site Recovery Manager Installation and Configuration n SRM Server D, that is paired with SRM Server B n vCenter Server C, that is extended by SRM Server C and SRM Server D Figure 11‑1.
Chapter 11 Installing SRM to Use with a Shared Recovery Site n Use vSphere Replication in a Shared Recovery Site Configuration on page 92 You can use vSphere Replication with SRM in a shared recovery site configuration in the same way that you do in a standard one-to-one configuration. Limitations of Using SRM in Shared Recovery Site Configuration When you configure SRM to use a shared recovery site, SRM supports the same operations as it does in a standard one-to-one configuration.
Site Recovery Manager Installation and Configuration Example: Sharing SRM Licenses on a Shared Recovery Site You connect two protected sites to a shared recovery site. You install a single SRM license on the shared recovery site. n If you protect 20 virtual machines on protected site A, you require a license for 20 virtual machines on protected site A to recover these virtual machines to the shared recovery site.
Chapter 11 Installing SRM to Use with a Shared Recovery Site Install SRM Server on Multiple Protected Sites to Use with a Shared Recovery Site You install SRM Server to use with a shared recovery site by running the SRM installer from the command line with a custom setup option. When you run the installer from the command line with the custom setup option, the SRM installer presents additional screens on which you specify a unique SRM extension ID.
Site Recovery Manager Installation and Configuration Install Multiple SRM Server Instances on a Shared Recovery Site In a shared recovery site configuration, you can install multiple SRM Server instances that all extend the same vCenter Server instance. The SRM Server instances that you install on a shared recovery site each correspond to an SRM Server on a protected site. Prerequisites n You created one or more protected sites, each with an SRM Server instance for which you configured a unique SRM ID.
Chapter 11 Installing SRM to Use with a Shared Recovery Site Prerequisites n You installed one or more SRM Server instances on a shared recovery site. n You assigned the same SRM extension ID to an SRM Server instance on a protected site and to an SRM Server instance on the shared recovery site. Procedure 1 Connect the vSphere Client to vCenter Server on the shared recovery site. 2 Select Plugins > Manage Plug-ins.
Site Recovery Manager Installation and Configuration Connect the SRM Sites in a Shared Recovery Site Configuration In a shared recovery site configuration, you connect the SRM sites in the same way as for a standard one-toone configuration. If you start the site connection from one of the protected sites, SRM uses the SRM ID that you set during installation to connect to the correct SRM Server instance on the recovery site.
Chapter 11 Installing SRM to Use with a Shared Recovery Site Prerequisites n You installed SRM in a shared recovery site configuration. n You connected the protected sites with the shared recovery site. n Familiarize yourself with the procedure for configuring placeholders and mappings. For information about configuring placeholders and mappings in a standard configuration, see Chapter 10, “Creating SRM Placeholders and Mappings,” on page 79.
Site Recovery Manager Installation and Configuration n You connected the protected sites with the shared recovery site. n Familiarize yourself with the procedure for configuring array-based replication. For information about how to configure array-based replication in a standard configuration, see Chapter 7, “Configuring Array-Based Protection,” on page 49. Procedure 1 Set up storage arrays on the protected sites following the instructions that your storage array provides.
Chapter 11 Installing SRM to Use with a Shared Recovery Site 3 Log in to SRM on each of the protected sites and configure the vSphere Replication connection to the recovery site. All of the vSphere Replication appliances on the protected sites connect to the same vSphere Replication appliance on the recovery site. 4 (Optional) Deploy additional vSphere Replication servers on the shared recovery site.
Site Recovery Manager Installation and Configuration 94 VMware, Inc.
Troubleshooting SRM Installation and Configuration 12 Known troubleshooting information can help you diagnose and correct problems during the installation and configuration of SRM. Solution n Cannot Restore SQL Database to a 32-Bit Target Virtual Machine During SRM Upgrade on page 96 You might encounter problems restoring a SQL database on a 32-bit target virtual machine when you upgrade or migrate SRM. n SRM Server Does Not Start on page 97 SRM depends on other services.
Site Recovery Manager Installation and Configuration n Increase the Memory of the vSphere Replication Server for Large Deployments on page 102 If you deploy an additional vSphere Replication server, you might need to increase the memory of the vSphere Replication server if that server manages large numbers of virtual machines.
Chapter 12 Troubleshooting SRM Installation and Configuration SRM Server Does Not Start SRM depends on other services. If one of those services is not running, the SRM Server does not start. Problem After you install, repair, or modify SRM by running the SRM installer, or after you reboot the SRM Server, the SRM Server does not start. Cause The SRM Server might not start if vCenter Server is not running, if it cannot connect to the SRM database, or if other services that SRM requires are not running.
Site Recovery Manager Installation and Configuration f Click Test Data Source. If the connection is configured correctly, the ODBC Data Source Test window shows a positive result. g 6 If the connection test fails, reconfigure the SRM database by using the administration software from your database provider. Verify that the SRM database permits sufficient connections.
Chapter 12 Troubleshooting SRM Installation and Configuration Cause This problem can occur if the certificate for vCenter Server does not match the certificate that SRM requires, for example if the certificate for vCenter Server changed since you installed SRM. Solution Restore the vCenter Server certificate to the certificate that you used when you installed SRM or install a new vCenter Server certificate.
Site Recovery Manager Installation and Configuration OVF Package is Invalid and Cannot be Deployed When you attempt to deploy OVF for the vSphere Replication appliance, an OVF package error might occur. Problem The error OVF package is invalid and cannot be deployed might appear while you attempt to deploy the vSphere Replication appliance. Cause This problem is due to the vCenter Server port being changed from the default of 80. Solution If possible, change the vCenter Server port back to 80.
Chapter 12 Troubleshooting SRM Installation and Configuration Solution 1 Use a file management tool to connect to the vSphere Replication appliance. For example, you might use SCP or WinSCP. Connect using the root account, which is the same account used to connect to the VAMI. 2 Delete any files you find in /opt/vmware/hms/logs. 3 Connect to the VAMI and attempt to save the vSphere Replication configuration. This action recreates the SQL error.
Site Recovery Manager Installation and Configuration vSphere Replication Service Fails with Unresolved Host Error If the address of vCenter Server is not set to a fully qualified domain name (FQDN) or to a literal address, the vSphere Replication service can stop unexpectedly or fail to start after a reboot. Problem The vSphere Replication service stops running or does not start after a reboot. The error unable to resolve host: non-fully-qualified-name appears in the vSphere Replication logs.
Chapter 12 Troubleshooting SRM Installation and Configuration Uploading a Valid Certificate to vSphere Replication Results in a Warning When you upload a custom certificate to the vSphere Replication appliance, you see a warning even if the certificate is valid. Problem When you use the virtual appliance management interface (VAMI) in Internet Explorer to upload certificates to the vSphere Replication appliance, you see a certificate error: The certificate installed with warnings.
Site Recovery Manager Installation and Configuration Cause vSphere Replication updates each host's SSL thumbprint registry. The vCenter Server Events pane displays Host is configured for vSphere Replication for each host as the vSphere Replication server registration task progresses. Solution 1 Wait for the registration task to complete. After it finishes, you can use vSphere Replication for incoming replication traffic. 2 Alternatively, edit /opt/vmware/hms/conf/hms-configuration.
Index Numerics 404 Error when pairing vSphere Replication appliances 101 A array managers and storage replication adapters 50 edit 51 replicated device discovery 50 to configure 50 to rescan arrays 51 array-based replication, and vSphere Replication 17 authentication certificate warnings and 27 methods used by Site Recovery Manager 27 B bidirectional protection 11 C certificate change type 35 public key 27 SRM requirements for 28 to update 35 certificate authority root certificate 99 certificate warning
Site Recovery Manager Installation and Configuration P permissions required 33 placeholder datastore, add 82 placeholder datastores 81 placeholder virtual machine templates 79 placeholder virtual machines 79 placeholders 79 planned migration 9 plug-in Site Recovery Manager client 32 to install 32 point-in-time recovery 13 ports, used by SRM 22 protected and recovery sites different configurations 11 heterogeneous 11 protected site configure array managers for 50 configuring 49 host compatibility requiremen
Index upgrading vSphere Replication without Internet access 78 using virtual SAN datastores in vSphere Replication 16 V vCenter, and Site Recovery Manager 18 vCenter Server change connection information 35 change credentials used by Site Recovery Manager 35 change SSL certificate 104 vCenter Server Appliance, and SRM 18 vCenter Server cannot connect to SRM 98 Virtual Flash 12 Virtual SAN 13, 15 virtual appliance, unregister 70 virtual machines, maximum number supported 22 VSAN 13 vSphere features, compati
Site Recovery Manager Installation and Configuration 108 VMware, Inc.
