Sync and compare options are in legacy state and provided "as is", with no plans of future support or improvement, at least for now, but the option to sync only missing files should help in your case, since it performs synchronization only for the files with mismatching time stamps.

For anyone who's experiencing the same issue: in this particular case it seems to have been caused by setting thread count to 25. We recommend using higher thread counts only if you have any issues with large data sets, in all other cases better to leave this option at its default parameters.

Sorry, still don't see anything on my end. Make sure this forum thread is referenced in the support ticket so I can find it.

ok, thanks for the update. That's a reasonable number of files, so please continue working with support on this in case any problems occur during the procedure.

That's quite unusual. We actually start all plans with "starting, please wait" immediately once you click the "play" button. Can you provide a video or a gif?

Let me provide some insight on the problem:
Once OneDrive starts to throttle uploads it eventually simply cuts connection to their servers if you're transferring large amounts of data. 99% of the users who utilize this cloud storage have no idea on what's happening and start to contact us regarding this problem. Microsoft confirmed they are not going to change anything on their side, since they have Azure for the backup needs, so this leaves us at an impasse, where customers blame us for problems that are not possible to fix by our developers' alone.

I completely understand your frustration, but at this point the management decided to drop official support for OneDrive, Google Drive, and Amazon Cloud Drive.

I've not been informed of any logs from you by our support team, so if you didn't receive any notification regarding that please contact our support department first and create a ticket.

Check the message above, please. Currently you'd need to contact our support department.

You need to contact our support department regarding that.

What's the number of files you're trying to delete and what is the size of the repository? Since you mentioned "previous server", is this a fresh install on a new machine?

This is a per-plan option, you need to edit the corresponding backup job and modify this setting on the retention policy screen:

Better to manage all transitions via tools > lifecycle policy menu in the backup software, otherwise the application wouldn't be aware of any movement between storage classes in the cloud.

Ok, got it! Transferred that info to our R&D.

Can you elaborate on this please? What parameters do you want to see in that report? Is it simply for the plan settings like encryption/compression/VSS or something more in-depth?

Database is re-created automatically upon installing the software on a new machine, so technically there's no need to back it up. In case of disaster recovery you can switch destination to restore-only mode and restore your data without re-creating the database.

in a case where the system that runs the CBB backup s/w crashes and all data is lost,... how would CBB find / know about any backups it has made previously... — Mark Hamblin

The procedure is automatic. Once the application recognizes our folder structure that starts with CBB_%prefix% it'll automatically starts sync.

Hi!

Modified your initial message because it included your personal email.

Feel free to describe your issue here in more details so me, our product managers, or other users like you could help you with the problem.

Error messages like that are handled by support team and R&D. First of all, update the software to the latest version.
If that doesn't help we'd need diagnostic logs from the machine. Please add a link to this thread in the issue description.

In most cases block-level backup is not beneficial for file plans. If you have frequently changed files that are dozens of gigabytes in size, then that would be helpful, otherwise it doesn't affect file backups as much as image-based ones.

Synthetic full for VM backups is not yet available, so these plans would require normal full backups for proper versioning and purging.
Bandwidth cap is a pretty serious limitation, especially if we're talking about cloud backups, so, to be honest, I only see 2 ways to resolve this:
1) Install Server/Ultimate edition on each of your PCs and do image-based backups with synthetic full.
2) Upgrade your internet plan.

Synthetic for VMs should be introduced once we roll out our archive mode update.

You can use file and image-based plans to back up your the host, there should be no problems with that.