Hi

Does anyone know why, when backing up a VMWare VM with Changed Block Tracking enabled, if that VM is powered off then MSP360 Backup reads the entire disk and ignores the fact that no bytes have changed according to CBT. I have several VMs that I just use intermittently. If they are powered on then backups are usually fairly quick but when they get switched off they can take many hours or even days.

Spending eight hours to read a 100GB disk on a remote system over the internet just to decide that nothing has changed since last time seems very inefficient when it could, if CBT is showing no changes, just look at the last update time of the disk and realise that it's not been used at all since the last backup.

To confirm this I have run the following tests. Note that the VM has CBT disabled and re-enabled before the tests to ensure it's clean and not corrupted.
1) VM powered off - Very slow backup. 0 CBT bytes, entire disk read over network, 0 bytes to backup.
2) VM powered on - Faster backup, CBT changes found, chunk of disk read over network, smaller chunk backed up.
3) VM powered on - Fast backup, fewer CBT changes found, smaller chunk of disk read and backed up.
4) VM powered off - Fast backup, few CBT changes found, small chunk read and backed up
5) VM powered off - Very slow backup. 0 CBT bytes, entire disk read over network, 0 bytes to backup.

So a second or subsequent backup of a powered off VM results in horrendous performance. There must be a way to optimise this to backup powered off VM s much faster. One of the reasons I switch them off is to reduce resources and consumption on the hosting server but MSP360 then goes and pointlessly thrashes the disk for hours or days on end for no good reason.

Any suggestions how to work around this until it gets a proper fix in the application?