Does SyncBack work with WebDrive?

You'll need to change all the paths in this article as appropriate if you are using SyncBackPro, SyncBackSE 32-bit or SyncBackFree.

A number of users have reported that SyncBack works without problem with WebDrive (which allows you to access an FTP server as if it was a local drive, i.e. via a drive letter).

When using the Windows Task Scheduler you need to configure the job in SyncBack to run under the same Windows user account that you created your WebDrive site profile in. Make sure you enter a password as well as this is required for the Windows scheduler.

By default the command line passed to the Windows scheduler by SyncBack will look like the following:

"C:\Program Files\2BrightSparks\SyncBackSE\SyncBackSE.exe" -m "Profile Name"

where Profile Name is the name of the profile you created in SyncBack. If you plan on running this scheduled job while being logged in, this will work as-is.

However if you schedule it to run at say system startup or nightly after logging out you will need to change this command line to a batch file that you will need to create in a text editor. The batch file will consist of 3 lines as follows:

start /wait /D "C:\Program Files\WebDrive\webdrive.exe" /s:"YourWebDriveSiteName"
"C:\Program Files\2BrightSparks\SyncBackSE\SyncBackSE.exe" -m "Profile Name"
net use W: /d

1. The first line will use command line parameters in WebDrive to map the drive letter (adjust the path to WebDrive if different in your system).

2. The second line is the standard way to run the SyncBack profile. In 64-bit systems, this will likely use "C:\Program Files (x86)\..." instead

3. The last line simply disconnects the drive.

If you have problems with SyncBackSE/Pro not seeing the mapped drive then you may need configure SyncBackSE/Pro to run without elevation by using a different manifest file or by creating an alternate copy of the program that runs non-elevated. This article has details (again, based on SyncBackSE; adjust names and paths to suit if using SyncBackPro).

Note that running at the lowest security level means you cannot copy open/locked files, for example. It also means any profiles that are stored in the same folder as SyncBackSE/Pro cannot be used unless you have write permission to that folder (which is unlikely by default).

SyncBackFree does not run elevated so there is no need to change the manifest file for that version.