VMware Site Recovery Manager (SRM) 5.0.2 and 5.1.01 Released!


VMware has released two new versions of SRM, Version 5.0.2 and 5.1.01

VMware vCenter Site Recovery Manager 5.0.2

  • Release Notes:


  • What’s New:
    • Added support for protection and IP customization of the following guest operating systems:
      • Windows 8 (32-bit and 64-bit)
      • Windows Server 2012 (32-bit and 64-bit)
      • RHEL Server 6.2 and 6.3 (32-bit and 64-bit)
      • Ubuntu 12.04

      NOTE: To protect virtual machines that run the above operating systems, you must upgrade ESXi Server to version 5.0 update 2 on both the protected and recovery sites.

    • The vSphere Replication management server accepts MD5 certificates. See Caveats and Limitations.
    • Upgraded OpenSSL 0.9.8m to 0.9.8t for improved security. This addresses the security advisory that was issued for OpenSSL in January 2012.
    • Auto-generated certificates use RSA keys of 2048 bits.
    • Bug fixes
  • Download:


VMware vCenter Site Recovery Manager

  • Release Notes:


  • What’s New:
    • Resolves critical issues in SRM 5.1. If you have installed SRM 5.1 (build 820150), you must upgrade your installation to SRM (build 941848).
    • Includes vSphere Replication If you have installed vSphere Replication 5.1, after you upgrade SRM to, you must also vSphere Replication to vSphere Replication
    • Bug fixes:
      • Installing SRM 5.1 or upgrading to SRM 5.1 using an imported certificate fails
        If you attempt to install SRM 5.1 or upgrade to SRM 5.1 using an imported PKCS12 certificate rather than an auto-generated certificate, the installer runs to completion but then fails with the error Failed to install certificate. See KB 2036909. This issue has been fixed in SRM
      • SRM Server on the recovery site fails during cleanup of recovery plans
        SRM Server on the recovery site fails repeatedly during cleanup if there is nothing to clean up, for example if there are no LUNs to detach, or no datastores to unmount. This problem occurs when the command to start the test recovery from SRM Server to the SRA reports success with at least one LUN, but finds no LUNs when the ESXi hosts on the recovery site run a rescan. This issue has been fixed in SRM
  • Download:


By Rotem Agmon Posted in Info

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s