Migrating SRM during a vCenter Server migration and upgrade from 32-bit to 64-bit
search cancel

Migrating SRM during a vCenter Server migration and upgrade from 32-bit to 64-bit

book

Article ID: 309564

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

A vCenter Server migration and upgrade from 32-bit to 64-bit does not migrate a VMware vCenter Site Recovery Manager (SRM) installation.
This article provides steps to migrate SRM to another host during the migration and upgrade of vCenter Server from a 32-bit to 64-bit server.


Environment

VMware vCenter Site Recovery Manager 4.0.x
VMware vCenter Site Recovery Manager 4.1.x

Resolution

Caution: Perform the proceeding steps only after the successful completion of a vCenter Server migration and upgrade from 32-bit to 64-bit.
Before proceeding with the SRM migration and upgrade:
  1. Make a backup of the original SRM database. Do not skip this step.
  2. Check the VMware Product Interoperability Matrix to ensure that you are using supported versions of vCenter Server and SRM.
To migrate and upgrade SRM:
  1. Create a new database instance for SRM on the new server. The database instance can be on an independent machine, on the SRM server, or on the vCenter Server.

    Note: If the SRM database is already located on an independent machine and you want to continue using it, proceed to step 2.

  2. Export the SRM database tables from the original SRM server and import them into the new database instance. To determine the location of the original SRM database, locate the SRM entry in the ODBC Administrator (on the System DSN tab), and read the Properties. For more information, see http://windows.microsoft.com/en-US/windows7/Using-the-ODBC-Data-Source-Administrator.
    Note: The preceding link was correct as of July 8, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link.

  3. Install SRM 4.1.x. During the installation, select Use existing database instance and select the new database instance. The new database instance is upgraded.


Additional Information

Please note you will need to perform the following IF you already have an established SRA in place and SRM is coming from a 32-bit machine to a 64-bit machine.

Change the "scriptpath" value to include the "(x86)" value in the program files tree within the "dbo.pd_arraymanager" table within the SRM database.

For example:

C:/Program Files/VMware/VMware vCenter Site Recovery Manager/scripts/SAN/MirrorView SRA will need to be changed to: C:/Program Files (x86)/VMware/VMware vCenter Site Recovery Manager/scripts/SAN/MirrorView SRA if this is not done,

The installation will halt and the SRM Service will not start.

These warnings and errors can be found in the srm install logs.

Database Connection Information That SRM Requires(http--pubsvmwarecom-srm-51-topic-comvmwaresrminsfigdoc-GUID-515D8807-2D5C-4F1C-8E8F-B394D25E7AD1html)



Powered by Wolken Software