Syncovery Support Forum

Not sure what's going on but almost every day the Syncovery.exe process will max out the CPU and remain stuck at 100%. I tried looking at the logs but did not see much. App also starts to hang and when I cancel the task I get Red Errors but it hangs and does not cancel.

Setting the app to use 1 CPU would then max out CPU and remain stuck at 50%. No further uploading would occur either.

Specs:
Virtual Machine running in Proxmox
Windows 10 Pro x64 (19045.4894) 22H2 with September updates.
2x CPU @ 2.9ghz
8GB of Ram (3GB used)

Configuration is Exact Copy Mirror (Left to Right)
Left: From SMB Network Share
Right: B2 BackBlaze
Filename Encryption with Format .sz

SOLUTION
This was fixed by going into Proxmox and setting CPU Type: to "Host"
In Proxmox
Click on "hardware" for the VM
Click Edit on "processors" and set "Type" to "Host"

Hello,
the error messages indicate that the Backblaze server are having issues. Errors include "Internal Server Error" and "Service Unavailable".

Syncovery will retry accordingly, but if this occurs too much, it will not work smoothly.

If you use many threads and compression and encryption, that will indeed use some CPU. You can reduce CPU usage by going to the Performance tab sheet on the Program Settings dialog and remove one of the CPU checkmarks, causing Syncovery to always leave one or more CPU cores free.

Please make sure you have the latest Syncovery version.

CPU usage can also be analyzed by right-clicking the job and choosing "Diagnose Activity". You can send such a report to support@syncovery.com.

You could also send longer or complete log files to support.

Maybe you need to reduce the number of files being copied in parallel, on the Files tab sheet in the profile. For Backblaze B2, I recommend using between 1 and 10 files in parallel. But if you upload really large files, don't go over 3. Each large file will use multiple threads on its own.

Thank you Tobias for that information I will send more logs to the email address.

Pretty sure I am on the latest version. Usually the app uses 1-10% max CPU but when it has an issue it hits 100% cpu.

This was Solved, please see 1st post in this thread for information.