You can upgrade Site Recovery Manager and migrate Site Recovery Manager Server to a different host than the previous Site Recovery Manager Server installation.
About this task
To upgrade Site Recovery Manager and migrate Site Recovery Manager Server to a different host, you create a new Site Recovery Manager Server installation on the new host, and connect it to the Site Recovery Manager database from the previous installation.
Do not uninstall the old Site Recovery Manager Server installation after you complete the upgrade. If you uninstall the old Site Recovery Manager Server installation, this will unregister the new installation from vCenter Server.
You can only upgrade Site Recovery Manager with migration if you use an external database with the previous installation. You cannot migrate the contents of the embedded database.
To upgrade Site Recovery Manager and keep Site Recovery Manager Server on the same host as the previous installation, see In-Place Upgrade of Site Recovery Manager Server.
Before you update Site Recovery Manager 6.5 to a 6.5.x update release or to a 6.5.x.x patch release by using migration, see the respective Release Notes document at VMware Site Recovery Manager Documentation for information about the supported upgrade methods.
You completed the tasks and obtained the information described inPrerequisites and Best Practices for Site Recovery Manager Upgrade.
Log in to the host machine on which the previous version of Site Recovery Manager Server is running. Log in using an account with sufficient privileges. This is often an Active Directory domain administrator, but can also be local administrator.
Log in to the host machine on which to install the new version of Site Recovery Manager Server. Log in using an account with sufficient privileges. This is often an Active Directory domain administrator, but can also be a local administrator.
Create a 64-bit ODBC system data source name (DSN) on the new host machine to connect to the existing Site Recovery Manager database that you used with the previous version. For information about creating an ODBC DSN, see Create an ODBC System DSN for Site Recovery Manager.
If you use an SQL Server database with Integrated Windows Authentication as the Site Recovery Manager database, you must use the same user account or an account with the same privileges when you upgrade Site Recovery Manager Server as you used when you created the Integrated Windows Authentication DSN for SQL Server.
- Stop the Site Recovery Manager Server service on the old Site Recovery Manager Server host.
- On the host on which you want to install the new version of Site Recovery Manager Server, double-click the Site Recovery Manager installer, select an installation language, and click OK.
- Follow the installer prompts to accept the license agreement, and verify that you satisfied the installation prerequisites.
- Choose where to install Site Recovery Manager Server, and click Next.
Keep the default destination folder.
Click Change to change the destination folder, and select a target volume.
The default installation folder for Site Recovery Manager is C:\Program Files\VMware\VMware vCenter Site Recovery Manager. If you use a different folder, the pathname cannot be longer than 120 characters including the end slash, and cannot include non-ASCII characters.
- Enter information about the Platform Services Controller at the site where you are upgrading Site Recovery Manager Server and click Next.
The host name or IP address of the Platform Services Controller for the vCenter Server with which to register Site Recovery Manager. 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.Important:
To facilitate IP address changes in your infrastructure, provide a fully qualified domain name (FQDN) whenever possible, rather than an IP address.Important:
If the Platform Services Controller uses an FQDN rather than an IP address, you must specify the FQDN when you install Site Recovery Manager.
Accept the default value of 443 or enter a new value if Platform Services Controller uses a different port. Platform Services Controller only supports connections over HTTPS and does not support HTTP connections.
The vCenter Single Sign-On user name for the vCenter Single Sign-On domain to which this Platform Services Controller instance belongs. This user account must be a member of the vCenter Single Sign-On Administrator group on the Platform Services Controller instance. Only members of the Administrator group have the necessary permissions to create or recreate the Site Recovery Manager solution user.
The password for the specified vCenter Single Sign-On user name. The password text box can be empty.
- If prompted, verify the Platform Services Controller certificate and click Accept to accept it.
- Select the vCenter Server instance with which to register Site Recovery Manager and click Next.
The drop-down menu includes all of the vCenter Server instances that are registered with the Platform Services Controller. In an environment that uses Enhanced Linked Mode, it can also include vCenter Server instances from other Platform Services Controller instances. Make sure that you select the correct vCenter Server instance. Once the Site Recovery Manager installation is complete, you cannot modify it to select a different vCenter Server instance.
- Enter information with which to register the Site Recovery Manager extension with vCenter Server, and click Next.
Local Site Name
A name for this Site Recovery Manager site, which appears in the Site Recovery Manager interface. The vCenter Server address is used by default, but you can enter any name. You cannot use the same name that you use for another Site Recovery Manager installation with which this one will be paired.
Email address of the Site Recovery Manager administrator. This information is required even though you use the standard vCenter Server alarms to configure email notifications for Site Recovery Manager events.
Name or IP address of the local host. The Site Recovery Manager installer obtains this value. Only change it if it is incorrect. For example, the local host might have more than one network interface and the one that the Site Recovery Manager installer detects is not the interface you want to use.Important:
To facilitate IP address changes in your infrastructure, provide a fully qualified domain name (FQDN) whenever possible, rather than an IP address.
HTTPS port for all management traffic to Site Recovery Manager Server, including traffic with external API clients for task automation. The port is also used by vSphere Web Client to download the Site Recovery Manager client plug-in. This port must be accessible from the vCenter Server proxy system. Do not change the port unless the default of 9086 causes port conflicts.
- Select the default Site Recovery Manager plug-in identifier, or create a plug-in identifier for this Site Recovery Manager Server pair, and click Next.
Both Site Recovery Manager Server instances in a site pair must use the same plug-in identifier.
- Click Yes to confirm that you want to overwrite the existing Site Recovery Manager extension on this vCenter Server instance.
- Select a certificate type and click Next.
Automatically generate certificate
Use an automatically generated certificate:
Select Automatically generate certificate and click Next.
Enter text values for your organization and organization unit, typically your company name and the name of your group in the company.
Load a certificate file
Use a custom certificate:
Select Use a PKCS#12 certificate file and click Next.
Click Browse, navigate to the certificate file, and click Open. The certificate file must contain exactly one certificate with exactly one private key matching the certificate.
Enter the certificate password.
- Select Use a custom database server, select the 64-bit DSN that connects to the Site Recovery Manager database that you used with the previous installation, click Next, and provide the database connection information.
Enter a valid user name for the specified database. If you use Integrated Windows Authentication, this option is not available.
Enter the password for the specified user name. If you use Integrated Windows Authentication, this option is not available.
Enter the initial connection pool size. In most cases, it is not necessary to change this setting. Before changing this setting, consult with your database administrator.
Enter the maximum number of database connections that can be open simultaneously. Usually, it is not necessary to change this setting. Before changing this setting, consult with your database administrator.
- Select the user account under which to run the Site Recovery Manager Server service and click Next.
Select Use Local System Account to run the Site Recovery Manager Server service under the Local System account.
Enter the username and password of an existing LDAP user account to run the Site Recovery Manager Server service under a different user account. This can be any user account, including local users, that is a member of the built-in Administrators group.
This option is not available if you use an SQL Server database with Integrated Windows Authentication. In this case, the Site Recovery Manager Server service runs under the account that you use to install Site Recovery Manager.
- Click Install.
- When the installation is finished, click Finish.
What to do next
Log in to vSphere Web Client, or if you are already connected to vSphere Web Client, log out of vSphere Web Client and log in again. The upgraded Site Recovery Manager extension appears in vSphere Web Client. You might need to clear the browser cache for the upgrade to appear in vSphere Web Client. If the upgrade still does not appear, restart the vSphere Web Client service.
Repeat the procedure to upgrade the Site Recovery Manager Server on the other Site Recovery Manager site.
When you have upgraded both sites, perform the post-upgrade tasks in Configure and Verify the Upgraded Site Recovery Manager Installation.