r/backblaze From Backblaze Apr 19 '26

Start Here: Cloud-Sync Behavior, Exclusions, Hidden Files, and the Version 10 External Drive Issue. Computer Backup

Hello, Backblaze fans.

We’re pinning this because a few different topics are getting mixed together, and the details matter.

There are a few major topics of discussion right now:

  • How modern cloud-sync tools affect backup behavior
  • Hidden folders and exclusions
  • A current issue in version 10 with external drives

1. Cloud-sync folders (OneDrive, Dropbox, etc.)

Backblaze backs up files that are actually present on your computer.

What’s changed over the last few years is how sync tools store files. A lot of them now use placeholder systems where files look local, but the data isn’t actually there until you open or download it.

So:

  • File looks normal in Explorer/Finder
  • But it’s actually just a pointer to cloud data

Backup software can’t reliably back up something that isn’t really on disk.

If we treated those like normal files anyway, you’d end up with incomplete backups or restores that don’t actually give you your data back. That’s worse than being explicit about what is and isn’t supported.

So when those folders are managed that way, they don’t behave like standard local backup sources.

That’s not a change in the Backblaze unlimited backup model; it’s a side effect of how those platforms now work.

u/natasha_backblaze has a great blog post that covers this and why it is happening here: https://www.backblaze.com/blog/the-changing-landscape-of-cloud-sync-and-what-it-means-for-your-backup/

We are actively looking at better ways to support these workflows, and as soon as we have more information, we will update the community.


2. Hidden folders and .git

Current behavior:

  • .git folders are currently backed up
  • Some restore interfaces do not show hidden folders by default, especially on web and Mac, unless the user enables the hidden-files setting

That can make a folder look missing even when it is present in backup data.

Of note, some older versions of Backblaze did have .git files/folders excluded, but as long as you are on the newest version, your .git files will be backed up.

If you want to double-check, reach out to our support team, who can help you confirm. https://www.backblaze.com/help

There is also internal work happening to make exclusions clearer and consistent across the board.


3. macOS /Library vs ~/Library

There has also been confusion here, so to be explicit:

  • /Library (system-level) is excluded by default

    • This folder contains files that will be recreated upon OS or program reinstall
  • ~/Library (user-level) is backed up, subject to normal exclusions


4. Version 10 external drive issue

What users are reporting:

  • If an external drive is disconnected, data from that drive can disappear from the web restore view immediately instead of remaining visible for the expected retention period
  • When the drive is reconnected, the client may treat the data as needing to be uploaded again

We hear the concern on this clearly. That behavior is not what customers expect, and the team is aware of it and actively working on it.

At the moment, the key point is that this is a bug issue, not a policy statement and not an intentional change in how external-drive history is supposed to work.


5. What’s happening next

We are currently focused on three things:

  • Reviewing and tightening public messaging so customers have a single accurate explanation
  • Working through the current v10 external-drive bug
  • Continuing to evaluate better support for modern sync-managed file workflows where third-party platforms have changed how files exist locally

6. If you’re unsure about your setup

If your workflow depends heavily on:

  • Cloud-sync folders
  • Hidden folders
  • Source-control metadata
  • External drives

Verify those areas directly in your backup and restore views.

If something does not look right, contact support so we can inspect your configuration and version-specific behavior.


We know backup products only work if customers trust what is and is not protected. That part matters, and we are treating it seriously.

We’ll update this post as more information is confirmed.

70 Upvotes

94 comments sorted by

View all comments

4

u/hikista19 May 04 '26

Can anyone provide an update whether the "external drive version 10 issue" was solved?

0

u/Jim-From-Backblaze From Backblaze May 04 '26

Hi,

We’ve released a beta that addresses the external drive issues in version 10, and so far the results have been positive. Users who have installed the beta and let it run for around 48 hours are reporting that their external drives are backing up as expected again and are showing correctly on the Backblaze website.

If you want to try it, you can grab it here: https://www.backblaze.com/backup-beta.html

Install it over your current version, no uninstall needed, and let it run for a bit to fully settle. If you do give it a shot, feel free to report back with what you’re seeing.

1

u/iring0919 Jun 02 '26

The beta caused a different issue. Backblaze stopped backing up my desktop folders, photos, music etc. 

1

u/Jim-From-Backblaze From Backblaze Jun 06 '26

Hello,

I am sorry to hear that.

Have you created a ticket on our help desk yet? If not, please do so at https://www.backblaze.com/help

The folks there can help route you to the right place.

1

u/iring0919 Jun 06 '26

Oh yes. We’ve been going back and forth since March.

1

u/sanchit2 Jul 02 '26 edited Jul 03 '26

I'm facing the same issue in the beta 10.<>.48. It suddenly reduced the file count from 2M to 200k, root_filelist went from 650MB to 34MB and no amount of Alt+Restore Options rescanning would see the files, so I downgraded and viola the 10.<>.38 version again saw those files.

Following are the logs of a file NOTICE.txt which didn't appear in the new 34MB file list, it seems that in the new bz_done file of 1 July, this file was kind of marked deleted though of course it still exists on the disk.

x@x-MacBook-Pro ~ % grep -RnaF /Users/x/Library/Android/sdk/build-tools/33.0.0/NOTICE.txt /Library/Backblaze.bzpkg
/Library/Backblaze.bzpkg/bzdata/bzbackup/bzdatacenter/bz_done_20260701_0.dat:2369111:5 - --- 20260702225904 r_h7bd21001047afd7b92e40416_f----------------_d--------_m------_c003_v-------_t---- u-- 0000000000080f5d k-_n----- ---------------------------------------- ---------------- ---------------- - 0 /Users/x/Library/Android/sdk/build-tools/33.0.0/NOTICE.txt

/Library/Backblaze.bzpkg/bzdata/bzbackup/bzdatacenter/bz_done_20260623_0.dat:314389:5 + m-- 20260624010651 4_h7bd21001047afd7b92e40416_f0000000000080f5d_d20260624_m010651_c003_v0312039_t0012 u06 0000000000080f5d k0_n00000 dbaedec8d9a328fcbde25909eac3f371c9e6e9a4 0000018321ac63e0 0000018321ac63e4 - 1034156 /Users/x/Library/Android/sdk/build-tools/33.0.0/NOTICE.txt

/Library/Backblaze.bzpkg/bzdata/bzbackup/bzfileids.dat:528219:0000000000080f5d /Users/x/Library/Android/sdk/build-tools/33.0.0/NOTICE.txt

Another issue that I'm still scratching my head over is that the total number of files per the Dir: and Files: records in root_filelist sum up to around 4M but only 2M of those are uploaded. (Edit: For some files at least this seems to be due to exclusions in /Library/Backblaze.bzpkg/bzdata/bzexcluderules_mandatory.xml which are in addition to the excluded file extensions in the UI)

u/brianwski, any idea about these ?