[SOLVED] Question on backups with backup disabled on a VM

[Spirog]

hello,
I have a quick question on what actually does this backed VM102 - do if you disable it from backups?

I see below my 2 VM's 100 and 102

100 is on stop mode and gets backed ok.

102 is disabled but shows as if something gets written?

I have it highlighted in Bold below where I am inquiring about what that actually means?

VMID	NAME	STATUS	TIME	SIZE	FILENAME
100	Alma-cP	OK	00:02:07	2.58GB​	/mnt/pve/newbackup/dump/vzdump-qemu-100-2022_04_17-12_32_04.vma.zst
102	ubuntu-cP	OK	00:00:00	0KB​	/mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.vma.zst
TOTAL	00:02:08	2.58GB

Detailed backup logs:

vzdump 100 102 --storage newbackup --node proxmox --prune-backups 'keep-daily=1,keep-last=2,keep-weekly=1' --compress zstd --mailnotification always --mailto href="mailto:server@gmail9(com)target="_blank">server@gmail(com) --quiet 1 --mode snapshot


VM100



100: 2022-04-17 12:32:04 INFO: Starting Backup of VM 100 (qemu)
100: 2022-04-17 12:32:04 INFO: status = stopped
100: 2022-04-17 12:32:04 INFO: backup mode: stop
100: 2022-04-17 12:32:04 INFO: ionice priority: 7
100: 2022-04-17 12:32:04 INFO: VM Name: Alma-cP
100: 2022-04-17 12:32:04 INFO: include disk 'scsi0' 'local-lvm:vm-100-disk-0' 96G
100: 2022-04-17 12:32:04 INFO: creating vzdump archive '/mnt/pve/newbackup/dump/vzdump-qemu-100-2022_04_17-12_32_04.vma.zst'
100: 2022-04-17 12:32:04 INFO: starting kvm to execute backup task
100: 2022-04-17 12:32:06 INFO: started backup task '3ea0705b-c5f9-4655-af9c-1631874b41f4'
100: 2022-04-17 12:32:09 INFO: 1% (1.1 GiB of 96.0 GiB) in 3s, read: 369.8 MiB/s, write: 97.2 MiB/s
100: 2022-04-17 12:32:12 INFO: 4% (4.2 GiB of 96.0 GiB) in 6s, read: 1.1 GiB/s, write: 13.1 MiB/s
100: 2022-04-17 12:32:18 INFO: 5% (4.9 GiB of 96.0 GiB) in 12s, read: 111.8 MiB/s, write: 103.8 MiB/s
100: 2022-04-17 12:32:25 INFO: 6% (5.8 GiB of 96.0 GiB) in 19s, read: 127.9 MiB/s, write: 125.8 MiB/s
100: 2022-04-17 12:32:34 INFO: 7% (6.8 GiB of 96.0 GiB) in 28s, read: 120.4 MiB/s, write: 111.6 MiB/s
100: 2022-04-17 12:32:37 INFO: 10% (10.1 GiB of 96.0 GiB) in 31s, read: 1.1 GiB/s, write: 73.9 MiB/s
100: 2022-04-17 12:32:40 INFO: 11% (11.4 GiB of 96.0 GiB) in 34s, read: 451.9 MiB/s, write: 68.3 MiB/s
100: 2022-04-17 12:32:43 INFO: 12% (11.8 GiB of 96.0 GiB) in 37s, read: 129.3 MiB/s, write: 120.2 MiB/s
100: 2022-04-17 12:32:49 INFO: 13% (12.6 GiB of 96.0 GiB) in 43s, read: 140.2 MiB/s, write: 124.2 MiB/s
100: 2022-04-17 12:32:54 INFO: 15% (14.9 GiB of 96.0 GiB) in 48s, read: 468.3 MiB/s, write: 105.2 MiB/s
100: 2022-04-17 12:32:57 INFO: 18% (18.2 GiB of 96.0 GiB) in 51s, read: 1.1 GiB/s, write: 35.8 MiB/s
100: 2022-04-17 12:33:00 INFO: 19% (18.5 GiB of 96.0 GiB) in 54s, read: 91.8 MiB/s, write: 91.4 MiB/s
100: 2022-04-17 12:33:07 INFO: 20% (19.2 GiB of 96.0 GiB) in 1m 1s, read: 111.9 MiB/s, write: 108.6 MiB/s
100: 2022-04-17 12:33:16 INFO: 21% (20.2 GiB of 96.0 GiB) in 1m 10s, read: 111.2 MiB/s, write: 105.6 MiB/s
100: 2022-04-17 12:33:19 INFO: 26% (25.1 GiB of 96.0 GiB) in 1m 13s, read: 1.6 GiB/s, write: 34.7 MiB/s
100: 2022-04-17 12:33:27 INFO: 27% (25.9 GiB of 96.0 GiB) in 1m 21s, read: 112.8 MiB/s, write: 106.7 MiB/s
100: 2022-04-17 12:33:36 INFO: 28% (27.0 GiB of 96.0 GiB) in 1m 30s, read: 114.8 MiB/s, write: 99.5 MiB/s
100: 2022-04-17 12:33:39 INFO: 32% (31.6 GiB of 96.0 GiB) in 1m 33s, read: 1.6 GiB/s, write: 40.7 MiB/s
100: 2022-04-17 12:33:42 INFO: 38% (37.1 GiB of 96.0 GiB) in 1m 36s, read: 1.8 GiB/s, write: 0 B/s
100: 2022-04-17 12:33:45 INFO: 46% (45.0 GiB of 96.0 GiB) in 1m 39s, read: 2.6 GiB/s, write: 0 B/s
100: 2022-04-17 12:33:48 INFO: 52% (50.3 GiB of 96.0 GiB) in 1m 42s, read: 1.8 GiB/s, write: 0 B/s
100: 2022-04-17 12:33:51 INFO: 60% (58.4 GiB of 96.0 GiB) in 1m 45s, read: 2.7 GiB/s, write: 0 B/s
100: 2022-04-17 12:33:54 INFO: 66% (63.9 GiB of 96.0 GiB) in 1m 48s, read: 1.9 GiB/s, write: 0 B/s
100: 2022-04-17 12:33:57 INFO: 74% (71.6 GiB of 96.0 GiB) in 1m 51s, read: 2.6 GiB/s, write: 0 B/s
100: 2022-04-17 12:34:00 INFO: 80% (76.9 GiB of 96.0 GiB) in 1m 54s, read: 1.8 GiB/s, write: 0 B/s
100: 2022-04-17 12:34:03 INFO: 85% (82.1 GiB of 96.0 GiB) in 1m 57s, read: 1.7 GiB/s, write: 0 B/s
100: 2022-04-17 12:34:06 INFO: 93% (90.0 GiB of 96.0 GiB) in 2m, read: 2.6 GiB/s, write: 0 B/s
100: 2022-04-17 12:34:09 INFO: 99% (95.1 GiB of 96.0 GiB) in 2m 3s, read: 1.7 GiB/s, write: 0 B/s
100: 2022-04-17 12:34:10 INFO: 100% (96.0 GiB of 96.0 GiB) in 2m 4s, read: 885.8 MiB/s, write: 0 B/s
100: 2022-04-17 12:34:10 INFO: backup is sparse: 87.25 GiB (90%) total zero data
100: 2022-04-17 12:34:10 INFO: transferred 96.00 GiB in 124 seconds (792.8 MiB/s)
100: 2022-04-17 12:34:10 INFO: stopping kvm after backup task
100: 2022-04-17 12:34:11 INFO: archive file size: 2.58GB
100: 2022-04-17 12:34:11 INFO: prune older backups with retention: keep-daily=1, keep-last=2, keep-weekly=1
100: 2022-04-17 12:34:11 INFO: removing backup 'newbackup:backup/vzdump-qemu-100-2022_04_14-12_32_03.vma.zst'
100: 2022-04-17 12:34:11 INFO: pruned 1 backup(s) not covered by keep-retention policy
100: 2022-04-17 12:34:11 INFO: Finished Backup of VM 100 (00:02:07)



