What version is that?

If you want to use the new backup format, you'll need to reupload. Consider using it for new customers / endpoints once you play with it a little and get a feel for the new features.

You can use any Windows edition on Windows Desktop operating systems. You should reach out to support and see what the price is to add a higher maximum storage allowed to the Desktop Edition. Depending on the total storage needed, that might be a less expensive option than moving to Ultimate. If that does not look like a good option for your needs, then Ultimate may be the better choice.

A couple things you can try:

1. Try increasing the number of threads - maybe to 7. While I agree that 20Mbit is low if your upstream bandwidth is higher and available, you may have more luck running some additional streams. I assume you have at least 8 CPU cores. If you have more, you could try 8 threads as a test.
2. Try using a larger chunk size. 10MB Chunk Size may be too low as it will create a large number of chunks - and that requires additional I/O. Maybe try 50 MB and see how that goes.

I would try one test at a time.

Can you tell me if you're uploading large amounts of very small files and also if you're using the new backup format or using the legacy format?

how many threads are using for uploads? Is this a purchased pro edition or are you using freeware? I asked because freeware is limited to single-threaded uploads. I don't believe backblaze has posted any upstream bandwidth limits to B2. Any limits are usually single stream limits but products like ours that can do multi-stream uploads through multi-threading can get far superior speed.

I think you'll need to open a support case in order to get this resolved. It may be related to the errors you're seeing in the log. Please use the diagnostic option in the client to submit the logs to support and mention that I asked you to open a support case in case you don't have maintenance.

how do you have the external USB drive formatted? What file system? If it's ExFAT that's probably the issue.

Can you specify the version of the product you're using? And also let us know if this is using the new backup format or the legacy format. This is a file backup? You say you're backing up locally, but are you backing up locally to a dedicated drive but can you specify if this is a direct attached storage drive or is it a USB drive, and if USB are you connected through USB 3.0? Also can you check the logging in options to ensure it's not on high. If it is move it to the lower default option and try the backup again. Another thing you can check is the multi-threading settings in options. You want to make sure you're not overloading your CPU during the compression and encryption phase. Either way back up that small should have been pretty quickly. If we can't figure it out here I'll have you open up a support case so the team can review your logs.

You can open the same of different buckets in B2 in both panes of Explorer. You should see a Move option on the right-click context menu. The move operation may require the object is first copied locally and then moved back to B2. I would test on a file large enough that you can see if this happens since that's a concern. B2 used to not support moving objects. They may have added it recently, possibly when using S3 compatible buckets, but I'm not sure. If you see the data copied locally from Explorer, you may want to reach out to Backblaze and ask them - they may have such a capability from their management interface if available.

Based on your description, you can likely delete the data from Reporting > Capacity Report for the user and prefix no longer used.

In the future, please do not use Explorer to remove data. Delete backup data via the Organization > User > Cross button or via the Backup Storage tab + subsequent automatic sync from the agent before decommissioned.

Using the legacy backup format is fine and fully supported, and will continue to be supported for a long time. I don't suspect that's the issue. If you continue to run into the same issue please reply here.

I'll move the post. Without some error in the logs, it's hard to know if the problem you had was just an intermittent one. Can you clarify the backup version, the type of backup (file, image, VM, etc.), and whether you are using the new backup format released with 7.0 or the legacy backup format (you can tell this quickly in the backup wizard Retention tab - if you see GFS options you are using the new format. If you see File Version based retention options, you are using the legacy format). Thanks.

You posted in the Managed Backup section of the forum. Are you using Managed Backup or stand-alone?

I would request you submit the logs to support either using the agent's tools diagnostic toolbar option or from the management interface under the gear icon for that endpoint. There may be something in the logs that support sees.

That's a service user account for authentication for likely more than one agent (or all) at the customer. Are you saying that service account is used only on a single endpoint?

okay I'll have the team verify and I'll get back to you. It may take a few days for them to get through some testing. The limitation was not added with 6.0 but it's possible you're running into another unknown issue, so let us check and I hope you can be patient while we look into it.

That's what happened. When you trial the product, it trials in full Pro mode so you have access to all features and can make an informed decision about whether it's a good fit for your needs. I am guessing that is when you originally backed up the files to B2. When the trial ends, if you do not purchase a Pro license, the software falls back to freeware-mode and that's where you are seeing the limitation on maximum object size. The solution, which may not be exactly what you were hoping for, is to purchase the Pro version. Please refer to this matrix to understand Freeware versus Pro differences: https://www.msp360.com/explorer/licensing/

You also get compression and encryption as well as multi-threaded copy support which can help a lot when backing up large numbers of small files or very large files.

Please let me know if you have any other questions / concerns.

I'll pass your comments on to the team. It's my understanding and I did confirm it with the engineers and the marketing team, that the 5 GB limit was in place for a very long time. If it turns out to be an issue related to B2 storage then I'll talk to the team about what options we have for you that won't cost you anything so you can upgrade. Stay tuned.

And you're confident that version 5.9 has no issues uploading a file of that size to B2? Could you verify with a full backup of that file?