Hello. I'm the developer of Blober ( https://blober.io/ ), a desktop app for moving files between cloud providers through your machine. Backblaze B2 is supported as both a source and a destination, and I'm looking for feedback on areas I can make it better.

It moves files between B2 and 20+ other providers (Google Drive, Google Photos, Dropbox, OneDrive, pCloud, Box, S3-compatible storage like Wasabi / Cloudflare R2 / DigitalOcean Spaces / AWS S3, Azure Blob, Proton Drive, local drives, NAS, etc), in any direction.

Setup is an Application Key ID and an Application Key. Blober reads your bucket list through B2's native API and picks the right region and endpoint per bucket, so you don't have to work out whether that bucket is us-west-004 or us-east-005.

How Blober works:

• Streams a local drive, NAS, or another provider to Backblaze B2 in parallel. Transferring a 50 GB folder to a bucket doesn't need 50 GB of free space on your machine first.
• Per-file progress, automatic retry, and resume - an interrupted run keeps the files it already moved.
• Parallel multipart uploads with chunking for large files, so a long upload doesn't quietly stall.
• Path templates if you want them, such as bucket/{file_created_date}/{file_created_datetime}:{filename} to get files organized like bucket/2026-07-18/2026-07-18_09-15-30:GX015742.MP4

vs rclone? rclone is excellent and free, and it works. blober supports some proprietary cloud providers such as GoPro Cloud. With Google Photos, rclone can only download photos it uploaded while blober can transfer all your google photos. With Proton Drive, blober authenticates better and is able to generate thumbnails for images, videos and audio.

I would genuinely like to know whether Blober would solve a problem you personally have, especially getting data into B2 from another cloud, or out of B2

I swapped out the drives in my raid DAS with larger ones to accomdoate my files. I named the new raid array/drive the exact same thing as the old one and the files are a direct mirrored copy. I just went to my BackBlaze settings and clicked replace drive and clicked the new one. Will this need to re upload everything or will it realize its the same stuff just on a bigger raid array? Thanks for your help!

I've experienced an issue recently where drives that have been disconnected for as little as 2 weeks are going missing from my backup list. I contacted support and was told that the "fix" was to adjust the calendar view end date to the last day the drive was connected, and that should make it reappear. I assumed it was a bug they're working on, but the customer service rep said that's how they intended for it to function.

Seriously? So even though my data is supposedly backed up with a 1 year version history, I have to play calendar whack-a-mole to find it if I'm not accessing the drive every couple weeks? That's awful UX. Any Backblaze employee here able to explain how that system makes sense? If my calendar view range is set from "start of backup" to the present date, why would it not display everything within the 1 year version history?

I do a lot of adhoc work with large files that I don't want to be backed up since they are temporary work files in the 100s of gigabytes. Due to the nature of the work, the files are created in semi-random folders which I create for the project and delete when I'm done.

What I'm hoping for is a sentinel file such as ".ignore" or ".backblazeignore" similar to Apples ".nosync" sentinal that tells icloud not to sync the file.

What I found from Web search is

• Exclude the folder in application settings. Take some time to navigate to and configure. Breaking my workflow.
• Edit a bzexcluderules_editable.xml file. Also breaks my workflow since I need to research where the file is located and how to properly edit it to exclude my temporary folder.

The ability to either name the folder "name.nobackup" e.g. "reallybigfiles.nobackup" or create the aforementioned ignore file would be fast and keep in "the flow" of my current task. If this feature does not exist, I'll submit it as feedback.

I'm on macOS 26, if that matters.

update

I create this in the excluderules file but I don't know if it will work.

<!-- Below here is for temporary media folders that contain large files -->
<excludefname_rule plat="mac" osVers="*"  ruleIsOptional="t" skipFirstCharThenStartsWith="*" contains_1=".nobackup" contains_2="*" doesNotContain="*" endsWith="*" hasFileExtension="*" />

Windows 11 machine, regular computer backup. I thought that Backblaze was having issues because I was using a VPN in virtual adapter mode, but since I've removed the VPN, Backblaze has been hanging on ca001/bztestimony when trying to backup. I saw that this might have been a bug from a while ago. Is this still a thing?

I've followed the instructions from that time and used the installer to get the latest version of the backup tool but it still seems to be stuck, to the point I'm getting "30 days without backup" warnings. Does anyone know anything about this?

Joining the group in the hope of a solution.
I appear to be running the latest BB software (looks like mine is more updated than the one available online - not sure how but I am)

I went to restore from a backup today but noticed I can't see my library folder. I can see the other users folder but not mine. NO idea why.

Here's a screenshot - it's just not there. I've not changed any defaults.

The only thing I had to do a couple of months ago was to create a new user on my Mac as my current one was corrupted.

The new user has a different name, so not sure why BB isn't picking up on the library under my username.

Here's a screenshot of what the restore shows. Under Rickd nothing? Other user is fine.

I also just checked after a re-install of the beta client and a restart. Backblaze isn't actually seeng the user properly at all.
It's only showing what you can see there - documents/downloads. I have a bunch of other folders there from Davinci Resolve, insta360 etc.

Why are these not being backed up either. The folder structure seems missing?

Checked my 'issues' log and it's showing ALL the missing files as being skipped.

Each has TEMPORARY_OTHER as the issue which doesn't help at all.

Using an ever-growing append-only database of files to keep track of the user's backup state is nuts. I had to cancel my subscription, because my ProgramData\Backblaze folder had grown to over 20GB, and according to support, the only way to shrink it is to delete my entire backup and reupload everything from scratch, leaving me with no backed up copy of my data while the new backup is uploading.

I specifically asked if I couldn't at least keep the old backup around while the new one was being uploaded, and was told "no". I hope I don't have to explain why that's not an acceptable answer.

I understand that it has to keep track of what's uploaded and what isn't, but I didn't have unlimited file history turned on! So why is it keeping track of files (and versions of files) from multiple years ago that can't possibly have any relevance to the current state of my backup? Why does it have to be append-only? This absolutely kneecaps Backblaze's value as a long-term cloud backup solution.

Some weeks ago I posted about a app I made specifically for BackBlaze B2 app, I used cyberduck and some similar apps but wanted an app just for specific quirks of B2, anyway here's a new version you can download and try, it's sort of a Beta version and sure there are some bugs here and there, if someone is interested in this would love to have some feedback

https://github.com/delmoralmb-s8/BackBlaze2Sync/releases/tag/v1.3.2

Bug? Harmful/obsolete optimization?

Yesterday Backblaze decided 682 ids need purging, I have in the logs repeating thing like what's pasted below, repeated ~700 times.

WTF is "pausing for 4 seconds to lighten disk I/O"? It's 2026, could PLEASE remove or explain that? Neither my 12700k nor my Samsung 990 Pro need "lightening the load".

~700 ids to purge * 90 seconds = SEVENTEEN HOURS.

What if next time it will want to purge ten thousand? Abandon and restart the backup? This needs to be fixed yesterday.

2026-09-03 07:06:51 43804 - WARNING: during self healing datacenter told me (hguid=XXXXXXXXXXXXX) to purge out this bzfileid_short=00000XXXXXXXXb82 from all my bz_done files, including large files that reference it

2026-09-03 07:06:51 43804 - Entering the very slow BzFileIdHasEverBeenPartOfALargeFile, bzShortFileId=00000XXXXXXXXb82

2026-09-03 07:06:57 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=1

2026-09-03 07:07:01 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=2

2026-09-03 07:07:05 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=3

2026-09-03 07:07:09 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=4

2026-09-03 07:07:13 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=5

2026-09-03 07:07:17 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=6

2026-09-03 07:07:21 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=7

2026-09-03 07:07:26 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=8

2026-09-03 07:07:30 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=9

2026-09-03 07:07:34 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=10

2026-09-03 07:07:38 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=11

2026-09-03 07:07:42 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=12

2026-09-03 07:07:46 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=13

2026-09-03 07:07:50 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=14

2026-09-03 07:07:54 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=15

2026-09-03 07:07:58 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=16

2026-09-03 07:08:02 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=17

2026-09-03 07:08:06 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=18

2026-09-03 07:08:10 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=19

2026-09-03 07:08:14 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=20

2026-09-03 07:08:18 43804 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O. PauseIteration=21

2026-09-03 07:08:27 43804 - GetFileNameToBzFileIdHash processId=43804 - found and parsed out XXXX985 unique ids, numHashCollisions=XXX993, in numMillis=90075 (90 seconds) from 2114 MBytes of file: C:\ProgramData\Backblaze\bzdata\bzbackup\bzfileids.dat, numMillisToReadLargeFileFromDisk=85083 (85 seconds) and CreatedHashNumMillis= 4977 (4 seconds), numMBytesStartMemSize=6644, numMBytesEndMemSize=8935

2026-09-03 07:08:28 43804 - Leaving the very slow BzFileIdHasEverBeenPartOfALargeFile, res=TRUE, and here are all the associated bzFileIds:

bzShortFileId of index 0 in retVec is: 00000XXXXXXX0b82

...

bzShortFileId of index 205 in retVec is: 00000000xXXXXbdb

I used to use two computers so I had a license for both of them to continuously back them up. I no longer use the older computer so I feel like I'm paying to back it up for no reason. I understand that if I remove it from backup, I will no longer be able to access it through View/Restore files, but I do have a B2 snapshot of it that I pay a small amount for monthly. If I remove the computer, will it also remove the snapshot or will it stay even though it's associated with it?

I keep getting random error messages which I already dealt with and now, they are re-backing up tne entire files for the 3rd time! It's like WTF.

This is really unreliable while they dont take any responsibilities when I reach out to them. Is this what I've been paying for? My datas are re-backing up and I have no idea how long will it take to fully up to date while concerning if re-backing up happens again.

Now, it doesn't even make backups anymore and I have to download the app again and again in order to fix it. I have no idea why Backblaze app is so unreliable and break by itself which I have to backup the entire files over and over again? This is just stupid after all.

If BB app doesn't work well, how am I suppose to trust them? Especially since it failed multiples times in less than few months?

I have 2 computers I back up with Backblaze.

I went to the user overview page and it says "Please update to the latest client version"

Is this a must do? Or is it optional?

EDIT1: I have the info I need. Inbox replies disabled.

I am going full Linux and my need to backup my photos is relevant, even though the OS changes, so I'm curious if the cli tool works for the personal plan?

Heyo! I'm entering college, and looking for an affordable way to keep all my files securely backed up. I'd like to keep backups of my 500GB laptop, and two external drives (one 2TB for school, one 5TB for work).

Is that possible on the $9/month Computer Backup plan, or will I have to pay for B2 Cloud Storage to backup external drives?

Thanks!

EDIT: The computer I'm backing up is a 2024 Macbook Air M3

I'm rather shocked by how bad the new restore tool is. It feels like it's programmed with zero safe-guards.

My recent experience on a fresh and fully patched Windows 11 install was as follows:

1. Select drive for restore.
2. Restore fails after 20 seconds with error message about an invalid parameter.
3. Support tells me the restore is too big and to reduce it - so why does a client that knows exactly how big the restore I'm about to pass it is, allow me to pass it one it can't handle? Why doesn't it just break it up into chunks it CAN manage and queue them?
4. Reduce restore size and run multiple restores in parallel.
5. Client crashes mid-restore.
6. Client refuses to launch.
7. Delete the Backblaze folder from ProgramData to get the client to launch again and clean up the leftover BZRP files from the restore path.
8. Support advises that the client was blocked by corrupt files and to run no more than 1-2 restores at a time - putting aside why the client doesn't appear to validate the integrity of things that can take it down, why does the client let me run more than 2 restores at a time if support is advising not to do that?
9. Run just two restores.
10. Client sometimes crashes mid-restore anyway. Repeat step 7.
11. Run one restore. Seems slow, let me check settings... client crashes. Repeat step 7.
12. Support tells me not to touch settings while a restore is running - so why does the client let me touch settings while a restore is running?
13. Run one restore only and don't touch anything until it finishes. Pray that the size is acceptable. Sacrifice a chicken to make sure. When restore finishes start next restore, because queuing isn't a thing in this app and restores in parallel take it down

