Ironically drop box and one drive folders I can still somewhat understand as they are "backuped" in other ways (but potentially not reliable so I also understand why people do not like that).

But .git? It does not mean you have it synced to GitHub or anything reliable?

If you do anything then only backup the .git folder and not the checkout.

But backing up the checkout and not the .git folder is crazy.

▲

dnnddidiej 6 hours ago | parent | next [-]

I use backblaze and have repos I dont push for this reason so I am a bit stunned lol

▲

Hendrikto 6 hours ago | parent | prev | next [-]

> drop box and one drive folders I can still somewhat understand as they are "backuped" in other ways

No they are not. This is explicitly addressed in the article itself.

▲

dathinab 5 hours ago | parent | next [-]

normally this folder are synced to dropbox and/or onedrive

both services have internal backups to reduce the chance they lose data

both services allow some limited form of "going back to older version" (like the article states itself).

Just because the article says "sync is not backup" doesn't mean that is true, I mean it literally is backup by definition as it: makes a copy in another location and even has versioning.

It's just not _good enough_ backup for their standards. Maybe even standards of most people on HN, but out there many people are happy with way worse backups, especially wrt. versioning for a lot of (mostly static) media the only reason you need version rollback is in case of a corrupted version being backed up. And a lot of people mostly backup personal photos/videos and important documents, all static by nature.

Through

1. it doesn't really fulfill the 3-2-1 rules it's only 2-1-1 places (local, one backup on ms/drop box cloud, one offsite). Before when it was also backed up to backblaze it was 3-2-1 (kinda). So them silently stopping still is a huge issue.

2. newer versions of the 3-2-1 rule also say treat 2 not just as 2 backups, but also 2 "vendors/access accounts" with the one-drive folder pretty much being onedrive controlled this is 1 vendor across local and all backups. Which is risky.

▲

Tempest1981 5 hours ago | parent | prev [-]

Parent is using "backuped" to mean "likely in some cloud (latest version)". And that may explain why BB excludes .git folders.

You are using it to mean "maintaining full version history", I believe? Another important consideration.

▲

gilrain 5 hours ago | parent [-]

> You are using it to mean "maintaining full version history", I believe?

No, they are using it to mean “backed up”. Like, “if this data gets deleted or is in any way lost locally, it’s still backed remotely (even years later, when finally needed)”.

I’m astonished so many people here don’t know what a backup is! No wonder it’s easy for Backblaze to play them for fools.

	▲	dathinab 3 hours ago \| parent [-]
		definition of the term backup by most sources is one the line of: > a copy of information held on a computer that is stored separately from the computer there is nothing about _any_ versioning, or duration requirements or similar To use your own words, I fear its you who doesn't know what a backup is and assume a lot other additional (often preferable(1)) things are part of that term. Which is a common problem, not just for the term backup. There is a reason lawyers define technical terms in a for this contract specific precise way when making contracts. Or just requirements engineering. Failing there and you might end up having a backup of all your companies important data in a way susceptible to encrypting your files ransomware or similar. --- (1): What often is preferable is also sometimes the think you really don't want. Like sometimes keeping data around too long is outright illegal. Sometimes that also applies to older versions only. And sometimes just some short term backups are more then enough for you use case. The point here is the term backup can't mean what you are imply it does because a lot of existing use cases are incompatible with it.

▲

Timwi 6 hours ago | parent | prev | next [-]

Oftentimes the important data that needs restoring is in the checkout: uncommitted and unstaged changes that represent hours of work.

▲

nikanj 7 hours ago | parent | prev [-]

Microsoft makes no guarantees on onedrive, you are responsible for backing up that data. Of course they try hard to keep it safe, but contractually they give no promises