Page tree
Skip to end of metadata
Go to start of metadata

Introduction

CapaInstaller Synchronization Service (CiSync) is a windows service responsible for synchronizing data between CapaInstaller Management Points, CapaInstaller Management Servers and CapaInstaller OS Deployment Servers. The data being synchronized can be software packages, OS images or simply (SMP)share content.

The purpose of the CapaInstaller Synchronization service is to keep the CapaInstaller Management Points or CapaInstaller Management Servers up to date.

The service, like all services, is controlled from another application; the CapaInstaller Management Console and more specifically; the System Administration, OS Deployment and Configuration Management plugins.


Element

Description

What is installed?

The service is always installed on the CapaInstaller management point.  but on the CapaInstaller Management Server, it is a choice you have to make.
 
If you don’t install the service (Advanced Synchronization) on the CapaInstaller Management Server, then the simple synchronization is used.
 
Simple Synchronization is a push action taken by the parent CapaInstaller management point, whereas Advanced synchronization is done by the installed synchronization installed on the CapaInstaller Management Server, as a pull job.
 
Installation of the Service can be selected during the installation of the CMS. Alternatively, it can be installed with a right-click action on the installed CapaInstaller Management Server.
 

What is sync?

Synchronization is basically the term used for the actions taken to ensure that two objects are equal. This is by far different from the task of copying from point A to B.
 
Synchronization will only copy the difference between the two, and furthermore, it will slash the remaining data on the target. This is the most cost-efficient approach when taking into account that network bandwidth should be minimized in order to reduce the time it takes to perform the actual synchronization.
 

When does it synchronize?

When you create a CapaInstaller management point or deploy a CapaInstaller Management Server then an initial synchronization is issued. To keep your servers up to date, you can set up a schedule to perform synchronization at regular intervals.
 
For example, it is a good idea to set up a nightly synchronization, so that the bulk load of data is moved while not in use by users and thereby avoiding access conflicts between clients trying to install a package, and synchronization services trying to update the server.
 
If you have urgent updates, it is possible to request an extraordinary update with a right-click on the server/point.
 

What is synchronized?

Essentially, all data, configuration, and packages.
 
 


Synchronization in CapaInstaller is divided into two technologies, that is either a push copy or pull synchronization.
The synchronization is a service that must have access to the CapaInstaller database.
If the computer holding the service is within the same domain as the SQL server, the recommended method for accessing the database is as Windows authentication.
Otherwise, SQL authentication is available.
Be aware that since each synchronization service requires access to the SQL server, a SQL Server Client Access License (CAL) must be obtained.


Element

Description

Pull Synchronization

Used when:

  • Target is a Domain server

    The synchronization is carried out by the target server service, hence the name; pull synchronization. The synchronization itself consists only of data that differs between the source and target and is compressed prior to copying. BITS is used to move the data.
     
    Orphaned software packages are deleted on the target.

Push Synchronization

Used when:

  • The target server is a NAS
  • The target server is a Workgroup Server
  • The target server is in a trusted domain

    This synchronization method is when it is not possible to install a working (and communicating) sample of the service on the target server.
     
    Push Synchronization is very simple. This is a file copy between the two servers. For this to work the service on the source server must be able to gain access to the share(s) on the target server; possibly by means of supplied credentials.
     
    Please note that there is no cleaning up of additional files on the target server.


Deeper description


 
 
Right-click on the sync service brings the following possibilities:

Element

Description

Remove advanced synchronization

This will remove the service from the server.

Synchronization Service Settings

This will show the property page for the service.



  • No labels