Search Postgresql Archives

Advice on contingency plan for DAS array with separate local WAL drives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.





      


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux