11<!--
2- $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.77 2006/02/24 14:03:01 momjian Exp $
2+ $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.78 2006/03/03 22:02:07 momjian Exp $
33-->
44<chapter id="backup">
55 <title>Backup and Restore</title>
@@ -19,7 +19,7 @@ $PostgreSQL: pgsql/doc/src/sgml/backup.sgml,v 2.77 2006/02/24 14:03:01 momjian E
1919 <itemizedlist>
2020 <listitem><para><acronym>SQL</> dump</para></listitem>
2121 <listitem><para>File system level backup</para></listitem>
22- <listitem><para>On-line backup </para></listitem>
22+ <listitem><para>Continuous Archiving </para></listitem>
2323 </itemizedlist>
2424 Each has its own strengths and weaknesses.
2525 </para>
@@ -372,11 +372,11 @@ tar -cf backup.tar /usr/local/pgsql/data
372372 </para>
373373 </sect1>
374374
375- <sect1 id="backup-online ">
376- <title>On-line backup andpoint-in-time recovery (PITR)</title>
375+ <sect1 id="continuous-archiving ">
376+ <title>Continuous Archiving andPoint-In-Time Recovery (PITR)</title>
377377
378378 <indexterm zone="backup">
379- <primary>on-line backup </primary>
379+ <primary>continuous archiving </primary>
380380 </indexterm>
381381
382382 <indexterm zone="backup">
@@ -452,7 +452,8 @@ tar -cf backup.tar /usr/local/pgsql/data
452452 </para>
453453
454454 <para>
455- To recover successfully using an on-line backup, you need a continuous
455+ To recover successfully using continuous archiving (also called "online
456+ backup" by many database vendors), you need a continuous
456457 sequence of archived WAL files that extends back at least as far as the
457458 start time of your backup. So to get started, you should set up and test
458459 your procedure for archiving WAL files <emphasis>before</> you take your
@@ -783,12 +784,12 @@ SELECT pg_stop_backup();
783784 <function>pg_start_backup</> or <function>pg_stop_backup</>, and
784785 you will therefore be left to your own devices to keep track of which
785786 backup dump is which and how far back the associated WAL files go.
786- It is generally better to follow theon-line backup procedure above.
787+ It is generally better to follow thecontinuous archiving procedure above.
787788 </para>
788789 </sect2>
789790
790791 <sect2 id="backup-pitr-recovery">
791- <title>Recoveringwith an On-line Backup</title>
792+ <title>Recoveringusing a Continuous Archive Backup</title>
792793
793794 <para>
794795 Okay, the worst has happened and you need to recover from your backup.
@@ -1120,11 +1121,11 @@ restore_command = 'copy /mnt/server/archivedir/%f "%p"' # Windows
11201121 </para>
11211122 </sect2>
11221123
1123- <sect2 id="backup-online -caveats">
1124+ <sect2 id="continuous-archiving -caveats">
11241125 <title>Caveats</title>
11251126
11261127 <para>
1127- At this writing, there are several limitations of theon-line backup
1128+ At this writing, there are several limitations of thecontinuous archiving
11281129 technique. These will probably be fixed in future releases:
11291130
11301131 <itemizedlist>