SRM(Site Recovery Manager) Basic Troubleshooting.

Site Recovery Manager supports protection for up to 5,000 virtual machines and is able to simultaneously run up to 10 recovery plans containing up to 2,000 virtual machines. Up to 500 virtual machines can be included in a single protection group and Site Recovery Manager provides support for up to 500 protection groups.

Enabling debug logging for VMware Tools within a guest operating system

C:\ProgramData\VMware\VMware Tools\tools.conf

VMware Tools process	Description	Available in VMware Tools version
vmsvc	Primary VMware Tools service	All
vmvss	Volume Shadow Copy service	All
vmresset	Resolution Set Tool	All
vmtray	The Tray icon in Windows	All

Connecting to SRM server fails with the error: The remote server returned an error: (503) Server Unavailable (2012112)

Verify that the user account for Site Recovery Manager in Active Directory is not locked, the password for the user has not been changed since SRM was installed, and the password is set not to expire.
The Site Recovery Manager service may not be running. Check the services on the SRM server to be sure that the Site Recovery Manager Service is running.

Alternatively, you can change the stored password from the command line.
For example: cd C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin
Run the command: srm-config.exe -cmd updateuser -cfg ..\config\vmware-dr.xml -u <userID>
Follow the prompts from srm-config.exe to update the user credentials.
Run the services.msc command to open Windows service manager


Determine if the vCenter server's DNS name has been modified. If the hostname or the IP address has changed, ensure that extension.xml users at both sites must have the VRM remote.Manage VRM privilege assigned.

vSphere Replication transfers blocks based on the RPO schedule. If you set an RPO of one hour,vSphere Replication transfers any block that has changed in that hour to meet that RPO.

1 Use ssh into the vSphere Replication appliance and type:
# /opt/vmware/hms/bin/hms-configtool -cmd reconfig -property
2 Restart the HMS service.
# service hms restart
You can now unregister the embedded

Leave a Reply

Your email address will not be published. Required fields are marked *