Proxmox uses BTRFS subvolumes for block level type volumes : https://pve.proxmox.com/wiki/BTRFS
As said, if homelab/budget constraint , use M2 disc N1 as LVMthin , then backup (like an asynchronous raid) to the M2 disc N2 , with PBS.
If N1 fails...
Title should be edited, as problem is about Windows "conversion",
which is a problem since Windows exists, even before virtualization.
Windows "conversion" is always a "YMMV", because it doesn't like swapping motherboard/cpu and mainly disk...
Proxmox doesn't support RAID with LVM. Only ZFS and BTRFS are supported by Proxmox for RAID.
and ZFS/BTRFS/Ceph and any RAID require datacenter drives if you really care of your data.
For Homelab, I should use backup before RAID.
With PBS ...
The backup runs against readable data, otherwise the source would be gibberish.
The data is encrypted by the job's configured encryption key, if any, and sent to PBS. PBS then stores the encrypted data chunks.
If two chunks to be stored in PBS...
as i wrote, the journal from the host would be interesting. you can get that with 'journalctl' e.g. all the logs since the last boot would be 'journalctl -b' or if you want to specify a date you can do something like 'journalctl --since 2025-09-15'
People have been disappointed by the performance difference as past threads about ESXi migrations will show. ZFS RAIDz1 (on consumer drives) is not at all like hardware RAID5 (with BBU) and VMs that use non-VirtIO disks are also known to be slow...
I just mentioned those things as they are common performance issues. I don't know much about =1&c[nodes][0]=16&o=date']NFS performance for virtual disks, sorry. QEMU does use a difference file-based storage format than ESXi (and I would expect...
BTW, proxmox-backup-debug recover index output is RAW .img with fully allocated space even zeroes are written to destination drive which is slow when allocated space is lot of more than used space.
If PBS is available, proxmox-backup-client map...
Hi,
I have found one more variant:
proxmox-backup-debug recover index drive-scsi0.img.fidx /path/to/.chunks
or something like
cd /mnt/usb
proxmox-backup-debug recover index /backup/vm/875/2025-09-11T18:12:13Z/drive-scsi0.img.fidx...
They are informational, each time a guest is shutdown/started.
Here, I disable "dmesg" displaying on console with crontab :
@reboot echo "1" > /proc/sys/kernel/printk
Issue - unable to mount NFS shares from Synology NAS.
Main symptoms:
unable to add NFS share to Datacenter Storage (timeout)
mount command timing out (on Proxmox hosts as well as CTs and VMs)
rpcinfo -p <nas-host> also timeout
After a day of...
some sort of threshold-based warnings - like if there is more than 90% new chunks - would be nice (not just for this, but also for accidents). it's hard to guard against malicious actors though - after all, you can always modify your malicious...