Windows Tips RSS feed for this section

OpenSSL update for Amazon S3 for Super Flexible v5.73

Some time in 2013, the OpenSSL libraries shipped with the older version 5.73 of Super Flexible File Synchronizer stopped working because of changes on the Amazon servers.

You will get SOCKET ERRORS with version 5.73.

To fix them, you can either install version 6 or replace the OpenSSL DLLs in the program folder with these updated ones:

https://www.syncovery.com/release/openssl.zip

Unzip the file and copy the DLLs to C:\Program Files (x86)\SuperFlexible or C:\Program Files\SuperFlexible on 32-bit systems.

Copying NTFS File Security (Permissions)

Syncovery can copy NTFS security along with files.

On the tab sheet Special in the profiles, you will find a checkmark called “Process Security and Shares”. On the dialog that pops up, you need at least three checkmarks on the left-hand side (Copy Owner/Group/Permissions).

In addition, the program needs to be running “As Administrator”. To ensure it runs as admin, you need to right-click its icon and choose
“Run As Administrator”, unless you have Windows versions older than Vista, or you have disabled UAC.

If using the scheduler, it probably needs to run as a service. Please see
Installing the scheduler as a service

System Requirements

Syncovery runs on:

Windows
All versions of Windows since Windows 2000 are fully supported. It runs on both 32-bit and 64-bit operating systems. The software itself is mostly 32-bit code, but includes some 64-bit code to enable Volume Shadowing on 64-bit Windows.

Macintosh
Syncovery runs on all Intel Macs, and on all Mac OS X versions since 10.4 “Tiger” up to including the latest version (currently 10.9 “Mavericks”).

To install it, you may need to go to the Mac OS System Preferences, Security & Privacy, and specify that you want to allow apps downloaded from: Anywhere.

An older version 5.73 is also available if you need to run it on older PowerPC Macs. This version also requires at least Mac OS 10.4 “Tiger”.

Linux
A version of Super Flexible File Synchronizer is available for Linux. It may or may not run on your Linux distribution. See the Linux download page for more details.

FTP over HTTP Proxy or SOCKS

One of the new features in Syncovery version 6 is the ability to connect to an FTP server via an HTTP Proxy as well as SOCKS. This feature is somewhat hidden in the software, so here’s how to find it.

If you are using the FTP protocol, then on the Internet/FTP dialog, change the FTP library to 2. Then on the Proxy tab sheet, you will see the option to use an HTTP Proxy or to use SOCKS to connect.

If you are using SSH/SFTP, Web Tunneling and SOCKS is also supported via the Proxy tab sheet. In that case, use library 1 (SFTP).

Running the scheduler as a service on Windows


This article applies only to Microsoft Windows.

Running the scheduler as a service is a little more difficult to set up, but it has some advantages. The service will start up automatically with Windows, even while no user has logged on yet. The
service runs invisibly in the background without users noticing it. A user can also log out while the service is running a job. Neither will disturb the other. The name of the service is the Syncovery Service.

Tips

  • The scheduler can run as a Windows Service. This means that scheduled synchronizations take place without users having to log on.
  • The service is installed and started from the Scheduler tab sheet of the main application window. If the “Background Scheduler” is running, please stop it and then choose Use: Service Scheduler. Then you will see the service-specific install/uninstall, start/stop buttons.
  • In order to access network drives, the service must be given a log on account. This is done when clicking on the Install… button on the Scheduler tab sheet to install the service. To change the log on account, please uninstall and then re-install the service. Make sure that you specify a user account where you know that Windows Explorer has access to the volumes that you need. Choose an account that has network access without Windows Explorer asking for a password for the network drive. Windows Explorer should have already stored the password.
  • Also in order to enable access to a network drive, please try using a UNC path such as \\servername\sharename\foldername rather than a mapped drive letter.
  • If this is not sufficient, you can provide a username and password for the network resource in each profile. Use this setting on the Job tab sheet in the profile: Network Connections… However, in many cases this is not needed. Rather than specifying the full path for the network connection, you can also try specifying just \\servername
  • Deleting to the recycle bin is not supported by the service.
  • Even though the service is normally invisible, you can get a pretty good picture of what it’s currently doing or planning to do, using the Scheduler tab sheet of the main application window. You can even connect to a remote computer and control and watch the service running there.