Hi,

I would suggest you perform a migration of your configuration database from old to new VBR server, this migrates your core VBR element with history and config intact. Then, provided you’re on V12, you could leverage the VeeaMover functionality to migrate VMs to new backup jobs or repository to repository, with restore point history intact and whether you’re using ReFS/XFS or not, if that becomes your new destination you’ll benefit from fast clone technology

So “just” copying all backup job files to new repo → folder and then create a new job on new Veeam server - and do the “map” backup under storage setup of job wouldn´t /is recommended ?
( I have the new repo mapped accordingly on new Veeam server first)

Br Peter

Hi, you can use the map backup functionality, but it’d argue it’s simpler to bring across your existing jobs and just ask Veeam to do the copy/paste via its own mechanisms because you can then leverage fast clone functionality too

Thanks
Is there a Veeam article that describes that (what you suggest) in details - maybe ? 

Sure thing:

As I alluded to, you’d do this in two parts. Part one is config migration:

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120
 

give this a good read in case you’ve installed your new server with Postgres but your old is MSSQL for example.

And here’s the second part that contains how to move a backup: https://helpcenter.veeam.com/docs/backup/vsphere/backup_moving.html?ver=120

Thanks 
Much appreciated

Most welcome, let us know how it goes and if you’ve got any further questions

100% use the config backup for this method. 

I have done it myself when going from Server2016 to Server2022.

If you have tape, just remember that it may have to rescan the library and has the potential to take a while.  

https://helpcenter.veeam.com/docs/backup/vsphere/vbr_config_migrate.html?ver=120

There is also the option to stack up a NEW Veeam server and recreate the jobs if you have a very simple infrastructure.