[andybak]

I commented on this topic elsewhere on this page. This is an email from 2021. Maybe they changed policy but here:

> Bob (Backblaze Help)

> Aug 5, 2021, 11:33 PDT

> Hello there,

> Thank you for taking the time to write in,

> Unfortunately .git directories are excluded by Backblaze by default. File

> changes within .git directories occur far too often and over so many files

> that the Backblaze software simply would not be able to keep up. It's beyond

> the scope of our application.

> The Personal Backup Plan is a consumer grade backup product. Unfortunately we

> will not be able to meet your needs in this regard.

> Let me know if you have any other questions.

> Regards,

> Bob The Backblaze Team

[layer8]

> changes within .git directories occur far too often and over so many files that the Backblaze software simply would not be able to keep up.

I don’t really understand that. I’m using Windows File History, and while it’s limited to backing up changes only every 15 minutes, and is writing to a local network drive, it doesn’t seem to have any trouble with .git directories.

[Tor3]

>File changes within .git directories occur far too often[..]

That's a crazy statement. The cloud backup system I use can be configured to how often it should bother even looking for new files, and for the section where I have my .git repos (they're actually "bare" git repos and I push to them, locally) I've set it to every two hours. Which is actually overkill because they absolutely do not change that quickly.

[foobiekr]

This is idiotic. All they have to do is schedule them and then introduce enough hysteresis to not constantly churn on their end. Even if they backed up at most once a day this would be better than this idiocy.