An in-place upgrade provides a quick way to upgrade Site Recovery Manager Server to a new release without changing any of the information that you provided for the current installation. You can upgrade Site Recovery Manager Server on the same host machine as an existing Site Recovery Manager Server installation.
About this task
To upgrade Site Recovery Manager and migrate the Site Recovery Manager Server to a different host machine, see Upgrade Site Recovery Manager Server with Migration.
If you are updating Site Recovery Manager 5.8 to a 5.8.x update release or to a 5.8.x.x patch release, you must perform in-place upgrade. You cannot perform upgrade with migration if you are updating Site Recovery Manager 5.8 to a 5.8.x update release or to a 5.8.x.x patch release.
When you upgrade an existing version of Site Recovery Manager Server, the Site Recovery Manager installer reuses information about vCenter Server connections, certificates, and database configuration from the existing installation. The installer populates the text boxes in the installation wizard with the values from the previous installation.
To change 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 Site Recovery Manager Server.
If existing configuration information is invalid for the upgrade, the upgrade fails. For example, the upgrade fails if the database is not accessible at the same DSN, or if vCenter Server is not accessible at the same port.
You cannot change the vCenter Server instance to which Site Recovery Manager connects. To connect to a different vCenter Server instance, you must install a new Site Recovery Manager Server.
If you are using credential-based authentication, you receive prompts to accept the vCenter Server certificate during the installation. If you are using certificate-based authentication, you do not receive a prompt to accept the certificate.
If you are updating an existing Site Recovery Manager 5.8 release to a 5.8.x update release or to a 5.8.x.x patch release, not all of the steps in the procedure apply.
If you created custom permissions that you assigned to the previous Site Recovery Manager instance, you must upgrade the Site Recovery Manager Server with migration. If you upgrade the Site Recovery Manager Server without migration, custom permissions are lost. See Upgrade Site Recovery Manager Server with Migration.
You completed the tasks in Prepare for Site Recovery Manager Upgrade.
Log in to the Site Recovery Manager host machine to upgrade. Log in using an account with sufficient privileges. This is often an Active Directory domain administrator, but can also be a local administrator.
Download the Site Recovery Manager installation file to a folder on the Site Recovery Manager Server host.
If you use an SQL Server database with Integrated Windows Authentication as the Site Recovery Manager database, 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 data source name (DSN) for SQL 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.
- Provide the user name and password for vCenter Server and click Next.
- Verify the Administrator E-mail and Local Host values and click Next.
- Select an authentication method and click Next.
You must use the same authentication method on both sites. If you attempt to use credential-based authentication on one site and certificate-based authentication on the other, site pairing fails.
Authenticate with vCenter Server by using credential-based authentication with 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.
Authenticate with vCenter Server by using a custom certificate
Select Load a 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.
- Enter the user name and password for the database, and click Next.
- Select Use existing database and click Next.
If you select Recreate the database, the installer overwrites the existing database and you lose all configuration information from the previous installation.
- Select the user account under which to run the Site Recovery Manager Server service.
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
Repeat the procedure to upgrade the Site Recovery Manager Server on the other Site Recovery Manager site.
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 Site Recovery Manager extension appears in vSphere Web Client.
If you are updating an existing Site Recovery Manager 5.8.x installation, you might need to clear the browser cache for the update to appear in vSphere Web Client. You might also see RPC fault errors when you log into vSphere Web Client for the first time after the update. Logging out of vSphere Web Client and logging in again removes the errors.
Select vSphere Web Client to verify that the build numbers for Site Recovery Manager Server and the Site Recovery Manager plugin reflect the upgrade.in the