FAQ - What are the Minimum Specs for the CI Sync Multi-Source On-Prem Agent

Host VM Topology

• You should install the CI Sync Agent on a Windows VM that has low network latency to the on-prem data source it will read from (e.g. near your Lansweeper SQL Server or SCCM SQL server etc).

• The CI Sync Agent (Windows Service) does not need to be installed on a dedicated VM.

Host VM Internet Accesas

• The CI Sync Agent requires outbound HTTPS to the Internet to the following destinations:

  • To Microsoft Azure Login at https://login.microsoftonline.com (for the Agent to reach the App Registration created in the customer’s own Entra ID/Azure AD).

  • To the “extractor” API within your customer specific SaaS instance of CI Sync. The path to this will be https://yourcompanyname.syncfish.app/extractor (where “yourcompanyname” is the value you specify to Syncfish when your CI Sync SaaS instance is first provisioned).

Host VM Specifications

• The CI Sync Agent has compute requirements (hence it can be hosted on a shared VM as noted above).

• The following specs are for the VM Syncfish use internally to host our test/QA CI Sync Agent which is used to synchronize very large datasets on a regular basis. 

  • We use an Azure VM of “Standard D2 v3” with:

    • 2 x vCPUs

    • 8GB RAM

    • 127 GB SSD (max throughput of 60 MBps & Max IOPS of 500)

    • Standard SSD LRS.

    • Adding another 16GB of RAM will boost performance.

• We recommend at least Windows Server 2019 or later.

CI Sync “RecVer” Database

The CI Sync Agent’s relies on a CI Sync specific database to support our“delta sync” feature. Key points are:

1. The database is referred to as the “RecVer” database or just RecVerDB (you will see this term used in various Syncfish documentation).

2. Depending on certain factors (described throughout our setup documentation) the database technology can be either SQL or a local instance MongoDB.

3. If the RecVer database type will be SQL, then:

   1. The RecVerDB needs to be hosted on the same SQL server as the source system itself (e.g. if the source system is Lansweeper, then RecVerDB and Lansweeper SQL DB must be hosted on the same SQL server).

   2. SQL Edition: Must be at least SQL Express, however Syncfish recommend SQL Standard Edition to simply the setup of SQL Maintenance Plans.

   3. SQL Version: Must be 2014 or later.