3 ms·

Yeah. Probably going to need to add a bunch more error catching and handling-of-specific-situations. Edge cases being a thing and all. :)

westurner 3y ago
Chapter 26. Backup and Restore: https://www.postgresql.org/docs/current/backup.html https://www.postgresql.org/docs/current/backup.html Chapter 26. Backup and Restore > 26.3. Continuous Archiving and Point-in-Time Recovery (PITR) > 26.3.4. Recovering Using a Continuous Archive Backup: https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-PITR-RECOVERY https://www.postgresql.org/docs/current/continuous-archiving... IIRC there are fancier ways than pg_dump to do Postgres backups that aren't postgres native PITR? gh topic postgresql-backup: https://github.com/topics/postgresql-backup https://github.com/topics/postgresql-backup - pgsql-backup.sh: https://github.com/fukawi2/pgsql-backup/blob/develop/src/pgsql-backup.sh https://github.com/fukawi2/pgsql-backup/blob/develop/src/pgs... - https://github.com/SadeghHayeri/pgkit#backup https://github.com/SadeghHayeri/pgkit#backup https://github.com/SadeghHayeri/pgkit/blob/main/pgkit/cli/commands/pitr.py https://github.com/SadeghHayeri/pgkit/blob/main/pgkit/cli/co... : $ sudo pgkit pitr backup <name> <delay> > Recover: This command is used to recover a delayed replica to a specified point in time between now and the database's delay amount. The time can be given in the YYYY-mm-ddTHH:MM format. The latest keyword can also be used to recover the database up to the latest transaction available.: $ sudo pgkit pitr recover <name> <time> $ sudo pgkit pitr recover <name> latest > The database will then start replaying the WAL files. It's progress can be tracked through the log files at /var/log/postgresql/. - "PostgreSQL-Disaster-Recovery-With-Barman" https://github.com/softwarebrahma/PostgreSQL-Disaster-Recovery-With-Barman https://github.com/softwarebrahma/PostgreSQL-Disaster-Recove... : > The solution architecture chosen here is a 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features. Glossary of backup terms: https://en.wikipedia.org/wiki/Glossary_of_backup_terms https://en.wikipedia.org/wiki/Glossary_of_backup_terms Continuous Data Protection > Continuous vs near continuous: https://en.wikipedia.org/wiki/Continuous_Data_Protection#Continuous_vs_near_continuous https://en.wikipedia.org/wiki/Continuous_Data_Protection#Con...
- justinclift 3y ago
  Thanks. I hadn't come across pgkit before. :)

westurner 3y ago

Chapter 26. Backup and Restore: https://www.postgresql.org/docs/current/backup.html https://www.postgresql.org/docs/current/backup.html Chapter 26. Backup and Restore > 26.3. Continuous Archiving and Point-in-Time Recovery (PITR) > 26.3.4. Recovering Using a Continuous Archive Backup: https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-PITR-RECOVERY https://www.postgresql.org/docs/current/continuous-archiving... IIRC there are fancier ways than pg_dump to do Postgres backups that aren't postgres native PITR? gh topic postgresql-backup: https://github.com/topics/postgresql-backup https://github.com/topics/postgresql-backup - pgsql-backup.sh: https://github.com/fukawi2/pgsql-backup/blob/develop/src/pgsql-backup.sh https://github.com/fukawi2/pgsql-backup/blob/develop/src/pgs... - https://github.com/SadeghHayeri/pgkit#backup https://github.com/SadeghHayeri/pgkit#backup https://github.com/SadeghHayeri/pgkit/blob/main/pgkit/cli/commands/pitr.py https://github.com/SadeghHayeri/pgkit/blob/main/pgkit/cli/co... : $ sudo pgkit pitr backup <name> <delay> > Recover: This command is used to recover a delayed replica to a specified point in time between now and the database's delay amount. The time can be given in the YYYY-mm-ddTHH:MM format. The latest keyword can also be used to recover the database up to the latest transaction available.: $ sudo pgkit pitr recover <name> <time> $ sudo pgkit pitr recover <name> latest > The database will then start replaying the WAL files. It's progress can be tracked through the log files at /var/log/postgresql/. - "PostgreSQL-Disaster-Recovery-With-Barman" https://github.com/softwarebrahma/PostgreSQL-Disaster-Recovery-With-Barman https://github.com/softwarebrahma/PostgreSQL-Disaster-Recove... : > The solution architecture chosen here is a 'Traditional backup with WAL streaming' architecture implementation (Backup via rsync/SSH + WAL streaming). This is chosen as it provides incremental backup/restore & a bunch of other features. Glossary of backup terms: https://en.wikipedia.org/wiki/Glossary_of_backup_terms https://en.wikipedia.org/wiki/Glossary_of_backup_terms Continuous Data Protection > Continuous vs near continuous: https://en.wikipedia.org/wiki/Continuous_Data_Protection#Continuous_vs_near_continuous https://en.wikipedia.org/wiki/Continuous_Data_Protection#Con...

justinclift 3y ago
Thanks. I hadn't come across pgkit before. :)