So Logscape does have the ability to run active/active Managers - which gives you the ability to have a secure Failover. But what if you don't have a spare server you can dedicate to being a Failover. Or what if you want to migrate to a fresh environment...
Enter the LogscapeFailoverApp-1.0 - a simple tool that allows you to reconfigure Agents to target a new Manager Agents. It's nothing complex, but it can help if you have several hundred agents to move at once. Once you have the source files:
1. Edit the lib\config.properties file and make the hostname property your new Manager (you can also change the ports if you want to)
2. Edit the bundle file to ensure that it's going to target the Agents you want - it defaults to Forwarders as they're the one's I tend to move around.
3. Zip it up into LogscapeFailoverApp-1.0 and deploy it. The required properties will be changed on all hosts.
However... there is one other step.
Here's the tricky part. Simply bouncing Logscape won't reset the Agents - the variable is cached by Windows Services. So you need to restart those agents before they'll contact their new parent. In the lib folder is a Powershell script RestartService.ps1 and a csv called serverlist.csv. Put the Windows hosts you want restarting into the Csv and run the Powershell (you'll need permissions to run scripts on the Hosts for this though). However you do it, on restart they leave the old environment and join the new.
Sorry Linux bods, I haven't written a bash script to automatically restart those agents (I haven't had a need to test it on a Nix environment). If anyone does, let me know if bouncing works or if you have a script that would do the trick!
