| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Steve Poe <steve(dot)poe(at)gmail(dot)com> |
| Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgresql data integrity during RAID10 drive rebuild |
| Date: | 2006-11-29 19:39:55 |
| Message-ID: | 1164829195.14565.210.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 2006-11-29 at 13:21, Steve Poe wrote:
> Yep, I've done it a few times. A few tips:
>
> backup your database with pg_dump. confirm you can restore on
> a test
> machine.
>
> Thanks. We do nightly dump and restore to a second server for
> testing/backup purposes.
> The data is entact. Are you recommending a dump before we begin the
> drive rebuild?
Either that, or wait until the nightly dump / restore has run and start
then.
> replace the drive during the lowest traffic period for your
> database.
>
> Sounds good. According to LSI, the drive will take 8 hrs to rebuild a
> 146GB disc (at a 30% rebuild rate), so doing this in the middle of the
> day is not ideal.
The rebuild time also tends to depend on how full the array is. If
you're only using 5% or so, it won't take the full 8 hours they're
projecting.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-11-29 19:40:29 | Re: Development of cross-platform GUI for Open Source DBs |
| Previous Message | Tom Lane | 2006-11-29 19:38:10 | Re: coalesce with all nulls can only be assigned to |