Comprehensive data protection for all workloads
Post Reply
slackhouse
Influencer
Posts: 15
Liked: 3 times
Joined: May 21, 2018 12:13 pm
Full Name: Jeremy Slack
Contact:

Move VMs to different Backup Job VBR12.1

Post by slackhouse »

I'm running VBR 12.1.1.56. I have multiple backup jobs that have Windows and Linux VMs. I want to move the Linux VMs to their own backup job so that I can have different settings for those VM backups than the Windows VMs. I am currently using per-machine backup files. What are the steps to move these Linux VMs to a different job without losing existing backup data?
Mildur
Product Manager
Posts: 8779
Liked: 2312 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by Mildur »

Hi Jeremy

You can use our "Backup Move" feature to move your VM to a different jobs:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Make sure that the target job has the correct retention. The moved backup files will be removed accordingly to the specified retention of the target job.

Best,
Fabian
Product Management Analyst @ Veeam Software
slackhouse
Influencer
Posts: 15
Liked: 3 times
Joined: May 21, 2018 12:13 pm
Full Name: Jeremy Slack
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by slackhouse »

So, it looks like you can only move individual workloads if you have the per-machine backup files setting with separate metadata files for each workload. According to the documentation, it looks like the "separate metadata files for each workload" occurs when you create a new backup repository after upgrading to VBR 12. Is there a way to convert existing backup repositories created prior to VBR 12 to this new "separate metadata files for each workload" settings?
Mildur
Product Manager
Posts: 8779
Liked: 2312 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by Mildur »

Hi Jeremy

Yes, you can "Upgrade" your backup chains to the new format with "separate metadata file per machine":
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian
Product Management Analyst @ Veeam Software
slackhouse
Influencer
Posts: 15
Liked: 3 times
Joined: May 21, 2018 12:13 pm
Full Name: Jeremy Slack
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by slackhouse »

Thanks for that link. Is there any way to estimate the length of time this takes since it disables the job while it is upgrading the backup chain format?
Mildur
Product Manager
Posts: 8779
Liked: 2312 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by Mildur » 1 person likes this post

Hi Jeremy

It depends on different factors, we see normally update times from 10-60 seconds per workload.
I suggest to run the upgrade on a single job first to see how long it will take you to run the chain upgrade.

If you can, please share with me the amount of VMs and time to upgrade the backup chains.
You can also send me the feedback in a private message here in the forum.

Best,
Fabian
Product Management Analyst @ Veeam Software
slackhouse
Influencer
Posts: 15
Liked: 3 times
Joined: May 21, 2018 12:13 pm
Full Name: Jeremy Slack
Contact:

Re: Move VMs to different Backup Job VBR12.1

Post by slackhouse » 1 person likes this post

Nevermind. It only took a minute per job to upgrade the backup chain format.
Post Reply

Who is online

Users browsing this forum: No registered users and 48 guests