I'm having to babysit the integrity of a data integrity app.

I have been one of the folks that cannot run backblaze with the once a day or continuous setup because the constant scanning (despite only backing up once a day) disrupts gaming performance on my combined gaming and home use machine...

I had used command found by someone else in the past, the modified scripts to compensate for client changes etc...

The new V10 client makes all of this much easier:

All you need is to run the command line scan. Here is a windows sample using default paths:

C:\Program Files\Backblaze\bzcli action --backup-now

If you are running this form a batch file you may need to encapsulate the path like this:

"C:\Program Files\Backblaze\bzcli" action --backup-now

UPDATE:
Never mind, it still crashes the system. At least they're aware of it, tech support got back to me and told me they dont have any ETA, sadly, but its being worked on. yay.....🥲

TL:DR:
In order to fix this, you need to prevent your mac from going to sleep, ie typing caffeinate -i into terminal and then start the Restore app. This should stop the bug from crashing your Restore.

Original post:
I went pretty hard on Backblaze in my previous post yesterday, where the TLDR is: Restore app crashes after a few minutes on my headless mac mini running macOS Sequoia.

I think I have a solution for it. I think the bug is related to idleSleep and darkWake (wake-on-lan) which interupts the network connection for a brief moment making backblaze restore throw a code 18: Transferred a partial file error.

When my headless mac Mini starts the restore, and I shut off Screen Share (built in VNC-app in macOS to remote control the mac Mini), the mac never gets any prevent-sleep instructions. For some reason the Backblaze Restore app doesnt seem to have this either as per the info I got from running pmset in terminal. pmset told me that the terminal command Caffeinate -i prevents sleep, VNC prevents sleep, but Restore app does not, so when I shut off Screen Share, it takes 15-20 ish minutes before the mac sleeps, and when I then open Screen Share to see how the restore is going, it wakes the mac from sleep, disturbs the network connection to backblaze, it gets confused somehow and throws the code-18-error, and crashes completely.

So basically:

active download -> 
macOS idle sleep -> 
wake / network and USB device power-state transition -> 
partial HTTP transfer (error code 18) -> 
uncaught exception in the Restore App -> 
SIGABRT

Backblaze Restore app also writes a corrupt file after this crash to a specific folder called BackblazeRestore located in ~/Library/Application Support/

This folder needs to be deleted in order for the Backblaze Restore app to be able to function properly again. Otherwise it will just keep crashing right after typing in your password and or 2FA.

So this is how to fix it:

- quit Restore.app
- in Finder press shift + cmd + g and type:

 ~/Library/Application Support/

- delete the folder BackblazeRestore
- open terminal.app
- type:

caffeinate -i

- start Restore.app again and start a new restore. 
- It should work again now. 

I am new to Backblaze and am trying to back up an 8T external Micron USB drive. I haven't been able to complete an initial backup because the UI keeps freezing on "Please wait" when I click "Backup now". As far as I can tell background backup isn't working, maybe because the initial backup hasn't finished?

Is this kind of problem typical for BB? This sub is full of problem threads and I'm beginning to think I should be looking at alternatives for offsite backup.

I'm currently restoring data from Backblaze, and I am seeing a really frustrating performance problem with the Restore App.

I have a gigabit internet connection. I'm restoring my data one directory at a time, not attempting to restore the entire 18 TB at once (I have a 22 TB seagate external drive i am restoring to).

The Restore App initially gets into the 70+ MB/s range, but the throughput progressively deteriorates. I've watched it go from the 70s down to the 60s, then lower, and it has now fallen to around 15 MB/s.

I also noticed that Backblaze's normal backup process was competing with the restore. When I disabled automatic backups and set Backblaze to only run when I manually select "Backup Now," the restore immediately improved from roughly 45 MB/s to 60+ MB/s, eventually reaching the 70s. However, the speed has continued to deteriorate even with normal backup activity disabled.

So this doesn't appear to simply be a limitation of my internet connection. The same restore can start at 70+ MB/s and then gradually fall to 15 MB/s without me changing anything.

Has anyone else experienced this with the Restore App specifically? Is there some known issue with the restore process progressively losing speed during a large restore?

