Query about merging

Availability for the Always-On Enterprise

Query about merging

Veeam Logoby pkelly_sts » Tue Jul 18, 2017 9:17 am

Just wondering the answer to this one.

Let's say you create a backup copy job & configure it with 14 RPs, then run the job for a week.

If you then add a couple of new VMs to the same job, when does the first merge happen, and what exactly gets merged?

I'd assume that if it's going to a "traditional" single .vbk then the merge would simply happen after the 15th iteration of the job so there would be a big .VIB for the day you added the extra VMs, until that VIB was "ingested" & expired by the coming merge.

However, with a per-vm backup repository, should I expect it to merge the originally added VMs as per schedule, and also the later-added VMs won't be merged until they reach their own 15th RP?

Just checking...
[New Sig: PLEASE get GFS tape support for incrementals!!!]
pkelly_sts
Expert
 
Posts: 502
Liked: 55 times
Joined: Thu Jun 13, 2013 10:08 am
Full Name: Paul Kelly

Re: Query about merging

Veeam Logoby DGrinev » Tue Jul 18, 2017 4:44 pm

Hi Paul,

pkelly_sts wrote:so there would be a big .VIB for the day you added the extra VMs, until that VIB was "ingested" & expired by the coming merge.

That's correct. Newly added VMs will be included in the next incremental run and injected in the .vbk according to the retention policy.

pkelly_sts wrote:However, with a per-vm backup repository, should I expect it to merge the originally added VMs as per schedule, and also the later-added VMs won't be merged until they reach their own 15th RP?

If I get you right, under merge you mean injection of incremental files to the full backup, then yes, originally added VMs will start to merge according to the retention policy. Thanks!
DGrinev
Veeam Software
 
Posts: 381
Liked: 48 times
Joined: Thu Dec 01, 2016 3:49 pm
Full Name: Dmitry Grinev


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], Google [Bot] and 35 guests