architecture question, CBT/Full/job stats

[jpeake]

I am running some fresh fulls since 6.5 upgrade. I am curious about what is happening under the hood.

Below is a screen grab of the job details, with a server highlighted. This VM has two thinned disks, residing in one datastore which is on the SAN.

Both disks have about 30GB used space.

The backup seems to indicate it is using CBT to back these up, I thought that was just for incremental runs?

Also, the amount of data read is much higher on one disk.

Can someone tie this together for me?

[poulpreben]

You are right, CBT is only used for incremental jobs. It is just indicated in the status window, that it is available.

As for Hard Disk 2, it has read 200.9 GB, and that is because the VMDK size is 200.9 GB, regardless how much is used within the VM. This thin provisioned disk; at a certain point, 200 GB was used on that disk causing it to expand the VMDK. Space reclaim on VMDKs was unsupported until now with the vSphere 5.1 release.

[jpeake]

ah, that looks to be spot on. That 2nd drive used to be a file share for scanned docs and did have about 200GB of files on it.

thanks for the info!

[Gostev]

You are right, CBT is only used for incremental jobs.

Actually that is incorrect, as CBT is used during full job runs as well.
There is an existing thread where I explain this in more details, please search if you are interested.