Re: Write cache for a SAN

From: Rich Jesse <rjoralist_at_society.servebeer.com>
Date: Mon, 3 Nov 2008 13:33:23 -0600 (CST)
Message-ID: <65e863a97ce8a4a1ab50c96c521e79d9.squirrel@society.servebeer.com>


Amen, Brother!

A few years back, SAN hardware vendor sent out a team to upgrade the firmware. Since our ERP system had dual-paths to the SAN, they did one controller at a time. But because The Plan was not followed, the DB was up at the time, and they failed to let HPUX rediscover the primary path before unplugging the secondary.

It was also realized at that time exactly why I wanted a controlfile copy on local storage...

Rich

> On Mon, Nov 3, 2008 at 7:19 AM, Freeman, Donald
> <dofreeman_at_state.pa.us>wrote:
>
>> We don't disable it. The SAN manufacturers have made this as bullet
>> proof as possible.
>>
>
> Guess what happens when the storage vendor sends out a tech to replace
> batteries
> (the batteries that ensure the write cache stays put), and the tech can't be
> bothered
> to follow instructions?
>
> What do you think might happen to the write cache?
>
> I'm not saying that the write cache should be disabled, but you need to
> ensure that
> the folks that maintain the HW actually know what they are doing.

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Nov 03 2008 - 13:33:23 CST

Original text of this message