From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-raid@vger.kernel.org
Subject: Re: HBA Adaptor advice
Date: Sun, 22 May 2011 03:13:09 -0500 [thread overview]
Message-ID: <4DD8C595.6070307@hardwarefreak.com> (raw)
In-Reply-To: <4DD7A100.2010807@wildgooses.com>
On 5/21/2011 6:24 AM, Ed W wrote:
> On 20/05/2011 21:58, Stan Hoeppner wrote:
>
>> As always, a good data persistence strategy starts with a good UPS.
>
> I'm sure you are going to tell me that my APCs aren't good UPSs, but I
In my experience APC are good UPS. Interestingly, I have an APC
SU1400RMNET manufactured in *1997*, powering my home office rack. I've
replaced the batteries 4 times, but the UPS itself is like the Energizer
Bunny. 14 years and still going strong.
> have something like 5 APCs and 4 have failed in odd ways due to the
> battery dying, inside of around 2 years from new. Sure you replace the
Then I'd guess you're not performing proper UPS maintenance. Once
yearly you need to perform a deep cycle self test which can notify you
of marginal batteries at a much earlier stage. Your APC manual has
instructions for performing this test, or you can download the manual
from there site if it's been lost.
All APCs inform you when the battery needs to be replaced, via front
panel LED and via software or network notification (Email/SNMP). But
you don't want to wait for that. Do the deep self test.
> battery, but failure modes each time caused a sudden power failure. In
> nearly all cases the UPS failed before I would have had a sudden power
> loss for other reasons...
Yep. Lack of proper UPS maintenance and monitoring.
> So, I'm not convinced that UPSs dramatically raise the uptime, and where
Without a UPS in Missouri USA, your servers will go down from power loss
at *minimum* 50-100 times per year due to electrical storms, high winds,
power line maintenance, brown outs and sags caused by all manner of
things, truck hitting power pole, etc, etc.
> they do it's in well designed, racked, datacenter environments where
> "accidents" don't dominate the downtime risk?
Doesn't matter if it's a corporate datacenter, your rack in the
basement, or an office pedestal server. What counts is proper design
and installation. It's is trivially simple in an office environment to
route all cables in a manner that they won't be tripped over. I'm truly
shocked that cable tripping could be an issue for anyone in 2011, let
alone 1999. Get a rack cabinet and stick it in a corner. Here, get this:
http://cgi.ebay.co.uk/COMPAQ-42U-SERVER-RACK-CABINET-ENCLOSURE-/150608001643?pt=UK_Computing_Networking_SM&hash=item2310efba6b
and 2 or 3 of these, since all your servers are non-rack boxes:
http://cgi.ebay.co.uk/StarTech-Adjustable-Depth-Fixed-Server-Rack-Cabinet-She-/320618338412?pt=UK_Computing_ComputerComponents_Monitors&hash=item4aa657986c
Problem solved.
--
Stan
next prev parent reply other threads:[~2011-05-22 8:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 12:26 HBA Adaptor advice Ed W
2011-05-19 12:36 ` Roman Mamedov
2011-05-19 12:43 ` Mathias Burén
2011-05-19 14:06 ` Michael Sallaway
2011-05-19 19:10 ` Thomas Harold
2011-05-19 21:12 ` Rudy Zijlstra
2011-05-19 21:07 ` Brad Campbell
2011-05-20 20:58 ` Tobias McNulty
2011-05-20 21:23 ` Brad Campbell
2011-05-20 2:08 ` Andy Smith
2011-05-20 5:30 ` Stan Hoeppner
2011-05-21 9:52 ` Ed W
2011-05-20 7:33 ` Ed W
2011-05-20 10:21 ` Stan Hoeppner
2011-05-21 11:17 ` Ed W
2011-05-21 11:29 ` Rudy Zijlstra
2011-05-21 11:54 ` Ed W
2011-05-21 17:37 ` Leslie Rhorer
2011-05-22 9:41 ` Stan Hoeppner
2011-05-22 10:03 ` Rudy Zijlstra
2011-05-23 9:32 ` Ed W
2011-05-21 17:05 ` Leslie Rhorer
2011-05-22 9:04 ` Stan Hoeppner
2011-05-22 10:09 ` Brad Campbell
2011-05-22 19:25 ` Stan Hoeppner
2011-05-22 20:57 ` Tobias McNulty
2011-05-22 21:13 ` Johannes Truschnigg
2011-05-23 9:48 ` Ed W
2011-05-23 10:44 ` John Robinson
2011-05-22 23:19 ` Brad Campbell
2011-05-23 4:09 ` Roman Mamedov
2011-05-23 5:54 ` Brad Campbell
2011-05-23 6:08 ` Roman Mamedov
2011-05-23 10:42 ` Stan Hoeppner
2011-05-23 11:35 ` David Brown
2011-05-23 6:54 ` Stan Hoeppner
2011-05-23 7:23 ` Brad Campbell
2011-05-22 23:44 ` Brad Campbell
2011-05-23 0:07 ` Brad Campbell
2011-05-23 5:30 ` Stefan /*St0fF*/ Hübner
2011-05-23 10:18 ` Ed W
2011-05-23 9:58 ` Stan Hoeppner
2011-05-23 10:33 ` Ed W
2011-05-23 11:21 ` Stan Hoeppner
2011-05-20 12:18 ` Joe Landman
2011-05-20 12:34 ` Roman Mamedov
2011-05-20 12:36 ` Mathias Burén
2011-05-20 12:48 ` Joe Landman
2011-05-20 13:21 ` Ed W
2011-05-20 14:23 ` Joe Landman
2011-05-20 20:01 ` Andy Smith
2011-05-20 20:12 ` Stan Hoeppner
2011-05-20 20:24 ` Drew
2011-05-20 20:58 ` Stan Hoeppner
[not found] ` <4DD7A100.2010807@wildgooses.com>
2011-05-22 8:13 ` Stan Hoeppner [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-23 2:11 Jim Schatzman
2011-05-23 3:39 ` Tobias McNulty
2011-05-23 10:42 ` Ed W
2011-05-23 11:14 HBA Adaptor Advice Ed W
2011-05-23 11:55 ` Joe Landman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DD8C595.6070307@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).