I have a problem with the fail-over mode

I start 24x7 on ServerA, it starts in Master mode
I start 24x7 on ServerB, it starts in Standby mode
I stop 24x7 on ServerA,
the 24x7 changes modes on ServerB, but it does not change to Standby mode
24x7 on ServerB changes to a stand-alone mode,
There is no designation of master or standby in the title bar

I checked the settings on both ServerA and ServerB
You have said to follow the directions here (in past forum posts)
http://www.softtreetech.com/24x7/archive/37.htm

All my settings look right to me
ServerA points to ServerB for location and
ServerB points to ServerA for location
Both are set to use port 1096
however
the page you mention displays the option
“Multi-instance synchronization enabled:”
but the Network tab in the 24x7s I have displays
“Distributed Server mode enabled:”
I have it checked
But I suspect this is my issue

Other info

ServerA running 24x7 version 3.424
ServerB running 24x7 version 3.426

Any idea on what is wrong

This is the default behavior. By default, standby server switches to auto-pilot mode after the master becomes unavailable.

If you rather want standby to switch to master mode, set registry variable "HKEY_LOCAL_MACHINE\SOFTWARE\SoftTree Technologies, Inc.\24x7 Scheduler\3.0\StandbyMode" to 2.
Note: StandbyMode is a DWORD value.

: I have a problem with the fail-over mode

: I start 24x7 on ServerA, it starts in Master mode
: I start 24x7 on ServerB, it starts in Standby mode
: I stop 24x7 on ServerA,
: the 24x7 changes modes on ServerB, but it does not change to Standby mode
: 24x7 on ServerB changes to a stand-alone mode,
: There is no designation of master or standby in the title bar

: I checked the settings on both ServerA and ServerB
: You have said to follow the directions here (in past forum posts)
: http://www.softtreetech.com/24x7/archive/37.htm

: All my settings look right to me
: ServerA points to ServerB for location and
: ServerB points to ServerA for location
: Both are set to use port 1096
: however
: the page you mention displays the option
: “Multi-instance synchronization enabled:”
: but the Network tab in the 24x7s I have displays
: “Distributed Server mode enabled:”
: I have it checked
: But I suspect this is my issue

: Other info

: ServerA running 24x7 version 3.424
: ServerB running 24x7 version 3.426

: Any idea on what is wrong

GREAT!, got that working now, however,

I can not create this senario when the 24x7 instances are services

testing enviornment:
job on ServerA running every minute that emails me
Start 24x7 as a service on ServerA, started first
Start 24x7 regular on ServerB, started second, it started up in STANDBY Mode...
(Good, the second instatnce knew that there was a service out there, running MASTER)
Shutdown 24x7 on ServerB
Start 24x7 as a service on ServerB, started third
Received first email from job
shutdown service on ServerA
waited twice as long as the connection parameters
no new email (from ServerB)
So ServerB did not become the master

so....

Does this cyclical fail-over configuration work with both instances of 24x7 running as services?
Is there another hack I can able to make the services act as MASTER and STANDBY instances?

: This is the default behavior. By default, standby server switches to
: auto-pilot mode after the master becomes unavailable.

: If you rather want standby to switch to master mode, set registry variable
: "HKEY_LOCAL_MACHINE\SOFTWARE\SoftTree Technologies, Inc.\24x7
: Scheduler\3.0\StandbyMode" to 2.
: Note: StandbyMode is a DWORD value.

Did you configure email settings on server B as they are on server A?

: GREAT!, got that working now, however,

: I can not create this senario when the 24x7 instances are services

: testing enviornment: job on ServerA running every minute that emails me
: Start 24x7 as a service on ServerA, started first
: Start 24x7 regular on ServerB, started second, it started up in STANDBY
: Mode...
: (Good, the second instatnce knew that there was a service out there, running
: MASTER)
: Shutdown 24x7 on ServerB
: Start 24x7 as a service on ServerB, started third
: Received first email from job
: shutdown service on ServerA
: waited twice as long as the connection parameters
: no new email (from ServerB)
: So ServerB did not become the master

: so....

: Does this cyclical fail-over configuration work with both instances of 24x7
: running as services?
: Is there another hack I can able to make the services act as MASTER and
: STANDBY instances?

yes,

I also created a second job to run every minute that creates a file with a timestamp
Niether the email is sent or the file saved after I shutdown the service on ServerA
and have already started the service on ServerB
How can I tell if a service started in MASTER or STANDBY mode?

: Did you configure email settings on server B as they are on server A?

What do you get in the schedule.log on server B? Does it have lines like "Found MAster schedluer" "Swithing to standby mode", any error messages or indications of what is going on?

: yes,

: I also created a second job to run every minute that creates a file with a
: timestamp
: Niether the email is sent or the file saved after I shutdown the service on
: ServerA
: and have already started the service on ServerB
: How can I tell if a service started in MASTER or STANDBY mode?