Skip to main content
  • EN

Hi,

I’m using VBR 12.3.1.1139 and have already successfully migrated the configuration database to a local PostgreSQL server (which was installed during the VBR update/setup).

Now I’d like to move from the local db server to a centralized one. Therefore I started the configuration “Restore” process and again chose”migrate”. Typed in hostname, database name, name and password of native authorization. But when clickin on “connect”, I get a dialog (from the db server?) that the connection is refused, the phrase is “no pg_hpa.conf entry for host <hhhh>, user <uuuu>, database <dddd>, SSL off”

The problem seems to be “...database <dddd>...” whereas <dddd> is NOT what I entered into the migration dialog under “database name”. The centralized pg server only permits a certain database for each of their users.

Our pg server tells me that VBR wants to connect to <dddd> where <dddd> is in fact the name of the user VBR is running with!? e.g. “BCKSRV2\horst”.

This way I can’t connect to our pg server. Is this a bug in VBR?

By the way: If I use the psql utility shipped with the local PostgreSQL software, I can easily connect to our centralized pg server, create tables etc. I.e. its configuration is just fine.

Is someone with me and/ or can help?

Many thanks!

This should work but maybe check this community article - https://community.veeam.com/blogs-and-podcasts-57/steps-to-move-veeam-configuration-database-to-postgresql-server-6582

If that does not help then support is the other option.

connection refused is probably because you dont have such vlan allowed to connect to database like

pg_hba.conf:

 

# TYPE DATABASE     USER ADDRESS METHOD

# IPv4 local connections:

host all all 127.0.0.1/32 trust

 

and then is important method of authentication

if you have scram-sha-256 change it to trust

and try

Honestly ​@greenwall  ...unless someone chimes in who’s had a similar issue, I’d get ahold of Support. This either sounds like a bug as you may think, or at the very least, maybe some kind of DB script may need to be run for this to work; and both are really something you should use Veeam Support for as Chris suggested.

Best.

One other thing - if you are using the same VBR server just moving the database you should select the “Restore” option not migrate.  The Migrate one is typically used if you are moving the database to a new VBR server.

But as noted check the CONF files for access as that typically is where things trip up.

Thanks for your quick replies!

​@makacmar : As I can connect from the host that’s running VBR with another tool (pqsl) with the same credentials, I’m pretty sure it has nothing to do with the network.

​@Chris.Childerhose : You’re right, “restore” is the better choice, there one can also edit the destination db server. But anyway the problem stays the same. it looks like VBR tries to connect with the wrong database name.

I’m afraid that eligible PostgreSQL server is managed by another department and tinkering at their configuration is not an option.

I’m thinking about another idea, maybe one can help me here:

What if I manually would copy the database (dump+...) to the new db server. Is there a way to manually change the server configuration of VBR so it will point to/ use the new one? I guess no, as that sounds far too easy.

​@greenwall

No way that I've heard of to do that... 

Thanks for your quick replies!

​@makacmar : As I can connect from the host that’s running VBR with another tool (pqsl) with the same credentials, I’m pretty sure it has nothing to do with the network.

​@Chris.Childerhose : You’re right, “restore” is the better choice, there one can also edit the destination db server. But anyway the problem stays the same. it looks like VBR tries to connect with the wrong database name.

I’m afraid that eligible PostgreSQL server is managed by another department and tinkering at their configuration is not an option.

I’m thinking about another idea, maybe one can help me here:

What if I manually would copy the database (dump+...) to the new db server. Is there a way to manually change the server configuration of VBR so it will point to/ use the new one? I guess no, as that sounds far too easy.

No you cannot do that as you need to use the DB Configuration tool for Veeam to point to the right server, configs, etc.  If you run the DB Configuration tool on the VBR server what is the server name and DB name?

The restore option should create the database if it is not already there so unsure why you are having this issue.  Support would be the next call to get help.

First try to restore to another VM with fresh PostgreSQL, if its working, then issue is with configuration of that DB as you described. Then you can try to create another instance on VM, where you would like to restore DB and restore into it.

I literally just ran into the same issue. A couple things were required:

In pg_hba.conf:

# IPv6 local connections:
host    all             pgadmin        X.X.X.X/32          md5

In postgres.conf:

# - Connection Settings -

listen_addresses = '*'

(x.x.x.x is the VBR server IP, pgadmin is your postgres admin)

 

After this, I was able to connect to the DB.

Nice! ​@greenwall ...try what ​@Tommy O'Shea shared and see if that takes care of it. Let us know!

Comment


Terms & Conditions