Moogle Stiltzkin wrote: ↑Thu May 02, 2019 2:18 am
i'm sure other people have their own recommendations, but mine is the following
once a month - raid scrub
short smart test - weekly
long smart test - monthly
My recommendation is to schedule tasks automaticly like this:
Short SMART tests - daily
Long SMART tests - weekly
RAID scrubbing - monthly or bi-monthly (by scheduling scrubbing on the 31st it becomes almost bi-monthly)
Also it's important to make sure that notifications are enabled and working in the NAS to get notified about any issues during testing as soon as possible.
during a raid scrub, your NAS performance will be very slow..... i don't recommend doing much writes (e.g. copy/cut paste moving files around in the NAS during a raid scrub.) but i reckon read should be fine (e.g. i can watch a movie during the process). Buffering is slow, but i can still watch a movie without issue.
I don't understand why there would be any significant differences between read or write. The main problem with accessing the disks during a RAID scrub is that the disk read/write head will have to move back and forth between where it's working with the scrub and where the data you access is located. The more concurrent disk access you have (read or write), the slower everything will be as the heads will be hunting back and forward between it's different tasks.
But ideally you would schedule the raid scrub during sleep hours when you don't actually use the NAS, so the slow performance during the process won't really impact you.
Absolutely, start it as early as possible when there's a known non/low usage period for the NAS. Sometimes that may not be enough but at least that's the best we can do to get as much as possible done when it affects us the least.
Also as the RAID scrub priority can manually be changed on the fly, it's clever to prioritize scrubbing (Resync First, High Speed) when there's no other usage to speed it up as much as possible during those hours and then tune it down (Service First, Low Speed) if other usage is necessary to increase the responsiveness to the user.
RAID_sync_prio.jpg
I do not recommend scheduling raid scrubs and smart test to occur or coincide at the same time.
I've never experienced any problems with having them running concurrently. The SMART testing probably have a very low priority in the disks to affect usage by the host system as little as possible.
I think it's ok for all the hdds to run the smart test same time.
It definitely is. I've been doing that for the last 10 years. I prefer to space their starting time a few minutes though as that will keep them nicely lined up in sequential order to make the system logs more easily readable. It's important to remember to schedule the short test with a sufficient earlier starting time (like 10-15 minutes earlier) to make sure it will have finished at the long SMART Test start as otherwise that won't be able to start.
You do not have the required permissions to view the files attached to this post.
RAID have never ever been a replacement for backups. Without backups on a different system (preferably placed at another site), you will eventually lose data!
A non-RAID configuration (including RAID 0, which isn't really RAID) with a backup on a separate media protects your data far better than any RAID-volume without backup.
All data storage consists of both the primary storage and the backups. It's your money and your data, spend the storage budget wisely or pay with your data!
?