Any way to restore VBR install to MS SQL from Postgresql

[squebel]

Yeah, this is a weird one but hear me out...

We did an install of VBR v12 and used the postgresql default db option. Everything was good until we went to join it to Enterprise Manager. We then got an ugly message about nothing being able to connect a Postgresql instance of VBR to Enterprise Manager using MS SQL. First off... really?! I found the info regarding this buried in some KB articles but I would have never thought this would pop up. Pretty silly this wasn't accounted for. Anyways...

So my question is: can I somehow convert or reinstall or restore from config backup of the postgresql VBR database into a MS SQL instance or am I stuck doing a fresh install of VBR and recreating my jobs and importing backups?

I have opened a ticket (06351488) on this and the tech suggested trying restore from the config backup into MS SQL but I don't want to even bother trying if the people here know it won't work.

[Mildur]

Hello Squebel

Yes, VBR and Enterprise Manager must use the same database type.

For VBR you can simply export a configuration backup and use the configuration restore wizard to restore it to a MSSQL server: https://helpcenter.veeam.com/docs/backu ... ml?ver=120

May I ask, is there a reason why you cannot migrate Enterprise Manager database to PostgreSQL?
Please note, for Enterprise Manager it's a "one way" migration to PostgreSQL.

Best,
Fabian

[squebel]

Fabian, thanks for your response! I will try this. I assume this only works restoring into MSSQL and won't work the other way around for MSSQL > Postgresql?

We have 18 VBR environments (all on MSSQL) pointed to one VEM and we rely heavily on VEM as the central point for data collection, reporting, and our internal support services. If we migrated VEM to postgresql, we'd have to turn around and immediately migrate all the VBR instances to postgresql. That's not going to be an easy task.

[Mildur]

For VBR you can use configuration backup and restore to switch the database type in both directions (MSSQL <> PostgreSQL).

We have 18 VBR environments (all on MSSQL) pointed to one VEM and we rely heavily on VEM as the central point for data collection, reporting, and our internal support services. If we migrated VEM to postgresql, we'd have to turn around and immediately migrate all the VBR instances to postgresql. That's not going to be an easy task.

Thank you. Yes, makes sense to migrate VBR database to MSSQL in that case.

Best,
Fabian