The Scriptįirst, we looked at what the command for a PostgresSQL dump looks like and created a simple shell script on top of it. For such a project, the pre- and post-thaw script routine in Veeam is ideally suited. Our goal was to keep a consistent dump of the PostgreSQL databases on the same system during the Veeam backup, so that it backed up during the image-level backup. If only one database is affected by a failure this can be very cumbersome. In principle, it would be possible to restore the entire system each time. This makes a granular db restore difficult afterwards. Basically the agent also only creates a write-ahead checkpoint of the database. Consequently, no SureBackup functionalities are available. But the problem is that we have to work with an agent in the virtual machine. Basically, Veeam has been offering PostgreSQL integration with the Agent for Linux for quite some time. In the current situation, however, the customer wanted to ensure a consistent backup of the database via Veeam. So usually regular dumps are written away via the native database tools. Most database administrators in the past had their own backup routines for PostgreSQL and wanted to stick with it. From my experience, I have rarely had requests for this specific topic in the past. Recently, one of my customers had a request to perform a PostgreSQL backup with Veeam, consistently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |