In a large Site Recovery Manager environment, you might encounter timeout errors when powering on virtual machines on a shared recovery site.
When you power on virtual machines on a shared recovery site, you see the error message Error:Operation timed out:900 seconds.
This problem can occur if a single vCenter Server instance manages a large number of virtual machines on the shared recovery site, for example 1000 or more.
- Increase the remoteManager.defaultTimeout timeout value on the Site Recovery Manager Server on the recovery site.
For example, increase the timeout from the default of 300 seconds to 1200 seconds. For information about how to increase the remoteManager.defaultTimeout setting, see Change Remote Manager Settings in the Site Recovery Manager Administration.
Do not increase the timeout period excessively. Setting the timeout to an unrealistically long period can hide other problems, for example problems related to communication between Site Recovery Manager Server and vCenter Server or other services that Site Recovery Manager requires.
- Open the vmware-dr.xml file in a text editor.
- If you are using Site Recovery Manager for Windows, you find the vmware-dr.xml file in the C:\Program Files\VMware\VMware vCenter Site Recovery Manager\config folder on the Site Recovery Manager Server host machine.
- If you are using the Site Recovery Manager Virtual Appliance, you find the vmware-dr.xml file in the /opt/vmware/srm/conf/ directory on the appliance.
- Set the timeout for reading from the vSphere Web Client.
Set the timeout to 900 seconds (15 minutes) by adding a line to the
<vmacore> <http> <defaultClientReadTimeoutSeconds>900</defaultClientReadTimeoutSeconds> </http> </vmacore>
- Restart the Site Recovery Manager Server service.
What to do next
If you still experience timeouts after increasing the RemoteManager timeout value, experiment with progressively longer timeout settings.