Contents


Profile Settings - Block Level Copying

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.

There are several ways that changed blocks can be determined. Please choose whether to use Checksums, File System Monitoring, and whether checksumming should use the Remote Service for the right-hand side. If the Remote Service is not used, a local database will remember the checksums for the destination side. If the Remote Service or File System Monitoring is used, block level copying can work with a remotely stored source file too. Otherwise, it is recommended to install Syncovery on the same machine where the data is stored, so that block level changes can be detected quickly.

Use Remote Service to Copy Files for Block Level Copying + Versioning
When combining block level copying with versioning, Syncovery can either upload the changes in separate compressed files every time (= Synthetic Backup), or it can use the Remote Service to make a copy of the file, so the older version can be kept separately, and the newest version can be updated on a block level. So this checkmark helps combine block level copying and versioning if you don't want to use compression, encryption, and Synthetic Backup. The Syncovery Remote Service must be installed and configured on the destination system.

See also: Block Level Copying (Partial File Updating)