Best Practices RSS feed for this section

Confirmations missing, deletions disabled and similar warnings

When a job runs in unattended mode, there can be some conditions which have to be confirmed when the profile is configured. For example, file deletions have to be confirmed specially, in addition to configuring the sync operating mode to include deletions.

To give the confirmations, please edit your profile in Advanced Mode, go to the Safety section at the bottom and choose the tab sheet “Unattended Mode”.

For an Exact Mirror profile, you would usually make sure that the top four checkmarks are chosen and that the last one is not chosen (Special Safety Checks). The first four checkmarks allow things like replacing files and deleting files. The last checkmark would impose additional safety checks which can prevent file deletions, so you’ll want to remove that checkmark.

In addition, you should specify a percentage of files which may be deleted during a profile run. You should not set this to 100% unless you expect that nearly all files are regularly going to be deleted. This is a safety percentage. If more files than allowed need to be deleted, the program realizes that something is wrong and disables the deletions completely. This will protect you against rare error conditions like disk errors or network communication errors, which can sometimes cause empty folders to be reported on the source side. Due to the percentage limit, the program will not delete everything from the destination if suddenly the source seems to be empty, or nearly empty.

However, even if you do specify 100% for deletions, the program will never delete all files in order to protect your data. If the source side is empty, it will throw an error and refuse to delete everything from the destination. This should be a good safety measure for most use cases. Some customers, on the other hand, have use cases where deleting all files is a regular, normal requirement. These customers can disable the 100% deletion protection by adding the following line to the [Main] section of the INI file:


(Add this only if you need to delete 100% of files in a destination folder in unattended mode!)

Keeping 5-7 Full Backup Copies of Your Data in Separate Folders

There are different ways to keep several versions of your files on your backup storage. Firstly, in the profile under Versioning, you can specify to keep a number of
older versions for each file. Each file will be versioned independently, and the Restore Wizard can restore your newest data, or restore according to a specified target date in the past.

However, some customers prefer to have 5 to 7 complete and independent copies of their data. To achieve this, you can use the variable $WEEKDAY in the destination path. In that case, you would not use anything from the Versioning tab sheet.

This will keep seven days of complete folder copies, if the profile runs on every day of the week. It will cause your backup folders to be named Monday, Tuesday, Wednesday, etc. and the next week’s backup is simply going to re-use the same folder from the week before.

For example, your destination path could be like this:
D:\Daily Backups\$WEEKDAY

Use Exact Mirror Mode to make sure that the backup is always identical even though the folder is re-used. Under Safety->Unattende Mode, allow file deletions as well as overwriting newer files with older ones (which will hardly ever be necessary, but should be chosen).

See also: Variables to use in your sync paths

How to deal with changing USB drive letters easily

A lot of customers ask how they can define a job so that it always copies to or from a USB drive, even if that drive’s letter changes. For example, on one day, your external hard drive might be drive F: and on another day, Windows changes it to drive G:.

The solution is to change the “Base Path” for the external drive in the profile. Instead of the drive letter, type the volume label (volume name). For example, if your drive is named MyUSBDrive, then you would type MyUSBDrive:\FolderA instead of F:\FolderA.

Amazon Glacier Backup

Since version 6.20, Syncovery can upload files to Amazon Glacier. To set up Glacier as the destination, click on the Internet button for the right-hand side and choose Glacier as the Internet Protocol.

Amazon Glacier is intended for long term archiving and backup with the expectation that most operations are uploads and not downloads. Downloads should be a rare exception, since they can be extremely slow. To download a file, Syncovery needs to initiate a job with Amazon Glacier, and even with small files, it takes at least three hours for Amazon Glacier to retrieve the item. The same is true for file listings. Therefore, Glacier cannot be used for two-way synchronizations. It is intended only for backing up and archiving.

Please be aware that there is a download fee from Amazon if you download more than 5% of your data per month (or something like that). It seems that in some special cases, the download fee can be extreme. If you intend to make a full backup and restore for testing, please read the fee schedule closely, and also read articles such as this one:
Is There a Landmine Hidden in Amazon’s Glacier?

Two methods to use Glacier

  • Choose S3 inside our software, and use a lifecycle rule in S3 to move files to Glacier to reduce costs. See the Amazon Web Services Blog
  • Choose Glacier directly in our software. The rest of this article describes this method.

Because there is no quick way to get a file listing from Glacier, Syncovery maintains a local database with the information of all the files on Glacier. This database is automatically maintained and it is independent from the checkmark “Cache Destination File List”. Therefore, with Glacier, there is no need to use the caching option. The local databases used for Glacier are separate for each vault, but shared among all profiles. When you create a new profile that accesses an existing vault, it will alraedy know the vault contents, if the vault has been used on the same machine.

Glacier also cannot rename items which have been uploaded. When you rename or move files on the local side, they have to be uploaded again.

In version 6.20, the download process is still inefficient if you need to download many files. It will initiate the download job for each file and wait for it to complete, then download the file, and then proceed to the next file. You can specify a number of files to copy in parallel in this fashion (on the Files tab sheet), but the limit is 30. So, you can download up to 30 files in 3 to 5 hours, but downloading 300 files will take 30 to 50 hours. This limitation will be removed in a future update.

In light of this, if there is a chance you will need a complete restore, it may make sense to use “Zip Packages” with many files per zip archive, instead of uploading individual files.

This information will be updated as support for Glacier is optimized and more experiences are made with Amazon’s new service.

Mountain Lion Compatibility

A Mountain Lion compatible update of Syncovery is now available. The version number must be 6.03 or higher.

To be able to continue using your old configuration and profiles, please use at least version 6.04 or higher.

The migration wizard should appear automatically, or you can invoke it via the File menu. You can also manually import config files via the File menu.

Since version 6.04, no special action is required any more to migrate your settings.

Creating Profile Groups

You can create profile groups by naming your profiles as shown in this example:

Backup Home
Backup Office
Backup Music

This will create the group “Backup” containing these three profiles because the first word in the profile names is identical.

Then you can easily select them or choose them with checkmarks (Windows only) and start them all at once.

Be sure to check out the right-click menu that you get in the Profile Overview. It contains options to start the profiles in various ways, such as:

  • Run in Attended Mode
  • Run in Unattended Mode
  • Run in Background

How can I make sure the scheduler starts automatically?

Method 1 (using the Background Scheduler – recommended)

The background scheduler is configured to start automatically when you save a profile that uses a schedule. You can also check the Auto-Start option on the “Tools and Settings” menu from the Scheduler tab sheet.

Method 2 (using the Syncovery Service – Windows only)

The main advantage of the Syncovery Service is that it runs even when no user is logged on. However, it is more difficult to set up and since it runs as an invisible service, it is less intuitive. For example, it can’t prompt the user in case an FTP password has changed, or when there is a SmartTracking conflict.

Using the service can fix some “Access Denied” problems because it normally runs with more privileges than the main program GUI.

You will find more information on the service here.

Copying open / locked files, such as Outlook or SQL databases

  • On Windows, the software can copy locked files by using the Volume Shadow Copy Service that is integrated into Windows. This feature is automatically used when needed. It can be configured on the tab sheet “File Access”.

  • On Macintosh or Linux, open files can always be copied unless “Database-safe mode” is chosen on the File Access tab sheet.

Modification dates of files are not retained. What can be done?

This problem usually occurs when using Internet Protocols such as FTP, WebDAV, as well as Cloud Services such as Amazon S3 and Google Docs. The problem does not occur with Windows networking (CIFS/Samba), SSH/SFTP, and many modern FTP or even some WebDAV servers.

FTP and WebDAV servers traditionally use the current system time for all incoming files. So the timestamp on the FTP server becomes different from the Last Modified time on your computer. In some cases, this is not a problem (for example if you only copy files to the FTP server). However, if you need to copy bidirectionally or really need to preserve the timestamp, here’s what can be done.

The best thing to do would be to install a more modern FTP server software that is able to keep the timestamps, for example the very latest Windows Server 2008R2 version, or Gene6 FTP Server from, or switching to a different protocol, such as SSH/SFTP.

If the server software can’t be replaced, you could use Filename Encoding to retain the timestamps on the FTP server. You’ll find that option on the Versioning tab sheet. Filename Encoding will modify the filenames by adding the date and time to them, so you can only use it if it’s OK that the filenames look encoded on the server.

If filename encoding can’t be used and you need to do a bidirectional synchronization, there is still another option. You can use SmartTracking, which can remember the timestamp that the server assigns to the files when they were uploaded. That way, it can recognize if the files have been changed or not, even if the timestamp is not identical to the one on your computer. For this, please choose the SmartTracking operating mode on click the Configure button. Go to the Options tab sheet and choose “Detect Unchanged Files” for the online side. Uncheck the other option “Also Ignore File Sizes” which rarely needed.

If you have already uploaded files and their timestamps do not match, you can use this SmartTracking method (as described above) to handle the problem. First you need to let the program build the database so that it remembers the existing timestamps. Do this by starting the profile manually and choosing “Show: Unaffected” in the Sync Preview so that it doesn’t copy any files but adds them all to the database.

Building the file list takes too long. How to make it faster?

There are various ways to speed up building the file listing.

  • Make sure you haven’t chosen “Binary Comparison” on the tab sheet Comparison->More.

  • If you are using “Process Security and Shares” on the Special tab sheet, make sure that in the pop-up dialog that appears when you click on that checkbox, you have not chosen “Update existing files” because that will be slow.

  • If you are using FTP, you can choose the recursive FTP Listing Command LIST -alR on the second tab sheet of the Internet dialog. If you are using SSH/SFTP and the server is a Linux/Unix type of server, you can try the “Recursive Listing” checkmark.

  • You can install the Syncovery Remote Service on the other computer to generate the file list remotely. The Remote Service is available for Windows and Mac.

  • If you have a one-way sync and you are just mirroring or backing up, you may be able to use the option “Cache Destination File List” from the Special tab sheet. However this option means that any changes on the destination by another person or program are not seen by the software, because it always remembers the last state in its cache and never looks at the destination folders again. Also please note that the cache is still slower than direct disk scanning of local drives and drives in the LAN. Use it only if you are copying over the Internet.
  • You can use Real Time Synchronization which simply copies new and changed files rather than comparing the two folder structures. However, it is recommended to also schedule a full run regularly to catch any files that may have been missed in real time. Also, Real Time changes are only detected on local drives and via LAN or VPN. Changes are not detected via FTP, WebDAV and so forth. Some computers or network devices may not be sending real-time notifications over the LAN.

  • If you only need to copy new and modified files to the destination and never delete any files from the destination, you could turn off scanning the destination completely (on the Files tab sheet), and under General Filters, use the two Archive Flag checkmarks (available on Windows only). On the first run, this will mean copying all files because the Archive flags are still set for all files. You can avoid that by adding a fixed date/time filter such as Date later than XX/YY/ZZZZ.

  • If the Archive Flags cannot be used, you could still turn off scanning the destination and use a File Age filter such as “less than 1 days” old.