Question 3 What could be the issue.


Userlevel 7
Badge +22

This question comes from a suggestion from Community Hub superstar code named Member of Parliament?  Who can that be? double clue in the code name. 

 

Dynamic Dan is keen to leverage new features in Veeam. At present he has 10 VBR servers over in 10 different locations all connected by the fast corporate VPN. For convenience sake he leverages Enterprise Manager to provide at a glance access to all of his VBR servers and RBAC capabilities. 2 weeks ago his company for the first time in 4 years acquired a new location and Dan was quick to install a new VBR server. However, when back at the head office he is having issues adding this VBR server to VEM. What could be the problem?


8 comments

Userlevel 7
Badge +20

If he enabled MFA there is an issue adding servers to VEM and it is required to be disabled to add then enabled after connection to VEM.  😁

Userlevel 4
Badge +2

or, the VBR version is newer/higher than the VEM server version.

Userlevel 7
Badge +20

or, the VBR version is newer/higher than the VEM server version.

Ah yes forgot about the obvious one.  Good call there. 👍🏼

Userlevel 4
Badge +2

or, the VBR version is newer/higher than the VEM server version.

Ah yes forgot about the obvious one.  Good call there. 👍🏼

The pitfall of being an expert, forgetting the obvious 🤣

Userlevel 7
Badge +22

Hint.. database

Userlevel 7
Badge +22

@MicoolPaul 

We may need your genius here :) 

Userlevel 7
Badge +20

Ah yes SQL cannot support Postgres and vice versa so the new one is PG and the VEM is SQL.

Userlevel 7
Badge +20

Hi everyone!

 

So the conversation point that this question focuses on is that VBEM can only manage VBR’s that utilise the same database type as itself. So if your VBEM & existing VBR fleet was SQL Server and then you went to adopt a new VBR server with Postgres, you won’t be able to manage it in VBEM.

 

Also, a key thing to call out here is that, whilst you have the ability to migrate your VBR server between SQL Server and Postgres, with VBEM this is a one way street! You can migrate to Postgres but you can’t migrate back afterwards! So if you start deploying VBR with Postgres you can migrate the VBR over to SQL Server if you’ve got a VBEM with SQL Server, but if your VBEM is using Postgres, all your VBRs will need Postgres, or you’ll need to deploy a new VBEM with SQL Server.

Comment