Target Issue

VMware specific discussions

Re: Target Issue

Veeam Logoby Zew » Mon Apr 03, 2017 1:06 pm

foggy wrote:It will pick it up as a new VM and perform a full backup of it during the next incremental job run (entire VM data will be read and written into the corresponding VIB file).


But you said it does a full. What goods a VIB if you only have one VM in the chain, and it has to do a full after recovery?
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby foggy » Mon Apr 03, 2017 2:49 pm

This way you do not end up with two separate chains for the same VM, but continue the same chain maintaining its retention.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Target Issue

Veeam Logoby Zew » Wed Apr 05, 2017 3:53 pm

I get that, but the chain (VIB file) will be huge cause it contains technically a full copy of the restored VM, as well as the old (before restore) copy of the same VM, correct?
Zew
Expert
 
Posts: 173
Liked: 39 times
Joined: Tue Mar 17, 2015 9:50 pm
Full Name: Aemilianus Kehler

Re: Target Issue

Veeam Logoby foggy » Wed Apr 05, 2017 4:18 pm

VIB will contain the entire data for the restored VM, right. Ifthe old VM is still running and backed up, VIB will also contain changes occurred in it since the last job run.
foggy
Veeam Software
 
Posts: 15094
Liked: 1111 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Previous

Return to VMware vSphere



Who is online

Users browsing this forum: lukedaynz and 22 guests