![]() ![]() ![]() |
|
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.
Dynamic:Sideface: Array 1 is backed up to array 2 once a day.
Nice setup.
What is your strategy for recovering an accidentally deleted/damaged/overwritten file that is not noticed for a day or two? Or are these boxes for archives for finished work only?
Wherever possible an offline backup si highly desirable in case corruption on NAS1 is replicated to NAS2. Stranger things have happened.
macuser: Hey about to go pickup a Synology DS1515+ tomorrow, it is a 5 bay NAS box.
I'm going to run RAID 10 as it is more redundant and better suited as a backup for our photography studio.
I was thinking of putting in 5 4TB WD REDS, with 4 running in raid 10, and one in hot spare for failure protection. Will this work? Or is that bay more for SSD cache, or for RAID 5? Is it worth buying the 5th HDD? We've already prepared to buy 5, but if the device doesn't support using the 5th drive to replace one that has failed, then there is no point.
Sony Xperia XA2 running Sailfish OS. https://sailfishos.org The true independent open source mobile OS
Samsung Galaxy Tab S6
Dell Inspiron 14z i5
Technofreak:macuser: Hey about to go pickup a Synology DS1515+ tomorrow, it is a 5 bay NAS box.
I'm going to run RAID 10 as it is more redundant and better suited as a backup for our photography studio.
I was thinking of putting in 5 4TB WD REDS, with 4 running in raid 10, and one in hot spare for failure protection. Will this work? Or is that bay more for SSD cache, or for RAID 5? Is it worth buying the 5th HDD? We've already prepared to buy 5, but if the device doesn't support using the 5th drive to replace one that has failed, then there is no point.
A RAID setup is not a backup. This point has been alluded to by other posters, I think it's a point worth emphasising.
RAID provides redundancy giving hopefully seamless service if a disk fails. However a corrupted file on one disk will be replicated on the other disks, or worse still a fire or other disaster will wipe out your data.
You also need a backup system. Many businesses do not need a RAID but all businesses do need a backup.
Thanks mate!
Dynamic
Best I can do is give it a test.
macuser:
Honestly, I fully understand why it shouldn't be considered a backup (raid fail, hardware fail, drive fail, user error, act of god) but this will be used as as the single storage device for a lot of images- the current system is to have a bunch of internal HDD's sitting around with single copies of files (yeap, not my choice) - so in comparison to that, this will be a huge improvement.
I can only advise that this will be 'not enough' and that a backup (LTO) and keeping versions offsite is a good idea, but that's another big spend.
The final production images go to the client and that's the end of it, this is more of a 'keep the good images for a rainy day'
Probably not good enough in an environment where if the work is lost the business is screwed, but I think this is the most versatile spend for shared network drive that has great redundancy. Thanks mate!
Sony Xperia XA2 running Sailfish OS. https://sailfishos.org The true independent open source mobile OS
Samsung Galaxy Tab S6
Dell Inspiron 14z i5
Sideface:Dynamic: .,.. What is your strategy for recovering an accidentally deleted/damaged/overwritten file that is not noticed for a day or two? Or are these boxes for archives for finished work only?
Wherever possible an offline backup is highly desirable in case corruption on NAS1 is replicated to NAS2. Stranger things have happened.
The two Synology DS1515+ boxes are for finished work only.
Mission-critical stuff (about 1% of files) is also on OneDrive.
But there is no protection from human stupidity - if I've accidentally deleted a file without noticing, and it's not still in the recycle bin, it's gone.
macuser: The final production images go to the client and that's the end of it, this is more of a 'keep the good images for a rainy day'
Probably not good enough in an environment where if the work is lost the business is screwed, but I think this is the most versatile spend for shared network drive that has great redundancy. Thanks mate!
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.
Dynamic:macuser: The final production images go to the client and that's the end of it, this is more of a 'keep the good images for a rainy day'
Probably not good enough in an environment where if the work is lost the business is screwed, but I think this is the most versatile spend for shared network drive that has great redundancy. Thanks mate!
4Tb External USB HDDs can be purchased for $200 on special. A couple of those and drag&drop once a month is better than no fall-back position.
I'm just working on a failed RAID system now (by complete coincidence). I'm not having any fun and the client is not happy. But they have backups.
macuser:
Hopefully can scoop up a couple of those 5TB drives from NL when they next come on special
While the other reply is very old…if I ran into this…other people still are, too. RAID 5 is not “less than” RAID 10, which incorrectly implies that the higher number is better, instead of demonstrating that it’s a combination RAID set.
In case I’m not being clear, RAID 10 is 1+0, not “ten”. This distinction is important for two reasons: 1) RAID 01 isn’t RAID 1, which is what we’d get pronouncing it as a number, and 2) if we imply that higher is better, RAID 50 should be even better still…when it’s just a different way of doing things. This just isn’t what “5” vs “10” vs “50” means.
For the relevant discussion:
|
![]() ![]() ![]() |