| Title: | HSZ40 Product Conference |
| Moderator: | SSDEVO::EDMONDS |
| Created: | Mon Apr 11 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 902 |
| Total number of notes: | 3319 |
Hello,
The world bank has been suffering problems with the batteries on there
dual-redundant HSZ40's They are running DU 3.2g. When a battery goes into
a failed state the raidset goes offline and the system hangs. The current
cache policy is A. If we change to cache policy B will the raidsets stay
available if the battery fails? Is there a way to get the preferred ids to
failover if a battery fails?
Many Thanks,
Tony
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 897.1 | SSDEVO::T_GONZALES | Mon Jun 02 1997 11:52 | 19 | ||
What version of hsof are you running.
The only time that cache policy has any effect is when you first boot
the controller, if the cache policy is A and the batteries fail the
boot diagnosticts then the mirror sets and raid sets are taken off
line. If the cache policy is B, the the mirror sets and raid sets
will be put into write thru mode. However if the batteries continue
to fail battery tests and do not pass the tests within 10 hours, the
raid sets and mirror sets will be taken off line, regardless of policy.
That is what will happen if you are running 2.x.
If you are running version 3.x, then if the system does not pass the
battery test within 10 hours the controller will crash and the units
will fail over. The cache policy works the same for 2.x and 3.x
| |||||
| 897.2 | HS0f 2.7 | NNTPD::"[email protected]" | Tony Papandrea | Mon Jun 02 1997 15:19 | 4 |
Currently, HSof 2.7 is running. That will be upgraded tonight to 3.1. Thank you for your quick response [Posted by WWW Notes gateway] | |||||