aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-03-17 05:03:37 +0000
committerBruce Momjian <bruce@momjian.us>2005-03-17 05:03:37 +0000
commitca2d08579e27192867a421ab2c324c8c0c6b2440 (patch)
treeb7a0a0b24ec21fe54402311f24a29ae93da0069e
parent82c46e5a7075dc450da856cfaaafaa71552c5d01 (diff)
downloadpostgresql-ca2d08579e27192867a421ab2c324c8c0c6b2440.tar.gz
postgresql-ca2d08579e27192867a421ab2c324c8c0c6b2440.zip
Document use of rsync for file system backups.
Tino Wildenhain
-rw-r--r--doc/src/sgml/backup.sgml11
1 files changed, 10 insertions, 1 deletions
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index 02d07f6c2f4..00efde7ee29 100644
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
<!--
-$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.56 2005/02/25 04:56:01 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.57 2005/03/17 05:03:37 momjian Exp $
-->
<chapter id="backup">
<title>Backup and Restore</title>
@@ -374,6 +374,15 @@ tar -cf backup.tar /usr/local/pgsql/data
</para>
<para>
+ Another option is to use <application>rsync</> to perform a file
+ system backup. First, while the database server is running,
+ run <application>rsync</>, then shut down the database
+ server and perform a second <application>rsync</>, then
+ restart the database server. This allows a file system backup to be
+ performed with minimal downtime.
+ </para>
+
+ <para>
Note that a file system backup will not necessarily be
smaller than an SQL dump. On the contrary, it will most likely be
larger. (<application>pg_dump</application> does not need to dump