| Author |
Message |
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
 |
 |
You have 2 options really.
1. Use the default setup to allow the fail-over then manually bring the master up and manually stop the standby. This setup is documented in the manual and on-line help.
2. Use the semi-documented method for circular fail-over. In this mode the standby scheduler after taking over the processing starts it own network listener. The failed master, after it is brought up, on startup finds old standby now running as a new master, and starts in the standby mode. See http://www.softtreetech.com/24x7/archive/37.htm for details
PS. I heard of someone who tried to use the circular mode for making the master scheduler always start as a master. They tried using a batch file for starting the scheduler and made that batch first start a special job attempting to connect to the standby scheduler before starting the master. The special job was indented to restart the standby if it could connect to it. So in theory while the standby was restarting, the master scheduler could start as if it was the only one. I don't know if they have succeeded with this method and never tried it myself.
|
|
| Mon Sep 10, 2007 1:57 am |
  |
 |
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Ok after some testing I think I've discovered a flaw in the circular failover, when I knock down scheduler 1, scheduler 2 the original standby comes up in 'auto-pilot mode' according to the event log. The problem is, auto-pilot ain't master mode (doesn't display master in the title bar for a start) and if I bring up scheduler 1 again then it will not standby for scheduler 2 unless scheduler 2 is restarted while 1 is still down.
??
|
|
| Mon Sep 10, 2007 6:31 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
|
| Mon Sep 10, 2007 6:41 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
er......not the post you thought it was? :-)
Simon Ranger
Joined: 07 Dec 2005
Posts: 1
Post Phosphatidylserine Dmae Complex Reply with quote
Some people enjoy the phosphatidylserine dmae complex for extra action.
|
|
| Mon Sep 10, 2007 6:52 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
|
| Mon Sep 10, 2007 7:04 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
I've tried a circular failover with both schedulers in process mode successfully.
I'm now trying in service mode, I stop the master service and I see in the schedule.log of the standby
11/09/2007 12:33:48 1 0 0 24x7 Scheduler Synchronization with master scheduler failed! Requested server not active. Will retry 2 more times.
11/09/2007 12:36:48 1 0 0 24x7 Scheduler Synchronization with master scheduler failed! Requested server not active. Will retry 1 more time.
11/09/2007 12:39:48 2 0 0 24x7 Scheduler Synchronization with master scheduler failed! Requested server not active. Restarting in Master mode.
But nothing after that to indicate that the restart happened?
|
|
| Mon Sep 10, 2007 9:51 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
You should have a file called c:\24x7restart.bat. Edit this file and replace the contents with the following
 |
|
NET STOP "24x7 Scheduler"
NET START "24x7 Scheduler" |
Make this file read only and hidden. This should do the trick for the service.
|
|
| Mon Sep 10, 2007 10:55 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
That file doesn't exist at that location but I'll create it
|
|
| Mon Sep 10, 2007 10:57 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Ah it does on the standby not the original master
|
|
| Mon Sep 10, 2007 10:59 pm |
|
|
SysOp
Site Admin
Joined: 26 Nov 2006
Posts: 7969
|
|
| |
|
You actually need it in both places
|
|
| Mon Sep 10, 2007 11:42 pm |
|
|
LeeD
Joined: 17 May 2007
Posts: 311
Country: New Zealand |
|
| |
|
Right that works, any reason thats not fixed in the build?
|
|
| Tue Sep 11, 2007 1:15 am |
|
|
|
