Skip to main content

I am striking out on my Google-Fu and Forums-Fu ! I can't find a definitive result for what happens to backups when the source VMDK is resized (larger). Can anyone point me to the correct link for a customer to review? I think the backup job runs a new full because the block map changes. But for Replication, a rescan of the disk supposedly prevents resending the whole disk. 

If you resize the vmdk file yes the CBT resets and does a full read of the disk again for backups to create a new full.


There is a rather old thread on the forums about this topic, but it should still work like described there.


Comment