Proxmox VM Backup

Ahmet Bas · Jul 8, 2021

Hello,

We have configured our Proxmox VE with the Proxmox Backup server. We are not backing up some VMs to the backup server, but the backup size of the VM are the same size as the VM disk of the VM.

Is this expected behavior?

Any help is appreciated.

dcsapak · Jul 8, 2021

Ahmet Bas said:
but the backup size of the VM are the same size as the VM disk of the VM.

what exactly do you mean? could you post an example task log of a backup ?

Ahmet Bas · Jul 8, 2021

dcsapak said:
what exactly do you mean? could you post an example task log of a backup ?

We have the following server configuration on the Proxmox VE:

Code:

cat .../qemu-server/3667.conf
agent: 1
boot: order=ide2;scsi0;net0
cores: 6
cpu: qemu64
ide2: none,media=cdrom
memory: 8192
name: ....
net0: virtio=e2:11:aa:04:70:c4,bridge=vmbr3042,firewall=1,rate=125
numa: 0
ostype: l26
scsi0: ceph:vm-3667-disk-0,cache=unsafe,discard=on,size=400G,ssd=1
scsihw: virtio-scsi-pci
smbios1: ....
sockets: 1
vmgenid: ...

If I check the used data space in ceph I see this:

Code:

# rbd diff rbd/vm-3667-disk-0 | awk '{ SUM += $2 } END { print SUM/1024/1024/1024 " GB" }'

320.028 GB

When I log in with SSH and check the used space in the OS i see this:

Code:

[root@s1 ~]# df -h
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        3.8G     0  3.8G   0% /dev
tmpfs           3.8G  4.0K  3.8G   1% /dev/shm
tmpfs           3.8G  171M  3.7G   5% /run
/dev/sda1       400G  161G  240G  41% /
tmpfs           777M     0  777M   0% /run/user/0

But the used disk space on the backup server is 400GB:

Is Proxmox Backup not compressing the data? The VM can use 400GB disk space and the VM backup is exactly the same size as configured.

dcsapak · Jul 8, 2021

Ahmet Bas said:
Is Proxmox Backup not compressing the data? The VM can use 400GB disk space and the VM backup is exactly the same size as configured.

this is inteded

it shows the size of the uncompressed restorable data (regardless of zeroes/etc.)
to see how much exactly was uploaded, you have to check the task log

since the backups are chunked / deduplicated across the datastore, it is not really possible to assign a 'size' to a single snapshot, because
it will most likely share major parts with earlier/later snapshots as well as similar vm backups

Ahmet Bas · Aug 19, 2021

dcsapak said:
this is inteded

it shows the size of the uncompressed restorable data (regardless of zeroes/etc.)
to see how much exactly was uploaded, you have to check the task log

since the backups are chunked / deduplicated across the datastore, it is not really possible to assign a 'size' to a single snapshot, because
it will most likely share major parts with earlier/later snapshots as well as similar vm backups

Sorry for the late reply Dominik. But the current storage usage of backups is a bit strange for me:

For test, we only backing up a few VMs but the storage usage is a bit strange. It seems like the storage:

The used backup storage seems to be equal to the VM allocated disk storage. It seems like there is no compression? For example, the server with 100 GB backup size does only has a few GB of data, and the backup storage is using 100GB.

>it shows the size of the uncompressed restorable data (regardless of zeroes/etc.)
>to see how much exactly was uploaded, you have to check the task log

But the total size of the backup is also 100G "2021-08-19T01:05:55+02:00: Size: 107374182400". If I use only 5 GB data on the VM I do not want a VM backup that is 100G. So the important question is why is my backup 100G and is there anything to lower this to the actual used storage as the VM? Otherwise I need to have 100GB space which is overkill.

oversite · Aug 20, 2021

Ahmet Bas said:
Sorry for the late reply Dominik. But the current storage usage of backups is a bit strange for me:

For test, we only backing up a few VMs but the storage usage is a bit strange. It seems like the storage:

View attachment 28783

The used backup storage seems to be equal to the VM allocated disk storage. It seems like there is no compression? For example, the server with 100 GB backup size does only has a few GB of data, and the backup storage is using 100GB.

>it shows the size of the uncompressed restorable data (regardless of zeroes/etc.)
>to see how much exactly was uploaded, you have to check the task log

But the total size of the backup is also 100G "2021-08-19T01:05:55+02:00: Size: 107374182400". If I use only 5 GB data on the VM I do not want a VM backup that is 100G. So the important question is why is my backup 100G and is there anything to lower this to the actual used storage as the VM? Otherwise I need to have 100GB space which is overkill.

No, the backup size is not 100GB. Please show the task log backing up the VM.

Ahmet Bas · Aug 20, 2021

oversite said:
No, the backup size is not 100GB. Please show the task log backing up the VM.

Here is the latest VM backup log which I pulled from the PBS:

Code:

2021-08-20T00:45:02+02:00: starting new backup on datastore 'vm-backup': "vm/1389/2021-08-19T22:45:02Z"
2021-08-20T00:45:02+02:00: download 'index.json.blob' from previous backup.
2021-08-20T00:45:02+02:00: register chunks in 'drive-scsi0.img.fidx' from previous backup.
2021-08-20T00:45:02+02:00: download 'drive-scsi0.img.fidx' from previous backup.
2021-08-20T00:45:02+02:00: created new fixed index 1 ("vm/1389/2021-08-19T22:45:02Z/drive-scsi0.img.fidx")
2021-08-20T00:45:02+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/qemu-server.conf.blob" (445 bytes, comp: 445)
2021-08-20T00:45:02+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/fw.conf.blob" (112 bytes, comp: 112)
2021-08-20T00:46:10+02:00: Upload statistics for 'drive-scsi0.img.fidx'
2021-08-20T00:46:10+02:00: UUID: 6346117f40a04673bb57daa56bcd4da5
2021-08-20T00:46:10+02:00: Checksum: 880785f01dab5cbadc858568e6367cd757eeafba9011fcc6289da1e7d4cc2cc0
2021-08-20T00:46:10+02:00: Size: 2143289344
2021-08-20T00:46:10+02:00: Chunk count: 511
2021-08-20T00:46:10+02:00: Upload size: 2139095040 (99%)
2021-08-20T00:46:10+02:00: Duplicates: 1+1 (0%)
2021-08-20T00:46:10+02:00: Compression: 99%
2021-08-20T00:46:10+02:00: successfully closed fixed index 1
2021-08-20T00:46:10+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/index.json.blob" (488 bytes, comp: 488)
2021-08-20T00:46:10+02:00: successfully finished backup
2021-08-20T00:46:10+02:00: backup finished successfully
2021-08-20T00:46:10+02:00: TASK OK

