FileCloud ServerSync Stages
Bandwidth, options, and limitations:
- FileCloud ServerSync will sync a maximum of 50,000 files per sync cycle.
- The amount of CPU and bandwidth used by ServerSync highly depends on the amount of files/folders scanned, uploaded, and downloaded.
- You can control the bandwidth allocated to ServerSync as well as the days and time syncing occurs.
- FileCloud ServerSync will be unable to Sync files if the file path exceeds 260 characters or if the file contains special characters.
You can reduce the time ServerSync takes to scan your local sync folders by changing the single-threaded logic used by default to run ServerSync to multi-threaded logic.
- FileCloud ServerSync can be configured to automatically resolve conflicts either using the local version of a file or the server version of a file.
FileCloud ServerSync can be run as a service.
To modify ServerSync's default configuration, access the syncclientconfig.xml file located under %AppData%\Roaming\FileCloudServerSync.
Restart ServerSync for the new settings/configurations to apply.
IMPORTANT: When modifying syncclientconfig.xml, follow the exact steps stated within our documentation. If a configuration is not added or modified correctly FileCloud ServerSync will not start.
FileCloud ServerSync Cycle
Stage 1: Server to Local Synchronization
- ServerSync initiates synchronization by pulling changes from the FileCloud server.
- ServerSync checks if it has records of the changed files in its local sync database, and creates them if they don't exist. It checks if the file exists in the local folder, and downloads it to a cache location if it does not. Then it goes on to the next file.
- As a final step of stage 1, it moves the files from the cache location to the local folder. Then it add these records to the local ServerSync database file. During this stage, ServerSync displays the message Moving to Sync folder when a file is download and Processing changes when files are added to the local sync database file.
Stage 2: Local to Server Synchronization
In the second stage, ServerSync monitors local sync folders for changes. Any modified files (added, updated, or deleted) are then uploaded to the FileCloud server. No new records are added to the local database during this stage.
Stage 3: Validation and Conflict Check
FileCloud ServerSync does a final sync from the FileCloud server to validate that the information on the local sync folder and the FileCloud server are the same.
It creates a record on the local sync database for any file/folder that has been uploaded during Stage 2.
FileCloud ServerSync checks for conflicts. By default, ServerSync requests manual user input to resolve conflicts; however, conflict resolution can be automated to always resolve conflicts using the local version of a file or the server version of a file.
Finally, FileCloud ServerSync downloads any new files from the server to the local sync folder and adds the new records to the FileCloud ServerSync database. During this stage, ServerSync displays the message Moving to Sync folder when downloading a file and Processing changes when adding records to the local sync database.
Once stage 3 is complete FileCloud ServerSync begins a new cycle.