Skip to main content
  • EN

I did a research for consistent PostgreSQL backups with Kasten K10 and found:

https://docs.kasten.io/latest/kanister/postgresql/install_app_cons.html

Application Consistent PostgreSQL Backup

You described there to use a Kanister pre-hook (“pg_start_backup”) and post-hook (“pg_stop_backup”).

 

Afaik, that alone will not create a consistent backup. You also need any generated archived WAL file between. Archiving must be enabled (archive_mode=on), archived WAL files must be backuped too, therefore.

 

I did not find anything about how to backup archived WAL files. How will you handle them?

 

Thanks, Markus

@jaiganeshjk 

M.Z, Thank you for opening this topic.

The blueprint that you see in our documentation is just a sample and it can be taken as a baseline and developed further. 
It is just an example on how to run sql commands against your database. You can add more steps/checks as per your requirement in your environment.

Below is what we say in the documentation as well https://docs.kasten.io/latest/kanister/postgresql/install_app_cons.html

The PostgreSQL backup example provided above serves as a blueprint template for achieving application-consistent backups. Please note that these examples may need to be modified for specific production environments and setups. As a result, it is highly recommended to carefully review and modify the blueprints as needed before deploying them for production use.

Comment


Terms & Conditions