Live data from Hacker News

Backblaze 7.0 – Version History and Beyond

backblaze.com

81–90 of 130 posts

Re: Backblaze 7.0 – Version History and Beyond

#81

Earlier quoted context omitted.

Disclaimer: I work at Backblaze. > Has this policy changed at some point? It is more complicated than just "after 30 days" (and always has been). If your laptop is entirely offline (or you simply uninstall the client from your laptop), then the policy is ACTUALLY that we keep your backup for 6 months as long as you keep paying your bill. But to be honest, it's more like a year or two. The 6 month policy is we guarant…

> HOWEVER, with this new 7.0 release you can pay a little more and increase that retention time to one year, or forever. This was a highly requested feature for the situation you ran into. I'm glad to hear that Backblaze has finally made such an option available. However: > For cost reasons, Backblaze purges the files that you deleted from your local drive after 30 days. As someone who once almost lost his PGP key an…

What you're referring to, I'd call a historical archive, containing many backups.

When I think about a backup, I'm thinking in terms of recovering last good state after a drive failure or catastrophic filesystem corruption. I don't tend to think of a backup as implying a deep history unless that part is explicitly stated. That distinction was easier to notice back in the days of backing up to tape or optical discs - you don't expect each tape/disc to contain a version history, just a single snapshot, and you don't expect your collection to retain long-gone files unless it's an ever-growing pile of tapes/discs.

In that mindset, it's not reasonable to expect that a backup service necessarily provides the full historical archive.

Re: Backblaze 7.0 – Version History and Beyond

#82
Are you (BackBlaze) still happily deleting user's backup files if user's computer does not contact BackBlaze servers within some arbitrary time?

Yes/No?

Source: https://help.backblaze.com/hc/en-us/articles/217664898-What-...

This is malice.

If you are still doing this to your users - your service is a non-starter. Backup service that deletes user's valuable files under some TOS excuse should not exist.

Re: Backblaze 7.0 – Version History and Beyond

#83
post #79

Earlier quoted context omitted.

> HOWEVER, with this new 7.0 release you can pay a little more and increase that retention time to one year, or forever. This was a highly requested feature for the situation you ran into. I'm glad to hear that Backblaze has finally made such an option available. However: > For cost reasons, Backblaze purges the files that you deleted from your local drive after 30 days. As someone who once almost lost his PGP key an…

What's your criteria for backup? I completely agree that something like RAID is not backup, but 30-60 days seems comparable to other backup services and covers most scenarios. The old-school manual process of swapping a USB drive at work every week/month has the similar retention. The only consumer-facing system I've used with multi-year retention is Time Machine. Every few years it has trouble "verifying" the backup…

Backup means that if it takes me 6 months to realise that the 2014 finances folder had been accidentally deleted, I can still recover it.

I'd love to see BackBlaze offer the option to select "mission critical" folders that have super-long-life (Time Machine-like) version retention. Give everyone a few gigabytes of this for free, charge a premium to increase that space.

Re: Backblaze 7.0 – Version History and Beyond

#84
post #61

Earlier quoted context omitted.

Yev, thanks for intervening but I’ve just received an update so incredible and unapologetic that I’m tempted to share verbatim excerpts here, and I think you should take a look. Support is basically telling me that the inherit process on the server can’t handle my "too large backup state’s indexes", and that I’m gonna have to start afresh and reupload 2TB or so from scratch. Not only that, but in order to even be all…

Disclaimer: I work at Backblaze and I wrote the Inherit Backup State functionality. > inherit process on the server can’t handle my "too large backup state’s indexes" Yeah, I'm sorry about that and it is on my plate to fix it. The issue is that Backblaze uses a ZIP library that only handles up to 4 GByte zip files. We zip up your "backup state" (the list of files that were backed up) and download it to the client tha…

By the way, Comcast has announced that it literally intends to offer full 1 Gbit/sec service to every last customer in the United States, so another way to go is upgrade your internet for 1 month, then downgrade it later.

Comcast is promising 1GB download speeds. Their maximum upload speed is still an abysmal 35Mbps.

Re: Backblaze 7.0 – Version History and Beyond

#85
post #82

Are you (BackBlaze) still happily deleting user's backup files if user's computer does not contact BackBlaze servers within some arbitrary time? Yes/No? Source: https://help.backblaze.com/hc/en-us/articles/217664898-What-... This is malice. If you are still doing this to your users - your service is a non-starter. Backup service that deletes user's valuable files under some TOS excuse should not exist.

[deleted]

Re: Backblaze 7.0 – Version History and Beyond

#86

I really miss Backblaze. I was a customer for years and years and actually was fortunate (I guess?) enough to have to use them to recover around a terabyte once but when I switched to using a Chromebox as my daily driver (then a Chromebox 2) I found I was turning my Windows machine on once a month just to keep kosher with the Backblaze servers. Such a great service and I still always look forward to the emails, stuff…

> I found I was turning my Windows machine on once a month just to keep kosher with the Backblaze servers I’ve been burnt badly by this, I wish there was a better way. I was in the habit of doing this and when I fired the drive up for some reason it failed to be backed up and the backup was deleted at their end. 1TB had to be re-uploaded on a 4Mbps connection. I know I shouldn’t have done the backup on the last day (…

With the new service, they are announcing, that shouldn’t be an issue.

Re: Backblaze 7.0 – Version History and Beyond

#87
post #51

Earlier quoted context omitted.

Yes, that's exactly what happened. It required re-uploading more than 300GB of data. Will reach out to support.

Disclaimer: I work at Backblaze. > It required re-uploading more than 300GB of data. What should occur is that it must READ all of the files to make sure it has transmitted them already, which can take hours sometimes, but only a tiny, tiny amount of data is actually transmitted to the datacenter. The client basically shows endless streams of files flowing through it and saying "Currently Backup Up: puppy.jpg" but it…

Yes, makes sense that it has to read them (and presumably calculate a hash and send that hash to your service) to deduplicate; in this case, it took multiple days to complete the process. This is about how long it took to upload the directory in the first case. I did file a ticket after Yev's reply.

Re: Backblaze 7.0 – Version History and Beyond

#89

I've only ever had one problem with Backblaze, in my ... 7 or 8? ... years as a customer. The problem: The UI for excluding directories is horrific . It uses the Windows "Browse for Folder" *SHBrowseForFolder) dialog, which requires you click down through each and every level of your directory structure to get to the directory you want to exclude. You can't cut and paste, it doesn't start from the directory you added…

>> You can't cut and paste, it doesn't start from the directory you added your last exclusion in, it's just lots and lots and lots and lots of clicking.

But it's not entirely true. You can paste full path to needed folder in input below directory tree. I've used this many many times

https://dl.dropboxusercontent.com/s/58tncadu2z7ix29/bzbui_20...

Re: Backblaze 7.0 – Version History and Beyond

#90
post #42
post #32

Earlier quoted context omitted.

Well, not trying to turn this into a support forum any further, but I've just upgraded to 7.0 and right now SMS 2FA seems broken ("The verification code is invalid" every time)

Yev here -> I'll do support wherever I see my bat-signal :D Do you have an alternate method set? If you reach out to support -> https://help.backblaze.com/hc/en-us/requests/new (they have live chat right now) - they can try an alternate method if our primary provider isn't reaching your device!

It's completely broken here as well, which was really frustrating. I already wasted 117 days of a yearly subscription on one machine because it ran Catalina Beta (which was my fault, I needed a test machine, and I ate the time lost without complaint), but not being able to inherit that back up really sucked afterwards.
Post reply on HN