VM102


102: 2022-04-17 12:34:11 INFO: Starting Backup of VM 102 (qemu)
102: 2022-04-17 12:34:11 INFO: status = stopped
102: 2022-04-17 12:34:11 INFO: backup mode: stop
102: 2022-04-17 12:34:11 INFO: ionice priority: 7
102: 2022-04-17 12:34:11 INFO: VM Name: ubuntu-cP

HERE BELOW SHOWS :backup=no meaning disabled

102: 2022-04-17 12:34:11 INFO: exclude disk 'scsi0' 'local-lvm:vm-102-disk-0' (backup=no)

102: 2022-04-17 12:34:11 INFO: snapshots found (not included into backup)
102: 2022-04-17 12:34:11 INFO: creating vzdump archive '/mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.vma.zst'
102: 2022-04-17 12:34:11 INFO: backup contains no disks

HERE BELOW SEEMS ITS WRITING or trying too ?

102: 2022-04-17 12:34:11 INFO: starting template backup
102: 2022-04-17 12:34:11 INFO: /usr/bin/vma create -v -c /mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.tmp/qemu-server.conf exec:zstd --rsyncable --threads=1 > /mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.vma.dat

102: 2022-04-17 12:34:11 INFO: archive file size: 0KB


102: 2022-04-17 12:34:11 INFO: prune older backups with retention: keep-daily=1, keep-last=2, keep-weekly=1
102: 2022-04-17 12:34:11 INFO: removing backup 'newbackup:backup/vzdump-qemu-102-2022_04_14-12_34_21.vma.zst'
102: 2022-04-17 12:34:11 INFO: pruned 1 backup(s) not covered by keep-retention policy
102: 2022-04-17 12:34:11 INFO: Finished Backup of VM 102 (00:00:00)



- I can see archive files size is 0kb so it did not save anything, but why does it still try and create:

/usr/bin/vma create -v -c /mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.tmp/qemu-server.conf exec:zstd --rsyncable --threads=1 > /mnt/pve/newbackup/dump/vzdump-qemu-102-2022_04_17-12_34_11.vma.dat

thanks I am just trying to understand the logic and learning...

- if we disabled in the VM in GUI via a checkmark for backup .

why it still does all that work ?
and just does not ignore earlier in the process .
if it see disabled even though in scheduler its setup to backup, should it not read first it is disabled then just stop?
or is that basically what its doing but because it has to prune files in runs this process as well ?


thanks so much for your time and reply, sorry but I am learning and just had this question


thanks so much in advance
Kind Regards,
Spiro

 

[leesteken]

I think the VM is backed up (because you asked for it with vzdump 100 102 ...), but the only disk is excluded from the backup and won't be backed up. The VM configuration, which is part of any backup, is backed up (and smaller than 1KB, which is probably the cause of it showing 0).
I have a VM without any disks, and it is backed up when the "backup all VMs" job runs and is about 900 bytes. I think a backup of a VM with all disks excluded is similar.

 

[Spirog]

I think the VM is backed up (because you asked for it with vzdump 100 102 ...), but the only disk is excluded from the backup and won't be backed up. The VM configuration, which is part of any backup, is backed up (and smaller than 1KB, which is probably the cause of it showing 0).
I have a VM without any disks, and it is backed up when the "backup all VMs" job runs and is about 900 bytes. I think a backup of a VM with all disks excluded is similar.

That make more sense now.

thank you very much for your reply

KindRegrds,
Spiro