From: Bruce Momjian Date: Thu, 1 Feb 2007 21:02:48 +0000 (+0000) Subject: Mention file system replication as a high availability solution in the X-Git-Tag: REL8_3_BETA1~1348 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=52096ae119943287f04ecbe92f62e57f5b8c600e;p=postgresql Mention file system replication as a high availability solution in the shared hardware section, and mention DRBD as a popular solution. --- diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 01d2c90207..0caa6df568 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -1,4 +1,4 @@ - + High Availability and Load Balancing @@ -99,10 +99,17 @@ disk array fails or becomes corrupt, the primary and standby servers are both nonfunctional. Another issue is that the standby server should never access the shared storage while - the primary server is running. It is also possible to use - some type of file system mirroring to keep the standby server - current, but the mirroring must be done in a way that ensures the - standby server has a consistent copy of the file system. + the primary server is running. + + + + A modified version of shared hardware functionality is file system + replication, where all changes to a file system are mirrored to a file + system residing on another computer. The only restriction is that + the mirroring must be done in a way that ensures the standby server + has a consistent copy of the file system — specifically, writes + to the standby must be done in the same order as those on the master. + DRBD is a popular file system replication solution for Linux.