|
1 | 1 | <!-- |
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 $ |
3 | 3 | --> |
4 | 4 | <chapter id="backup"> |
5 | 5 | <title>Backup and Restore</title> |
@@ -373,6 +373,15 @@ tar -cf backup.tar /usr/local/pgsql/data |
373 | 373 | establish all the frozen snapshots. |
374 | 374 | </para> |
375 | 375 |
|
| 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 | + |
376 | 385 | <para> |
377 | 386 | Note that a file system backup will not necessarily be |
378 | 387 | smaller than an SQL dump. On the contrary, it will most likely be |
|