Skip to main content
Druva Documentation

Why is complete disk image uploaded when backing up VMs with dynamic disks

This article applies to:

  • OS: Hyper-V
  • Product edition: Phoenix

FAQs

Why is the complete disk backed up while backing up a VM that is configured with Dynamic disk?

This is an expected behavior, the backup mechanism for Hyper-V uses resilient change tracking (RCT) and only uploads the allocated data. The remaining sparse blocks get uploaded only for the first backup and do not consume any storage. The data displayed under Current source on the dashboard displays the maximum size of the disk.

How does backing up a VM configured with Dynamic disk affect credit consumption?

Druva uploads data after normalizing as per 1MB block-size, only the allocated disk size would consume credits and not the sparse blocks.

  • Was this article helpful?