Re: Best backup strategy for production systems
| От | Borislav Ivanov |
|---|---|
| Тема | Re: Best backup strategy for production systems |
| Дата | |
| Msg-id | CAEqRsYVyAOvKP94PTRfxTsmK0mKmuTzusqvx6s6fbvCP5PEEyA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Best backup strategy for production systems (John R Pierce <pierce@hogranch.com>) |
| Ответы |
Re: Best backup strategy for production systems
|
| Список | pgsql-general |
If your database is relatively small, I would recommend http://www.pgbarman.org/. It does binary backup and will take care of your WAL files. The laster version of pgbarman can also take backups from a slave using pgespresso extension. Note that pgbarman runs over streaming replication protocol.
If your database is big, go for pg_basebackup and archive_command. You can run this on a slave. The pg_basebackup will give you the base and during restore you can use restore_command with recovery_target_time for example to replay from the archived WAL files.
On 19 June 2014 11:28, John R Pierce <pierce@hogranch.com> wrote:
you need ALL the archived WAL files since the start of the last base backup, or none of them are useful.On 6/19/2014 3:14 AM, Oliver wrote:About wal files and archiving of them, I must delete both manually, isn't it? There isn't any option for automatically delete wal files with a given age in the postgresql.conf, isn't it? (Away of archive_command). Do you use Linux? Could you pass me your archive_command or script that you use for copying/gzipping the files?Thanks beforehand.-- john r pierce 37N 122W somewhere on the middle of the left coast
В списке pgsql-general по дате отправления: