![]() Overkill implies way better protection than necessary. This is definitely overkill but as the family history data storer, Google or Amazon or Microsoft do that on scale, much better, and cheaper. You can of course, but it is not clear to me how is that beneficial at all: to maintain viability of your data you have to have storage with checksumming (for integrity validation) and redundancy (for healing) and keep maintaining it. I hope to replicate what Crashplan gives me (a local copy that stays next to my device, a semi local copy that I can store close by, and a truly offsite cloud version). Please don’t use this contraption for any long term data retention, including as a backup target. The dude in this video discusses and explains data integrity issues that arise when you want long term data storage and even explicitly mentions your setup: RAID: Obsolete? New Tech BTRFS/ZFS and "traditional" RAID - YouTube This is especially true for photos and other media that are written once and never touched again. You likely have already lost data but unless you attempt to restore all of it you will never know. ![]() ![]() This is effectively JBOD and is not different that just a bunch of drives (which is in fact what this abbreviation stands for), with reliability worse than that of a single drive. I’ll have to think about that.ĭrivePool to create one “drive letter “ that goes across multiple actual drives.n To that point, it sounds like I should not use DrivePool but, instead figure out which backup sets will fit on what drives and set them that way. I figure I will start with getting my two “local” copies first while I learn about the other. I think I can get there, I just don’t know anything about it yet. Crashplan has been easy since I didn’t have to worry about setting up the cloud, etc. This is definitely overkill but as the family history data storer, I can’t let this data get lost under any circumstances. ![]() Using something like Duplicacy, I hope to replicate what Crashplan gives me (a local copy that stays next to my device, a semi local copy that I can store close by, and a truly offsite cloud version). This was done because it was easier to handle since I have used Crashplan for many years (Mozy before that, etc.) to backup all of my data both to local disks as well as to their offsite locations. I use DrivePool to create one “drive letter “ that goes across multiple actual drives. If it helps explain my situation, I do not have a NAS in any RAID configuration. Thank you for the information, it is very helpful. ![]()
0 Comments
Leave a Reply. |