Postgres' website mentions DRBD, but not on the data files. They recommend a setup with two servers sharing a common mount point (SAN or similar). That common mount point has the data files. The first server has postgres running with DRBD pushing changes to everything other than the postgres data files to the second server. If the first server takes a dump, the second server simply starts postgres and lets postgres do a recovery on the shared mount and continue running. (Also using Heartbeat to move the virtual IP.)
If you do get this working on the data files as well...I'd definitely like to know what you did. Having the common mount point with the data files is the only thing that's kept me from trying this setup on my postgres databases. Darrin On Mon, Oct 13, 2008 at 2:18 PM, Steven S. Critchfield <[EMAIL PROTECTED]>wrote: > > > We may even look into doing some of these same things to other machines. We > have even thought about trying this out with Postgresql as a cheap > replication system. Essentially making sure that recovery not really any > different from power failure. In progress queries are lost, but a reconnect > and you are back running again. > > > > -- > Steven Critchfield [EMAIL PROTECTED] > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en -~----------~----~----~----~------~----~------~--~---
