Before you install Site Recovery Manager Server, you must perform several tasks and verify that you have certain information.
Install the appropriate version of Platform Services Controller and vCenter Server on both sites. You cannot mix Site Recovery Manager, Platform Services Controller, or vCenter Server versions across sites. For information about compatibility between vCenter Server and Site Recovery Manager versions, see vCenter Server Requirements in the Compatibility Matrixes for Site Recovery Manager 8.0 at https://www.vmware.com/support/srm/srm-compat-matrix-8-0.html.
For environments with a small number of virtual machines to protect, you can run Site Recovery Manager Server and vCenter Server on the same system. For environments that approach the maximum limits of Site Recovery Manager and vCenter Server, install Site Recovery Manager Server on a system that is different from the system on which vCenter Server is installed. If Site Recovery Manager Server and vCenter Server are installed on the same system, administrative tasks might become more difficult to perform in large environments. Furthermore, if you install Site Recovery Manager Server in a virtual machine, and this virtual machine is not the same as the one that runs vCenter Server, you can use vSphere High Availability and VMware Fault Tolerance to protect the Site Recovery Manager Server virtual machine.
When you install and configure Platform Services Controller, vCenter Server, and vSphere Replication, use fully qualified domain names (FQDN) whenever possible rather than IP addresses. Using FQDN rather than IP addresses allows you to change the vSphere infrastructure, for example by using DHCP, without having to redeploy or reconfigure Site Recovery Manager. You must also use FQDN if you use custom certificates, because most certificate authorities do not accept certificates that use IP addresses for the SAN or CN value.
The way in which you deploy Platform Services Controller, vCenter Server, and vCenter Single Sign-On on a site affects how you deploy Site Recovery Manager. For information about how the vCenter Server deployment model affects Site Recovery Manager, see Site Recovery Manager and vCenter Server Deployment Models.
Obtain the address of the Platform Services Controller instance for both sites. The Platform Services Controller must be running and accessible during Site Recovery Manager installation.
Obtain the vCenter Single Sign-On administrator user name and password for both of the local and remote sites.
Synchronize the clock settings of the systems on which Platform Services Controller, vCenter Server, and Site Recovery Manager Server run. To avoid conflicts in the time management across these systems, use a persistent synchronization agent such as network time protocol daemon (NTPD), W32Time, or VMware Tools time synchronization. If you run Platform Services Controller, vCenter Server, and Site Recovery Manager Server in virtual machines, set up NTP time synchronization on the ESXi host on which the virtual machines run. For information about timekeeping best practices, see http://kb.vmware.com/kb/1318.
Obtain a Windows user account with the appropriate privileges on the system on which to install and run Site Recovery Manager Server. You can configure the Site Recovery Manager service to run under a specified user account. The account can be a local user or a domain user that is a member of the Administrators group on the machine on which you are installing Site Recovery Manager. Alternatively, you can configure Site Recovery Manager to run under the Local System account during installation.
Obtain the user name and password for the Site Recovery Manager database, if you are not using the embedded database.
If you do not use the embedded Site Recovery Manager database, configure and start the Site Recovery Manager database service on both sites before you install the Site Recovery Manager Server. Each Site Recovery Manager instance requires its own database. See Creating the Site Recovery Manager Database.
If you do not use the embedded Site Recovery Manager database, Site Recovery Manager requires a database source name (DSN) for 64-bit open database connectivity (ODBC). You can create the ODBC system DSN before you run the Site Recovery Manager installer, or you can create the DSN during the installation process. For details about creating the ODBC system DSN, see Create an ODBC System DSN for Site Recovery Manager. If you use the embedded Site Recovery Manager database, the Site Recovery Manager installer creates the necessary DSN.
To use Site Recovery Manager with vSphere Replication, deploy the appropriate version of vSphere Replication on both of the protected and recovery sites before you install Site Recovery Manager Server. The Site Recovery Manager installer verifies the version of vSphere Replication during installation and stops if it detects an incompatible version. This verification is not performed if you install vSphere Replication after you install Site Recovery Manager Server, which might lead to incompatible versions. Incompatible versions of Site Recovery Manager and vSphere Replication cause the vSphere Web Client to stop working. For information about compatibility between vSphere Replication and Site Recovery Manager versions, see vSphere Replication Requirements in the Compatibility Matrixes for Site Recovery Manager 8.0 at https://www.vmware.com/support/srm/srm-compat-matrix-8-0.html.
The Site Recovery Manager installer presents the SSL/TLS certificate of the Platform Services Controller for validation when it runs. Obtain the necessary information to allow you validate the certificate.
If you use custom certificates, obtain an appropriate certificate file. See Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager.
Download the Site Recovery Manager installation file to a folder on the machine on which to install Site Recovery Manager.
Verify that no reboot is pending on the Windows machine on which to install Site Recovery Manager Server. Verify that no other installation is running, including the silent installation of Windows updates. Pending reboots or running installations can cause the installation of Site Recovery Manager Server or the embedded Site Recovery Manager database to fail.
Optimize the Adobe Flash Player settings in your browser to increase the amount of storage space that the vSphere Web Client can use. Performing a recovery with Site Recovery Manager can sometimes exceed the default amount of storage space that Flash Player is permitted to consume. For information about how to optimize the Flash Player settings for Site Recovery Manager in the vSphere Web Client, see http://kb.vmware.com/kb/2106096.