Skip to main content
Question

What is the best way to migrate Backup jobs including restore points between servers (old -> new)


Hallo everyone
I am trying to figure out what the best way to transfer Running backup jobs with tons of restore points pr. job, to a new Veeam server, without loosing any backup data/history

The “old” Veeam server has to be decommissioned - and so will the current repository, over time.

The new Veeam server should have all jobs and backup data (restore points) from “old” Veeam server and run on new repository/storage as well

What will be the best way on migrating all, from old to new server - and from old repo to new repo, with out loosing vital backup data and history

Anyone ?

8 comments

MicoolPaul
Forum|alt.badge.img+23
  • 2362 comments
  • October 19, 2023

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 🙂


  • Author
  • Not a newbie anymore
  • 3 comments
  • October 19, 2023

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


MicoolPaul
Forum|alt.badge.img+23
  • 2362 comments
  • October 19, 2023

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 🙂


  • Author
  • Not a newbie anymore
  • 3 comments
  • October 19, 2023

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


MicoolPaul
Forum|alt.badge.img+23
  • 2362 comments
  • October 19, 2023

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


  • Author
  • Not a newbie anymore
  • 3 comments
  • October 19, 2023

Thanks 
Much appreciated


MicoolPaul
Forum|alt.badge.img+23
  • 2362 comments
  • October 19, 2023

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


Scott
Forum|alt.badge.img+9
  • Veeam Legend
  • 1003 comments
  • October 23, 2023

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.