Aiven-Open / Aiven-Open/pghoard

Discussion - restore backup using remote daemon

Abierto
#203 2 comentarios 5 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Python
Estrellas
1.4k
Forks
111
Merge medio
1 d 5 h
PR fusionados (30 d)
2

Descripción

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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.