We decided to test PostgreSQL logs backup and got it working. But when we tried to restore it then it was not successful. I opened the case with support, Case #07584277, and it's open and seems to be even escalated but decided to ask here if someone had similar experience. Every time we start restore it does it's things, mounts file system, stops original instance, uploads log files and then always stops with error - Failed to start PostgreSQL service: /usr/lib/postgresql/16/bin/pg_ctl (options: -c config_file='/tmp/Veeam.Mount.FS.b4146ca4-4dfd-4915-9569-4445fd21300b/postgres-server-flat.vmdk_0/etc/postgresql/16/main/postgresql.conf' -c listen_addresses='' -c unix_socket_directories='/var/tmp/VePgSockets/6c52a3f217b9413bb9d04c8c8b903bed').
There seems to be no other helpful information in log files. As PostgreSQL log files backup and database restore is been available quite some times then I guess restore works usually. But not for us as it seems.
-
- Expert
- Posts: 108
- Liked: 14 times
- Joined: Jun 12, 2014 11:01 am
- Full Name: Markko Meriniit
- Contact:
-
- Veeam Software
- Posts: 3820
- Liked: 643 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: PostgreSQL database restore fails
Hi Markko,
I believe you should continue working with our support team to identify the root cause of this issue. In the meantime, you may also check the required permissions.
Thanks!
I believe you should continue working with our support team to identify the root cause of this issue. In the meantime, you may also check the required permissions.
Thanks!
-
- Expert
- Posts: 108
- Liked: 14 times
- Joined: Jun 12, 2014 11:01 am
- Full Name: Markko Meriniit
- Contact:
Re: PostgreSQL database restore fails
It took time but the problem at the end was not reading/understanding required articles like https://helpcenter.veeam.com/docs/backu ... ml?ver=120 . Veeam backs up PostgreSQL without problems but VEP doesn't support sub configuration files which are included with include clause in main configuration file. So when it restores it gets wrong configuration file and PostgreSQL doesn't like that and won't start. That was my understanding. That was in case when restoring with "Restore instance". Instant recovery still didn't work even without sub-conf files but as it's not needed right now then we didn't pursue this issue further.
Who is online
Users browsing this forum: No registered users and 1 guest