Automatic Agent Failover
Setup: Live Site 1 - RMS, MS1, OpsDB DR Site 2 - MS2, MS3, OpsDB Site 2 is a DR site. Log Shipping keeps the DB's in sync. I don't wish to use AD Integration (unless I am wrongly assuming it isn't needed). I want ALL my agents to communicate only with MS1. It will be the Primary (and only MS in use). Upon failure of MS1 only, I want agents to failover to MS3 only. Upon complete site failure, I also want agents to failover to MS3 only. Can I explicitly set this without using AD integration? I have seen a powershell command though I am unsure if it will lead to the same problem as AD integration i.e. potentail agent orphaning. (Obviously if MS1 was to failover to MS3 and then MS3 failed, I'd want MS2 or the RMS to take over i.e. automatic failover). Can I set several failover servers in order?
March 29th, 2011 9:59pm

Is the use of the powershell script in that first link in Graham's last post not essentially the same as using AD integration...with both procedures leading to the possibility of agent orphaning. Ideally (although not possible from what I have seen)...I would like all agents to be assigned to MS1, then if MS1 fails, MS2 takes over (then I suppose if it was to fail in the interim which would be unlikely, I suppose MS3 or RMS could take over). Unfortunately the scripts wont allow for that.
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2011 2:15pm

Yes...all machines report to OpsDB on site 1. Site 2 is simply a cold standby OpsDB for logshipping purposes. Yes, fast links across DataCenter. If I use the pwershell script, I assume it can only be used after agents have been deployed (i.e. not up front)...in which case (since agents are continually deployed), I assume I need to schedule the script to run daily?
April 11th, 2011 5:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics