Zitat150 TB?
Really?
That would lead to something like that: aberdeeninc.com/abcatg/8U-Nehalem-Linux-NAS.htm
Just setting an end point of 150TB. Most likely I wont or just reach half of that
ZitatAlles anzeigen3. Good question. We don't have a lot of people with that much storage. So, you will have to tell us I would 6tb drives would be easier to implement.
4. Yep. That is what I do. I have two OMV boxes. One runs the rsync job on a schedule and the other runs the rsyncd server. Works great.
5. Most of my servers don't have ECC. With media and snapraid, I don't think you need it. One bad bit in a media file wouldn't be noticeable.
7. I wouldn't use Snapraid's pooling. It is read only as well. I would install the unionfilesystems plugin and add all data/content (non-parity) drives to a mergerfs pool. Then you share the pool in all plugins.
3. Still searching info on this, will post here if I find out either from other people or by testing
4. Do you do any offsite/cloud backup as well? Can share your method/s?
5. So, my data would still be okay without using any ECC?
7. Do I need drive pooling? Do I lose anything by not pooling? If let's say, instead of OMV, i were to install in Windows 7; my drives would appear as A-Z but if I use drive pool, it only appears as A?
ZitatThere's more to it than that.
See:snapraid.it/manual Section 4.4 Recovering
ZitatI guess you are correct. The additional steps have to be done from the command line as well.
ZitatI may be mistaken, but I think that running a sync before running the fix procedure could wipe out the parity information for the failed disk making it impossible to recover that failed disk. Hopefully someone will correct me if I am wrong.
Will consult the manual for more details on this
Thank you.