Since that is API limitation on MS side we currently can suggest modifying certain configuration parameters manually, that can help.

1)
- close the Backup application
- open settings folder: C:\ProgramData\CloudBerryLab\CloudBerry Backup\
- find file enginesettings.list
- edit this file with notepad
- Find the string "10000000"
- change 10000000 to 2000000
- close and save the file
- restart the Backup application

2) Reduce number of threads (Tools/Options/Advanced) to 1.

Yes, Synthetic Full for Hyper-V/VMWare backups is also in the works.

Regarding Dedup - yes, that is possible.

No ETA on the release date yet, unfortunately.

Hi,

Synthetic full for local backups along with cloud ones is something we currently work on. Target release for this feature is version 6.1.

Yes, you will be able to perform various operations with the files, it doesn't matter how they were transferred to the cloud.

Just an update regarding the case: looks like the issue is related the problems with the repository. Synchronization should fix the issue.

Just an update in case anyone else encounter the same issue:
It is related to API limitations on Onedrive side. Uploads are being throttled due to the amount of data transferred.

Apparently no tickets were created regarding that, so let us know if you require support assistance in that matter.

Seems like no ticket were created in our support portal regarding that, so let us know if you still require assistance with the issue.

Hi,

Seems like the ticket was created regarding that and my colleague requested additional details about the problem.

I see a lot of "service unavailable" messages from B2 and connection errors like that:
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 162.244.62.198:443

So this is a complex issue that is related to both the issues on B2 side and issues in your network environment.

I understand that it's been 2 months since you created a ticket but you can re-open it by simply replying to it if you require any further assistance.

I see you'vre created a ticket regarding that and one of my colleagues provided some suggestions. Let us know if any further support assistance is required.

Seems like there were 2 threads created regarding this case. I see that the issue was related to some temporary problems in network environment and everything is working now.

A bit of an update on this one: looks like there were some issues with records in local database, so repository synchronization fixed the issue, judging by the communication in our ticket system.

Doesn't look like a ticket was created in our support portal, so let us know if any further assistance is required regarding that.

Judging by the support ticket the issue is related to the destination being not big enough, so proper resizing of the disk is required in that case.
Unfortunately we didn't receive any update on the case.

It doesn't look like a ticket was created by you in our support portal. Let us know if any further support assistance is required.

Just an update regarding this case: it looks like an SFTP misconfiguration, the storage is in read-only mode. Sorry, but you would need to tweak things on your side.
And yes, we can only provide limited troubleshooting steps regarding FTP configurations, since we consider it a legacy protocol.

It seems we didn't receive any diagnostic logs from you. Let us know if any further support assistance is required regarding that.

It doesn't look like any logs were sent from you. Let us know if any tech support assistance is required on that matter.

Unfortunately we didn't receive your diagnostic logs. Let us know if any tech support assistance is required on that matter.

Just an update in case anyone else is encountering the same issue:
Apparently that data was deleted manually and placed into a Recycle Bin by NAS, so those files were removed from being displayed in the software but still occupied HDD space.