Known issues are resolved in this release of Site Recovery Manager:
SRM Fails To Complete Installation And Configure Firewall Ports
It is possible to install SRM into environments that use firewalls. For SRM to complete necessary communications, ports must be opened in the firewall. In the past, these ports were not opened. These ports are now opened.
Network Connection Problems May Make Service Restart Necessary
In some cases, network connections between SRM servers were lost. If a configuration change was made and a connection was lost, it was necessary to restart the SRM service for the changes to be applied. Configuration changes are now applied as expected, and no restart is required.
SRM Service Failed To Start Due Malformed XML
If a database field contained a string that was exactly 256 characters, the last character could be omitted. In cases where the field contained XML data, the last character of the XML close token was lost, resulting in an XML parse exception being thrown. Strings are now properly read from the database, regardless of item length, thereby eliminating this issue.
Disconnection Errors Occur In Environments Using Firewalls
Due to the way connections were managed, disconnection errors sometimes occurred when using SRM in an environment with a firewall. To resolve this issue, a timeout option has been added. By adding <WaitForUpdatesTimeout> to the vmware-dr.xml file, SRM is configured to wait for the specified number of seconds before closing the connection. The default value is 900, which equals 15 minutes. If disconnection errors are occurring in an environment with a firewall, set the <WaitForUpdatesTimeout> value to be less than the firewall timeout on connections.
Database Tables Are Lost During Installation Rollbacks
It is possible to complete an upgrade or installation using an existing database. In some cases, if an installation or upgrade failed, during the rollback process, the existing database was deleted. Databases from previous installations are now kept if a rollback is required.
SRM Service Encounters Problems With Duplicate Entries For A Volume
When multiple datastores are created in very rapid succession over a short period of time, vCenter Server may provide SRM with duplicate information about the new datastores. This might have occurred, for example, if one hundred datastores were created in one second. In the past, this created problems, but SRM now handles this information as expected.
Unregistered Windows Firewall Results In Installation Rollback
In Windows Server, in the case where Windows Firewall is unregistered, SRM installation could fail, resulting in installation rollback. This issue has been resolved, so installation now completes as expected.
Timeout of idle session between SRM Services results in problems with firewalls
Sometimes, idle sessions between SRM Services would result in firewalls closing connections. This issue has been resolved and SRM now checks its connected site regularly for updates rather than timing out.
Applying the Update
This update can only be applied to SRM 4.1 server. After applying this update, then update each vSphere client that is using an older SRM client plug-in.
Download the update and save it on a volume that is accessible to all of your SRM 4.1 server hosts. The update file name is VMware-srm-4.1.1-340092.exe.
To apply the update to an SRM server host, log in to the host as a member of the Administrators group.
Run the update file. The update installation stops the SRM service, installs the updated files, and restarts the SRM service.
Update the SRM plug-ins on client hosts. For each host whose vSphere client has downloaded, installed, and enabled the SRM 4.1 plug-in:
Close any open instances of the vSphere Client.
Use the Windows Add or Remove Programs tool to uninstall the VMware Site Recovery Manager plug-in
Connect to the SRM server that you updated in Step 3.
Follow the procedure in Chapter 2 of the Administration Guide to install and enable the new plug-in.
Removing the Update
To remove this update:
Use the Windows Add or Remove Programs tool to uninstall VMware vCenter Site Recovery Manager.
Install VMware vCenter Site Recovery Manager 4.1, as described in Chapter 2 of the Administration Guide.