My notes and steps for Migrating to Veeam Backup Appliance

[unsichtbarre]

Here are my notes on migrating to the VBR VSA. i apologize for the rudimentary formatting, forum does not allow formatted text paste.

1. Install VBR VSA
1.a. 2 disks, 240GB each, cache=none
1.b. UEFI
1.c. 8 vCPU
1.d. 16GB vRAM (32GB better)
2. License VBR VSA
3. Update VBR VSA
4. Stop and Disable all Jobs on VBR Windows
5. Manually Create an encrypted Configuration Backup on VBR Windows
6. Update VBR Windows, not past 13.0.X
7. At this point I like to open the VBR Console pointed to the VBR Windows instance and verify configuration and remote components updated.
8. Download log files (component: VBR Server only, last 1 days) from both VBR Windows source and VBR VSA
9. Upload logs to Veeam Support for Key generation
10. Manually Create an encrypted Configuration Backup on VBR Windows

--STOP-- NOTE: I was directed by Veeam Support to upgrade the PostgreSQL DB on VBR Windows prior to migration due to failures. In a subsequent migration this was not required per: viewtopic.php?p=573855#p573855 I suggest trying the migration and updating the Windows DB only after failures and/or contacting support

11. Upgrade VBR Windows PostgreSQL to postgresql-17.10-1-windows-x64 (found on the VBR Windows ISO - VeeamBackup&Replication_13.0.2.29_20260522 D:\Redistr\x64\PostgreSQL\17.10-1)
11.a. Manually Create an encrypted Configuration Backup on VBR Windows
11.b. Stop all Veeam-related services on the Veeam Backup Server
11.b.1. PS: Get-Service Veeam* | Stop-Service -Force
11.c. Install postgresql-17.10-1-windows-x64
11.d. On VBR Windows Run Veeam Configuration Restore in Migrate Mode pointing at the postgresql-17.10-1 database
11.e. If DB upgrade required, Manually Create an encrypted Configuration Backup on VBR Windows

--RESUME--
12. Stop and disable all VBR Windows services
12.a. PowerShell script in: https://www.veeam.com/kb4800
13. Log in to the VBR VSA Host Management: https://<URL>:10443
13.a. Backup Infrastructure > Configuration Restore > Start Configuration Restore > Migrate
13.b. Point at most recent encrypted Configuration Backup
13.c. Point at source VBR Windows
13.d. Apply key from Veeam Support
13.e. Start migration

NOTES:
• Before starting, we created a network share repo specifically for the VBR configuration backup. Not only does this let us backup the VBR configuration backup (you can’t backup “Default Backup Repository”) but it provides easy access to the configuration backup over a network path.
• We have found the MFA component for the VBR VSA to be problematic, sometimes requiring 3-5 or more key entries before successful authentication.
• We have chosen to run the VBR VSA off any domain and using generic DNS + hosts files. This keeps dependencies minimal and eliminates any possibility of sideways migration/escalation on a domain.
• Your VBR Windows will remain as a disabled component/proxy of the VBR VSA until you migrate all roles off it, then it can be removed and decommissioned.

[Mildur]

Hi John

Thanks for sharing your experience.

• We have found the MFA component for the VBR VSA to be problematic, sometimes requiring 3-5 or more key entries before successful authentication.

This is certainly unexpected and should be investigated in a separate case. I cannot confirm this behavior from my personal lab, where we have been running it since day one with v13.0. Maybe there is some larger time difference between MFA client and backup appliance? I suggest to give our support team a chance to verify the logs.

Best,
Fabian