From 014c1cd4e5160e2383927e74970a4e0d794584a1 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Fri, 15 Jan 2021 13:27:41 +0100 Subject: include overview picture --- replication.png | Bin 0 -> 46376 bytes replication.svg | 427 +++++++++++++++++++++++++++++++++++++++++++++++ taler-auditor-manual.rst | 5 +- 3 files changed, 431 insertions(+), 1 deletion(-) create mode 100644 replication.png create mode 100644 replication.svg diff --git a/replication.png b/replication.png new file mode 100644 index 00000000..855237fc Binary files /dev/null and b/replication.png differ diff --git a/replication.svg b/replication.svg new file mode 100644 index 00000000..4a9eff34 --- /dev/null +++ b/replication.svg @@ -0,0 +1,427 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + image/svg+xml + + + + + + + + + + + Exchange production DB + + + + + + Exchange hotspare DB + + + + + + Exchange ingres DB + + + + + + Exchange "safe" DB + + + + + + Auditor internal DB + + Postgres replication + Postgres replication + taler-auditor-sync + taler-auditor-httpd + + taler-auditor + + + taler-exchange-httpd + + + + + + + + + + + + + + diff --git a/taler-auditor-manual.rst b/taler-auditor-manual.rst index adfb57a7..66e3d05d 100644 --- a/taler-auditor-manual.rst +++ b/taler-auditor-manual.rst @@ -438,7 +438,10 @@ Database -------- The next key step for the auditor is to configure replication of the -*exchange*'s database in-house. This should be performed in two steps. +*exchange*'s database in-house. This should be performed in two steps +as illustrated in the following figure: + +.. image:: replication.png First, the exchange should use standard Postgres replication features to enable the auditor to obtain a full copy of the exchange's database. -- cgit v1.2.3