Hi,
I try to add VBR server to Veeam EM, there is no problem. But sessions tab I see “Database Replication” failed.
And the logs like that;
“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”
VBR build is 12.1.0.2131, is not community license, and db is postgre.
Thanks,
+7
Hi
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,
+17
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.
+20
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.
+17
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.
+20
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.
+20
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. 👍🏼
Daniel
+17
Hi
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.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
