Just make sure you have you have a bot network storing the information in with multiple accounts. Also with with enough parity bits (E.g. PAR2) to recover broken vids or removed accounts.
It only support 32k parts in total (or in reality that means in practice 16k parts of source and 16k parts of parity).
Lets take 100GB of data (relatively large, but within realm of reason of what someone might want to protect), that means each part will be ~6MB in size. But you're thinking you also created 100GB of parity data (6MB*16384 parity parts) so you're well protected. You're wrong.
Now lets say one has 20000 random bit error over that 100GB. Not a lot of errors, but guess what, par will not be able to protect you (assuming those 20000 errors are spread over > 16384 blocks it precalculated in the source). so at the simplest level , 20KB of errors can be unrecoverable.
par2 was created for usenet when a) the size of binaries being posted wasn't so large b) the size of article parts being posted wasn't so large c) the error model they were trying to protect was whole articles not coming through or equivalently having errors. In the olden days of usenet binary posting you would see many "part repost requests", that basically disappeared with par (then quickly par2) introduction. It fails badly with many other error models.
yes, but it just moves the needle a bit, if you lose 1 of the 1GB parts in totality, you also can't recover, so it really depends in on your error model you are trying to protect from.
In practice a DVD like PI/PO model would be the best for many people (protect the 1GB parts like you said with 5-10% redundancy, and then protect all 100 1GB parts together with 5-10% redundancy. the PI will repair as much as it can at the 1GB size, while the PO will be able to repair 1GB blocks that can't be repaired otherwise.
It be interesting if Par2 or something like it could implement it natively without people having to hack together their own one off solutions.
just pay for storage instead. It's absurd that rich developers are doing ANYTHING but to pay for basic services - ruining the internet for those in real need.
Plus restic or borg or similar. I tried natively pushing from truenas for a while and it's just slow and unreliable (particularly when it comes to trying to bus out active datasets) and rsync encryption is janky. Restic is built for this kind of archival task. You'll never get hit with surprise bills for storing billions of small files.
6$ / TB / month is a fool's bargain even for something as low as 10 TB. One can buy a used LTO-6 drive for a few hundred bucks and build tape libraries that span hundreds of TBs.
There's no Cloud-based backup service that's competive with tape.
What does Backblaze's backup software have to do with B2? Backblaze B2 is just storage that exposes the same API as S3. You can use any backup software that supports S3 as a target.
I have a relatively recent Microsoft account, but at this point I refuse to even type it into my Windows computer. Given their user-hostile posture, I wouldn't put it past Microsoft to have a keystroke logger listening for me typing my MS account into some other software. Then, it could pop up with "Surprise! We just upgraded your local account to this Microsoft account that we just saw you type in! Now you have to log in with your Microsoft account. Gotcha, sucker!"
I haven't dug into it, but I have a (personal) win10 machine that is used for a combination of gaming and some of my dev work (visual studio & .net). I recently needed to install excel on this machine, and used my work account. I believed I was only logging into MS office, but now that machine has printers added that are added on my machine at the office, so somehow logging into MS Office but on a local windows10 account added printers from a different network. I'm not surprised, but definitely demonstrating that there's potential for information leakage if using their online accounts.
It's very possible. I've honestly stopped counting the ways Microsoft is attacking my computer and network through Windows. At this point I treat the entire OS as adversarial, and go so far as isolating my few Windows machines onto their own VLAN where they can do the least damage.
I'm ashamed to admit that I didn't get this joke until I reread it a few times. Probably because my entire life, I've internally pronounced "qt" as "quart". It took a bit before I realized the joke was shooting for "cutie".
reply