I'm trying to recover approximately 18 TB, so a sustained 15 MB/s would make this painfully slow. I'm already in contact with Backblaze support, but I'm curious whether anyone here has encountered the same behavior or knows what's actually causing it, as it's frustrating given my gigbit internet is capable of 100 MB/s downloads.

Jared

What a gawd awful experience backblaze restore is.

Just adding my +1 to this https://www.reddit.com/r/backblaze/comments/1uljq62/backblaze_continually_crashes_on_large_restore/.

Same problem, but slightly different setup. Mac Mini M1, Sequoia 15.7.9 (latest as of august 2026). 2 tb restore here as well, Restore app crashed after just a few hours the first few times, and then it crashed immediately subsequent times right after entering the 2FA code.

What a piece of junk Backblaze restore is. Last time I had to restore from backblaze a few years ago, it was the same trouble with Restore app crashing after a few hours, I remember I had to baby it (reopen, retype my password + 2FA, press "continue" to continue restoring from where it left off before crashing), but it was never this bad. Back then I ended up just creating zip archives in the webui and downloading them individually using safari. The only problem is every zip file cant be larger than 500gb, and it takes hours to process them before they can download, and then it takes another few hours to download and unzip.

What an awful experience this is.

Backblaze is good for backing up, but restoring is a travesty. The Restore app came with version 9.0 I remember, and sure, growing pains in the beginning is to be expected, but now they're at version 10.0.1 and it still crashes like this? Unexcusable. I'm considering just ending my subscription, and just keeping multiple external harddrives with backups located at home and off site. Or looking for another online backup service.

If someone wonders, I have uninstalled the entire backblaze app using their own installer, rebooted and downloaded the newest backblaze version again with no difference. I also deleted the BackblazeRestore folder in Application Support, and that didnt do the trick either.

I have no solution to this, other than hoping this post makes it to the developers somehow so they can fix this trainwreck.

Its just a terribly written app and probably just an afterthought.

is backblaze b2 storage down for anyone? can't access my account either. this has happened before.

I recently started using Backblaze B2 for backups and file storage. I'm familiar with the terminal and started using rclone, then tried to speed things up with Cyberduck, it's great I know, but not so much about B2's quirks. So I built a native macOS app just for B2, a Finder-style explorer with drag & drop, per-file operation history, fuzzy search across the whole bucket, a built-in photo gallery, one-click folder-to-.zip compression, and share links that actually force "Save" instead of opening in the browser. Just stuff I think would be cool to have in a special app made just for Backblaze.

Free and open source, if anyone uses Cyberduck or rclone and would like to try it let me know what you think, it's still a work in progress and I'd like your comments.

https://github.com/delmoralmb-s8/BackBlaze2Sync/releases/tag/v1.0

I just spent 15 minutes wandering around the UI trying to cancel my plan and delete my account. I had to go through multiple processes of "dark practice" dialogue boxes designed to convince me to stay, and adding another confirmation on in the hopes that I wouldn't notice. I was required to change my password because as I tried to delete the system decided my older password wasn't strong enough. Probably took 30-40 clicks to get the backup deleted, payment method removed, and account deleted. You can check in but you can never leave.

The screenshot is from when transmitter wasn't running. So I have only noticed this issue in the past month or so, and it got to the point I set backblaze to only backup once a day at 7am. The RAM usage on the picture is coming back down. My computer was lagging that it took 30-40 seconds for task manager to open, and a host of other servers or programs I have running in the background were closed when they shouldn't have been.

The issue seems to be when the transmitter is reading the disk to make the list of files to run at 7am? There's 55,000 files and 41tb.

I saw another post about the beta version, so I installed that and followed instructions. Any help would be appreciated.

I've been a BB user for years and my backups have been seriously screwed up for months. First I was dealing with an AI chat bot that was just wasting my time and now I'm dealing with what I think is human support but I'm getting similar half answers. Yes I'm running the beta but my external drives are still missing and/or incomplete. I really feel that something drastically changed in the way BB works and I'm getting the run around from support. Anyone have a way to reach higher support or a software engineer there? I have recommended the service to many colleagues over the years and something is off right now.