Skip to main content

Proxmox Backup Proxy OVA Deployment Fails

Proxmox Backup Proxy OVA Deployment Fails

Problem Description

When deploying the Druva Proxmox Backup Proxy using an OVA template, the import process fails with the following error:

Parameter verification failed (400)

content: type 'disk image' is not allowed on storage 'local'

Cause

During the OVA import, Proxmox VE uses the storage pool where the OVA is uploaded as a temporary Import Working Storage to extract and stage the virtual disks.

By default, Proxmox’s local storage pool is configured to host only ISO images, container templates, and backups. Because the Disk image (images) content type is disabled on this pool, Proxmox blocks the disk extraction step and throws a 400 verification error.

Resolution

To resolve this issue, temporarily enable the Disk image content type on your local storage pool so Proxmox can stage the extracted virtual disks.

Step-by-Step Fix:

  1. Log into the Proxmox VE Web UI.

  2. Go to Datacenter > Storage.

  3. Select local from the list and click Edit.

  4. Click the Content drop-down menu and add Disk image (ensure existing selections like ISO image and VZDump backup file remain selected).

  5. Click OK to save changes.

Verification

Retry the OVA import. The Druva Proxmox Backup Proxy deployment should now complete successfully without triggering the Parameter verification failed (400) error.

Did this answer your question?