From: | Jeff Amiel <becauseimjeff(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Advice on contingency plan for DAS array with separate local WAL drives |
Date: | 2010-06-14 13:05:53 |
Message-ID: | 779057.59977.qm@web65516.mail.ac4.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Recently migrated to a shiny new 8.4.4 postgres instance....data stored on attached storage array. Transaction logs stored on 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 database server itself) was to disconnect the SAS cables from it (connected to the DAS) and connect them to a 'similar' box we have on standby. With the WAL logs physically on the drives of the original database server, this obviously becomes an issue.
What is recommended in terms of prep/switchover in this instance? Should we be rsyncing or using built-in wal-log shipping of 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Ulas Albayrak | 2010-06-14 13:09:16 | Re: Moving a live production database to different server and postgres release |
Previous Message | Raymond O'Donnell | 2010-06-14 13:05:27 | Re: Is there a way to backup Postgres via SQL commands? |