Nominal copy speed on 1Gb local network

[cristian.it]

Hello,
I don't know what could cause that, but the Windows API copying option was added for cases like these. Maybe I need to make it the default in future Syncovery versions.

Hi I´m using Symcovery to copy from a local server to cloud, but speed transfer is to low. I don´t understand how do you use de Windows API to fixed it.

Thanks

[tobias]

Hello,
for cloud servers, there is no option to use a "Windows API Copying Function". That's only for local copying.

Speeds may vary, depending on the cloud service and the Internet connection. In general, you can get high transfer rates only with very large files. If you copy typical office documents, the rates will be relatively low because each file can take up to a second to transfer.

Something you can do is increase the number of files being copied in parallel on the "Files" tab sheet in the Syncovery profile.

Can you provide more details on which cloud server you are using exactly, and what your file sizes are, and how many files you need to upload?

And which Syncovery version you are using ...

[cristian.it]

Thanks for your time.
We are using a Data Center in Bs As (Arg) so we made the copy using Syncovery uploading small files in some cases and the largest files are databases that weigh up to 2 terabytes, the version of syncovery is 9.50d.

[tobias]

Thanks. Which protocol are you using? For example, FTP, WebDAV, or simply UNC paths?

[cristian.it]

I´m using SSH/SFTP, implementation: TGPuttyLib

[tobias]

Hello,
OK that's great. You should be copying between 8 and 10 files simultaneously. Possibly more if the server allows it.

Please set the number of files to copy in parallel on the "Files" tab sheet in the profile.

In some cases, Syncovery may have switched to smaller block sizes because of transfer errors. Please check the section [LastSuccessfulSFTPBlockSizes] in Syncovery.ini. The block sizes should be at least 65536. If you see a smaller one, you can delete the line or change the number.

Upgrading to Syncovery 10 may enable additional speed improvements because it supports larger buffer sizes. The buffer size is specified on the Advanced SSH Settings dialog. You can find that dialog via the Internet Protocol Settings dialog in the profile, and there on the Security tab sheet, there's a button for the Advanced SSH Settings.

Remove the checkmark "Auto-Adjust Transfer Block Size" and specify an upload block size such as:
131072

The absolute maximum you can specify in Syncovery is 524288 bytes, because no SFTP server can handle larger sizes. Many will fail with sizes over 65536.

To ensure that Syncovery 10 will never switch to a smaller size even if there is a transfer error, add the following line to the [Main] section of Syncovery.ini:
NoPuTTYBlockSizeAdjustment=1

Note that Syncovery.ini should be edited with a modern text editor like Notpad++ and not the simple Windows Notepad, because it might corrupt some settings (there are some very long lines with special characters in Syncovery.ini).

Read more about Syncovery 10 here:
https://www.syncovery.com/syncovery10/

And here's an article about the latest developments:
https://www.syncovery.com/documentation ... elopments/

[cristian.it]

Thanks for your help, I'm going to try what you propose and then I'll let you know.