pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jay A. Kreibich <jak@uiuc.edu>
To: Goulet, Dick <DGoulet@vicr.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Multiple WALs for PITR ?
Date: Thu, 7 Oct 2004 09:59:36 -0500
Message-ID: <20041007145936.GA3779@uiuc.edu> (raw)
In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA6501B9D747@25exch1.vicorpower.vicr.com>
References: <4001DEAF7DF9BD498B58B45051FBEA6501B9D747@25exch1.vicorpower.vicr.com>

On Thu, Oct 07, 2004 at 10:32:04AM -0400, Goulet, Dick scratched on the wall:
>  Some disk array manufacturers had a problem with their writes in that
> although the write the data was being stored in volatile memory instead
> of on disk.  The disk buffers were volatile in that if power suddenly
> died all writes in memory that had not made it to disk were lost.
> Lately most array manufacturers (at least those I have experience with
> namely EMC & NetApp) have internal battery backup systems in place so
> that in the event of a power failure the array will accept no new data,
> but has sufficient battery power available to flush memory to a disk
> drive cleanly before crashing. 

  All of the RAID systems I've dealt with work a little differently.  In
  most cases the internal array battery is only there to keep the
  contents of the buffer alive-- there is not enough power to actually
  keep a disk spinning and write the data out. You'd need a real UPS
  for that.  Typically the internal batteries have enough power to
  keep the volatile memory contents active for two weeks or more.
  Once power is re-applied to the array, the buffers are
  automatically flushed by the RAID controller.

  They are also, frankly, a pain in the butt.  We've had most of our
  batteries fail within 18 months or so, and replacements are often
  extremely expensive.  For most of our applications we've just
  disabled the RAID controller write-caches (our application writes
  data at a very very slow rate; the main reason we have RAIDs is
  protection, size, and *read* speed).

   -j

-- 
                     Jay A. Kreibich | Comm. Technologies, R&D
                        jak@uiuc.edu | Campus IT & Edu. Svcs.
          <http://www.uiuc.edu/~jak; | University of Illinois at U/C



view thread (9+ messages)  latest in thread

Message-ID: <20041007145936.GA3779@uiuc.edu>
Permalink:  ../20041007145936.GA3779@uiuc.edu/
Also on:    postgresql.org/message-id/20041007145936.GA3779@uiuc.edu

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jak@uiuc.edu, DGoulet@vicr.com
  Subject: Re: Multiple WALs for PITR ?
  In-Reply-To: <20041007145936.GA3779@uiuc.edu>
  References: <4001DEAF7DF9BD498B58B45051FBEA6501B9D747@25exch1.vicorpower.vicr.com> <20041007145936.GA3779@uiuc.edu>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox