"As part of our backup process, Backblaze will run a checksum against each file before uploading it. This requires the entire bzfileids.dat file to be loaded into RAM. After a long time, or if you have an extraordinarily large number of files, the bzfileids.dat file can grow large causing the Backblaze directory to appear bloated, and use more RAM (potentially slowing down your system). In your case your bzfileids are extremely large, likely because you have a lot of files and an older backup."
here's my backblaze folder: http://imgur.com/ohqUERr (i have my temporary data drive set to a secondary drive)
What kind of internet connection are you on? I recently reinstalled my mac from scratch (El Capitan upgrade went haywire) and had to redo my backblaze backup. I uploaded the 500 GB to Backblaze in under 24 hours.
Also, could it be that the "re-upload" was able to detect your older copy of the files and reuse them? I can rsync terabytes in minutes over slow connections when the other side already has the files ...
Initial sync is a nighmare. The upload is on the slow side. Biggest gripe so far is that I just cannot tell the client that some files are more important than the others. I would love my pdf invoices and changed KDBX files to be synced before uploading the uncompressed blu ray of Guardians of the galaxy. On the other hand there are people that produce a lot of critically important raw video which will probably have the opposite preferences.
I can understand why they have not implemented priority interface. It is hard to get it right.
Also, I would hope no one doing mastering is uploading their raws, in real time, to a service like backblaze. On-site thunderbolt / NAS solutions are almost exclusively used in RAW backups in studios. With offsite copies stored at regular intervals via good old sneaker-net.
BB folder and file type structure makes it relatively hard to back up just some files of given type. And some stuff like tars and zips could be arbitrary in size and importance.
Having said that, we offer the ability to exclude folders and filetypes if you have certain things you want to backup later.
(Not disagreeing with anything you're saying...just fyi.)
Gleb from Backblaze
Backups transfers are also a minor pain point - the error horse (on freshly installed BB on windows) and when, how and why it disappears and allows you to do the backup is still a mystery.
I guess that the BB cloud storage will solve some of the customization problems though - if you are power enough user you could write a custom strategy on top of the API.
What's the point of backing up anything?
> Either you have the source material, in which case its almost always going to be faster to rerip than restore from backup
Sure, it will be faster, because it will be a local operation, because you probably keep the original near the same place you keep the main rip. That also means that the original source and the in-use rip are vulnerable to being destroyed together in a site-affecting event (fire, flood, robbery, etc.), which makes having a remote backup valuable.
WRT priority backup - I ended up just excluding the "big folders" manually (reducing backup size by 90%) then including them when the initial backup of the important files was complete. Also, the client backs up small files first, then moves onto bigger files, which is a nice touch - generally I'd tend to care more about losing a large number of files than a few huge files.
Not affiliated with the company, just love their product!...
In your case, I guess it would be much better to look at other solutions. For example if you have a Mac, get an extra Time Machine drive and put it at your employer's place. Every week, bring your laptop there and back it up.