I noticed that we are using the term "Online Backup" in our documentation when we are talking about continuous backup and PITR.
To me, "online backup" is doing a backup while the system is online (online-backup), and that is accomplished by pg_dump. I know a lot of databases us "Online Backup" but I assume this is for historical reasons because at some time in the past their full backups didn't work while the database was online. Other systems use the term "Continuous Logging", but I think that is too easily confused with the server activity logs. I suggest the following patch to rename our capability "Continuous Backup". -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073
Index: backup.sgml =================================================================== RCS file: /cvsroot/pgsql/doc/src/sgml/backup.sgml,v retrieving revision 2.76 diff -c -r2.76 backup.sgml *** backup.sgml 7 Nov 2005 17:36:44 -0000 2.76 --- backup.sgml 26 Dec 2005 16:30:48 -0000 *************** *** 19,25 **** <itemizedlist> <listitem><para><acronym>SQL</> dump</para></listitem> <listitem><para>File system level backup</para></listitem> ! <listitem><para>On-line backup</para></listitem> </itemizedlist> Each has its own strengths and weaknesses. </para> --- 19,25 ---- <itemizedlist> <listitem><para><acronym>SQL</> dump</para></listitem> <listitem><para>File system level backup</para></listitem> ! <listitem><para>Continuous backup</para></listitem> </itemizedlist> Each has its own strengths and weaknesses. </para> *************** *** 373,382 **** </sect1> <sect1 id="backup-online"> ! <title>On-line backup and point-in-time recovery (PITR)</title> <indexterm zone="backup"> ! <primary>on-line backup</primary> </indexterm> <indexterm zone="backup"> --- 373,382 ---- </sect1> <sect1 id="backup-online"> ! <title>Continuous backup and point-in-time recovery (PITR)</title> <indexterm zone="backup"> ! <primary>continuous backup</primary> </indexterm> <indexterm zone="backup"> *************** *** 452,458 **** </para> <para> ! To recover successfully using an on-line backup, you need a continuous sequence of archived WAL files that extends back at least as far as the start time of your backup. So to get started, you should set up and test your procedure for archiving WAL files <emphasis>before</> you take your --- 452,458 ---- </para> <para> ! To recover successfully using a continuous backup, you need a continuous sequence of archived WAL files that extends back at least as far as the start time of your backup. So to get started, you should set up and test your procedure for archiving WAL files <emphasis>before</> you take your *************** *** 782,793 **** <function>pg_start_backup</> or <function>pg_stop_backup</>, and you will therefore be left to your own devices to keep track of which backup dump is which and how far back the associated WAL files go. ! It is generally better to follow the on-line backup procedure above. </para> </sect2> <sect2 id="backup-pitr-recovery"> ! <title>Recovering with an On-line Backup</title> <para> Okay, the worst has happened and you need to recover from your backup. --- 782,793 ---- <function>pg_start_backup</> or <function>pg_stop_backup</>, and you will therefore be left to your own devices to keep track of which backup dump is which and how far back the associated WAL files go. ! It is generally better to follow the continuous backup procedure above. </para> </sect2> <sect2 id="backup-pitr-recovery"> ! <title>Recovering with a Continuous Backup</title> <para> Okay, the worst has happened and you need to recover from your backup. *************** *** 1123,1129 **** <title>Caveats</title> <para> ! At this writing, there are several limitations of the on-line backup technique. These will probably be fixed in future releases: <itemizedlist> --- 1123,1129 ---- <title>Caveats</title> <para> ! At this writing, there are several limitations of the continuous backup technique. These will probably be fixed in future releases: <itemizedlist>
---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq