The big news today is the release of VMware vSphere 4.1, but let’s not forget SRM! From the release notes:

New in This Release

This release of Site Recovery Manager introduces several new features and fixes:

  • Full compatibility with vCenter 4.1.
  • Support for IP customization of Windows 7 and Windows Server 2008 R2.
  • Test recovery times have been improved for ESX 4.0.1 hosts that use iSCSI arrays.
  • Full compatibility with vCenter Solution Licensing.
  • New configuration file options: change guest operating system shutdown retry timeout when customizing IP address during recovery, and change datastore discovery timeout during recovery (see Configuration Notes).
  • Full support for networks backed by a VMware vNetwork Distributed Switch (vDS) at the protected and recovery sites.
  • Fixes for several problems identified in previous releases. For more information, see VMware Knowledge Base Articles 1019890, 1021827, 1021491, 1021829, 1017882, 1021919, and 1021920.


SRM 4.1 server software can be installed only on 64-bit host platforms. The SRM 4.1 server is incompatible with 32-bit hosts. The SRM 4.1 client plug-in remains compatible with 32-bit hosts. Regardless of the database server you are using, you must install a 32-bit database client (ODBC driver) on the SRM server host. The SRM server is not compatible with 64-bit database clients.

SRM 4.1 is designed for compatibility with vCenter 4.1. SRM 4.1 is incompatible with vCenter 4.0 and earlier releases.

SRM 4.1 can be installed as a new release or as an update to SRM 4.0. You cannot install SRM 4.1 as an update to SRM 1.x releases.

The Site Recovery Manager Compatibility Matrixes guide lists all compatible versions of VMware vSphere components, and also lists supported supported databases and guest operating systems. Compatible storage arrays and SRAs are listed in Site Recovery Manager Storage Partners.

Installation Notes for This Release

You can install SRM 4.1 in one of two ways:

  • As a new installation on a 64-bit server host. This installation can either create a new SRM database or update an existing SRM 4.0database.
  • As an update of an existing SRM 4.0 installation on a 64-bit server host, which also updates an existing SRM 4.0 database to the SRM 4.1 schema.

Additional information about installing SRM is available in the following documents:

  • Getting Started with Site Recovery Manager provides a high-level architectural overview and workflow.
  • The Administration Guide includes step-by-step guidance on installing and configuring SRM. This guide contains information about all requirements and procedures to set up SRM and also addresses prerequisites and scaling limits.
  • The Site Recovery Manager Evaluation Guide provides a conceptual overview as well as step-by-step workflows describing planning for using SRM, setting up protected and recovery sites, testing failover, the failover and failback process, alarms and status monitoring, and a discussion of roles and privileges.

Note: If the SRM host is unable to contact vCenter during SRM installation, the installer will retry the connection for up to 30 minutes. Canceling the installation during the retry period can have unpredictable results. If you cannot correct the problems with the connection between SRM and vCenter, you should allow the retry timeout to expire so that the installer can terminate gracefully and roll back.

The VMware Uptime blog has posted a nice article about upgrading to SRM 4.1.