Cerberus in a cluster - Making only "Active" server run scheduled events
I've got 4 cerberus enterprise servers in a HA cluster. I'm using the events, more specifically, a scheduled event to run a powershell script on a schedule. The task runs on all four servers at the same time. Is there a way to specify which server is the "active" server that should run the scheduled tasks?
I tried disabling the scheduled event on 3 of the servers, but the sync manager overwrites the task, and reenables it. I do not want to turn off event syncing between the servers.
-
Official comment
Hi Jorge, you can disable the sync'ing of Events by Sync Manager and still sync everything else. Go to 'Sync Manager' on your primary Cerberus instance (the one sending the settings to the other 3 instances of Cerberus) and, on the 'Server List' tab, select each of your secondary servers. For each server, under 'Sync Options', you will see you can turn off 'Include Events' and press 'Update' to save. Turning that off will turn off sync'ing the Events from it to the other 3 servers. If you would like more detailed instructions, please open a Support Ticket at support@cerberusftp.com.
-
Please see my original post, last sentence:
I do not want to turn off event syncing between the servers.
0 -
Hi Jorge, sorry I did miss that. In that case you really don't have any good automated options as I'm afraid there is no way to 'nuance' which events get sync'd or not.
My only suggestion is this: Turn off automated sync'ing of events for the normal, automated, sync'ing. When there is a time you need to sync events, temporarily disable the Scheduled Tasks on the primary server. Then, go to 'Sync Manager' and, for each of the three servers, turn on 'Include Events' one time, press 'Sync' to run a manual sync, and then turn 'Include Events' back off again. Once you've completed the manual sync, you can turn the Scheduled Events back on in the primary server's settings.
Not ideal, but it at least prevents those Scheduled Events back being turned back on on the secondary servers and everything else gets automatically sync'd as desired.
0 -
I think I will try to finesse the powershell script to detect that one of the other servers has already ran it. I'm sure i'll run into a race condition.
We would never under any circumstances want to disable event syncing in the case of a failover to one of the other servers. Cerberus needs some "active node" detection for HA setups.
0 -
OK Jorge, sorry we could not provide a more workable solution via the application.
0
Please sign in to leave a comment.
Comments
5 comments