Advice on contingency plan for DAS array with separate local WAL drives - Mailing list pgsql-general

From Jeff Amiel
Subject Advice on contingency plan for DAS array with separate local WAL drives
Date
Msg-id 779057.59977.qm@web65516.mail.ac4.yahoo.com
Whole thread Raw
Responses Re: Advice on contingency plan for DAS array with separate local WAL drives  (Jeff Amiel <jamiel@istreamimaging.com>)
Re: Advice on contingency plan for DAS array with separate local WAL drives  (Greg Smith <greg@2ndquadrant.com>)
List pgsql-general
Recently migrated to a shiny new 8.4.4 postgres instance....data stored on attached storage array.  Transaction logs
storedon 2 local mirrored drives (local to the database server itself) for best performance. 

While we are replicating (using slony) to our DR site, our first-choice plan (in the event of an issue simply with the
databaseserver itself) was to disconnect the SAS cables from it (connected to the DAS) and connect them to a 'similar'
boxwe have on standby.  With the WAL logs physically on the drives of the original database server, this obviously
becomesan issue.   

What is recommended in terms of prep/switchover in this instance?  Should we be rsyncing or using built-in wal-log
shippingof these transaction logs to our stand-by server?  Simply pop out these drives and hand-move them to the
standby-server?(assuming they are not the issue in the first place)    

Any thoughts would be appreciated.








pgsql-general by date:

Previous
From: Raymond O'Donnell
Date:
Subject: Re: Is there a way to backup Postgres via SQL commands?
Next
From: Ulas Albayrak
Date:
Subject: Re: Moving a live production database to different server and postgres release