...
The third stage of configuration includes all the options specific to configuration type. This includes the path to the remote server or folder and any authentication details. The different remote synchronization types take the following details:
| Synchronization Type | Available Options | |||||
|---|---|---|---|---|---|---|
| Windows Network Share | Network share path in UNC format (\\server\share\folder, backslash separated), username, password, and domain. If a domain is entered as part of the username (in DOMAIN\User or [email protected] form), the domain field is disabled. | |||||
| Local Path | Local path in Windows path format (backslash separated) with optional username, password, and domain. If these are omitted, the path is accessed using the SYSTEM account of the Site Manager server. | |||||
| File Transfer | Type of protocol (FTP, FTPS or SFTP in the URI dropdown), Path to the server in URI format (sftp://example.com/home/backups/macrium, omitting the leading sftp:// and using forward slash separators), username and password for the remote server. A custom port may also be supplied.
| |||||
| Amazon S3 |
Further information can be found in this article. |
...
| Option | Description | ||
|---|---|---|---|
| Custom Name | The custom name is shown in the UI to identify the sync. If left blank, the server/local path of the sync will be used instead. | ||
| Folder Name | The folder name set here will be created on the server/remote path to store the synchronized backups.
Multiple repositories can sync to the same server/network path so long as the folder name is different for each one. | ||
| Synchronization Window - Times | The synchronization window controls what time of day the sync will run. When the start time is reached, Site Manager will stop scheduling backups on the repository, wait for any existing backups to finish then run the sync. After the sync has finished, backups resume. If the sync can't be started before the sync end time is reached, the sync attempt is abandoned until the following day. This option allows some control over when high internet bandwidth options like sync get run. | ||
| Synchronization Window - Frequency | The sync process can be limited to only happening on some days of the week by selecting the desired days here. | ||
| Options - Allow Backups During Remote Sync | If this option is selected, backups to the repository will be allowed to continue during the synchronization process, with some limitations.
| ||
| Enable per folder upload | Uploaded backups are committed to the remote location immediately after new data has been uploaded for each folder. A folder in the repository corresponds to the backups for an individual computer and backup definition. This option reduces the impact of upload failures by more frequently checkpointing so that less work is required to recover a consistent checkpoint and continue the sync on reupload. It can also reduce the amount of temporary storage space on the remote sync target as each checkpoint will flush old files that are no longer needed. When using this option, the remote store will always remain in a state where it can be rolled back to the last checkpoint should a connection be interrupted. This is generally not an issue - if the sync is retried after interruption, the sync will continue from the checkpoint until completion, but if the sync cannot be retried (due to repository disk failure for example), some folders in the remote sync will have the pre-sync contents and some post-sync contents. If there is a requirement that the backups for two computers remain in close sync (e.g. a replication set of servers), this option may be inappropriate. |
Finishing the Wizard
When finishing the wizard, a connection test is performed by the server and any errors are highlighted to be fixed:
...