After live resizing a VHDX file, the following issue can occur based on the operation that was performed:

• Shrink — If the VHDX associated with a VM is shrunk, the backup task for that VM will fail, and the following exception will be found in the Agent.<Job name>.Source.<VM name> log file:

  cli| VHDX.GetDiskInformation
  cli|   (EString) DiskPath = vhdx://<shadowSpec><extent path="full path to the disk" shadow="full path to the disk in the shadow copy" isAutoRecovery="False" /></shadowSpec>
  cli|   (EString) Option.Container = {disk}
  cli| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  vhd| Opening VHDX by full path: [full path to the disk].
  cli| File 'HostFile{full path to the disk in the shadow copy}' opened (read_only: true, no_cache: false)
  dsk| Loading VHDX log.
  dsk| Loading VHDX log. Failed.
  cli| File 'HostFile{full path to the disk in the shadow copy}' closed
  cli| ERR |Failed to process method {VHDX.GetDiskInformation}
  cli| >>  |VHDX file was truncated. Current file size: [1503242747904]. Flushed file size: [1825365295104].
  cli| >>  |Failed to replay VHDX log.
  cli| >>  |--tr:Failed to load VHDX log.
  cli| >>  |An exception was thrown from thread [6440].
  cli| Trying to poll message from the notification channel (from server side).
  net| Triggering AUX channel synchronization. Request id: {guid}
  net| Received synchronization response {guid}
  cli| No server exception available.
  cli| ERR |Failed to process {Invoke} command
  cli| >>  |Details:
  cli| >>  |VHDX file was truncated. Current file size: [1503242747904]. Flushed file size: [1825365295104].
  cli| >>  |Failed to replay VHDX log.
  cli| >>  |--tr:Failed to load VHDX log.
  cli| >>  |Agent failed to process method {VHDX.GetDiskInformation}.
  

• Expand — If the VHDX associated with a VM is expanded, the backup job for that VM may become inconsistent.

Consider the following when performing live VHDX resizing:

• Shrinking — After shrinking a disk associated with a VM that is protected by Veeam Backup & Replication, the VM must be power cycled (not a reboot, but a full shutdown and power on).
• Expanding — After expanding a disk associated with a VM that is protected by Veeam Backup & Replication, an Active Full for that individual VM must be run.