I am running a 24X7 version which has been patched to 3.3.1

I am attempting to run fail-over mode, configured to use WinSocks.

In attempting to test the fail-over mode I encounter several problems.

1. The standby Scheduler would attempt to fail-over to Master, if begins running jobs like a Master
but it doesn't go in Master Mode. ie(the window heading doesnt change to Master and when over 24X7(old Master) comes back up it wont recongnise this version as
a Master therefore fail-over is only possible once.
There is a message at the bottom of the screen which states that 24X7 is
trying to "initializing remote control interface" which last until 24X7
recieves another message.

2. Once during a test, I attempted to simulate a crash by closing 24X7 Master, the Standby was attempting to connect at this time.
This cause the Standby to hang trying to fetch information from the master.
Is there a way to ensure that this doesnt happen. It would be really bad if both Schedulers were to crash
because of 1 one going down.

The most recent version is 3.3.6.

In the current version fail-back is not supported. It is assumed that the personal should fix the problem and figure out if there is a need to avoid or manually restart certain jobs before stopping the Standby and restarting the Master.
Version 4 will support optional fail-back.

After taking the control the Standby scheduler should convert to the new Master if every required component for this mode can be initialized. Make sure you correctly specify Networks settings in the Tools/Options menu. It is possible to setup cyclical fail mode if the Master is configured to lookup for the Standby machine. In that case when the Master is restarted by the Standby is running after fail-over in the Master mode the old Master will switch to the Standby mode and so on...

In regard to the simulated crash: after certain period of time the synchronization should timeout and abort. I think the timeout should occur in about 3 minutes.

: I am running a 24X7 version which has been patched to 3.3.1

: I am attempting to run fail-over mode, configured to use WinSocks.

: In attempting to test the fail-over mode I encounter several problems.

: 1. The standby Scheduler would attempt to fail-over to Master, if begins
: running jobs like a Master
: but it doesn't go in Master Mode. ie(the window heading doesnt change to
: Master and when over 24X7(old Master) comes back up it wont recongnise
: this version as
: a Master therefore fail-over is only possible once.
: There is a message at the bottom of the screen which states that 24X7 is
: trying to "initializing remote control interface" which last until
: 24X7
: recieves another message.

: 2. Once during a test, I attempted to simulate a crash by closing 24X7
: Master, the Standby was attempting to connect at this time.
: This cause the Standby to hang trying to fetch information from the master.
: Is there a way to ensure that this doesnt happen. It would be really bad if
: both Schedulers were to crash
: because of 1 one going down.

I am attempting the procedure you describe in the second paragraph of your response.

Are you saying that it wont be possible until version 4 or are you saying that I did something wrong.

If you are saying that I did something wrong, I dont see how that is possible. This aint rocket science. There are such few options Tools/Options and everything else seems to work fine.
I have both set to connect to default port (though is on the different machines) could this be a problem?

Maybe you could tell me what exactly is "initializing remote control interface" this is the problem. What would cause it to stall?

: The most recent version is 3.3.6.

: In the current version fail-back is not supported. It is assumed that the
: personal should fix the problem and figure out if there is a need to avoid
: or manually restart certain jobs before stopping the Standby and
: restarting the Master.
: Version 4 will support optional fail-back.

: After taking the control the Standby scheduler should convert to the new
: Master if every required component for this mode can be initialized. Make
: sure you correctly specify Networks settings in the Tools/Options menu. It
: is possible to setup cyclical fail mode if the Master is configured to
: lookup for the Standby machine. In that case when the Master is restarted
: by the Standby is running after fail-over in the Master mode the old
: Master will switch to the Standby mode and so on...

: In regard to the simulated crash: after certain period of time the
: synchronization should timeout and abort. I think the timeout should occur
: in about 3 minutes.

Sorry if I wasn't clear.
Version 4 will support automatic fail-back when the original Master is restarted meaning that the Standby working as a Master while the original Master is unavailable will go back to the Standby mode and the original Master will always run in the Master mode.

Version 3 already supports cycling Master/Standby. This means that when the Standby takes over it becomes the new Master. When the original Master is restarted it becomes the new Standby and so on… It is like switching roles. To implement such cycling both Master and Standby should be configured to use the same port and point to the each other in the Location properties. Please see http://www.softtreetech.com/24x7/archive/37.htm for more info.

The "initializing remote control" message should not appear for a long time. More likely you should just blink. If the remote control cannot initialize the Standby cannot switch to the Master mode. Please upgrade to latest version to see if that will fix the problem.

: I am attempting the procedure you describe in the second paragraph of your
: response.

: Are you saying that it wont be possible until version 4 or are you saying
: that I did something wrong.

: If you are saying that I did something wrong, I dont see how that is
: possible. This aint rocket science. There are such few options
: Tools/Options and everything else seems to work fine.
: I have both set to connect to default port (though is on the different
: machines) could this be a problem?

: Maybe you could tell me what exactly is "initializing remote control
: interface" this is the problem. What would cause it to stall?

I have upgraded to 3.3.6 and still the Standby does not become a Master. The standy does
become an active scheduler which can run jobs like the master but it doesnt act like a master.
In that there is no Master in the Windows heading and likewise it still does not allow fail-over more than
once (since when crashed master comes back it will become a master since it cant detect another master)
Therefore it doesn't support cycling Master/Standby.

: Sorry if I wasn't clear.
: Version 4 will support automatic fail-back when the original Master is
: restarted meaning that the Standby working as a Master while the original
: Master is unavailable will go back to the Standby mode and the original
: Master will always run in the Master mode.

: Version 3 already supports cycling Master/Standby. This means that when the
: Standby takes over it becomes the new Master. When the original Master is
: restarted it becomes the new Standby and so on… It is like switching
: roles. To implement such cycling both Master and Standby should be
: configured to use the same port and point to the each other in the
: Location properties. Please see
: http://www.softtreetech.com/24x7/archive/37.htm for more info.

: The "initializing remote control" message should not appear for a
: long time. More likely you should just blink. If the remote control cannot
: initialize the Standby cannot switch to the Master mode. Please upgrade to
: latest version to see if that will fix the problem.