Backup restore on Low configuration Machine

[asifahmed009]

Hi I am New bee.
My primary proxmox server configuration is 06 core Processor, 16gb RAM and 1TB hdd. Only 1 VM is running on it.
I take backup and want to restore on another low configuration machine. 02 core Processor, 08gb RAM and 500Gb hdd.
Is this achievable? Kindly guide me.

 

[asifahmed009]

Primary proxomx configuration:

 

[Dunuin]

Yes, but I would then lower the vCPUs down from 6 to 1 and RAM from 12 to 6GB. You always want some CPU cores and RAM for the hypervisor and don't want to overprovision.

 

[asifahmed009]

Thanks for your Reply @Dunuin
Actually my question is for worst case when i have only low configuration machine.
Can yo please guide steps to achieve that.

 

[Dunuin]

You simply backup the VM and restore it on the new host. New RAM and vCPUs can be set at the restore form.

 

[asifahmed009]

getting error

_22-14_30_18.vma.zst : Decoding error (36) : Data corruption detected
vma: restore failed - short vma extent (1190912 < 3736064)
/bin/bash: line 1: 1104 Exit 1 zstd -q -d -c /var/lib/vz/dump/vzdump-qemu-100-2023_11_22-14_30_18.vma.zst
1105 Trace/breakpoint trap | vma extract -v -r /var/tmp/vzdumptmp1095.fifo - /var/tmp/vzdumptmp1095
Logical volume "vm-100-disk-0" successfully removed.
temporary volume 'local-lvm:vm-100-disk-0' sucessfuly removed
no lock found trying to remove 'create' lock
error before or during data restore, some or all disks were not completely restored. VM 100 state is NOT cleaned up.
TASK ERROR: command 'set -o pipefail && zstd -q -d -c /var/lib/vz/dump/vzdump-qemu-100-2023_11_22-14_30_18.vma.zst | vma extract -v -r /var/tmp/vzdumptmp1095.fifo - /var/tmp/vzdumptmp1095' failed: exit code 133

 

[Dunuin]

Data corruption detected

Try another backup image. Sounds like that one got corrupted.
In case you are copying the backup image from one to another machine make sure to hash the file before and after the transfer to be sure it doesn't get corrupted in the transfer.
Also run memtest86+ on the servers to make sure bad RAM isn't corrupting your backup images.