Search the VMware Knowledge Base (KB)
View by Article ID
VMware vCenter Site Recovery Manager 4.1 Upgrade FAQ (1024175)
This article answers frequently asked questions about upgrading to VMware vCenter Site Recovery Manager (SRM) 4.1.
- What version of vCenter Server do I need for upgrading to SRM 4.1?
SRM 4.1 works only with vCenter Server 4.1.
- How do I upgrade to vCenter Server 4.1?
See the vSphere Upgrade Guide for details on upgrading vCenter Server 4.1.
- What server operating system versions can the SRM 4.1 server be installed into?
The SRM 4.1 server component can be installed into a 64-bit server operating systems only. If you are an existing SRM customer and are currently using a 32-bit operating system to host your SRM servers you need to migrate your existing SRM servers to one of the supported 64-bit operating systems. For a complete list of supported 64-bit server operating systems, see the Compatibility Matrixes for VMware vCenter Server Site Recovery Manger 4.0 and Later.
- How do I migrate from SRM 4.0.x running on 32-bit server operating system to SRM 4.1?
For details on migrating from SRM 4.0.x on 32-bit to SRM 4.1 server operating systems (64-bit only), see the VMware vCenter Server Site Recovery Manager 4.1 Release Notes and the VMware Uptime blog.
- Do I need to upgrade both protected and recovery sites SRM servers to SRM 4.1?
Yes, SRM requires identical versions at both protected and recovery sites. You need to upgrade vCenter Server servers and SRM servers at both the protected and recovery sites with vCenter Server 4.1 and SRM 4.1.
- If I have an existing SRM 1.x installation what is my upgrade path to SRM 4.1?
You need to upgrade to SRM 4.0 prior to SRM 4.1 upgrade. For details on upgrading to SRM 4.0 from SRM 1.x, see the VMware vCenter Server Site Recovery Manager 4.0 Release Notes.
- If I have an existing SRM 4.0.x installation with existing SRM databases, can I preserve the existing databases during the upgrade process or will the upgrade overwrite them?
You can preserve your existing SRM databases during the upgrade process. See the VMware vCenter Server Site Recovery Manager 4.1 Release Notes and VMware Uptime blog for more information.
Note: If you are re-using the existing SRM 4.0 database, you must specify the hostname and port of the local and remote vCenter Server hosts exactly the way you specified them in the previous (SRM 4.0) installation. For example, if the hostnames were specified as fully-qualified domain names, you must enter the same fully-qualified domain names during the installation of SRM 4.1. The hostname and port of the local and remote vCenter Server Servers are stored in the SRM database. If either of those hostnames or ports change, the SRM database is invalidated.
- If my existing SRM 4.0.x databases are installed on the same server as the SRM server component how do I upgrade to SRM 4.1 and preserve the existing SRM databases if I also need to migrate to a 64-bit operating system at the same time?
If the database is SQL, a new SQL installation should be done on the target server operating system (the 64-bit) and the database should be migrated. This is done by backing up the existing database and then copying it to the target server and attaching it to the SQL. After that, create a DSN that points to the migrated database and start SRM installation, providing the mentioned DSN on the database step.
- If my existing SRM 4.0.x databases are installed on separate database servers that are running 32-bit operating system versions do I need to upgrade the database server OS to 64-bit as well?
No. You do not need to upgrade the database server operating system to 64-bit.
- Should I backup both my SRM databases before I attempt any kind of upgrade?
Yes. It is important to create a backup of SRM database at both the protected and recovery site prior to SRM upgrade.
- Will the existing SRAs work with SRM 4.1 or do I need to download new SRAs before starting the upgrade process?
You can only use SRAs certified to work with SRM 4.1 by VMware. Please note that not all SRAs are certified to work with SRM 4.1 at GA. See the Site Recovery Manager Storage Partner Compatibility Matrix to identify if there is a version of your SRA available that is certified to work with SRM 4.1. If you do not see a version of your SRA that is certified with SRM 4.1, check with your storage vendor on their plans to certify their SRA with SRM 4.1.
- How do I upgrade the SRM vSphere client plug-in?
You can download the latest version of SRM vSphere client plug-in from vSphere 4.1 Client.
- Do I need to uninstall/disable the existing SRM 4.0.x plug-in inside my vSphere Client?
Yes. You need to uninstall the existing SRM 4.0.x plug-in inside the vSphere Client.
For more information, see
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.