The detailed exception is: features 'cketTimeoutException: Read timed out' Workaround: Rerun the operation when other operations on the ESXi Server have finished.
To upgrade vSphere features Replication you must vmware use vmware either the downloadable ISO, or the virtual appliance management interface (vami) of the vSphere Replication appliance.Connect to the database on the recovery site and delete the entries in the pds_rdmrecoveryinfo table.If you have a replication with an excluded disk and later reconfigure the replication to include that disk, and then you manually copy a disk file to use as a replication seed, vSphere Replication removes the copied.vmdk file, ignoring the fact that it was.End (Operation added with duplicate tag.See also vSphere Replication Server Registration Takes Several Minutes.Replication stalls after reverting features to a snapshot vmware if this snapshot was taken while replication was paused.In vSphere.5, if the vSphere installer detects Active Directory features services, it does not permit you to install vSphere Client.Restart the vCenter Server and SRM services. VSphere Replication reconfigure or move operations fail with the error SocketTimeoutException: Read timed out and tanpa replications go into the Error state.
Operations on vSphere Replication sometimes fail with a read timed out error.
SRM now attempts to guide shut down a virtual machine 3 times radio before sending the error.Reconfiguring replication to include a disk that style was previously excluded, and using a replication seed for this disk, results in update vSphere Replication erroneously removing the replication seed.SRM Server stops unexpectedly during reprotect forced recovery.Workaround: Rerun the recovery plan.For each of the n-rows that you radio inserted in step 5, update the values of the columns as follows: recovereddeviceinfo unique_key n peerdevicegroup ' peerdevicegrouphasvalue 0 For each of the n-rows inserted in step 5, create a new row in the pds_recovereddeviceinfo table galaxy as follows.This issue radio occurs in all cases where non-ascii passwords are used with vami.Repeat the upgrade process on the recovery site.In such a case, the virtual machine's status in the protection group changes to Invalid: Virtual machine 'VM' is no longer protected.Uninstall the SRM.5 client plug-in.
However, at the same time, vmware srm 5.5 features ESXi Server mounts the volume successfully.
After completing this for all affected virtual machines, re-run the recovery plan.