Skip to main content

Proxmox VM Restore: Storage Backends Not Visible in Destination Dropdown

Proxmox VM Restore: Storage Backends Not Visible in Destination Dropdown

Problem description

During a Proxmox VM restore operation in the Phoenix Management Console, only the local-lvm storage is displayed in the restore destination dropdown, even though additional storage backends (e.g., Ceph, NFS, ZFS) are configured and active on the Proxmox host.

Cause

This issue occurs due to one of the following reasons:

  1. Missing Storage Content Type: The target storage backend on Proxmox VE does not have the Disk image (images) content type enabled in its configuration.

  2. Unsupported Storage Type: The target storage backend type is not supported according to the Druva Proxmox Support Matrix (for example, non-qualified storage engines or unformatted volume types).

  3. Outdated Inventory Discovery: A discovery cycle has not run in the Phoenix Management Console since the new storage was added or reconfigured on the Proxmox host, leaving the console out of sync.

  4. Stale Backup Proxy Cache: The Backup Proxy appliance metadata cache has not synchronized with the Proxmox environment.

Resolution

Follow these steps to ensure storage backends are recognized by the Phoenix Management Console:

Step 1: Verify Storage Content Type and Compatibility in Proxmox VE

  1. Log in to the Proxmox VE Web UI.

  2. Navigate to Datacenter > Storage.

  3. Select the target storage backend and click Edit.

  4. In the Content drop-down menu, ensure Disk image (images) is checked.

  5. Confirm that the underlying storage type is supported according to the Proxmox Support Matrix.

  6. Click OK to save changes.

Step 2: Trigger a Manual Discovery

  1. Log in to the Phoenix Management Console.

  2. Navigate to Protect > Proxmox.

  3. Select the relevant Node/Cluster.

  4. Click Discover VMs to execute a manual inventory discovery cycle.

Step 3: Restart Backup Proxy (If Issue Persists)

If the newly configured storage still does not appear after completing Steps 1 and 2:

  1. Reboot or restart the Druva Backup Proxy appliance assigned to the Proxmox host.

  2. Wait 3 to 5 minutes for the proxy services to initialize and execute a complete storage metadata refresh.

Verification

  1. Log in to the Phoenix Management Console.

  2. Initiate the Proxmox VM Restore wizard.

  3. In the Restore Destination step, expand the target storage selection dropdown.

  4. Verify that the newly updated storage backend is now visible and selectable as a restore target.

See also

Related Articles
Did this answer your question?