I have installed two SRM 6.1.1 identically, pointing to local SQL server DSN at Primary (A) and Recovery (B) sites. The B site shows up in web client but A does not. I have reinstalled it twice, last time after cleaning up vCenter and PSC's MOB of any remnants of previous install -- removing all entries related to local server name, IP and vcDR.
Have rebooted the SRM server, have restarted the VMware web client service on vCenter, but still no joy.
When I try to Modify the SRM install, all settings seem correct; but when I tried to Repair, it failed at the very end. In other words, Repair damages it further!
In ODBC 64-bit, Tests completes successfully for DSN, but after attempted "repair", DSN is no longer seen by SRM. The Modify does not give option to point to DSN.
Please advise. Thanks.
Last time, your suggestions were better than VMware Support, so I decided to post here before calling VMware.
SRM certainly seems very buggy, odd. For example:
1. To modify settings, you have to go to Control Panel but first you must disable User Account Control (UAC) in registry and reboot. (Never saw such requirements with any other software in 20 years!)
2. Before Repair, the SRM service was running. Afterwards, service won't start. ("Break" may be better name than "Repair".)
3. On starting SRM, the green progress-bar goes all the way to the end (100%) and then starts again, and again.
Should we cut losses; drop SRM and start fresh with Zerto? Would appreciate feedback from other VMware users. Thanks.
AK