A mapping is an operation that associates an element of a given location (local Server path) with one or more elements of a second location (cloud repository), created for synchronization between a data source and a destination.

Create a Mapping

To create a new mapping between any folder on the local disc and either an existing SecuriSync top-level folder or a new SecuriSync folder:

  1. Right-click SecuriSync icon in tray and click Settings:
    Settings
  2. On the Mappings tab, click Add New Mapping:
    Add new mapping
  3. Choose a local folder
  4. Create a new SecuriSync folder or choose an existing one
  5. Click Add Mapping:
    Add new mapping

Manage Mappings

File Server Sync runs under the SYSTEM account.  In order to be able to sync the contents of mapped folders, the SYSTEM account has to have Full permissions on those folders and all of their contents.

If you notice that mapped content is not syncing, it is likely due to the missing SYSTEM permission.

  • File Server Sync log will show a warning such as this one:
    WARN | E6BB3BC7 | 55 | LocalIndexer | Failed to index folder 'D:\Site Photos\WaterProofing'. | Access is denied.
  • This issue can be fixed by adding the Full Control permission for the SYSTEM account at the top-level folder (on the File Server) and setting the permission to propagate down the folder tree.  After all the permissions are set, restart the File Server Sync windows service.

Important: removing the Full Control permission for the SYSTEM account for folders mapped to SecuriSync, once File Server Sync is running on a File Server, will put the application in an inconsistent state and result in undesired deletion of content.   

Notes:

    • if Choose existing folder option is selected, the folder can either be private or shared. For shared folders:
      • the user account used for File Server sync has to have Modify, Co-Owner, or Owner permissions on the folder
      • any existing content in the SecuriSync folder will be added to the File Server folder
      • any existing content in the File Server folder will be added to the SecuriSync folder
      • all sub-folders with matching names (from both sources) will be merged into one sub-folder with content both from SecuriSync and File Server. The app will recognize all files with matching names and content in source and target folders. These files will neither be synced again nor duplicated
      • all files with matching names (but different content) will be saved as conflict copies according to the following rule: files from Sync will be saved with original name, and files from File Server will be renamed as Conflict copy
    • if the target SecuriSync folder contains the same content as the source folder on the File Server (usually a result of adding a mapping, syncing the content, and then removing the mapping), when these folders are re-mapped, the File Server Sync app will recognize that the files and folder are the same, only new content would be synced to both the file server and the SecuriSync account
    • SecuriSync File Server Sync Windows Service is independent from UI App component, which allows to sync content even if Tray client is not launched or File Server is locked
    • the contents of mapped folders on File Server and SecuriSync will be synced. All subsequent changes made on either the File Server or SecuriSync will be synchronized.
    • if you stop SecuriSync Sync Service, then delete files from File Server, and add new ones, SecuriSync File Server will remove the files from the cloud, too, and sync new ones to the cloud once Sync Service is restarted. If files are deleted, added or moved using Web App when Sync Service is not running, all changes will be synced up to the File Server once Sync Service is restarted.


ImportantIf either the File Server mapped folder or the SecuriSync mapped folder is renamed, the mapping would be Deleted. By the same token, existing content on either side be kept, but the folders would not be synced any longer.

Known limitations with Mappings

  • Mapping cannot be created between the entire local disc and a SecuriSync folder
  • Mapping cannot be created between a mapped network drive or external hard drive and a SecuriSync folder
  • It is impossible to create Mappings between multiple source folders on File Server and one particular folder on SecuriSync
  • If a folder on File Server has an established Mapping, it is impossible to create Mappings for its child/parent folders
  • It is impossible to create a Mapping for a folder on File Server with a path longer than 256 symbols
  • Current mapping limitations are:
    • Full volume drive cannot be set up as source for mapping, for example, K:\ cannot be chosen to be synced, however, K:\Shared can be mapped with SecuriSync folder
    • Folder under the previously mapped folder cannot be chosen for new mapping. For example K:\Shared is mapped and K:\Shared\Presentations cannot be mapped separately. This folder will appear on $fileSync side underneath the folder that is mapped with K:\Shared

Delete a Mapping

To remove the mapping, click Remove next to the mapping name > Remove Mapping:
Remove mapping

Note: once the mapping is removed, content will be kept both on File Server and SecuriSync but these folders wouldn't be synced anymore.

Important: If you delete content on SecuriSync, the same mapped content will be deleted on the File Server, but it will be available in the SecuriSync Recycle Bin, and can be restored to both locations.

If a mapping is deleted by accident, the two folders can be remapped again. The File Server Sync app will recognize matching content in source and target folders and only sync any new files to both folders.