Root Cause

This alert usually appears for the following reasons:
  • The underlying storage is out of space or has very little free space (this refers to the actual storage hardware, not virtual datastore within vCenter or SCVMM).
  • A disk was either resized or that the disks' sizes on the production and recovery are not the same. As an example, expanding a disk on a protected VM from the Guest OS itself. This will lead to the Hypervisor not being aware of the change in size, thus the reflection remains outdated and the mirror is not automatically expanded.


The Alert VRA0013 "I/O error to recovery disk {disk_name} of virtual machine {vm_name} is triggered.


Based on the scenario encountered, to resolve this alert:
  1. Check for storage free space at the storage hardware level (array).
  2. Compare the size of the recovery disk with the size of the production VMs VMDK or VHDX. Do these match in provisioned size, at the OS level?
    • In case the disk was resized:
      • Note: Due to technical limitation, we can only resize volumes with a whole (integer) number of KBs. Please make sure this disk is expanded to a size that is a whole number of KBs which should allow the VM to be protected.
      • To locate the problematic disk, navigate to the VRA > Edit Settings of the VM > locate the corresponding disk > resize the disk size.
        • For more information on how to increase the size of a VMware virtual disk (VMDK), refer to VMware's KB 1004047
        • To find the corresponding disks, export the VPG settings under the VPG tab in the ZVR GUI, and get a detailed list of the VPG information.