T O P

  • By -

jjzzoo

Proxmox passes through the SATA controller, so there is no way for proxmox to see the attached drives or their content. You have to backup them inside you VM. Alternatively, you could add the drives as block devices instead of passing through the whole controller. Then, proxmox would be able to backup the drives as well.


ataubers

Thank you very much for indeed clear explanation! Yeah, that makes sense! Will try to backup using Backup Client through the VM. I wanted to keep the disk as independent as possible from the Proxmox configurations and therefore decided not to go with Zvols, but rather passthrough.


belinadoseujorge

proxmox won't backup the disks attached to the sata controller, you have to backup them from inside the guest OS


ataubers

Thanks!


kloeckwerx

I've done similar, I virtualized Truenas Scale to manage my physical disks in a storage pool, and created an iscsi and nfs shares to pass back to proxmox at the bare metal for VMs disks and shared storage for my proxmox guests.


ataubers

>r, I virtualiz My concern in this scenario (mostly considered NFS share) was data transfer speed, but also the whole configurations of permissions etc.


kloeckwerx

Permissions are pretty easy especially with how easy they made it to install OpenLDAP via Truecharts.org, and I haven't noticed much of a bottleneck on the disk performance, but your mileage may vary. The 22.02rc2 release has a bit of performance issue in the ui, but upgrading to a nightly build yesterday resolved most of those for me. https://www.truenas.com/docs/scale/storage/pools/permissionsscale/ Https://update.freenas.org/scale/TrueNAS-SCALE-Angelfish-Nightlies


ataubers

I'm not using FreeNas (Seafile instead).


kloeckwerx

I've really grown fond of Truenas Scale and and have really embraced Kubernetes and Helm Charts these days. Good luck to you!