Revolving around the core of technology
|Remote Server URL:||http://sync.xyz.com:5800|
|Restore Profile||DO NOT check|
Often users want to put the Syncrify server on one of the machine that is involved in synchronization. For example, machine 1 in the above example and have machine 2 and 3 run Syncrify Client.
Although this configuration is possible, it is not recommended for the following reasons:
- The Syncrify server creates temporary files on the server machine. Seeing these temporary files in your c:\wwwroot will definitely create confusion on a production machine.
- This can create synchronization problems. No one should be modifying files in the repository folder on the machine where the Syncrify server is running. Files in the repository should only be modified by Syncrify server. Consider a scenario where Syncrify client on machine 2 is running a backup and someone changes the contents of one file on machine 1. This can cause unpredictable behavior and can corrupt files.
- The repository path for the Syncrify server won't be C:\wwwroot. Meaning by default the backed up files are stored in
C:\Backup\firstname.lastname@example.org\WebSync\wwwrootfolder. Although you can change the actual path on disk by using Repository path exceptions or Junction Points, having a 4th machine is a much cleaner alternative.