Hi,
I'm trying to enable application-aware processing to perform PostgreSQL backups. One server worked really well, and I can successfully restore application items. However, the other server is experiencing an issue:
"26.09.2024 11:46:14 :: Failed to explore PostgreSQL instance SERVER-PSQL:5432: Command explore_instance completed with error: Invalid connection parameters were provided to PostgreSQL server on port 5432."
I am not the administrator of the PostgreSQL server, but they say they can't identify any problems, and neither can I. Could you help me? Does anything come to mind that could be causing this issue?
Thank you in advance
-
- Novice
- Posts: 5
- Liked: 3 times
- Joined: Jun 06, 2024 8:40 am
- Contact:
-
- Veeam Software
- Posts: 2593
- Liked: 606 times
- Joined: Jun 28, 2016 12:12 pm
- Contact:
Re: Veeam - Failed to explore PostgreSQL
Hi Noparator,
Sorry to hear about the troubles, but at first blush sounds like a pretty standard connection issue.
We won't be able to troubleshoot over the forums, so open a Support case as noted when creating a topic and let's allow Veeam Support to review the situation. Be sure to include logs for Support to review, they should be able to help point out why you're getting the connection error here.
Please share your case number once you've opened a case.
Thanks!
Sorry to hear about the troubles, but at first blush sounds like a pretty standard connection issue.
We won't be able to troubleshoot over the forums, so open a Support case as noted when creating a topic and let's allow Veeam Support to review the situation. Be sure to include logs for Support to review, they should be able to help point out why you're getting the connection error here.
Please share your case number once you've opened a case.
Thanks!
David Domask | Product Management: Principal Analyst
-
- Novice
- Posts: 5
- Liked: 3 times
- Joined: Jun 06, 2024 8:40 am
- Contact:
Re: Veeam - Failed to explore PostgreSQL
So I created a ticket; however, in the meantime, my colleagues and I had another meeting where we tried a few things regarding the database. It turned out that the issue was caused by an incorrect password. Although the password had been changed about three times over the course of the few weeks while we were resolving the issue, it seems there was a mistake on one side.
Who is online
Users browsing this forum: No registered users and 3 guests