Home / AWS Backup errors

VMware — unsupported disk size / independent disk

Warning FAILED AWS Backup
What AWS reports
unsupported disk size detected during backup creationunsupported disk size detectedindependent non-persistentindependent persistent

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

Two distinct causes share this message. AWS Backup does not support VMs with disks in independent persistent or independent non-persistent mode. It also only supports virtual disk sizes that are a multiple of 512 KiB — an odd disk size fails the whole VM.

How to fix it

  1. List every disk attached to the VM along with its disk mode, and look for independent persistent or independent non-persistent.
  2. Change those disks to dependent mode — independent disks cannot be snapshotted.
  3. Run fdisk -l from inside the failing VM to check the disk sizes.
  4. Confirm each virtual disk size is a multiple of 512 KiB; resize any that are not.
  5. Also confirm the VM version is on the AWS Backup supported list.

What AWS documents

AWS names four causes for this error: unsupported VM versions, gateway network connectivity, disks in independent mode, and disk sizes that are not a multiple of 512 KiB.

Source: AWS re:Post — Why does my AWS Backup job fail?

Stop finding this one failure at a time

BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.

Start free trial