Using Multiple Schedulers

It is possible to configure SureSync to use multiple SureSync Schedulers located on multiple machines. This provides some redundancy in case a Scheduler service is down. It also allows you to launch Schedules and Real-Time Monitors on multiple machines from one SureSync installation. This allows you to distribute workload across multiple machines easily.
Using multiple Schedulers requires that the machines running the Scheduler service be able to access the same database and access a UNC path for lock files (when using SQL). Due to the lock folder location being a UNC path, the machines must be in the same domain or in domains with a trust relationship established. With workgroup/standalone servers, you can only use on Scheduler due to the permissions issues.

Installing and Configuring Multiple Schedulers

To configure multiple SureSync Schedulers do the following:

 

  1. SureSync should already be installed on a machine with a database configured and a Scheduler service installed. Details on this process can be found in the Evaluator's Guide and Installing the Scheduler topics.
  2. On the additional machines that will be running a SureSync Scheduler install the SureSync installer (SureSync8Setup.exe).
  3. Launch SureSync on each machine that will run a SureSync Scheduler and open the database that contains the Jobs, Schedules and Real-Time Monitors you're going to run. For the additional Schedulers you're adding this database will be on a remote machine.
  4. Once the SureSync Desktop user interface loads, click on the Home button and select 'Scheduler Services' from the menu. Add the Scheduler for the additional machine(s). This can be done by clicking on 'Install' if you don't already have the SureSync Scheduler installed on the machine. If you already have the SureSync Scheduler installed you can add it by clicking on the '...' button, browsing to the name of the machine in question, and then clicking 'Add'.
  5. After you have added the other Scheduler(s) make sure they all report '(Running)'. If any report '(Stopped)' click on the Scheduler name and then click 'Start' to start that Scheduler.
If you are using a SQL database each machine running a SureSync Scheduler must be able to open that SQL database. If you're using an Access database the same rule applies. In this instance if the Access database is stored on a local drive on the main SureSync machine then you will need to configure a share on the folder which contains the database so that the other SureSync installations can open that Access database via UNC path.

 

Enabling Multiple Schedulers for a Job

On the Options tab of a Schedule is an option which says 'Run Schedule on'. This option allows you to define which Scheduler should run that Schedule. By default the option is set to '(Any Scheduler)'. This allows SureSync to use any active Scheduler to run the job. SureSync will use the local Scheduler if it is available and if it is not then it will move on to the next one in the list. The same option is available on the Options tab of a Real-Time Monitor but is named 'Computer that should execute this Monitor'.

 

You can also force a Schedule or a Real-Time Monitor to use a specific Scheduler by selecting the name of the Scheduler from the 'Run Schedule on' or 'Computer that should execute this Monitor' drop down lists. SureSync will then always launch the job using that Scheduler. This will result in that job always being launched on the machine which is running the selected Scheduler.

 

The 'If the specified server is unavailable, use any server running the Scheduler service' option is checked by default. This option allows SureSync to run the Job, Schedule or Real-Time Monitor using any Scheduler from the Scheduler Server Services list (accessed by clicking Home and then Scheduler Services) if the primary Scheduler is unavailable for some reason. If you want a particular Job, Schedule or Real-Time Monitor to always run on a particular Scheduler this box should be unchecked. However, please be aware that if the defined Scheduler is offline for any reason then the task in question will not run until the Scheduler is restarted.