SRM 4.0.2 GA

[emonjoin]

Site Recovery Manager 4.0.2 vient de sortir,il s'agit d'une maintenance release dont voici les corrections apporté :

Resolved Issues
SRM 4.0.2 corrects several problems in SRM 4.0.1. This release also includes those updates included in 4.0.1. For information on issues resolved in 4.0.1, see About SRM 4.0.1. This update can be installed either over 4.0 or 4.0.1.

This update corrects the following problems:

* Information about vNetwork Distributed Switches (vDS) is not properly preserved. During recovery, configuration of vDS was lost.
* Site Recovery Manager requires connections to remote vCenter Servers. If such a connection passes through a firewall and there is limited activity on that connection, the firewall may close the connection ungracefully.
* A recovery plan that includes multiple virtual machines all at the same recovery level and all with pre-boot messages would not result in the virtual machines starting as expected. The pre-boot message would appear and could be acknowledged on the first virtual machine, resulting in that virtual machine starting, but other virtual machines would not start as expected.
* The recovery process includes array discovery and synchronization of ports. If a new discovery process was started while an existing discovery was in process, the existing discovery would fail.
* Modifications to recovery plans did not save consistently. For example, the addition of command steps or messages might not be committed to the plan as expected.
* The version information for Site Recovery Manager was not correct. In some instances, Site Recovery Manager 4.0.1 displayed information indicating it was version 4.0.
* The Site Recovery Manager database schema was modified in such a way that could cause installation issues. This release supports the new database schema.
* The client might display error messages indicating that a recovery had not completed as expected. This was due to a failure to communicate final information about the completion of a recovery to the client.
* Site Recovery Manager operated inefficiently when shutting down a virtual machine with VMware Tools operations in progress.
* Recoveries that were stopped before completion sometimes left partially removed virtual machines. This was due to scheduling issues and required that users manually remove the virtual machines in question.
* Some Site Recovery Manager processes such as starting the service or creating protection groups took disproportionately large amounts of time to complete.
* When many operations were being completed simultaneously in an environment using DRS, insufficient threads could cause the operations to stop making progress.
* The primary Site Recovery Manager site could enter an unresponsive state due to errors in the way threads behaved.
* Installing Site Recovery Manager on 64-bit Windows machines failed due to issues with installation destination paths.
* Under certain conditions, components of a Site Recovery Manager installation were not displayed in the vSphere Client's view of the vSphere Server inventory. This issue occurred due to the creation of UUIDs that were longer than the supported length.
* It is possible to install Site Recovery Manager using an existing database. If such an installation is stopped, any partially completed changes should be rolled back, though some database changes were not reverted to their original state.