Hi @oktay 

Welcome to the Community!

Is this a new install of Veeam Enterprise Manager? Is VEM using MSSQL?

Hi,

Thanks for your response.

VBR is using PostgreSQL, and Veeam EM is using PostgreSQL, too. Yes, Veeam EM is new installation on same server with VBR. 

And also I checked VBR and Veeam EM DB connection  succeed. (https://helpcenter.veeam.com/docs/backup/em/dbconfig_launch.html?ver=120)

Thanks,

Do you have any jobs running in VBR? I wonder if the config db is locked at the moment because of jobs/tasks running? Maybe those errors will clear out?

At the very least, you could open a SR with Veeam Support and they can confirm, or provide a solution.

I was about to ask as well if jobs are running on the server causing the message that you see?  Also it seems that having Postgres on its own server seems to help more versus all on the same server as VEM and VBR.

https://forums.veeam.com/tape-f29/posgresql-the-sql-server-machine-hosting-the-configuration-database-is-currently-unavailable-t86270.html

Yeah...I was curious about running EM on the same server myself, but saw in the Guide and a few Forums post it’s supported, and can run fine. Personally, I’d run it on a different server, but with a physical server in play...may be best to run on 1? Depending on goals/constraints, etc. I’d create 2 VMs for VBR & EM. That being said..EM “should” run ok on same server as VBR, assuming the resources are sufficient. @oktay , I assume you have adequate resources (CPU/Memory/Disk) on your server? Reference the VBR and EM Guides for minimum requirements.

Yeah, running VEM/VBR on same server is fine as we do it on most, but it is the DB itself whether SQL or Postgres that is best on its own server versus the same server as Veeam.  With Veeam driving everything and constantly updating the DB having Postgres moved to a separate server might help here, but ensure no jobs are running.

Thank you all for your responses. I will open SR.

Thanks.

Keep us posted on what they say and if there is a fix to help others here in the community.  

@oktay since v12 and v12.1 you need the “new” port 9405 for certificate communication between vbr and em.. maybe you can check this also.

Daniel

Hi @oktay -

Did you open a SR with Veeam? Did Support get your error resolved? Can you post what they did to get you working?

Thank you.

Not the same problem but we recently had the same error message in our environment.
The cause was our antivirus solution (Kaspersky Endpoint Security), which blocked data and processes of the PostgreSQL database. 

As a result, the Veeam backup services kept losing the connection to the database. This led to various errors in the backup jobs and a Veeam Console that constantly lost the connection to the backup server or did not even establish it.

After changing the Kaspersky security policy by adding the path %ProgramFiles%\PostgreSQL\ to the trusted zone and allowing the execution of PostgreSQL processes, the errors were fixed.

Maybe this will help in your case

I would advise close this thread since the message itself is specific to the environment [0,1]

“The SQL Server machine hosting the configuration database is currently unavailable. Possible reasons are a network connectivity issue, server reboot, heavy load or hot backup.
Please try again later.

Error:
relation "licensing.cc.ınstancestobackupslinks" does not exist”

That’s being returned by the SQL engine and it’s discussing that there is a broken relation in the Configuration Database, it’s unclear why. For any SQL Exceptions like this besides very clear messages regarding like lack of space/permissions, like a Veeam Support Case is best as usually some investigation will be required for both root cause analysis and remediation. While some workarounds (Configuration Database Restore, reinstall) _might_ help in some situations, this is pretty time-consuming for “hoping it works” and also will likely hide the root cause, so it’s best to start with a Support Case.

Citations:

0 - Me

1 - Thousands of cases :)

@oktay 

Have you tried to upgrade your VBR/VEM to 12.1.2.172 build?  I see you are on a 12.0 build still.  Not sure that this will resolve the issue but it will update the database.  I will not say that it will fix it but you never know.