Comprehensive data protection for all workloads
Post Reply
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Veeam VBR Migration

Post by fspadaro »

Hi to all,

I need to migrate a VBR to another server. My environment is:

Production server (source)
VBR Server OS: Windows Server 2012 R2
VBR Server: 11.0.1.1261
VBR Database: MSSQL 2014 on external istance

New server (target)
VBR Server OS: Windows Server 2022
VBR Server: 12.0.0.1420
VBR Database: Postgres Embedded

Change ip on target new server with old source server (It's due to many issue with firewall rules)

Note: there's also Entrerprise Manager that must migrate as above and before (but for this I think I need to open another topic)

Thanks for all.
Mildur
Product Manager
Posts: 8642
Liked: 2270 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam VBR Migration

Post by Mildur » 1 person likes this post

Hi Federico

You cannot migrate a V11 configuration backup to a V12 backup server with PostgreSQL.

Backup Server
1) First update the source and target server to V12 cumulative patch 2 (12.0.0.1420 P20230412)
2) Then use configuration backup and restore to restore the entire configuration to the new server --> https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Enterprise Manager
Enterprise Manager must run with the same database type as your VBR server. I recommend:
1) Migrate only Enterprise Manager software to the new server and still keep the old database. --> https://www.veeam.com/kb1889 (Migrate the Backup Enterprise Manager software, but keep the configuration database in place.)
2) Migrate Enterprise Manager database to PostgreSQL: https://www.veeam.com/kb4409

You can change the IP address after the migration.

Best,
Fabian
Product Management Analyst @ Veeam Software
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Re: Veeam VBR Migration

Post by fspadaro »

Thanks Fabian,

so the correct sequence it would be:

1) Migrate on old infrastructure before Enterprise and after Backup server to V12 (inplace)
2) Migrate Enterprise Manager from old server 2012 to new server 2022 keeping external MSSQL database
3) Migrate Enterprise Manager database from MSSQL to Postgres
a) on this step there is a losing of VBR server because it's still on MSSQL
4) Install VBR Server V12 with postgres database on server 2022 and migrate configuration from old VBR
5) Reactivate Enterprise Manager Keyset
6) Change IP on all new servers 2022
7) Upgrade all proxy, agent, ecc..

Correct?

Regards
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Re: Veeam VBR Migration

Post by fspadaro »

Mildur wrote: May 12, 2023 8:26 am Hi Federico

You cannot migrate a V11 configuration backup to a V12 backup server with PostgreSQL.

Backup Server
1) First update the source and target server to V12 cumulative patch 2 (12.0.0.1420 P20230412)
2) Then use configuration backup and restore to restore the entire configuration to the new server --> https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Enterprise Manager
Enterprise Manager must run with the same database type as your VBR server. I recommend:
1) Migrate only Enterprise Manager software to the new server and still keep the old database. --> https://www.veeam.com/kb1889 (Migrate the Backup Enterprise Manager software, but keep the configuration database in place.)
2) Migrate Enterprise Manager database to PostgreSQL: https://www.veeam.com/kb4409

You can change the IP address after the migration.

Best,
Fabian
@Mildur
On my environment I'm using an AD service account and I want to use on the new servers.

I'm on this step of migration:

1- Install Enterprise Manager on new server 2022
2- backup sql db from old server
3- Veeam.EM.DB.Migration.exe /file:"c:\DB\v12sqlDB.emco" /backupemdatabase /encryptionpassword:Password /encryptionhint:DBpwd
4- Copy DB on new server
5- Shutdown source
6- Change IP and wait DNS replication
7- restore on the postgres instance in the new server 2022
8- Veeam.EM.DB.Migration.exe /file:"c:\DB\v12sqlDB.emco" /restoreemdatabase /encryptionpassword:Password /servername:localhost /initialcatalog:VeeamBackupReporting /serverport:5432 /login:domain/serviceaccount /password:


When I try to restore from a backup I'm receiving the following error:

"veeam Failed to connect to PostgreSQL server localhost:5432. GSS/SSPI authentication but IntegratedSecurity not enabled"

If on the command I remove the user information the restore work fine but on Enterprise Web I cannot find any data of restore.
I'm using this guide "https://www.veeam.com/kb4409".

Any ideas?

Regards
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Re: Veeam VBR Migration

Post by fspadaro »

Nothing to do. Enteprise manager won't to start when I change to DB connection to new restore DB (Postgres). Following the sequence steps:

