Schemus Synchronization Tool Primary / Secondary Standby

book

Article ID: 170299

calendar_today

Updated On:

Products

Email Security.cloud Web Security.cloud

Issue/Introduction

A second installation of Schemus is required for backup or business requirements

How to fail over to the Secondary standby server

Resolution

It is possible to have more than one instances of Schemus installed however the key thing to remember is that only one instance should be scheduled to run updates at any one time.

If you have multiple instances updating you run the risk of addresses being continually added and removed this is because each instance of the tool does not know what the other has done and can lead to problems with Data Protection, Address registration and Web Security policies.

When Schemus performs an update it saves the changes it makes to a .sus file (local database file), at the below location.

C:\ProgramData\Schemus\configurations\(name of your configuration)\syncdata.sus

There is no way to automatically replicate changes to the below file from one server to another through the Schemus tool.

Schemus stores the settings you enter into the tool in the below xml file,

C:\ProgramData\Schemus\application\settings\settings.xml

And your configuration(s) are stored here,

C:\ProgramData\Schemus\configurations

The folder will be called after the name of your configuration.

Copying these files and keeping them up to date in the same locations on your second server will allow you to have the same settings and configuration on your secondary server.

Rather than having two version running all the time overwriting each other you can have one tool running updates (Primary Server) and one tool ready if the other has issues (Secondary Server)

 

In the event of your Primary Schemus server failing

*If still accessible any Scheduled tasks on the Primary Server should be disabled

Open the Schemus tool on your Secondary Server and run a Refresh, this will builds the .sus file on your Secondary Server with all the Addresses, Users & Groups which you have previously uploaded to ClientNet.

Next a Test Update should be run and the results studied to ensure it is safe to proceed with the update.

You can then run an update from your Secondary site and it will only update what needs to be added or deleted since the last synch was done from your Primary Server.

You can then set the tool at your Secondary Server to update on a schedule if you are having prolonged issues with Primary Server

 

Once your issues have been resolved with your Primary server the above steps can be reversed to fail back over to your Primary Site.