Quote:
Originally Posted by
jmpage2 
I completely understand the risks. I have been working with data for about 15 years now so I am pretty comfortable with what I am dealing with.
Unless you have written disk drivers and filesystems, you (barely even) vaguely understand the risks. And those risks are exacerbated by the prevalence of non-ECC memory on typical systems nowadays. working with ... 15 years? Feh! I received my first software royalties 40+ years ago

.
Quote:
Originally Posted by
jmpage2 
For me, personally, backing up in the manner you suggest is more hassle than it is worth, especially when it is time to make a periodic incremental backup, something >>you<< can't easily do when you are separating out your content (movies A-J on disc 1, K-Z on disc 2, etc).
(Actually, *I* can.) And, such a simple tool should be available for this application. Although, I can accept that if it is a (relative) hassle for you, then you may (have to) be willing to accept a greater risk. But, if one is incurring the effort and expense of putting a backup of critical data in a safety deposit box, shouldn't they try to minimize the inherent risk in the procedure they use to do so?
Quote:
Originally Posted by
jmpage2 
What happens when amass 15-20 TB of data, you're really going to try to filter it down so you put parts of each share on their own individual hard drive?
Not "try" -- "do". Software is a beautiful thing.
Quote:
Originally Posted by
jmpage2 
Yick.
I'm not familiar with yick; I suggest you try perl.
Kidding aside, I'm not trying to give you a hard time. But, maybe you should suggest/request to Synology that they enhance their backup procedures to include such features. It *is* a better approach. And, it will improve their product.
-- Uh Clem "5 jobs; 2 detached."