• State Not Answered
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 2174 views
  • Users 0 members are here
Options
Related

Synchronisation Service client on multiple servers

padams
over 4 years ago

Our initial plan was to setup two Active Roles servers in a production environment, each hosting the Web Interface and Administration Service. Both servers will connect back to a single SQL server hosting the Configuration/Management History database. There will be a load balancer sitting in front of the two Active Roles servers to distribute the load and provide fault tolerance.

We now would like to introduce the Synchronisation Service into play with intentions for it to have it's own database on the single SQL server.

My question is Can we replicate the installation of the Synchronisation Service on both Active Roles servers or should we only install it on one server?

Ideally we want to replicate both Active Roles servers to be configured the same but I am not sure if this will work if we were to set up the same connectors on the Synchronisation Service on two servers. Is all configuration within the Synchronisation Service stored in the single database and therefore we can install the SS client on all Active Roles servers wtihout any conflict issues?

Thanks

  • 0 over 4 years ago

    Both AR01,02 Sync Services can point to the Single SQL Cluster\ARS Inatnce\ARSyncConfig and ARSyncHistory Dbs. The scenario used for HA. Though AR Sync does not have automated HA. If AR01 Sync stops, you need manually to access AR02 Sync and repoint/set the Sync Job to run on the alive AR02 Sync Service.

  • 0 over 4 years ago in reply to Aidar.Karabalaev

    Thanks for your quick response. So just to confirm, lets take Azure AD for example. If I had a connector setup to sync with Azure AD, the sync job would only be running on one of the servers. If that server was to go offlline I would need to manually start the sync job on the other server?

  • 0 over 4 years ago in reply to padams

    I'm not sure about the concrete AR connector to AAD/O365. It is used on "background" to speed up the process, and upfront AR uses REST API to talk to AAD/O365 triggered by AR ADmin Service internal workflow triggered by manual/adhoc HelpDesk client calling the ARS Website. Therefore, the concrete way how AR Connector AAD/O365 utilizes AR Sync and HA dependency: I would recommend to open SR to get answer from Devs. That part used to change in past.