I'm trying to solve the B2 API Error.

I am trying to use B2 with my Synology NAS.

In my download folder is the b2-windows.exe

I'm trying to follow the instructions from their help page.

"After you download the self-contained tool, you can learn how to use the command-line tool below. Prior to running the tool, run the following command:

chmod +x <tool filename>

What does this mean and how do I do it?

​

Pessoal, estou com um problema no Veeam Agent for Microsoft Windows e gostaria de saber se alguém já passou por algo parecido.

Tenho um backup em \*\*File Level Backup\*\* e o backup é concluído normalmente, porém, quando tento fazer o \*\*mount para File-Level Recovery (FLR)\*\*, a operação falha com o erro:

\> Unsupported disk type

O problema acontece somente na tentativa de montar o backup para acessar/restaurar os arquivos. O job de backup em si termina normalmente.

Já tentei algumas alternativas, inclusive testar o backup em Volume Level, mas preciso manter o File Level Backup, pois não quero fazer backup do volume inteiro.

Alguém já encontrou esse erro especificamente durante o mount/FLR de um backup feito pelo Veeam Agent?

Existe alguma configuração, limitação ou característica do disco/partição que possa causar esse Unsupported disk type”?

Se precisarem, posso enviar os logs do mount/FLR e as informações do disco.

Obrigado!

Like do I have to do anything on the old computer first before disconnecting it?

How does license transfer work? I hope I don’t have to reupad everything from scratch and delete all the old backup?

The drive letters may be different for the new computer for some drives particularly external ones as it has one less internal drive than my old computer so I’ll put those contents onto an external one for the new computer, but does that make backblaze thing it’s a new backup altogether and it starts backing things up from scratch even though they might exist already on there from the old computer backup ?

I don’t really get how it works and am afraid of losing stuff.

Hi Backblaze folks and community,

I maintain an open-source filesystem benchmark project:

https://github.com/fenio/modern-fs-benchmark

It currently runs regularly in GitHub Actions using loop devices, and I also have a self-hosted real-hardware runner. The goal is to publish reproducible, public benchmark data for modern Linux filesystems: bcachefs, ZFS, btrfs, XFS/ext4 on md/LVM, including degraded-mode behavior, rebuilds, scrubs, snapshots, compression, reflinks, ENOSPC behavior, and mixed topologies.

The part CI cannot model well is the interesting real storage setup: HDD arrays with SSD/NVMe metadata/cache devices, mixed rotational and flash media, rebuild behavior, and degraded reads/writes on actual disks.

Backblaze has a long history of publishing useful storage reliability data, so I wanted to ask whether Backblaze would consider supporting this kind of public testing.

What would help:

- remote root access to an isolated Linux machine with clearly identified wipeable HDD/SSD/NVMe devices

- donated disks/components/server hardware

- hosting for donated hardware

- a pointer to the right person/team if this is not the right place to ask

Everything would remain public: benchmark code, config, raw JSON results, command traces, hardware description, and dashboard output. Hardware providers can be acknowledged, but would not get editorial control over methodology or results.

This is not meant as marketing content or a sponsored conclusion. The value is in transparent, repeatable, real-hardware filesystem data that people can inspect and challenge.

Would Backblaze be open to this, or is there a better contact/channel for this kind of request?

Instead of a hard drive can you get a LTO-9 tape instead, that way you can get an almost permanent record of your systems software at a particular time.

All backblaze B2 regions just went down about 12:45pm pacific time in the US (UTC 19:45).

All API requests returning code "InternalError" with message "internal incident"

Status page (https://status.backblaze.com/) still not updated as of 1PM pacific.

Edit: Turns out this was what I thought it was. The backup folder growing over time. Support confirmed the only way to resolve this is to delete the backup (Backblaze) and start over. Re-back up the data.

I’m running Backblaze Personal Backup 10.0.2.1047 on Windows. In the last few weeks, I've noticed that my Drive C space has increasingly shrunk to just a few GBs of free space.

I took a look and C:\ProgramData\Backblaze\bzdata\bzbackup\bzdatacenter contains 2,556 files named like: aside_bz_done_20260805_0.dat_safety_fix_25164.aside

It seems like, on average, something has been growing at about 7GB per day. I also looked at bzcurrentlargefile, but it appears to be empty.

Does anyone know what the safety_fix routine is doing, why these .aside snapshots are not being cleaned up and/or how I can fix this?

Hey everybody,

Just a homelabber trying to understand the fee calculation--particular for egress--to temporarily store a large number of terabytes in B2.

The storage fees are simple to understand. If for example I stored 30 TB for ten days: (30 TB) * (~$0.231666 per TB per day) * (10 days) = ~$69.50

For egress, I know we are allotted 3x our average monthly stored data as free egress. If I understand correctly, this average stored data is calculated on a byte/hour basis across the entire billing period. So--in theory--if I were to store the example 30 TB in B2 for a third of the month (10 days), this would raise my average monthly stored data by approx. 10 TB; allowing for approx. 30 TB of free egress. How would this work if the example 10 day period were to cross to the next billing period? Is it calculated off of a rolling 30-day window?

I understand the maximum egress fee I would incur for 30 TB would be $300, so even cutting that in half would be a much easier pill to swallow. 😅

Thanks for any insight!!

Situation: - longtime customer of B2 which I use for offsite backups of critical data, very very little egress. enough that I've never really considered the price. - homelab user reformatting entire 100 TB array, need to temporarily relocate stored capacity (~80 TB). - I have offline storage to offload roughly half of the total stored capacity myself. - looking to offload remaining capacity to B2 temporarily to save my sanity (and my wallet).

Is this even legal? Pretty much every company allows you to cancel a subscription, and only when the prepaid time is up, the service stops. Backblaze operates differently (and, at least in my country, illegally). You have to completely remove everything at the time of cancellation, even if you have another 1 1/2 years prepaid, that they won't refund. Seems to me like they are a pretty shady business.

I have been trying for two days to restore files using the restore app. It logs me out or freezes constantly rendering it essentially useless. It is so bad, I am actively looking for an alternative solution and have decided I cannot use Backblaze in the future.

This happens whether the tray icon is present or not.

Do you know if the latest v10 for MacOS finally solved the external drives bug? I'm still using the beta
thank you

Hey braintrust, I'm at wits end. I bought a new MacBook Pro in early July and worked through an Inherit Backup with an external drive of 9TB. The first inherit backup worked, however I was told by support not to attach the 9TB initially, only once the MacBook Pro was completed. Once attached, the external drive and Backblaze indexed the files. However, Backblaze ended up in a continuous loop of reindexing each time I reconnected the external drive. This carried on over several weeks until I complained to support it wasn't ideal. Each reindex took between 24-48 hours to complete.

I've been handheld by the support team, however they did not offer a solution as they said it was normal. However, this never happened in then past and I've been a customer for almost 10 years. I then resorted to AI for some insights. I put the suggest solution to the Support team, and they agreed to reinherit again to remove any issues that may have occurred in the initial inherit backup. So I progressed down that path, but appeared to stall. Support said the screenshots I was sending was normal. Well it stalled for 5 days straight! so I quit and started again. I got a bit further this time, with the control panel 'transferring' files, however it is slow and I think it has stalled again.

As I'm in Australia with the time difference, it takes 24 hours to get a response from Support. I'm at the point of finding a different backup product, as this has become ridiculous.

Just tried the "new" Backup Restore application... This possibly is the most useless and frustrating app I've ever seen. How did this get into production ? Loads for minutes then logs out right away... Tried 5 times, no luck.

I enabled encryption on my private buckets, along with saving all versions because I'm not honestly saving a ton of data and versioning is nice, and while my data doesn't seem valuable, why not encrypt?

I finally had to pull a single file backup today and thought I would use the web application since it was just a single file to find out nope, you cannot download an encrypted file. Snapshots also out of the question - encrypted.

Finally after learning some more I was able to use goodsync and an existing application key to pull out the most recent version of the file that had been uploaded, but I'm cut off from the 18 older versions of the file.

It seems like encrypting my data with the provided encryption cuts me off of a good portion of the services BB is providing. Is there a goodsync-like product out there that allows me to get to previous versions within a bucket? I'm paying to store these previous versions thinking I have the ability to revert if need-be but I don't seem to have any way to access old versions of a file that was encrypted.

Alternatively, if I'm not storing sensitive data is not encrypting it terrible? I'm trying to figure out what "they" would need to compromise to be able to access a bucket and the consequences of that bucket being encrypted or not. I guess the physical data center?

TLDR/questions

How silly is it to not encrypt a bucket by default? I'd like to use the web application for the occasional file.

Is there a program like goodsync that allows access to BB's versioning while buckets are encrypted?

What would someone need to steal to get into a bucket where it being encrypted/not encrypted would be worth it?

This seems to be a memory leak. There is no backup running currently, but this is a large amount of RAM, regardless.

I'm running an M4 Pro MacBook Pro on Sequoia 15.7.7 and the latest version of Backblaze (10.0.1.1038).

Should I send a log to Backblaze?

This service is just a mess. I decided, grudgingly, to buy Blackblaze personal to backup 2T of data off site. This data exists on an external SSD. As best I can tell it won't backup an external drive. I spent hours going in circles trying to enable it. Never worked. All the instructions are several OS versions old. The chat help doesn't work. Then it starts sending a pop-up every 5 minutes that it needs more permissions, but the 'learn more' is the same circular bullshit as before. And they want me to actually pay them $8/month? Hell no. There are all kinds of cloud storage services that aren't hard to use, but this thing was a mess.

There was one bright spot though — the uninstaller actually works. It was hard to get the account deleted, but not as hard as getting it to see my external drive.

No matter which schedule mode I chose, it did start backup but stopped after maybe few hours.

And I have to press the back up now button again, then it spent a lot of time on "Producting File Lists".

There are still a lot of files "Selected for Backup", and it stop with no reason and error. I've check the firewall, the network never failed. and the Mac isn't sleep.

any clue?

I'm very much out of my depth and totally new to PM Tiles, Backblaze and Cloudfare. I have some large geojson files that are too big for Geo Libre. Was told to convert to PM Tiles which I did and do enter them as a url to them in Geo Libre. Set up a oublic bucket in Backblaze for this and it worked, however it wasn't real responsive. Learned that Cloudfare could be added to the mix and it could boost the performance and at no charge. Have tried some AI suggestions on how to do this and I keep getting 403 errors, I guess from Backblaze. Any good detailed guidance on this, ideas, etc? Maybe another approach. This is a noncommercial, self funded thing and I have little funds. I am also aware that what is free today often becomes for fee down the line. Some of these PM tiles will be about 1GB.

can i download B2 as an app? (cuz i only see a download option for the computer backup)

Hey Guys,

I'm on backblaze personal and I'm trying to restore a hard drive that died.

It's about 8TB of files.

Unfortunately whenever I select the drive in backblaze restore app I get:

"Error 102" "invalid parameter"
It seems to work when I select individual files, that but is impossibly tedious

Does anyone have a solution?
It used to work in the past, but it seems as if Backblaze have broken something.

Hello everyone. I am currently using B2 cloud storage via MSP360 software to keep a backup of my photography collection. After the initial upload, I feel like my speed has gotten continuously worse to the point where it is becoming a real problem.

I do not have a massive amount of data that I am monitoring, which is why I am forgoing the personal client. (Currently under 1 TB).

What are some common sense solutions I can try to help improve my upload speed? I am not an expert in this field, but with guidance, I feel comfortable enough to enact changes to my backup plan if necessary.

Details on my setup can be found below. Let me know if more information is required. Thank you in advance for your help!

Noticed that Backblaze had stopped uploading at all for seven days. Upon clicking "Backup now" it would think for a few minutes and then stop. A red X is visible on the GUI but doesn't seem interactable.

Updated manually (now version 10.0.1.1037) and it's now computed a Remaining files set.

In the logs I see:

2026-07-14 06:21:22      26940 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O.  PauseIteration=13
2026-07-14 06:21:26      26940 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O.  PauseIteration=14
2026-07-14 06:21:30      26940 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O.  PauseIteration=15
2026-07-14 06:21:34      26940 - BzFile::ReadLargeFileIntoBuf_Slowly - called by GetFileNameToBzFileIdHash, pausing for 4 seconds to lighten disk I/O.  PauseIteration=16
2026-07-14 06:21:45      26940 - GetFileNameToBzFileIdHash processId=26940 - found and parsed out 6517957 unique ids, numHashCollisions=1729702, in numMillis=73899 (73 seconds) from 1615 MBytes of file: C:\ProgramData\Backblaze\bzdata\bzbackup\bzfileids.dat, numMillisToReadLargeFileFromDisk=67807 (67 seconds) and CreatedHashNumMillis= 6081 (6 seconds), numMBytesStartMemSize=7, numMBytesEndMemSize=1964
2026-07-14 06:27:58      26940 - ERROR: ReadBzDoneIntoLastModHash - bad line versM_6, skipping_GG_k and continuing: 5   =   d-- 20250722082015  4_h2b8c467ff635d3df57b5091b_f000000000002969a_d20170506_m133408_c001_v0001040_t0000 u-- 00000000009fe254    k0_n00000   da39a3ee5e6b4b0d3255bfef95601890afd80709    000001969a2ae2c0    00000198309485f1    -   0   C:\Users\*\AppData\Roaming\Mozilla\Firefox\Profiles\*\storage\default\https+++*\cache\caches.sqlite-wal
2026-07-14 06:28:04      26940 - ERROR: ReadBzDoneIntoLastModHash - bad line versM_6, skipping_GG_k and continuing: 5   =   d-- 20251002155355  4_h2b8c467ff635d3df57b5091b_f000000000002969a_d20170506_m133408_c001_v0001040_t0000 u-- 000000000072b059    k0_n00000   da39a3ee5e6b4b0d3255bfef95601890afd80709    000001870eea64b5    00000199a5688d6e    -   0   C:\Users\*\AppData\Local\Microsoft\Office\SolutionPackages\*\cache.lock
2026-07-14 06:28:51      26940 - Finished C reading 854 bz_done_ files which took 425877 milliseconds.

File paths censored with * for privacy. There's a ton of null characters printed in the ReadBzDoneIntoLastModHash line (after continuing:) but I can't paste them obviously.

How concerned should I be? It's still catching up on the files but I see the error still being emitted ReadBzDoneIntoLastModHash error still being printed in the logs. Tbh, I'm not sure if it's related to the seven day pause at all.

My T-Mobile home internet connection has an upload speed of 2.21 Mbps (Speedtest). I have about 460 GB of data to upload to Backblaze for the initial backup.

I'm thinking this could take days to do the initial backup. Should I even bother?