Syncovery's Scheduler can run your profile automatically and repeatedly. Just specify the desired scheduling below. After saving the profile, please make sure that the Scheduler is running by opening the Scheduler tab sheet in Syncovery's main window. As an alternative to regular scheduling, you can use Real-Time Synchronization. And you can always run jobs manually.

This tab sheet contains additional options for scheduling.
On Windows, note that jobs running on logout or shutdown should not take more than one minute because Windows will otherwise abort the logout or shutdown and return to the Windows desktop.

The settings on this tab sheet allow you to limit when a profile can run.
You can specify weekdays as well as a time window for the profile.

This tab sheet contains settings related to real-time synchronization and monitoring. Real-time synchronization depends on file system events, which are usually available for local folders and folders in the LAN. In addition, some cloud storages can be polled for changes. It is also recommended to combine real-time sync with a regular schedule to ensure that a full folder comparison is done.
Be sure to read our documentation about real-time synchronization.

Syncovery compares files by their names, sizes, and modification timestamps. There are several options to fine-tune the comparison. Certain time differences can be ignored, as they may be caused by different file systems - but only if the size is identical. In addition, you can choose what to do if the size is different, but the timestamps are identical.

This tab sheet contains additional settings to fine-tune how Syncovery compares files and folder properties. The checkmark that is most frequently change is whether to compare and mirror Folder Timestamps. When it is chosen, you may see many folders shown in the Sync Preview, all with the proposed action "time→". This is because Syncovery tries to make the folder timestamps match. If you find this confusing, you can turn the checkmark off.

Block Level Copying copies only the changed blocks in a file. It can be a powerful way to save time and bandwidth, but it works only with eligible file types, such as databases, Outlook PST files, and disk images. It is not always beneficial since it incurs additional CPU usage and may result in a large sync database and additional processing time. It works mainly with local destinations, network folders, and SSH/SFTP servers.

You will find all details on the documentation page on our web site.

Syncovery offers various ways to treat deleted files. On many storages, they can be moved to the Recycle Bin. As an alternative, deleted files can be moved to a specified folder. This feature is compatible with all storages and Internet protocols, and Syncovery can remember the deletion date by encoding it into the file name.

This tab sheet contains additional options for fulfilling less common requirements.

Syncovery can use Volume Shadowing for local drives to copy locked files, and also to create a consistent snapshot when the profile run starts. In some cases, it is better to turn Volume Shadowing off, especially if you want to avoid copying incompletely created files.

Choose whether Syncovery should create empty folders. Empty folders can occur if they are already empty on the source side, or if filename masks and filters cause files to be omitted.

Syncovery can remove folders that it has emptied because of file deletions. This is not frequently used because folder deletions are already mirrored by Exact Mirror and SmartTracking modes.

You can choose to create separate destination folders every time the job runs, if your backup space allows.
As an alternative, consider variables in the base paths to use rotating folders or different date formats.

Some use cases require a flat destination side with no subfolders, or only 1 or 2 subfolder levels. If you need a flat right side, choose this checkmark and specify the number of subfolder levels (typically 0).

This tab sheet contains additional options for fulfilling less common requirements.

Inclusion Masks are used to specify which file types and file names to copy. Here are some examples:
*.docx;*.xlsx (copy Word and Excel documents)
ABC* (copy only files with names starting with ABC)
Separate multiple masks with semicolon or Enter key. See the F1 help for additional examples, including the ability to use a text file with masks and reference it here.

Exclusion Masks are an effective way to exclude certain file types or names. Here are some examples:
*.tmp;*.bak;*Private*
You can also type complete folder or file names, such as:
Archive;Private.pst
To exclude a folder on the top level of the hierarchy only, you can use a backslash:
\Archive (this is not an absolute path, it's relative to the profile's base folder)
Don't Copy means excluded files aren't copied, but might still be deleted according to the sync mode.

These filters enable you to include or exclude files with certain properties, such as hidden files, offline files, pinned files, or files without the archive attribute. Additional settings on this tab sheet are related to links, such as .lnk links and symbolic links.