1) Upgrade Enterprise Manager to v12
2) Upgrade VBR to v12
3) Backup Enterprise Manager
-Export all Keysets from the old Backup Enterprise Manager web console. Take note of which keyset was Active
-backup sql db from old server (https://www.veeam.com/kb4409)or(https://helpcenter.veeam.com/docs/backu ... ml?ver=120)
-Veeam.EM.DB.Migration.exe /file:"c:\Licenza\v12sqlDB.emco" /backupemdatabase /encryptionpassword:pwd123 /encryptionhint:DBpwd /verbose
-Copy everything on new server
4) Migrate VBR DB to Postgres
-stop all job on source VBR
-backup configuration and copy to new server
-Shutdown source
-rename e change ip
-install VBR
-migrate configuration
-check Job works
5) Migration Enterprise Manager to new server 2022 (ref. https://www.veeam.com/kb1889)
-Shutdown source
-rename e change ip
-Install Enterprise Manager on new server 2022
-restore on the postgres instance in the new server 2022
-Veeam.EM.DB.Migration.exe /file:"c:\Licenza\v12sqlDB.emco" /restoreemdatabase /encryptionpassword:pwd123 /servername:localhost /initialcatalog:VeeamBackupReporting /serverport:5432 /login:postgres /password:pwd123 /verbose
-repoint DB

To repoint I use the utility Veeam.Backup.DBConfig.exe and point to the new DB (generally "VeeamBackupReporting_00") but the service try to start and go in time-out.

Regards
Mildur
Product Manager
Posts: 8642
Liked: 2270 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam VBR Migration

Post by Mildur »

Hi Federico
“veeam Failed to connect to PostgreSQL server localhost:5432. GSS/SSPI authentication but IntegratedSecurity not enabled"
That error means, your backup server is not allowed to connect to the PostgreSQL server. You must check the PostgreSQL pg_hba.conf configuration.

If you have a PostgreSQL server on windows, you can find the file here:
C:\Program Files\PostgreSQL\15\data\pg_hba.conf

With that configuration file, you tell your PostgreSQL server on how a PostgreSQL client can connect.

If you face issues with the documented migration process, please consider to open a case with our customer support.

Best,
Fabian
Product Management Analyst @ Veeam Software
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Re: Veeam VBR Migration

Post by fspadaro »

Thanks Mildur,

I got around the SSPI problem by setting up local authentication and not the one with AD users.

I cannot open a customer support because I'm replicating in lab a migration for a customer to analyze all steps, I can't create a problem to my customer, I thing to leave SQL Instance, because on postgres db there aren't a lot of case study
bct44
Veeam Software
Posts: 110
Liked: 29 times
Joined: Jul 28, 2022 12:57 pm
Contact:

Re: Veeam VBR Migration

Post by bct44 »

@mildur how do you handle some specific registry keys for Veeam in your migration procedure?
Mildur
Product Manager
Posts: 8642
Liked: 2270 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam VBR Migration

Post by Mildur »

Such keys are not migrated.
If you have specific keys and they are still required, they must be manually migrated.

But before I would check with support if those keys are still required or useful in the new version. Especially if you don‘t have created a documentation about the non-default registry keys.

Best,
Fabian
Product Management Analyst @ Veeam Software
dpal
Novice
Posts: 4
Liked: never
Joined: Feb 15, 2017 2:01 pm
Contact:

Re: Veeam VBR Migration

Post by dpal »

Hi all,
one quick question, as I will be doing a similar migration very soon. Why not migrate VBR 11 from Win-2012 to target Windows20xx first and then perform an in-place upgrade on VBR to 12?
Mildur
Product Manager
Posts: 8642
Liked: 2270 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Veeam VBR Migration

Post by Mildur »

Hello dpal

This is also supported.

Best,
Fabian
Product Management Analyst @ Veeam Software
fspadaro
Influencer
Posts: 10
Liked: never
Joined: Jun 23, 2022 2:14 pm
Full Name: Federico Spadaro
Contact:

Re: Veeam VBR Migration

Post by fspadaro »

As Mildur reply it's also supported.

Remember, if you want to migrate from 2012R2 to 2022 you need 3 hops before target (with all relative snapshot to roll-back) and on 2022 there are a lot of change; on upgrade in place fo Enterprise Manager, that required different framework version, I have found a lot of problems.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 86 guests