I have a Windows 2003 server running on a 3Ware 9500S-4LP with RAID 5 on 4
hard disks; no battery backup unit
1) Even if the unit misses a BBU, the PC is depending on two cascaded UPS'.
What am I risking?
With a BBU, just about any non-raid component can fail without loosing
raid data. The UPS strategy is fine as long as everything is
operating properly.
A UPS does not protect against the tech behind the rack unplugging the
wrong power cable, or power cycling the wrong switch port. Or any of
a number of variations on that theme
Normally UPSs don't provide enough uptime for a rebuild if it begins
just before a long power outage. IF the controller has problems
stopping and resuming the rebuild a BBU is strongly indicated. You
might also consider looking at the maximum time the data resides in
cache (during worst case scenario i.e. rebuild) and the minimum time
the BBU will keep the controller alive.
Do you think I should avoid tha write cache feature?
You should definitely disable the write cache on the individual disks
regardless. Frankly I'd disable the controller cache also if there
was no BBU.
2) What if a disk breaks in a few years time?
If it is 3-5 years, count yourself lucky and plan to upgrade the
entire array. The service life of individual drives does not change
when they are RAIDed
Should I buy now a few disks
identical to the installed ones or can i use different brands/types?
You should have spare(s) on hand. Using only identical drives and
firmware is generally unnecessary today. Although it is often a good
idea to use the same model drives.
If all your online drives are identical models from an identical lot
with identical use they should have similar life spans unless there is
a grossly defective unit, integration problem, or handling issue. You
could rotate the media with spares, but that would jeopardize the
array's data with each rebuild. You could buy the disks from
different sources, or you could simply take your chances with disks
from a single order and a spare or 2 on hand. With a 4 disk raid 5
I'd probably try the last strategy.
3) Is sufficient to schedule the verification of the array, once a week, for
6 hours? Currently the array has a szie of about 650GB.
Generally yes. Although you should not let more than a week pass.
There is no harm in doing it more frequently unless you are noticing a
performance penalty. But I'd try throttling down the checks before
stretching the timeframe between them.