If it's not 100GB why is the VM-backup datastore showing that high in the summary?

oversite · Aug 20, 2021

Ahmet Bas said:

Here is the latest VM backup log which I pulled from the PBS:

Code:

2021-08-20T00:45:02+02:00: starting new backup on datastore 'vm-backup': "vm/1389/2021-08-19T22:45:02Z"
2021-08-20T00:45:02+02:00: download 'index.json.blob' from previous backup.
2021-08-20T00:45:02+02:00: register chunks in 'drive-scsi0.img.fidx' from previous backup.
2021-08-20T00:45:02+02:00: download 'drive-scsi0.img.fidx' from previous backup.
2021-08-20T00:45:02+02:00: created new fixed index 1 ("vm/1389/2021-08-19T22:45:02Z/drive-scsi0.img.fidx")
2021-08-20T00:45:02+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/qemu-server.conf.blob" (445 bytes, comp: 445)
2021-08-20T00:45:02+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/fw.conf.blob" (112 bytes, comp: 112)
2021-08-20T00:46:10+02:00: Upload statistics for 'drive-scsi0.img.fidx'
2021-08-20T00:46:10+02:00: UUID: 6346117f40a04673bb57daa56bcd4da5
2021-08-20T00:46:10+02:00: Checksum: 880785f01dab5cbadc858568e6367cd757eeafba9011fcc6289da1e7d4cc2cc0
2021-08-20T00:46:10+02:00: Size: 2143289344
2021-08-20T00:46:10+02:00: Chunk count: 511
2021-08-20T00:46:10+02:00: Upload size: 2139095040 (99%)
2021-08-20T00:46:10+02:00: Duplicates: 1+1 (0%)
2021-08-20T00:46:10+02:00: Compression: 99%
2021-08-20T00:46:10+02:00: successfully closed fixed index 1
2021-08-20T00:46:10+02:00: add blob "/mnt/datastore/vm-backup/vm/1389/2021-08-19T22:45:02Z/index.json.blob" (488 bytes, comp: 488)
2021-08-20T00:46:10+02:00: successfully finished backup
2021-08-20T00:46:10+02:00: backup finished successfully
2021-08-20T00:46:10+02:00: TASK OK

If it's not 100GB why is the VM-backup datastore showing that high in the summary?

Sorry i meant the backup task log from PVE box, not the PBS log. The size number in the content tab on PBS snapshot list is the size of the backuped disk, not the backup data. Just don't focus on that for the size of backup data. I promise you, the backup data size is low. What do you mean by "showing that high in the summary"?

Ahmet Bas · Aug 20, 2021

oversite said:
Sorry i meant the backup task log from PVE box, not the PBS log. The size number in the content tab on PBS snapshot list is the size of the backuped disk, not the backup data. Just don't focus on that for the size of backup data. I promise you, the backup data size is low. What do you mean by "showing that high in the summary"?

Hereby the PVE task for 1389:

Code:

