Generating Arcserve UDP Reports › How to Generate Arcserve UDP Reports › Customize Raw Data Size in Managed Capacity Report for Host-based Agentless VM Backup

Customize Raw Data Size in Managed Capacity Report for Host-based Agentless VM Backup

You can configure the following registries at the proxy level or VM level:

CountNtfsVolumeSize (Arcserve UDP v6), GetVMGuestVolumeUsedSize (Arcserve UDP v6 Update 1 and later)

Specifies whether to count the used space of all volumes of a VM.

ReportZeroIfHavingNonNtfsVolume

Specifies whether to show 0 if non-NTFS volumes exist. It is ignored if CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is set to 0.

BackupZeroBlock

Specifies whether to write all-zero data blocks to the backup destination. It is ignored if CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is set to 1.

At proxy level for all VMs protected by current the proxy:

[HKEY_LOCAL_MACHINE\SOFTWARE\Arcserve\Unified Data Protection\Engine\AFBackupDll]
"CountNtfsVolumeSize"=dword:00000001
"ReportZeroIfHavingNonNtfsVolume"=dword:00000001

At VM level for a specific VM:

[HKEY_LOCAL_MACHINE\SOFTWARE\Arcserve\Unified Data Protection\Engine\AFBackupDll\<vm-instance-uuid>]
"CountNtfsVolumeSize"=dword:00000001
"ReportZeroIfHavingNonNtfsVolume"=dword:00000001

Note: The VM-level registry takes precedence over the proxy-level registry.

The following behaviors are observed:

• If CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is not set (or is set with the value 0), ReportZeroIfHavingNonNtfsVolume is ignored. In this case, if BackupZeroBlock is set with value 1, all-zero data blocks are also written into the backup destination. It makes the Raw Data Size reported in Managed Capacity Report bigger than before.

  Note: By default (without BackupZeroBlock), when Arcserve UDP reads data from a backup source, if it detects that a data block is all-zero, this data block is skipped and not written into the backup destination.

• If CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is set with the value 1, but ReportZeroIfHavingNonNtfsVolume is not set (or is set with the value 0), the Raw Data Size reported in Managed Capacity Report is the sum of used space of all NTFS volumes in the guest OS of the VM. In other words, it equals to Used Space of NTFS volumes.

  Note: BackupZeroBlock is ignored in this case.

• If CountNtfsVolumeSize/GetVMGuestVolumeUsedSize and ReportZeroIfHavingNonNtfsVolume are set with the value 1 and the guest OS of the VM has at least one non-NTFS volume, zero is reported in the Raw Data Size of Managed Capacity Report for the VM.

  Note: BackupZeroBlock is ignored in this case.

Example

A VM has one thin-provision virtual disk with the provisioned size 1000 GB. The size of the virtual disk’s VMDK file is 800 GB, among which 200 GB data blocks are all-zero data blocks. In the guest OS of this VM, there are 2 NTFS volumes whose used space are 100 GB and 200 GB respectively, and 1 FAT32 volume with the used space as 1 GB.

The following behaviors are observed in Managed Capacity Report:

• If CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is set with value 1:
  • If ReportZeroIfHavingNonNtfsVolume is not set (or is set with value 0), Raw Data Size of this VM is 300 GB (which is the sum of the used space of the 2 NTFS volumes per this example).
  • If ReportZeroIfHavingNonNtfsVolume is set with value 1, Raw Data Size of this VM is 0 (because the VM has a FAT32 volume).
• If CountNtfsVolumeSize/GetVMGuestVolumeUsedSize is not set (or is set with value 0):
  • If BackupZeroBlock is not set (or is set with value 0), Raw Data Size of this VM is 600 GB (because 200 GB all-zero data blocks are skipped).
  • If BackupZeroBlock is set with value 1, Raw Data Size of this VM is 800 GB.