This is a problem I've been having for quite some time now, but I wanted to make absolutely sure that what I'm going to post was 100% correct so I tested it for several weeks.
I have one VMWare machine with 4 VMs running on it. I have two Veeam backup jobs running against that host. Each job backs up 2 VMs. I do it this way to keep file sizes (relatively) small.
The jobs are both setup to never perform a full backup and use synthetic backup forever. The jobs never give an error or anything else that is odd (yes, I posted earlier last week about this same job failing on one VM, but that issue had been resolved. The issue I'm describing now was present before and after).
So, on day 1 the first full backup is created, it is named 'Daffy en Exchange' (the names of the 2 VMs) and is has a file date of (for example): Aug 1 and a size of 1.000.000 MB.
On day two, an additional VRB file is created. The file size of the main VBK file changes to 1.200.000 MB and a file date of Aug 2.
And so it goes on every day, until around day 7.
Then, VRB files keep being created but the size and modified date of the main VBK file stops changing.
So, on day 7 the VBK file had a date of Aug 7 and a size of 1.700.000 MB.
On day 8 the VBK file has a date of Aug 8 and a size of 1.700.000 MB.
On day 9, the same.
Additional VRBs keep being created, but it appears the main archive doesn't change anymore.
When I order Veeam to perform a full backup, everything is fine again for another week.
The other job that's running against the same machine keeps updating the VBK just fine.
Below screenshot indicates my problem. This screenshot was taken on day 7. I can post another one tomorrow and it will show the same VBK date and size. You can trust me on this, I have verified this for at least 6 weeks to make absolutely sure this happens every time. You can see, that normally the VRB and VBK have the same modified date, as the other job shows. The job that's going wrong also has the dates in sync until day 7.
![Image](http://www.vincis-service.nl/veeam_files.png)
Is there any way to look inside the VBK file to see what's actually really in there?
If this is not the correct way to ask this, then Veeam should feel free to copy my text to a supportticket and delete my post from the forum. I just thought perhaps more people are seeing this and a solution can benefit them as well.
Thanks.