I'm trying to figure out the best approach for migrating my VMware backup jobs over to a new Hyper-V host using Veeam. Can I simply point my existing backup jobs to the Hyper-V host, or do I have to set up entirely new backup jobs from scratch? I'm hoping to avoid unnecessary work if possible.
4 Answers
You're going to need to set up completely new jobs for Hyper-V. Don't stress about it too much; just plan for it in advance.
You can technically point the existing jobs at Hyper-V, but Veeam will treat them as new VMs anyway. Basically, you're starting fresh, so it might be easier just to discard the old jobs and create new ones. It saves you the frustration of retention issues down the road.
While I can't give a direct answer about Hyper-V, I did the same migration to Proxmox and was able to select a different restore target. Just know that things won't be live right away and you might have some extra steps to handle OS configurations after migration. Even if Veeam handles the backup side smoothly, you might run into issues once the OS boots up. Might not be as painless as you think!
You'll definitely need to create a whole new set of backup jobs. I had to do it myself and it works better that way. It might seem like a hassle, but it keeps everything organized.
But once you've created new jobs, can you still use the old ones for restoration purposes? Do you find it varies between restoring guest files versus full VMs?
Yeah, when we switched hosts, I had to add the new ones to Veeam and set up jobs for each site. It actually helped us with our immutable storage too. Just a heads up, I had to wait 40 days for the timer on the old backups to expire before I could clean things up. Total pain!