Comprehensive data protection for all workloads
Post Reply
chriskarako
Novice
Posts: 6
Liked: never
Joined: Sep 06, 2018 9:03 am
Contact:

Changed Vm object in backup job

Post by chriskarako »

Hello all
I have an incremental job for one windows 2012R2 vm with two disks (os, and data) and 48 restore points configured.
Now we are in the 12th restore point
Recently we replaced this vm with one windows 2016 vm (different vm name) but with the same data disk.
How can we manage to "insert " this vm into the backup chain in the same scheduled job , without creating a full backup of the data disk ?
Thanks in advanced !!
Rick.Vanover
Veeam Software
Posts: 712
Liked: 168 times
Joined: Nov 30, 2010 3:19 pm
Full Name: Rick Vanover
Location: Columbus, Ohio USA
Contact:

Re: Changed Vm object in backup job

Post by Rick.Vanover »

Hi Chris - a Veeam Backup & Replication job can have multiple items in it - VMs, Datastores, vSphere Tags, vApps, Folders, etc. With the backup job having the one VM in it - if we simply add the new VM with a different name (not sure if you need to remove the old one or not, but you can) and the job will carry on. What will happen however is worst case a "snap and scan" - it will start looking and indicate that this is data already in the backup and not be a full transfer again. I expect there would be reads of the data disk, but no heavy writes to the backup repository.
Rick.Vanover
Veeam Software
Posts: 712
Liked: 168 times
Joined: Nov 30, 2010 3:19 pm
Full Name: Rick Vanover
Location: Columbus, Ohio USA
Contact:

Re: Changed Vm object in backup job

Post by Rick.Vanover »

Meaning... you will not have a new full backup. I think that's what you are asking :)
foggy
Veeam Software
Posts: 21138
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Changed Vm object in backup job

Post by foggy »

Rick.Vanover wrote: Oct 17, 2018 12:33 pmit will start looking and indicate that this is data already in the backup and not be a full transfer again.
This is valid in case the job is reverse incremental, since the blocks of the new VM will fall into the same full backup file and will be deduped. In case of forward incremental, where a new incremental backup file is created, the entire new VM data will fall there, since technically this is a different VM (having a different VM ID).
Post Reply

Who is online

Users browsing this forum: Egor Yakovlev, mariuszr and 156 guests