mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
doc: update links to Barman documentation
This commit is contained in:
@@ -205,7 +205,7 @@
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
&repmgr; supports standbys cloned by another method (e.g. using <application>barman</application>'s
|
&repmgr; supports standbys cloned by another method (e.g. using <application>barman</application>'s
|
||||||
<command><ulink url="http://docs.pgbarman.org/release/2.5/#recover">barman recover</ulink></command> command).
|
<command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command> command).
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
To integrate the standby as a &repmgr; node, once the standby has been cloned,
|
To integrate the standby as a &repmgr; node, once the standby has been cloned,
|
||||||
|
|||||||
@@ -108,7 +108,8 @@
|
|||||||
<title>Registering a node not cloned by repmgr</title>
|
<title>Registering a node not cloned by repmgr</title>
|
||||||
<para>
|
<para>
|
||||||
If you've cloned a standby using another method (e.g. <application>barman</application>'s
|
If you've cloned a standby using another method (e.g. <application>barman</application>'s
|
||||||
<command>barman recover</command> command), register the node as detailed in section
|
<command><ulink url="https://docs.pgbarman.org/#recover">barman recover</ulink></command>
|
||||||
|
command), register the node as detailed in section
|
||||||
<xref linkend="repmgr-standby-register-inactive-node"/> then execute
|
<xref linkend="repmgr-standby-register-inactive-node"/> then execute
|
||||||
<link linkend="repmgr-standby-create-recovery-conf">repmgr standby clone --recovery-conf-only</link>
|
<link linkend="repmgr-standby-create-recovery-conf">repmgr standby clone --recovery-conf-only</link>
|
||||||
to generate the appropriate replication configuration.
|
to generate the appropriate replication configuration.
|
||||||
|
|||||||
Reference in New Issue
Block a user