On this tab sheet, you can filter files by size or dates. File sizes are specified like this: 100K, 12M, 2G or 1T. When filtering by date, not that you should usually apply the date filter to Files only, not folders.

In Attended Mode, Syncovery may show various prompts to ask for your confirmation. You can turn the warnings off below.

The Special Safety prompts are shown in Attended Mode to ask for confirmation if certain thresholds are exceeded. You can change the thresholds or turn the warnings off below.

When jobs run unattended in the background (whether started manually or by the scheduler), Syncovery cannot ask you to confirm actions like deleting files or replacing newer files with older ones. Therefore, it is important to confirm these actions here, and adjust the limits according to your use case. For example, if you allow deleting up to 10% of one side, and there are more files to delete, Syncovery will disable deletions for that profile run, and you should review the situation manually. In such cases, you can see the file names that weren't deleted in the log file, or run the job in Attended Mode and study the Sync Preview. When running the job attended, you can confirm deletions that exceed the limits specified on this tab sheet.

The destination cache feature is a great way to speed up your sync profiles, since it makes the file list building phase very quick. However it can only be used for one-way sync jobs.
Please see our web site for additional ways to speed up your profiles.

Need to preserve folder and file permissions, or re-create folder shares on the destination?
Just use the checkmark below, which will open a dialog with the relevant settings.
For additional information, please refer to the documentation on our web site.

Syncovery's standard copying order is alphanumeric. You can change it below.

Another great way to speed up the folder scanning phase is to install the Syncovery Remote Service on the machine that you sync with. Whether it's a server on the LAN or a more distant machine that you connect to via FTP or other protocols, the Remote Service will provide complete listings super fast.

This tab sheet contains various settings which are used for special requirements.

Syncovery uses an SQL database if the profile uses one of the following features: SmartTracking, Delayed Deletions, Destination File List Cache, Block Level Copying, Synthetic Backup.

In most cases, you do not make any changes to the settings here.

There are two main ways to verify files and ensure that their content is 100% identical on both sides: Verification of files directly after copying, and verification of all existing files. Verifying copied files is recommended and while it makes the copying slower, the impact is still reasonable. On the other hand, verifying all files which already exist on both sides should usually not be done every time the profile runs. The Remember Results feature helps avoiding the re-verification of files already verified previously. Checksums (or hashes) can be used to speed the comparison up. Syncovery will use them automatically if a cloud service provides them. In addition, you can install the Syncovery Remote Service on the other machine to generate checksums remotely, which greatly speeds the process up.

Syncovery 11 is aware of a large number of file formats, and can analyze most of your files to verify the integrity of the internal file structure. The verification depth varies depending on the file types. The results of the integrity checks are shown in the log file, as well as the result summary. Unknown file types will be skipped. Sometimes, an integrity check may fail even though the file is still usable. This new feature does not use AI and does local processing only (no cloud service).

File Content Analysis can be used enforce exclusions and inclusions even when files have the wrong filename extension. For example, Syncovery can detect if a PDF file is actually an EXE file.

Versioning allows you to keep multiple versions of each file on the destination side, or even on both sides. Older versions are usually renamed so that multiple versions of a file can reside in the same versioning folder.

A related special feature is Filename Encoding, which will add the modification timestamp to all files on the right-hand side, not just the older versions.

Synthetic Backup combines versioning, compression, and block level copying. It allows you to back up larger files with incremental backups containing only the changed blocks. You can always restore the latest or previous versions of the file. As opposed to pure block level copying, Synthetic Backup works with all types of backup storage. Please see our web site for more details.

This tab sheet contains various additional settings related to versioning.

The first two checkmarks are the most important ones. During normal operation, Syncovery decodes certain filenames on the right-hand side. For example, it deduces the original file name from a compressed archive, if the archive name has been created and encoded by Syncovery. However, if you want to make another 1:1 mirror of such encoded files, then that mirror job should not decode any file names, and you need the first two checkmarks to be ticked.