This section details the files and directory locations used by the SYNCHRO Server during its operation.
All SYNCHRO Server executable files are installed into the following directory
This location may be selected during the installation process (see Installing the SYNCHRO Server for further information)
All project files are stored in the following location:
again, this directory may be selected during installation of the server, or modified by changing the Server Configuration file.
|Note:||Changes to the Server Configuration only take effect when the Server is restarted...|
For each project deployed, the SYNCHRO Server creates the following data structure:
|o||A SYNCHRO Project Database named <Project Name>.SYNCHRO.DB within the projects directory|
|o||A directory named transactions within the project directory|
|o||A directory named checkpoints within the project directory|
In SWP, a checkpoint is a running transaction log that keeps track of all project modifications since the last checkpoint.
The checkpoints directory stores checkpoint files.
|o||Depending on how the SYNCHRO Server is configured, checkpoints are serialised at certain points during the project. These checkpoints allow the SYNCHRO Server to rebuild the project information more quickly than relying on the transaction history alone.|
|o||Checkpoints are full project serialisations and should be tuned accordingly due to their large possible size. For example, consider a project that has a 10Mb project file and 8000 transactions applied to it; if a checkpoint was made after every transaction, then the project history directory would occupy nearly 80Gb of disk space. In this scenario specifying that the SYNCHRO Server checkpoint only every 50 transactions would save over 78Gb of disk space, since the directory would then only occupy 1.6Gb of disk space.|
In SWP a transaction is a modification to the project made by a connected SYNCHRO Client. Transactions applied to the project are stored in the transactions directory. The transactions directory contains the transaction history of the project and therefore:
Transactions are therefore the bridge between checkpoints.
If the SYNCHRO Server needs to rebuild the project information (due to terminal failure, or the issuing of a snapshot command by an SYNCHRO Professional client) then it looks for the latest checkpoint file, and then applies all the transactions that have happened since that checkpoint.