Failover/Remote agent conflict behaviour

Hi

Found an undesirable behaviour that you might want to block in the next release; if you have failover active between two windows schedulers, and you put the standby up in remote agent mode by accident or design and then restart the primary then the primary goes into standby mode for the remote agent. If you knock down the remote agent then the primary comes up in master mode.

Maybe a check to see what mode the failover box is in?

That's a valid point. I agree that it should do more than just test if something is listening on the other end and the data is available there.

An enactment has been implemented in 3.4.30 to test to the remote component type and if it is not recognized as a master scheduler, abort the connection and don't attempt to replicate jobs. If you decide to upgrade, you will need to update both ends: master and standby.