DriveSync is used to synchronize files from a mobile device into a team folder on DSM. The setup works reliably.

In some cases, it is useful to access the same data through an additional path inside a different shared folder. This can be achieved on Linux/DSM using a bind mount, which creates an alternative access point to the same underlying directory.

The steps below describe the setup in detail.

Placeholders

• TEAM
  Name of the shared folder used by the Drive client as a team folder.
• MAIN
  Name of an existing shared folder where an additional access path will be created.
• LINK
  A subfolder inside MAIN that should point to TEAM. This folder must initially be empty.

Prerequisites

1. The shared folder MAIN already exists and may contain any data.
2. The shared folder TEAM has been created and is used by DriveSync as a team folder.
3. The user used for mobile synchronization has read/write permissions for TEAM.

Implementation

Create a scheduled task in the Synology Task Scheduler that runs as root at system startup.

The task should execute the following command:

mount -o bind TEAM LINK

Example:

mount -o bind /volume1/sync /volume1/main4sync/link2sync

Alternatively, the command can be executed manually via SSH as root.

Post-Setup Steps

1. Ensure that both LINK and TEAM have read/write permissions for the synchronization user.
2. Configure DriveSync on the mobile device to use the user with access rights to both paths.
3. Start synchronization using DriveSync.
4. Create a Hyper Backup task that backs up the TEAM folder.

Result

The contents of the team folder are now accessible via both TEAM and the alternative path LINK inside MAIN.

Important Note on Hyper Backup

If only MAIN is included in a Hyper Backup task, the TEAM folder will not be backed up through the bind mount. Therefore, a separate backup task for TEAM is required.