INFO: Starting Backup of VM 1389 (qemu)
INFO: Backup started at 2021-08-20 00:45:02
INFO: status = running
INFO: VM Name: ws1.example.com
INFO: include disk 'scsi0' 'ceph:vm-1389-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/1389/2021-08-19T22:45:02Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: enabling encryption
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'c91a8af5-c664-4815-a279-4382402ecd89'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (2.0 GiB of 100.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 2.0 GiB dirty of 100.0 GiB total
INFO:   9% (196.0 MiB of 2.0 GiB) in 3s, read: 65.3 MiB/s, write: 64.0 MiB/s
INFO:  19% (400.0 MiB of 2.0 GiB) in 6s, read: 68.0 MiB/s, write: 68.0 MiB/s
INFO:  29% (600.0 MiB of 2.0 GiB) in 9s, read: 66.7 MiB/s, write: 65.3 MiB/s
INFO:  37% (764.0 MiB of 2.0 GiB) in 12s, read: 54.7 MiB/s, write: 54.7 MiB/s
INFO:  41% (840.0 MiB of 2.0 GiB) in 15s, read: 25.3 MiB/s, write: 25.3 MiB/s
INFO:  44% (904.0 MiB of 2.0 GiB) in 18s, read: 21.3 MiB/s, write: 21.3 MiB/s
INFO:  47% (980.0 MiB of 2.0 GiB) in 21s, read: 25.3 MiB/s, write: 25.3 MiB/s
INFO:  57% (1.1 GiB of 2.0 GiB) in 24s, read: 64.0 MiB/s, write: 64.0 MiB/s
INFO:  59% (1.2 GiB of 2.0 GiB) in 28s, read: 9.0 MiB/s, write: 9.0 MiB/s
INFO:  61% (1.2 GiB of 2.0 GiB) in 31s, read: 13.3 MiB/s, write: 13.3 MiB/s
INFO:  68% (1.4 GiB of 2.0 GiB) in 34s, read: 49.3 MiB/s, write: 49.3 MiB/s
INFO:  71% (1.4 GiB of 2.0 GiB) in 37s, read: 22.7 MiB/s, write: 22.7 MiB/s
INFO:  77% (1.5 GiB of 2.0 GiB) in 40s, read: 37.3 MiB/s, write: 37.3 MiB/s
INFO:  80% (1.6 GiB of 2.0 GiB) in 43s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO:  82% (1.7 GiB of 2.0 GiB) in 46s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO:  90% (1.8 GiB of 2.0 GiB) in 49s, read: 48.0 MiB/s, write: 48.0 MiB/s
INFO:  93% (1.9 GiB of 2.0 GiB) in 52s, read: 21.3 MiB/s, write: 21.3 MiB/s
INFO:  97% (1.9 GiB of 2.0 GiB) in 55s, read: 30.7 MiB/s, write: 30.7 MiB/s
INFO: 100% (2.0 GiB of 2.0 GiB) in 58s, read: 16.0 MiB/s, write: 16.0 MiB/s
INFO: backup was done incrementally, reused 98.01 GiB (98%)
INFO: transferred 2.00 GiB in 68 seconds (30.1 MiB/s)
INFO: Finished Backup of VM 1389 (00:01:09)
INFO: Backup finished at 2021-08-20 00:46:11

oversite · Aug 20, 2021

Ahmet Bas said:

Hereby the PVE task for 1389:

Code:

INFO: Starting Backup of VM 1389 (qemu)
INFO: Backup started at 2021-08-20 00:45:02
INFO: status = running
INFO: VM Name: ws1.example.com
INFO: include disk 'scsi0' 'ceph:vm-1389-disk-0' 100G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: snapshots found (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/1389/2021-08-19T22:45:02Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: enabling encryption
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task 'c91a8af5-c664-4815-a279-4382402ecd89'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: OK (2.0 GiB of 100.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 2.0 GiB dirty of 100.0 GiB total
INFO:   9% (196.0 MiB of 2.0 GiB) in 3s, read: 65.3 MiB/s, write: 64.0 MiB/s
INFO:  19% (400.0 MiB of 2.0 GiB) in 6s, read: 68.0 MiB/s, write: 68.0 MiB/s
INFO:  29% (600.0 MiB of 2.0 GiB) in 9s, read: 66.7 MiB/s, write: 65.3 MiB/s
INFO:  37% (764.0 MiB of 2.0 GiB) in 12s, read: 54.7 MiB/s, write: 54.7 MiB/s
INFO:  41% (840.0 MiB of 2.0 GiB) in 15s, read: 25.3 MiB/s, write: 25.3 MiB/s
INFO:  44% (904.0 MiB of 2.0 GiB) in 18s, read: 21.3 MiB/s, write: 21.3 MiB/s
INFO:  47% (980.0 MiB of 2.0 GiB) in 21s, read: 25.3 MiB/s, write: 25.3 MiB/s
INFO:  57% (1.1 GiB of 2.0 GiB) in 24s, read: 64.0 MiB/s, write: 64.0 MiB/s
INFO:  59% (1.2 GiB of 2.0 GiB) in 28s, read: 9.0 MiB/s, write: 9.0 MiB/s
INFO:  61% (1.2 GiB of 2.0 GiB) in 31s, read: 13.3 MiB/s, write: 13.3 MiB/s
INFO:  68% (1.4 GiB of 2.0 GiB) in 34s, read: 49.3 MiB/s, write: 49.3 MiB/s
INFO:  71% (1.4 GiB of 2.0 GiB) in 37s, read: 22.7 MiB/s, write: 22.7 MiB/s
INFO:  77% (1.5 GiB of 2.0 GiB) in 40s, read: 37.3 MiB/s, write: 37.3 MiB/s
INFO:  80% (1.6 GiB of 2.0 GiB) in 43s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO:  82% (1.7 GiB of 2.0 GiB) in 46s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO:  90% (1.8 GiB of 2.0 GiB) in 49s, read: 48.0 MiB/s, write: 48.0 MiB/s
INFO:  93% (1.9 GiB of 2.0 GiB) in 52s, read: 21.3 MiB/s, write: 21.3 MiB/s
INFO:  97% (1.9 GiB of 2.0 GiB) in 55s, read: 30.7 MiB/s, write: 30.7 MiB/s
INFO: 100% (2.0 GiB of 2.0 GiB) in 58s, read: 16.0 MiB/s, write: 16.0 MiB/s
INFO: backup was done incrementally, reused 98.01 GiB (98%)
INFO: transferred 2.00 GiB in 68 seconds (30.1 MiB/s)
INFO: Finished Backup of VM 1389 (00:01:09)
INFO: Backup finished at 2021-08-20 00:46:11

So, the backup data for this snapshot is 2GB, "INFO: transferred 2.00 GiB in 68 seconds (30.1 MiB/s)"

Ahmet Bas · Aug 21, 2021

oversite said:
So, the backup data for this snapshot is 2GB, "INFO: transferred 2.00 GiB in 68 seconds (30.1 MiB/s)"

Ok, so In order to find the actual size, I have to look into the task log. But for example one other Windows machine has the following usage:

Code:

INFO: starting new backup job: vzdump 2708 --remove 0 --storage pbs --mode snapshot --node hv01
INFO: Starting Backup of VM 2708 (qemu)
INFO: Backup started at 2021-08-20 22:06:26
INFO: status = running
INFO: VM Name:
INFO: include disk 'scsi0' 'ceph:vm-2708-disk-1' 200G
INFO: include disk 'scsi1' 'ceph:vm-2708-disk-2' 1000G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: skip unused drive 'ceph:vm-2708-disk-0' (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/2708/2021-08-20T20:06:26Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: enabling encryption
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '614cb6e4-7eea-4d31-88f5-06df5054a5fa'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: created new
INFO: scsi1: dirty-bitmap status: created new
INFO:   0% (388.0 MiB of 1.2 TiB) in 3s, read: 129.3 MiB/s, write: 4.0 MiB/s
INFO:   1% (12.1 GiB of 1.2 TiB) in 49s, read: 261.0 MiB/s, write: 3.3 MiB/s
INFO:   2% (24.1 GiB of 1.2 TiB) in 2m 28s, read: 123.7 MiB/s, write: 248.2 KiB/s
INFO:   3% (36.1 GiB of 1.2 TiB) in 4m 9s, read: 121.6 MiB/s, write: 0 B/s
INFO:   4% (48.0 GiB of 1.2 TiB) in 5m 49s, read: 122.4 MiB/s, write: 0 B/s
INFO:   5% (60.0 GiB of 1.2 TiB) in 7m 29s, read: 123.1 MiB/s, write: 0 B/s
INFO:   6% (72.0 GiB of 1.2 TiB) in 9m 2s, read: 131.9 MiB/s, write: 220.2 KiB/s
INFO:   7% (84.2 GiB of 1.2 TiB) in 10m 36s, read: 132.7 MiB/s, write: 0 B/s
INFO:   8% (96.1 GiB of 1.2 TiB) in 12m 8s, read: 132.2 MiB/s, write: 44.5 KiB/s
INFO:   9% (108.1 GiB of 1.2 TiB) in 13m 28s, read: 154.3 MiB/s, write: 102.4 KiB/s
INFO:  10% (120.0 GiB of 1.2 TiB) in 14m 26s, read: 210.2 MiB/s, write: 70.6 KiB/s
INFO:  11% (132.1 GiB of 1.2 TiB) in 15m 30s, read: 193.6 MiB/s, write: 128.0 KiB/s
INFO:  12% (144.0 GiB of 1.2 TiB) in 17m 4s, read: 129.9 MiB/s, write: 2.6 MiB/s
INFO:  13% (156.0 GiB of 1.2 TiB) in 18m 13s, read: 178.1 MiB/s, write: 14.8 MiB/s
INFO:  14% (168.0 GiB of 1.2 TiB) in 19m 52s, read: 123.7 MiB/s, write: 41.4 KiB/s
INFO:  15% (180.1 GiB of 1.2 TiB) in 20m 23s, read: 397.9 MiB/s, write: 132.1 KiB/s
INFO:  16% (192.0 GiB of 1.2 TiB) in 21m 53s, read: 136.1 MiB/s, write: 546.1 KiB/s
INFO:  17% (204.0 GiB of 1.2 TiB) in 23m 27s, read: 130.8 MiB/s, write: 130.7 KiB/s
INFO:  18% (216.0 GiB of 1.2 TiB) in 24m 56s, read: 138.2 MiB/s, write: 0 B/s
INFO:  19% (228.0 GiB of 1.2 TiB) in 26m 1s, read: 188.9 MiB/s, write: 3.9 MiB/s
INFO:  20% (240.1 GiB of 1.2 TiB) in 27m 41s, read: 123.2 MiB/s, write: 0 B/s
INFO:  21% (252.1 GiB of 1.2 TiB) in 28m 49s, read: 180.9 MiB/s, write: 60.2 KiB/s
INFO:  22% (268.4 GiB of 1.2 TiB) in 29m 14s, read: 670.6 MiB/s, write: 1.3 MiB/s
INFO:  23% (276.2 GiB of 1.2 TiB) in 29m 41s, read: 295.7 MiB/s, write: 72.9 MiB/s
INFO:  24% (290.4 GiB of 1.2 TiB) in 29m 44s, read: 4.7 GiB/s, write: 8.0 MiB/s
INFO:  25% (304.7 GiB of 1.2 TiB) in 29m 47s, read: 4.8 GiB/s, write: 0 B/s
INFO:  26% (314.0 GiB of 1.2 TiB) in 29m 51s, read: 2.3 GiB/s, write: 32.0 MiB/s
INFO:  27% (324.1 GiB of 1.2 TiB) in 30m 31s, read: 259.4 MiB/s, write: 2.4 MiB/s
INFO:  28% (339.7 GiB of 1.2 TiB) in 31m 7s, read: 441.9 MiB/s, write: 9.0 MiB/s
INFO:  29% (350.9 GiB of 1.2 TiB) in 31m 10s, read: 3.8 GiB/s, write: 29.3 MiB/s
INFO:  30% (366.8 GiB of 1.2 TiB) in 31m 13s, read: 5.3 GiB/s, write: 0 B/s
INFO:  31% (383.7 GiB of 1.2 TiB) in 31m 16s, read: 5.6 GiB/s, write: 1.3 MiB/s
INFO:  33% (400.4 GiB of 1.2 TiB) in 31m 19s, read: 5.6 GiB/s, write: 0 B/s
INFO:  34% (417.0 GiB of 1.2 TiB) in 31m 22s, read: 5.5 GiB/s, write: 0 B/s
INFO:  35% (428.4 GiB of 1.2 TiB) in 31m 25s, read: 3.8 GiB/s, write: 1.3 MiB/s
INFO:  36% (432.1 GiB of 1.2 TiB) in 31m 57s, read: 119.5 MiB/s, write: 6.8 MiB/s
INFO:  37% (444.1 GiB of 1.2 TiB) in 33m 24s, read: 140.8 MiB/s, write: 141.2 KiB/s
INFO:  38% (456.0 GiB of 1.2 TiB) in 35m 4s, read: 122.6 MiB/s, write: 0 B/s
INFO:  39% (468.0 GiB of 1.2 TiB) in 36m 45s, read: 121.5 MiB/s, write: 0 B/s
INFO:  40% (480.1 GiB of 1.2 TiB) in 38m 25s, read: 123.5 MiB/s, write: 0 B/s
INFO:  41% (494.2 GiB of 1.2 TiB) in 39m 24s, read: 244.5 MiB/s, write: 138.8 KiB/s
INFO:  42% (504.3 GiB of 1.2 TiB) in 40m 42s, read: 133.3 MiB/s, write: 31.6 MiB/s
INFO:  43% (520.2 GiB of 1.2 TiB) in 40m 45s, read: 5.3 GiB/s, write: 0 B/s
INFO:  44% (537.1 GiB of 1.2 TiB) in 40m 48s, read: 5.6 GiB/s, write: 0 B/s
INFO:  45% (548.1 GiB of 1.2 TiB) in 40m 51s, read: 3.7 GiB/s, write: 0 B/s
INFO:  46% (563.6 GiB of 1.2 TiB) in 40m 54s, read: 5.2 GiB/s, write: 0 B/s
INFO:  48% (580.7 GiB of 1.2 TiB) in 40m 57s, read: 5.7 GiB/s, write: 0 B/s
INFO:  49% (596.7 GiB of 1.2 TiB) in 41m, read: 5.3 GiB/s, write: 0 B/s
INFO:  51% (612.8 GiB of 1.2 TiB) in 41m 3s, read: 5.4 GiB/s, write: 0 B/s
INFO:  52% (628.2 GiB of 1.2 TiB) in 41m 6s, read: 5.1 GiB/s, write: 0 B/s
INFO:  53% (645.0 GiB of 1.2 TiB) in 41m 9s, read: 5.6 GiB/s, write: 0 B/s
INFO:  55% (662.1 GiB of 1.2 TiB) in 41m 12s, read: 5.7 GiB/s, write: 0 B/s
INFO:  56% (677.7 GiB of 1.2 TiB) in 41m 15s, read: 5.2 GiB/s, write: 0 B/s
INFO:  57% (694.5 GiB of 1.2 TiB) in 41m 18s, read: 5.6 GiB/s, write: 0 B/s
INFO:  59% (710.3 GiB of 1.2 TiB) in 41m 21s, read: 5.3 GiB/s, write: 0 B/s
INFO:  60% (727.2 GiB of 1.2 TiB) in 41m 24s, read: 5.6 GiB/s, write: 0 B/s
INFO:  62% (744.0 GiB of 1.2 TiB) in 41m 27s, read: 5.6 GiB/s, write: 0 B/s
INFO:  63% (759.6 GiB of 1.2 TiB) in 41m 30s, read: 5.2 GiB/s, write: 0 B/s
INFO:  64% (776.5 GiB of 1.2 TiB) in 41m 33s, read: 5.6 GiB/s, write: 0 B/s
INFO:  66% (792.1 GiB of 1.2 TiB) in 41m 36s, read: 5.2 GiB/s, write: 0 B/s
INFO:  67% (807.6 GiB of 1.2 TiB) in 41m 39s, read: 5.2 GiB/s, write: 0 B/s
INFO:  68% (823.9 GiB of 1.2 TiB) in 41m 42s, read: 5.4 GiB/s, write: 0 B/s
INFO:  70% (840.2 GiB of 1.2 TiB) in 41m 45s, read: 5.4 GiB/s, write: 0 B/s
INFO:  71% (855.2 GiB of 1.2 TiB) in 41m 48s, read: 5.0 GiB/s, write: 0 B/s
INFO:  72% (871.9 GiB of 1.2 TiB) in 41m 51s, read: 5.6 GiB/s, write: 0 B/s
INFO:  74% (888.8 GiB of 1.2 TiB) in 41m 54s, read: 5.6 GiB/s, write: 0 B/s
INFO:  75% (905.1 GiB of 1.2 TiB) in 41m 57s, read: 5.4 GiB/s, write: 0 B/s
INFO:  76% (922.1 GiB of 1.2 TiB) in 42m, read: 5.7 GiB/s, write: 0 B/s
INFO:  78% (937.9 GiB of 1.2 TiB) in 42m 3s, read: 5.3 GiB/s, write: 0 B/s
INFO:  79% (954.1 GiB of 1.2 TiB) in 42m 6s, read: 5.4 GiB/s, write: 0 B/s
INFO:  80% (969.9 GiB of 1.2 TiB) in 42m 9s, read: 5.3 GiB/s, write: 0 B/s
INFO:  82% (986.7 GiB of 1.2 TiB) in 42m 12s, read: 5.6 GiB/s, write: 0 B/s
INFO:  83% (1000.0 GiB of 1.2 TiB) in 42m 15s, read: 4.5 GiB/s, write: 12.0 MiB/s
INFO:  84% (1008.0 GiB of 1.2 TiB) in 43m 28s, read: 111.8 MiB/s, write: 65.9 MiB/s
INFO:  85% (1020.1 GiB of 1.2 TiB) in 45m 27s, read: 103.7 MiB/s, write: 79.2 MiB/s
INFO:  86% (1.0 TiB of 1.2 TiB) in 47m 4s, read: 128.1 MiB/s, write: 65.2 MiB/s
INFO:  87% (1.0 TiB of 1.2 TiB) in 48m 22s, read: 155.9 MiB/s, write: 21.1 MiB/s
INFO:  88% (1.0 TiB of 1.2 TiB) in 50m, read: 126.2 MiB/s, write: 72.8 MiB/s
INFO:  89% (1.0 TiB of 1.2 TiB) in 51m 19s, read: 160.7 MiB/s, write: 70.9 MiB/s
INFO:  90% (1.1 TiB of 1.2 TiB) in 52m 8s, read: 306.9 MiB/s, write: 67.5 MiB/s
INFO:  91% (1.1 TiB of 1.2 TiB) in 52m 24s, read: 581.2 MiB/s, write: 64.2 MiB/s
INFO:  92% (1.1 TiB of 1.2 TiB) in 52m 42s, read: 846.0 MiB/s, write: 58.2 MiB/s
INFO:  93% (1.1 TiB of 1.2 TiB) in 52m 48s, read: 1.5 GiB/s, write: 63.3 MiB/s
INFO:  94% (1.1 TiB of 1.2 TiB) in 52m 52s, read: 4.0 GiB/s, write: 25.0 MiB/s
INFO:  95% (1.1 TiB of 1.2 TiB) in 52m 55s, read: 5.1 GiB/s, write: 0 B/s
INFO:  96% (1.1 TiB of 1.2 TiB) in 52m 58s, read: 4.6 GiB/s, write: 0 B/s
INFO:  98% (1.1 TiB of 1.2 TiB) in 53m 1s, read: 5.2 GiB/s, write: 0 B/s
INFO:  99% (1.2 TiB of 1.2 TiB) in 53m 4s, read: 5.1 GiB/s, write: 0 B/s
INFO: 100% (1.2 TiB of 1.2 TiB) in 53m 6s, read: 3.9 GiB/s, write: 0 B/s
INFO: backup is sparse: 854.13 GiB (71%) total zero data
INFO: backup was done incrementally, reused 1.13 TiB (96%)
INFO: transferred 1.17 TiB in 3186 seconds (385.7 MiB/s)
INFO: Finished Backup of VM 2708 (00:53:10)
INFO: Backup finished at 2021-08-20 22:59:36
INFO: Backup job finished successfully
TASK OK

In this log you will see that this VM is using more backup space the required.

Ahmet Bas · Aug 21, 2021

dcsapak said:
this is inteded

it shows the size of the uncompressed restorable data (regardless of zeroes/etc.)
to see how much exactly was uploaded, you have to check the task log

since the backups are chunked / deduplicated across the datastore, it is not really possible to assign a 'size' to a single snapshot, because
it will most likely share major parts with earlier/later snapshots as well as similar vm backups

You help me a few weeks ago, this also intended that the windows VM is using more space than on the PVE?

oversite · Aug 21, 2021

Ahmet Bas said:

Ok, so In order to find the actual size, I have to look into the task log. But for example one other Windows machine has the following usage:

Code:

INFO: starting new backup job: vzdump 2708 --remove 0 --storage pbs --mode snapshot --node hv01
INFO: Starting Backup of VM 2708 (qemu)
INFO: Backup started at 2021-08-20 22:06:26
INFO: status = running
INFO: VM Name:
INFO: include disk 'scsi0' 'ceph:vm-2708-disk-1' 200G
INFO: include disk 'scsi1' 'ceph:vm-2708-disk-2' 1000G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: skip unused drive 'ceph:vm-2708-disk-0' (not included into backup)
INFO: creating Proxmox Backup Server archive 'vm/2708/2021-08-20T20:06:26Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: enabling encryption
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '614cb6e4-7eea-4d31-88f5-06df5054a5fa'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: created new
INFO: scsi1: dirty-bitmap status: created new
INFO:   0% (388.0 MiB of 1.2 TiB) in 3s, read: 129.3 MiB/s, write: 4.0 MiB/s
INFO:   1% (12.1 GiB of 1.2 TiB) in 49s, read: 261.0 MiB/s, write: 3.3 MiB/s
INFO:   2% (24.1 GiB of 1.2 TiB) in 2m 28s, read: 123.7 MiB/s, write: 248.2 KiB/s
INFO:   3% (36.1 GiB of 1.2 TiB) in 4m 9s, read: 121.6 MiB/s, write: 0 B/s
INFO:   4% (48.0 GiB of 1.2 TiB) in 5m 49s, read: 122.4 MiB/s, write: 0 B/s
INFO:   5% (60.0 GiB of 1.2 TiB) in 7m 29s, read: 123.1 MiB/s, write: 0 B/s
INFO:   6% (72.0 GiB of 1.2 TiB) in 9m 2s, read: 131.9 MiB/s, write: 220.2 KiB/s
INFO:   7% (84.2 GiB of 1.2 TiB) in 10m 36s, read: 132.7 MiB/s, write: 0 B/s
INFO:   8% (96.1 GiB of 1.2 TiB) in 12m 8s, read: 132.2 MiB/s, write: 44.5 KiB/s
INFO:   9% (108.1 GiB of 1.2 TiB) in 13m 28s, read: 154.3 MiB/s, write: 102.4 KiB/s
INFO:  10% (120.0 GiB of 1.2 TiB) in 14m 26s, read: 210.2 MiB/s, write: 70.6 KiB/s
INFO:  11% (132.1 GiB of 1.2 TiB) in 15m 30s, read: 193.6 MiB/s, write: 128.0 KiB/s
INFO:  12% (144.0 GiB of 1.2 TiB) in 17m 4s, read: 129.9 MiB/s, write: 2.6 MiB/s
INFO:  13% (156.0 GiB of 1.2 TiB) in 18m 13s, read: 178.1 MiB/s, write: 14.8 MiB/s
INFO:  14% (168.0 GiB of 1.2 TiB) in 19m 52s, read: 123.7 MiB/s, write: 41.4 KiB/s
INFO:  15% (180.1 GiB of 1.2 TiB) in 20m 23s, read: 397.9 MiB/s, write: 132.1 KiB/s
INFO:  16% (192.0 GiB of 1.2 TiB) in 21m 53s, read: 136.1 MiB/s, write: 546.1 KiB/s
INFO:  17% (204.0 GiB of 1.2 TiB) in 23m 27s, read: 130.8 MiB/s, write: 130.7 KiB/s
INFO:  18% (216.0 GiB of 1.2 TiB) in 24m 56s, read: 138.2 MiB/s, write: 0 B/s
INFO:  19% (228.0 GiB of 1.2 TiB) in 26m 1s, read: 188.9 MiB/s, write: 3.9 MiB/s
INFO:  20% (240.1 GiB of 1.2 TiB) in 27m 41s, read: 123.2 MiB/s, write: 0 B/s
INFO:  21% (252.1 GiB of 1.2 TiB) in 28m 49s, read: 180.9 MiB/s, write: 60.2 KiB/s
INFO:  22% (268.4 GiB of 1.2 TiB) in 29m 14s, read: 670.6 MiB/s, write: 1.3 MiB/s
INFO:  23% (276.2 GiB of 1.2 TiB) in 29m 41s, read: 295.7 MiB/s, write: 72.9 MiB/s
INFO:  24% (290.4 GiB of 1.2 TiB) in 29m 44s, read: 4.7 GiB/s, write: 8.0 MiB/s
INFO:  25% (304.7 GiB of 1.2 TiB) in 29m 47s, read: 4.8 GiB/s, write: 0 B/s
INFO:  26% (314.0 GiB of 1.2 TiB) in 29m 51s, read: 2.3 GiB/s, write: 32.0 MiB/s
INFO:  27% (324.1 GiB of 1.2 TiB) in 30m 31s, read: 259.4 MiB/s, write: 2.4 MiB/s
INFO:  28% (339.7 GiB of 1.2 TiB) in 31m 7s, read: 441.9 MiB/s, write: 9.0 MiB/s
INFO:  29% (350.9 GiB of 1.2 TiB) in 31m 10s, read: 3.8 GiB/s, write: 29.3 MiB/s
INFO:  30% (366.8 GiB of 1.2 TiB) in 31m 13s, read: 5.3 GiB/s, write: 0 B/s
INFO:  31% (383.7 GiB of 1.2 TiB) in 31m 16s, read: 5.6 GiB/s, write: 1.3 MiB/s
INFO:  33% (400.4 GiB of 1.2 TiB) in 31m 19s, read: 5.6 GiB/s, write: 0 B/s
INFO:  34% (417.0 GiB of 1.2 TiB) in 31m 22s, read: 5.5 GiB/s, write: 0 B/s
INFO:  35% (428.4 GiB of 1.2 TiB) in 31m 25s, read: 3.8 GiB/s, write: 1.3 MiB/s
INFO:  36% (432.1 GiB of 1.2 TiB) in 31m 57s, read: 119.5 MiB/s, write: 6.8 MiB/s
INFO:  37% (444.1 GiB of 1.2 TiB) in 33m 24s, read: 140.8 MiB/s, write: 141.2 KiB/s
INFO:  38% (456.0 GiB of 1.2 TiB) in 35m 4s, read: 122.6 MiB/s, write: 0 B/s
INFO:  39% (468.0 GiB of 1.2 TiB) in 36m 45s, read: 121.5 MiB/s, write: 0 B/s
INFO:  40% (480.1 GiB of 1.2 TiB) in 38m 25s, read: 123.5 MiB/s, write: 0 B/s
INFO:  41% (494.2 GiB of 1.2 TiB) in 39m 24s, read: 244.5 MiB/s, write: 138.8 KiB/s
INFO:  42% (504.3 GiB of 1.2 TiB) in 40m 42s, read: 133.3 MiB/s, write: 31.6 MiB/s
INFO:  43% (520.2 GiB of 1.2 TiB) in 40m 45s, read: 5.3 GiB/s, write: 0 B/s
INFO:  44% (537.1 GiB of 1.2 TiB) in 40m 48s, read: 5.6 GiB/s, write: 0 B/s
INFO:  45% (548.1 GiB of 1.2 TiB) in 40m 51s, read: 3.7 GiB/s, write: 0 B/s
INFO:  46% (563.6 GiB of 1.2 TiB) in 40m 54s, read: 5.2 GiB/s, write: 0 B/s
INFO:  48% (580.7 GiB of 1.2 TiB) in 40m 57s, read: 5.7 GiB/s, write: 0 B/s
INFO:  49% (596.7 GiB of 1.2 TiB) in 41m, read: 5.3 GiB/s, write: 0 B/s
INFO:  51% (612.8 GiB of 1.2 TiB) in 41m 3s, read: 5.4 GiB/s, write: 0 B/s
INFO:  52% (628.2 GiB of 1.2 TiB) in 41m 6s, read: 5.1 GiB/s, write: 0 B/s
INFO:  53% (645.0 GiB of 1.2 TiB) in 41m 9s, read: 5.6 GiB/s, write: 0 B/s
INFO:  55% (662.1 GiB of 1.2 TiB) in 41m 12s, read: 5.7 GiB/s, write: 0 B/s
INFO:  56% (677.7 GiB of 1.2 TiB) in 41m 15s, read: 5.2 GiB/s, write: 0 B/s
INFO:  57% (694.5 GiB of 1.2 TiB) in 41m 18s, read: 5.6 GiB/s, write: 0 B/s
INFO:  59% (710.3 GiB of 1.2 TiB) in 41m 21s, read: 5.3 GiB/s, write: 0 B/s
INFO:  60% (727.2 GiB of 1.2 TiB) in 41m 24s, read: 5.6 GiB/s, write: 0 B/s
INFO:  62% (744.0 GiB of 1.2 TiB) in 41m 27s, read: 5.6 GiB/s, write: 0 B/s
INFO:  63% (759.6 GiB of 1.2 TiB) in 41m 30s, read: 5.2 GiB/s, write: 0 B/s
INFO:  64% (776.5 GiB of 1.2 TiB) in 41m 33s, read: 5.6 GiB/s, write: 0 B/s
INFO:  66% (792.1 GiB of 1.2 TiB) in 41m 36s, read: 5.2 GiB/s, write: 0 B/s
INFO:  67% (807.6 GiB of 1.2 TiB) in 41m 39s, read: 5.2 GiB/s, write: 0 B/s
INFO:  68% (823.9 GiB of 1.2 TiB) in 41m 42s, read: 5.4 GiB/s, write: 0 B/s
INFO:  70% (840.2 GiB of 1.2 TiB) in 41m 45s, read: 5.4 GiB/s, write: 0 B/s
INFO:  71% (855.2 GiB of 1.2 TiB) in 41m 48s, read: 5.0 GiB/s, write: 0 B/s
INFO:  72% (871.9 GiB of 1.2 TiB) in 41m 51s, read: 5.6 GiB/s, write: 0 B/s
INFO:  74% (888.8 GiB of 1.2 TiB) in 41m 54s, read: 5.6 GiB/s, write: 0 B/s
INFO:  75% (905.1 GiB of 1.2 TiB) in 41m 57s, read: 5.4 GiB/s, write: 0 B/s
INFO:  76% (922.1 GiB of 1.2 TiB) in 42m, read: 5.7 GiB/s, write: 0 B/s
INFO:  78% (937.9 GiB of 1.2 TiB) in 42m 3s, read: 5.3 GiB/s, write: 0 B/s
INFO:  79% (954.1 GiB of 1.2 TiB) in 42m 6s, read: 5.4 GiB/s, write: 0 B/s
INFO:  80% (969.9 GiB of 1.2 TiB) in 42m 9s, read: 5.3 GiB/s, write: 0 B/s
INFO:  82% (986.7 GiB of 1.2 TiB) in 42m 12s, read: 5.6 GiB/s, write: 0 B/s
INFO:  83% (1000.0 GiB of 1.2 TiB) in 42m 15s, read: 4.5 GiB/s, write: 12.0 MiB/s
INFO:  84% (1008.0 GiB of 1.2 TiB) in 43m 28s, read: 111.8 MiB/s, write: 65.9 MiB/s
INFO:  85% (1020.1 GiB of 1.2 TiB) in 45m 27s, read: 103.7 MiB/s, write: 79.2 MiB/s
INFO:  86% (1.0 TiB of 1.2 TiB) in 47m 4s, read: 128.1 MiB/s, write: 65.2 MiB/s
INFO:  87% (1.0 TiB of 1.2 TiB) in 48m 22s, read: 155.9 MiB/s, write: 21.1 MiB/s
INFO:  88% (1.0 TiB of 1.2 TiB) in 50m, read: 126.2 MiB/s, write: 72.8 MiB/s
INFO:  89% (1.0 TiB of 1.2 TiB) in 51m 19s, read: 160.7 MiB/s, write: 70.9 MiB/s
INFO:  90% (1.1 TiB of 1.2 TiB) in 52m 8s, read: 306.9 MiB/s, write: 67.5 MiB/s
INFO:  91% (1.1 TiB of 1.2 TiB) in 52m 24s, read: 581.2 MiB/s, write: 64.2 MiB/s
INFO:  92% (1.1 TiB of 1.2 TiB) in 52m 42s, read: 846.0 MiB/s, write: 58.2 MiB/s
INFO:  93% (1.1 TiB of 1.2 TiB) in 52m 48s, read: 1.5 GiB/s, write: 63.3 MiB/s
INFO:  94% (1.1 TiB of 1.2 TiB) in 52m 52s, read: 4.0 GiB/s, write: 25.0 MiB/s
INFO:  95% (1.1 TiB of 1.2 TiB) in 52m 55s, read: 5.1 GiB/s, write: 0 B/s
INFO:  96% (1.1 TiB of 1.2 TiB) in 52m 58s, read: 4.6 GiB/s, write: 0 B/s
INFO:  98% (1.1 TiB of 1.2 TiB) in 53m 1s, read: 5.2 GiB/s, write: 0 B/s
INFO:  99% (1.2 TiB of 1.2 TiB) in 53m 4s, read: 5.1 GiB/s, write: 0 B/s
INFO: 100% (1.2 TiB of 1.2 TiB) in 53m 6s, read: 3.9 GiB/s, write: 0 B/s
INFO: backup is sparse: 854.13 GiB (71%) total zero data
INFO: backup was done incrementally, reused 1.13 TiB (96%)
INFO: transferred 1.17 TiB in 3186 seconds (385.7 MiB/s)
INFO: Finished Backup of VM 2708 (00:53:10)
INFO: Backup finished at 2021-08-20 22:59:36
INFO: Backup job finished successfully
TASK OK

View attachment 28809In this log you will see that this VM is using more backup space the required.

Wow, that is indeed unexpected, for this snapshot, it would be interesting to see the "index.json.blob" file on the PBS and the PBS log for this run.

Ahmet Bas · Aug 21, 2021

oversite said:
Wow, that is indeed unexpected, for this snapshot, it would be interesting to see the "index.json.blob" file on the PBS and the PBS log for this run.

It is indeed unexpected, what should be interesting to see of the index.json.blog?

oversite · Aug 22, 2021

Ahmet Bas said:
It is indeed unexpected, what should be interesting to see of the index.json.blog?

The content?

Sourcenux · Aug 23, 2021

Ahmet Bas said:
this also intended that the windows VM is using more space than on the PVE?

Did you enable "discard" on these vm-disks? If not: Enable it and wait some time. Windows should automatically free up this formerly used space.

Ahmet Bas · Aug 23, 2021

oversite said:
The content?

Hereby the content:

Code:

{
  "backup-id": "2708",
  "backup-time": 1627641873,
  "backup-type": "vm",
  "files": [
    {
      "crypt-mode": "encrypt",
      "csum": "...",
      "filename": "qemu-server.conf.blob",
      "size": 495
    },
    {
      "crypt-mode": "encrypt",
      "csum": "...",
      "filename": "drive-scsi1.img.fidx",
      "size": 1073741824000
    },
    {
      "crypt-mode": "encrypt",
      "csum": "...",
      "filename": "drive-scsi0.img.fidx",
      "size": 214748364800
    }
  ],
  "signature": "...",
  "unprotected": {
    "chunk_upload_stats": {
      "compressed_size": 750011486747,
      "count": 196147,
      "duplicates": 102976,
      "size": 822700147676
    },
    "key-fingerprint": "..."
  }
}

For what type of information are we looking?

Sourcenux said:
Did you enable "discard" on these vm-disks? If not: Enable it and wait some time. Windows should automatically free up this formerly used space.

Yes it is, on our Ceph storage we see the actual usage. Hereby the vm config:

Code:

agent: 1,fstrim_cloned_disks=1
boot: order=scsi0;ide2;net0
cores: 4
ide2: none,media=cdrom
memory: 8192
name: vm2708
net0: ...
net1: ...
net2: ...
net3: ...
net4: ...
net5: ...
numa: 1
ostype: win10
scsi0: ceph:vm-2708-disk-1,cache=unsafe,discard=on,size=200G,ssd=1
scsi1: ceph:vm-2708-disk-2,cache=unsafe,discard=on,size=1000G,ssd=1
scsihw: virtio-scsi-pci
smbios1: ...
sockets: 2
unused0: ceph:vm-2708-disk-0
vmgenid: ...

Search

Search

Proxmox VM Backup

Ahmet Bas

Well-Known Member

dcsapak

Proxmox Staff Member

Ahmet Bas

Well-Known Member

Attachments

dcsapak

Proxmox Staff Member

Ahmet Bas

Well-Known Member

oversite

Renowned Member

Ahmet Bas

Well-Known Member

oversite

Renowned Member

Ahmet Bas

Well-Known Member

oversite

Renowned Member

Ahmet Bas

Well-Known Member

Ahmet Bas

Well-Known Member

oversite

Renowned Member

Ahmet Bas

Well-Known Member

oversite

Renowned Member

Sourcenux

Member

Ahmet Bas

Well-Known Member