... | ... | @@ -649,8 +649,8 @@ it isn't available in Debian. |
|
|
|
|
|
<a name="direct-restore-procedures" />
|
|
|
|
|
|
Reminder: this procedure **streams** the files from the backup server
|
|
|
to the database server and restore directly. See the [disaster
|
|
|
Note: this procedure **streams** the files from the backup server to
|
|
|
the database server and restore directly. See the [disaster
|
|
|
recovery](#disaster-recovery) section for a more in-depth discussion on the recovery
|
|
|
systems.
|
|
|
|
... | ... | @@ -986,8 +986,13 @@ The correct way to recover here is to issue a `pg_promote` statement: |
|
|
|
|
|
<a name="indirect-restore-procedures" />
|
|
|
|
|
|
Reminder: this procedure **copies** the backup files from the backup
|
|
|
server to the database server and restores from those.
|
|
|
Note: this procedure **copies** the backup files from the backup
|
|
|
server to the database server and restores from those. It is a
|
|
|
slightly simpler procedure than the [direct backup recovery](#direct-backup-recovery)
|
|
|
procedure, see the [disaster recovery](#disaster-recovery) section for a discussion on
|
|
|
the two procedure.
|
|
|
|
|
|
You should more likely use the [direct backup recovery](#direct-backup-recovery).
|
|
|
|
|
|
1. First, you will need to give the backup server access to the new
|
|
|
postgresql server, which we'll call the "client" for now. First,
|
... | ... | |