Aiven-Open / Aiven-Open/pghoard

Discussion - restore backup using remote daemon

Offen
#203 2 Kommentare 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Python
Sterne
1.4k
Forks
111
Ø Merge
1 T. 5 Std.
Gemergte PRs (30 T.)
2

Beschreibung

I'm a little bit confused on how to best implement `pghoard` when it comes to managing multiple db servers. After playing around with local backups and restoring them to the same machine they were taken on, I then moved on to working on an environment that more closely matches our current setup.

Right now I have three AWS EC2 servers:
- Master Database
- Slave Database
- Dedicated PGHoard Server

I thought it would make sense to have a server dedicated to running the `pghoard` daemon taking basebackups and archiving WAL files with `pg_receivexlog`, but I then tried to spin up a new database server and restore from a basebackup and discovered that the `pghoard` webserver doesn't transfer WAL files remotely.

I'm curious to know how other people are implementing `pghoard`? When I restore, should I just start a local `pghoard` daemon and add a maintenance file so no backups are taken while I'm restoring? Is there a way to have a single remote `pghoard` daemon?

Thanks in advance.

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.