Skip to main content
Question

Large Incremental (.vib) Backup Size for Single Machine

  • June 10, 2026
  • 5 comments
  • 22 views

 Details: Files visible: Central_AD.vbm → metadata/config file

Central_AD2026-06-01...vbk → Full backup (~73 GB ✅ normal)

Central_AD2026-06-02...vib → ~2.4 GB

Central_AD2026-06-03...vib → ~2.6 GB

Central_AD2026-06-04...vib → ~2.1 GB

Central_AD2026-06-05...vib → ~2.5 GB

Central_AD2026-06-06...vib → ~2.5 GB

Central_AD2026-06-07...vib → ~1.5 GB

👉 These .vib files are incremental backups (daily changes only)

Hello Veeam Community,

I am using Veeam Agent for Microsoft Windows free for office use, with no big data exchange, and noticed that the incremental backup (.vib) files for a single machine are relatively large (around 1.5 GB to 5.6 GB per day), while the full backup is about 73 GB. Machine details: - Role: Active Directory server (Central_AD) - Backup type: Incremental (daily) I would like to understand:

1. Is this incremental size normal for this type of workload?

2. What factors could cause such daily change rates?

3. Are there recommended optimizations to reduce incremental backup size?

4. How can I identify which files or processes are contributing most to the changed data?

Attached is a sample of backup file sizes over several days.

Thank you.

 

5 comments

Tommy O'Shea
Forum|alt.badge.img+5
  • Veeam Legend
  • June 10, 2026

I wouldn’t say this kind of incremental size is abnormal. If I had to guess, I’d say that windows update could be downloading updates and they’re getting backed along with the rest of the server.

To decrease the incremental backup size, you could increase the compression level. However, this would affect your backup and restore size the higher you set the compression.


Forum|alt.badge.img+3
  • Experienced User
  • June 10, 2026

It’s very normal, I agree with Tommy.

However, keep in mind that any changes to existing data will result in the CBT mechanism seeing the block as “changed”, triggering the C in CBT.

That is, tons of files might get a minor update, only a few bytes even. But that means that the block the data resides on is changed.

Especially for an Active Directory server, the AD DB is going to be constantly updating with minor updates / changes, so you're going to have some churn.

The numbers you show look pretty normal, these are not unusual incremental sizes.

Compression change _may_ help, but I’m doubtful you’re going to see significant reduction. Test is, but I’m going to guess you’ll at best see a very minor improvement.


Tommy O'Shea
Forum|alt.badge.img+5
  • Veeam Legend
  • June 10, 2026

It’s very normal, I agree with Tommy.

However, keep in mind that any changes to existing data will result in the CBT mechanism seeing the block as “changed”, triggering the C in CBT.

That is, tons of files might get a minor update, only a few bytes even. But that means that the block the data resides on is changed.

Especially for an Active Directory server, the AD DB is going to be constantly updating with minor updates / changes, so you're going to have some churn.

The numbers you show look pretty normal, these are not unusual incremental sizes.

Compression change _may_ help, but I’m doubtful you’re going to see significant reduction. Test is, but I’m going to guess you’ll at best see a very minor improvement.

Thanks David, I was thinking something along those lines as well, but couldn’t figure out the best way to articulate it.


coolsport00
Forum|alt.badge.img+22
  • Veeam Legend
  • June 10, 2026

Hi ​@Esayas.T - welcome to the Community!

Can you share why you think 1-2GB Incremental is “large”? Do other Jobs have less Incremental size maybe? As shared by Tommy/David, this size is quite normal. And, for a DC, even moreso. Aside from any modifications within AD itself that may be happening, MS sends updates to Defender and Virus Definition files not just everyday, but at times multiple times throughout the day. Those changes are relatively small, but between them and AD & other OS changes, 1-2GB is no doubt easily achieved imo.

Hope that helps explain a bit.

Let us know if you have further questions.


wolff.mateus
Forum|alt.badge.img+12
  • Veeam Vanguard
  • June 10, 2026

This is a normal behavior.

In environments that we do not have so many changes is normal to get .vib on this size.

 

I can see that you are looking for this on repository side.

Try too look this on the Veeam side. Go to Backups menu and take the properties of this chain. Over there you can see other informations like the Data Reduction collun: