|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.15 2006/12/0103:19:48tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/high-availability.sgml,v 1.16 2007/02/0121:02:48momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="high-availability">
|
4 | 4 | <title>High Availability and Load Balancing</title>
|
|
99 | 99 | disk array fails or becomes corrupt, the primary and standby
|
100 | 100 | servers are both nonfunctional. Another issue is that the
|
101 | 101 | standby server should never access the shared storage while
|
102 |
| - the primary server is running. It is also possible to use |
103 |
| - some type of file system mirroring to keep the standby server |
104 |
| - current, but the mirroring must be done in a way that ensures the |
105 |
| - standby server has a consistent copy of the file system. |
| 102 | + the primary server is running. |
| 103 | + </para> |
| 104 | + |
| 105 | + <para> |
| 106 | + A modified version of shared hardware functionality is file system |
| 107 | + replication, where all changes to a file system are mirrored to a file |
| 108 | + system residing on another computer. The only restriction is that |
| 109 | + the mirroring must be done in a way that ensures the standby server |
| 110 | + has a consistent copy of the file system — specifically, writes |
| 111 | + to the standby must be done in the same order as those on the master. |
| 112 | + DRBD is a popular file system replication solution for Linux. |
106 | 113 | </para>
|
107 | 114 |
|
108 | 115 | <!--
|
|