Backup - too small size, unable to restore
- Thread starter Maximus11
- Start date
hi,
also what do you mean with backup size being too small?
compression and sparse allocation effect the size of the resulting archive, making it smaller than the total size of disks.
please also post the configs of the 2 VMs
could you provide an example log of a failed restore?
also what do you mean with backup size being too small?
compression and sparse allocation effect the size of the resulting archive, making it smaller than the total size of disks.
please also post the configs of the 2 VMs
I mean usual backup looks like that (yesterday's one)
And today's
No significant changes to actual VM size were made. Sometimes VM-102 is ~80Gb and sometimes VM-103. I've checked filesystem at both Proxmox server and NAS storage - no errors found. I'm trying to restore backup to a new VM so not to affect running one.
| VMID | NAME | STATUS | TIME | SIZE | FILENAME |
| 102 | VM 102 | OK | 01:52:30 | 255.00GB | /mnt/pve/NAS/dump/vzdump-qemu-102-2020_04_21-00_10_02.vma.lzo |
| 103 | VM 103 | OK | 01:43:58 | 239.28GB | /mnt/pve/NAS/dump/vzdump-qemu-103-2020_04_21-02_02_32.vma.lzo |
TOTAL | 03:36:28 | 494.28GB |
And today's
| VMID | NAME | STATUS | TIME | SIZE | FILENAME |
| 102 | VM 102 | OK | 01:45:35 | 82.50GB | /mnt/pve/NAS/dump/vzdump-qemu-102-2020_04_22-00_10_02.vma.lzo |
| 103 | VM 103 | OK | 01:47:33 | 239.69GB | /mnt/pve/NAS/dump/vzdump-qemu-103-2020_04_22-01_55_38.vma.lzo |
TOTAL | 03:33:09 | 322.19GB |
No significant changes to actual VM size were made. Sometimes VM-102 is ~80Gb and sometimes VM-103. I've checked filesystem at both Proxmox server and NAS storage - no errors found. I'm trying to restore backup to a new VM so not to affect running one.
hmm. from the restore log it looks like the archive is corrupt or wasn't created/compressed correctly.
this could be caused by a couple of things but it's hard to say.
first of all we need output of
to debug you can try a couple of things:
1. try a local backup instead of on NFS
2. try a different compression algorithm
3. try a different backup mode (i.e. stop mode)
we can try to pinpoint whats going wrong from there
this could be caused by a couple of things but it's hard to say.
first of all we need output of
pveversion -vto debug you can try a couple of things:
1. try a local backup instead of on NFS
2. try a different compression algorithm
3. try a different backup mode (i.e. stop mode)
we can try to pinpoint whats going wrong from there
As per you logs, you have very high number of sparse for VM 102
status: 100% (637341884416/637341884416), sparse 41%
check their
status: 100% (637341884416/637341884416), sparse 41%
check their
Well, at least it works fine without comression. Backup takes the same time, restore even faster. But the size of backups is, of course, significantly higher. Stop mode doesn't matter. Now trying lzop and local storage, though there is no sense in local backup storage. Gzip is very very slow.
| VMID | NAME | STATUS | TIME | SIZE | FILENAME |
| 102 | VM 102 | OK | 01:47:18 | 350.89GB | /mnt/pve/NAS/dump/vzdump-qemu-102-2020_04_25-00_10_02.vma |
| 103 | VM 103 | OK | 01:45:52 | 366.40GB | /mnt/pve/NAS/dump/vzdump-qemu-103-2020_04_25-01_57_20.vma |
TOTAL | 03:33:10 | 717.29GB |