Job reading full disk instead of only the used part

[nbo]

Hi,

I have some issues with a backup job that is taking a long time. While investigating this I noticed that for one particular server, the backup job was reading the full disk (250GB) instead of only the part that is being used while for other server it is only reading part of the disk. Here are 2 images to show what I mean:

This one is the server where it reads the full disk:


This one is one of the servers where it reads only part of the disk:


Any thoughts on what could be causing this and how I can make it only read the used space of that disk?

Thanks in advance

[veremin]

By looking at first picture it can be seen that CBT didn’t seem to work.

In case CBT doesn't work, It’s VB&R proprietary mechanism that is being leveraged - VB&R scans through the whole VM image and a checksum (hash) is calculated for every data block, then it verifies what blocks have been changed on your VM compared to the VM image stored in the backup file. This is why you see such high read value.

Most common reason for CBT being disabled on particular VM is the snapshot presence or if this VM is used as VB&R proxy server.

Hope this helps.
Thanks.

[tsightler]

Or a legacy VM that is still virtual hardware V4.

[nbo]

Thanks for the replies. There was indeed a snapshot present. After changing the location, the backup job was not reading the full disk anymore and the total job time dropped by almost 1.5 hrs. Problem solved, thanks for the help!

[cg167]

nbo, what do you mean by "changing the location"? Changing the location of what?

[foggy]

Corey, I suppose Nicola meant that he had removed the snapshot for CBT to be enabled on the VM. Thanks.