Skip to main content
  • EN

Hello Community!  I am new to Veeam (last used 7 years ago, so might as well be new).

 

Here is my current setup:  I have two Mini PC’s running Proxmox as the “Compute”.

They are connected over 10GB  to a different server running TrueNAS, via iSCSI.

So the VM “Data” does not actually reside on the Proxmox machine, it just acts as the compute side.

 

Now, I have installed Veeam on a Barebones Windows machine.  I configured the Veeam software to connect to the Proxmox servers (success) and it installed the proxy’s.

First backup tested was successful, but the others failed.

They show “succeeded” but with “Warnings” and no actual data has been backed up.
“disk scsi0 has been skipped due to unsupported storage type”

 

I find this odd since the storage type on the successful backup is the same as the other VM’s I am running, (Three Ubuntu VM’s & Home Assistant OS).

 

Any insight would be appreciated!

Hello,

Can you confirm which storage backend the affected VMs are using in Proxmox, and what disk format (RAW or QCOW2)?

Is the successful VM stored on the exact same storage and format as the ones failing?

 

I’m asking this because Veeam officially supports only certain storage backends — specifically file-based storages (like a directory with RAW/QCOW2 disks). If the VMs are stored on LVM-thin, ZFS, Ceph, or have iSCSI disks attached, Veeam will skip those disks and report them as “unsupported storage type”.

 

You can check this in Proxmox under VM → Hardware → Hard Disk to compare the storage/format of the working VM and the failing ones.

 

For reference, here’s the considerations and limitations doc:

https://helpcenter.veeam.com/docs/vbproxmoxve/userguide/limitations.html

 

Veeam Plug-in for Proxmox VE does not support backup of VMs that store their disks in the BTRFS and custom storage. All other Proxmox VE storage types are supported.

…

Veeam Plug-in for Proxmox VE does not support backup of iSCSI disks. If iSCSI disks are attached to a VM included into a backup job, these disks will be skipped from processing.”

Are the failing VMs using disks with BTFRS filesystem? This would not be supported, see this thread on the Veeam R&D forums: (5) BTRFS support dropped in 12.3.1.1139? - R&D Forums

Oh, ​@matheusgiovanini  beat me on that one 😅

 

Oh, ​@matheusgiovanini  beat me on that one 😅

Looks like we’re on the same page 🤣

Thanks for the quick response!

I double-checked all my VM’s and it looks like the format to all of them is “RAW”.  I grabbed a screenshot of just one VM as an example so as to not flood this thread.

 

 

I also need to backtrack on my original post, as it turns out the VM that backed up successfully was LVM and not iSCSI.  I noticed this when I was double-checking my setup.

So it looks like none of my iSCSI VM’s are backing up even though they are all RAW Format.

 

EDIT:  I read the article you linked, so now its my understanding that Veeam does not support iSCSI at all?  Or would there be an additional layer to the veeam setup to make it work?

For Clarity, the Backup that is successful is in the GB while those with warnings are in the MB.

My thought is for the ones with warnings, the VM Settings are being backed up just not the data that goes with them.

if iSCSI is not supported at all with veeam, i would figure i need to re-think backing up those Drives by another means while Veeam can still be used to save the VM Settings.  Just typing out loud.

Terms & ConditionsAccessibility statement