Remote Service Usage

[superflexible]

This is only the total size of the files processed. It does not mean what amount is actually copied. You can only see it in the logs.

[armopop]

I posted the lines you were referring roght before posting the picture. Would you please check it and confirm?
Thanks

[superflexible]

Yes, these lines confirm that it is working fantastic:

Transfer amount saved due to partial file updating : 144.9GB
Remaining actual transfer amount for eligible files: 6.7MB

[armopop]

Yes, these lines confirm that it is working fantastic:

Transfer amount saved due to partial file updating : 144.9GB
Remaining actual transfer amount for eligible files: 6.7MB

So just to confirm, the actual amount that went on our WAN link is the 6.7MB and the Transfer amount saved was only comparison of files?

[superflexible]

The actual amount that went thru the WAN link was the 6.7 MB plus possibly some files which were ineligible for block level copying, such as Office documents. I could tell you more if I could see the complete log.

In addition, there is some transfer while comparing the files. It takes a while because both the Remote Service and the local Syncovery have to calculate MD5 checksums for each block in each file. Then these checksums are downloaded from the Remote Service and compared. Then Syncovery knows which blocks to copy from the actual files. In this case, the checksums downloaded were probably a few MBs more than the actual data that had to be transferred. But no statistics is available on the size of the checksums, because they are negligible when compared to the sizes of your files.

You could choose "Fast Mode (process target directly)" which might be a little faster because no local copy of the file is made prior to the block level updating.

[armopop]

Awesome, thanks for all your help.