Adding a Sync

Once you have one or more remote servers defined, you are ready to add the remote server syncs to initiate the operation. The Remote Sync will specify the sync direction, remote path, whether to delete or keep synched files and folders, and name patterns for files and folders to be included or excluded from the sync.

For Sync, there are several options available to indicate the direction of the Sync. You have three choices:

1. Push to the remote server
2. Pull from the remote server
3. Two-way sync

This option uploads files and folders from the specified folder in your Files.com site and saves them to the remote server.

This option downloads files from the remote server and saves them in the specified folder in your Files.com site.

This option will push files from either server to the other so that both servers have the complete collection of all files. If the same file name exists on both servers with different file contents (as determined by file size), the last modification date is used to determine which version to keep. The file with the most recent modification date is then pushed to the other server. This option does not ever delete files from either server.

You have the option to delete files on the source server after a push or pull. Select whether you would like files that are successfully transferred to be deleted or kept on the source server. If you choose the delete option then only files in the source folder will be deleted while the corresponding files in the destination folder will remain unaffected.

When delete source files is selected, you have an option to delete empty folders from source once done syncing as an option to clean up empty resulting folder.

When syncing files to a folder with folder settings that alter file contents or filenames (e.g. GPG Encryption, GPG Decryption, or Filename rewriting rules), you should enable the option to delete files from the source. This will prevent repeated syncing of the same files every time the process runs, which could potentially lead to high transfer usage charges with no benefit to you.

The Remote Path is the folder on the Remote Server where you would like files and folders transferred, beginning from the folder/directory your remote user lands in upon authentication.

For example: if the remote server has a folder structure "folderA/folderB/folderC_"_, and the credentials land your user inside "folderA", then to configure your sync to use "folderC", you would enter the path as "folderB/folderC".

If the remote path doesn't exist then you can use the browse remote server feature to interact with the remote file system and create the required remote path.

You can specify name patterns for the items that should be included in a sync.

If set, only path names matching one or more of these patterns will be synced. Path globs are supported in the same way they are supported in Automations. Prefix patterns with **/ if you want them to apply to filenames in any folder or subfolder.

Multiple include patterns can be configured for a single sync.

You can specify name patterns for the items that should be excluded in a sync.

If set, any path names matching one or more of these patterns will be ignored and excluded from the sync.

This setting takes precedence over the include patterns setting if a path matches both settings.

If a folder name matches one of these patterns, it will be entirely excluded. That means that all contents of the folder, including all of its recursive subfolders and their contents, will also be excluded.

Path globs are supported in the same way they are supported in Automations. Prefix patterns with **/ if you want them to apply to filenames in any folder or subfolder.

Multiple exclude patterns can be configured for a single sync.