Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit ca2d085

Browse files
committed
Document use of rsync for file system backups.
Tino Wildenhain
1 parent 82c46e5 commit ca2d085

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

doc/src/sgml/backup.sgml

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.56 2005/02/25 04:56:01 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.57 2005/03/17 05:03:37 momjian Exp $
33
-->
44
<chapter id="backup">
55
<title>Backup and Restore</title>
@@ -373,6 +373,15 @@ tar -cf backup.tar /usr/local/pgsql/data
373373
establish all the frozen snapshots.
374374
</para>
375375

376+
<para>
377+
Another option is to use <application>rsync</> to perform a file
378+
system backup. First, while the database server is running,
379+
run <application>rsync</>, then shut down the database
380+
server and perform a second <application>rsync</>, then
381+
restart the database server. This allows a file system backup to be
382+
performed with minimal downtime.
383+
</para>
384+
376385
<para>
377386
Note that a file system backup will not necessarily be
378387
smaller than an SQL dump. On the contrary, it will most likely be

0 commit comments

Comments
 (0)