You don’t need to copy your data off or “migrate” your stuff. Zero dependencies on any external metadata. And “dd_rescue” can go to work on the pulled drive with other NTFS-aware applications being used for the recovery.ĭon’t like DrivePool? Just stop using it. In both the cases of DrivePool and SnapRaid, you can simply yank a drive out, and in the worst case you lose simply the files on that drive. Of course you have a backup(as do I have my setup), but why put yourself in jeopardy? There are nightmare examples all over the place. I can just imagine getting some cryptic error message and my stuff is just not accessible due to some weird synchronization problem. The idea that the entire “thing” (pool, array, whatever) can be rendered completely unreadable due to a partial failure is just an untenable state for me. While I’m mostly in the minority here, and in other forums, I simply don’t like standard RAID or alternative file systems. It’s two words “snapraid sync”, runs in the background, and does the business.ĭoes a fine job of describing the benefits and ideal use-cases for it. Some people script it like a cron job, but I usually just run the command manually after making big changes. The non-real time nature of SnapRaid is fine for me. Anytime I change a decent amount, I do a sync. I usually make mostly additions only, and I only do so a few times a week at most. In the future I will migrate to zfs, which is quite complex in data protection.įor mostly static content, where the bulk of the data isn’t changing, SnapRaid is great. In the past I was also thinking about connecting DrivePool to SnapRaid, but it seemed to me that this solution was not optimal. I’m still optimizing my setup, and I’m still learning too!Įxclude *.unrecoverableexclude Thumbs.dbexclude $RECYCLE.BINexclude \System Volume Informationexclude \Program Files\exclude \Program Files (x86)\exclude \Windows\exclude. I suppose during a file evacuation there could be some large scale moves which would screw with SnapRaid parity. I wouldn’t lose anything due to DrivePool’s duplication. SnapRaid gives me silent bit rot detection and correction and an easy way to Read Scrub the disks.įor the failure capabilities, I’m not sure if an actual failure occurred if I would actually go through the trouble of recreating the failed disk or not via SnapRaid. I consider the snapraid layer to be UNDER the drivepool layer. Occasionally, I’ll get a message that a file has moved during a snapraid sync. I leave DrivePool balancing on which in theory will move a bunch of files around, but in practice doesn’t.
content files on multiple disks outside of the pool – including the Boot OS SSD.
I store the parity information on other non-data disks. I point the data disks at the mount point folders for the individual disks - not the pool. No real quirks with b2 that I’ve found yet – everything seems to be working as before. I’m a full-paying customer of b2 – I pay what all customers of b2 pay for storage. Basically just waiting to be marginalized, slowed, and excluded. While b2 is much more than google drive, I don’t feel like screwing around with yet another provider where I’m the undesirable part of the equation. Rclone doesn’t support b2’s versioning with filename encryption due to appended date/time stamp of the versions, and b2 doesn’t support -backup-dir option of rclone due to lack of server-side moves.
I suppose there could be some bitrot after initial upload. I think b2 might store a checksum in its metadata, however I’ll have to think through whether that’s sufficient.
The only time I’ll be downloading is to test the backup, which will consist of spot-checking by downloading 10s of GBs throughout the directories, and then hashing the original vs uploaded. My storage requirements are in the single digit TBs. I’ve got reasonable enough speeds that I wasn’t gonna mess with a VPS or similar to do cloud->cloud. Easily 150-180mbps uploading, which is flooding my FIOS. There’s some minor API transaction costs, but it doesn’t appear that they will add up to anything significant.įrom the East Coast US, backblaze is pretty quick.
Will backblaze backup my files if i use filevault free#
Pricing is $5/TB/month for storage, free uploading, and $20/TB for downloading. As soon as I got wind of the ACD stuff going down, I setup rclone for backblaze b2.
0 kommentar(er)
