On October 27th the 4.1.2 release of SRM was published. It's a fairly small update, but has a few nice bug-fixes included:
- Site Recovery Manager 4.1 Test Failover Fails
- Recovery Fails When NFS Datastores are Mounted on Two Hosts with Different IP Addresses
- Rolling Back the Uninstallation of the SRM Service Fails
- Timeout During Network Customization of SUSE Linux 10 Virtual Machines
- Recovery Plan OS Heartbeat or IP Customization Timeout Settings Greater than 2000 Seconds Wait Forever
- Running the vCenter Site Recovery Manager dns_update script fails with the error "VMwareVMware was unexpected at this time"
- Creating a Protection Group or Protecting a Virtual Machine Fails with the Error: Operation Not Supported on the Object
- vCenter Server Session Does Not End when the vSphere Client Closes if the Remote Site is Unavailable.
- Unclear Error Message when Installation Fails Because the SRM User Account Does Not Have Administrator Privileges
- SRM Server Fails to Start the SRM Service if a Datastore Name is Invalid
- SRM Stops Responding During Failover when the Storage Array on the Protected Site is Offline
- SRM Uninstaller Does Not Remove Old SRM License Asset Data from the User Interface.
- Customization Specification Does Not Configure the Gateway for Red Hat Enterprise Linux 5.x.
Check out the release notes here:
-Ken
Related Posts:
