search

jancc / vma-extractor

Extraction tool for the VMA backup format used by Proxmox
https://janw.name/tools.html
zlib License
77 stars 19 forks source link

Thank you #5

Open Marc85BPG opened 2 years ago

Marc85BPG commented 2 years ago

Hey man, i want to say thank you so much for this.

I was in Big Trouble for Data-Losses and only got a .vma snapshot as Backup. With your stuff i got my latest update back and dont lost a wekk of work.

Keep up and thanks again

JD-Howard commented 3 months ago

Also want to say thank you!

I primarily run Linux, but do a fair bit of C# programming over RDP on a Win11 Proxmox VM. I wanted to VirtualBox this VM on a Linux laptop while I was traveling. If not for this script, then I would have some crazy docker configuration or other Proxmox specific tools installed on my daily driver I did not want... I think the only thing I had to install was qemu utils.

Here is my full bash script if anyone wants a reference:

#!/bin/bash
touch ./win11.vdi
rm ./win11.vdi
zstd -d ./win11.vma.zst
rm ./win11.vma.zst
python3 ./vma.py ./win11.vma ./extracted
mv ./extracted/drive-sata0 ./win11.raw
rm -rf ./extracted
rm ./win11.vma
qemu-img convert -f raw -O vdi ./win11.raw ./win11.vdi
rm ./win11.raw

My 250GB ZST took about 20 minute to copy off my NAS backup server onto an NVME with about 1.5TB of space free. The above script does what it can to control the total consumed size through the various stages of the conversion, but that RAW file is the full 500GB I allocated in Proxmox; make sure you have the space available.... The above script running on NVME takes about 40 minutes in total and produced a 441GB VDI file. The 1st boot in VBox takes a while as windows adapts to the new environment, some apps do detect the change in hardware and require a fresh login, but generally works. My Win11 VM was never licensed to begin with so that wasn't an issue for me, but it would be if Microsoft would actually allow that at a reasonable price point...