BACKUP WINDOWS SERVER 2012 R2 NO MORE BACKED INCREMENTAL

julicravo

Renowned Member
Aug 22, 2013
25
0
66
Salvador, Brazil
Folks, I am using the stable version of pbs. I have a windows server 2012 R2 machine, with 400 GB of data. I managed to do the full backup, which took 12 hours on a cloud server. I manage to do 6 incremental backups, I didn't delete anything from the backups. He just doesn't want to do the full-only incrementals now. Has anyone ever experienced this?
 
Bro! How did you do that without a dedicated client?! o_O
 
this windows is a VM, on top of the proxmox. I will try to shut down the server and connect again, but it is strange, because the other virtual machine (linux) is doing incremental backup normally.

Ícone Verificada pela comunidade
 
no, the guest OS potentially receives a sync/freeze request, but that's all it gets. all of the rest happens inside the Qemu process, not the guest itself.

the qemu process keeps track of writes since the last backup with a dirty bitmap. if this bitmap (per disk) is still valid and the previous snapshot still exists on the server side, it will do a fast incremental backup, which means only reading/hashing those parts that have changed. if there is no bitmap, or it has been invalidated (e.g. because the disk size or encryption mode/key have changed), the previous manifest will be downloaded, all of the data will be read and chunked, but only this chunks which are not yet on the server are uploaded (regular incremental mode). if there is no previous manifest, all chunks will be uploaded ('full' mode). in all cases, the server might throw away some of the uploaded chunks if they already exist (e.g., because they are shared over multiple guests/groups in a datastore).

please post a full backup log, it should show some more information about what's going on.
 
I didn't find the full log. I have the first backup after the full and others that follow. I canceled some backups. Show next.

----------------------------------------------------

INFO: starting new backup job: vzdump 100 --remove 0 --storage BKP_NUVEM --node prox01 --mode snapshot
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-16 11:48:42
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-16T14:48:42Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'dcf89a4c-5a7d-4d7b-92e7-a1df363ba458'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: OK (9.7 GiB of 500.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 9.7 GiB dirty of 500.0 GiB total
INFO: 1% (132.0 MiB of 9.7 GiB) in 3s, read: 44.0 MiB/s, write: 44.0 MiB/s
INFO: 2% (200.0 MiB of 9.7 GiB) in 9s, read: 11.3 MiB/s, write: 11.3 MiB/s
INFO: 3% (308.0 MiB of 9.7 GiB) in 13s, read: 27.0 MiB/s, write: 27.0 MiB/s
INFO: 4% (404.0 MiB of 9.7 GiB) in 21s, read: 12.0 MiB/s, write: 11.5 MiB/s
INFO: 5% (512.0 MiB of 9.7 GiB) in 28s, read: 15.4 MiB/s, write: 14.9 MiB/s
INFO: 6% (596.0 MiB of 9.7 GiB) in 33s, read: 16.8 MiB/s, write: 16.8 MiB/s
INFO: 7% (696.0 MiB of 9.7 GiB) in 41s, read: 12.5 MiB/s, write: 12.5 MiB/s
INFO: 8% (804.0 MiB of 9.7 GiB) in 49s, read: 13.5 MiB/s, write: 13.5 MiB/s
INFO: 9% (896.0 MiB of 9.7 GiB) in 56s, read: 13.1 MiB/s, write: 13.1 MiB/s
INFO: 10% (1000.0 MiB of 9.7 GiB) in 1m 3s, read: 14.9 MiB/s, write: 14.9 MiB/s
INFO: 11% (1.1 GiB of 9.7 GiB) in 1m 11s, read: 11.5 MiB/s, write: 11.5 MiB/s
INFO: 12% (1.2 GiB of 9.7 GiB) in 1m 21s, read: 10.0 MiB/s, write: 10.0 MiB/s
INFO: 13% (1.3 GiB of 9.7 GiB) in 1m 31s, read: 10.4 MiB/s, write: 10.4 MiB/s
INFO: 14% (1.4 GiB of 9.7 GiB) in 1m 41s, read: 10.4 MiB/s, write: 10.4 MiB/s
INFO: 15% (1.5 GiB of 9.7 GiB) in 1m 49s, read: 13.0 MiB/s, write: 13.0 MiB/s
INFO: 16% (1.6 GiB of 9.7 GiB) in 1m 57s, read: 12.5 MiB/s, write: 12.5 MiB/s
INFO: 17% (1.7 GiB of 9.7 GiB) in 2m 5s, read: 11.5 MiB/s, write: 11.5 MiB/s
INFO: 18% (1.7 GiB of 9.7 GiB) in 2m 14s, read: 10.2 MiB/s, write: 10.2 MiB/s
INFO: 19% (1.9 GiB of 9.7 GiB) in 2m 20s, read: 18.7 MiB/s, write: 18.7 MiB/s
INFO: 20% (1.9 GiB of 9.7 GiB) in 2m 26s, read: 14.0 MiB/s, write: 14.0 MiB/s
INFO: 21% (2.1 GiB of 9.7 GiB) in 2m 32s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO: 22% (2.1 GiB of 9.7 GiB) in 2m 36s, read: 20.0 MiB/s, write: 20.0 MiB/s
INFO: 23% (2.2 GiB of 9.7 GiB) in 2m 44s, read: 12.5 MiB/s, write: 12.5 MiB/s
INFO: 24% (2.3 GiB of 9.7 GiB) in 2m 54s, read: 10.0 MiB/s, write: 10.0 MiB/s
INFO: 25% (2.4 GiB of 9.7 GiB) in 3m 6s, read: 8.3 MiB/s, write: 8.3 MiB/s
INFO: 26% (2.5 GiB of 9.7 GiB) in 3m 15s, read: 10.7 MiB/s, write: 10.7 MiB/s
INFO: 27% (2.6 GiB of 9.7 GiB) in 3m 23s, read: 13.5 MiB/s, write: 13.5 MiB/s
INFO: 28% (2.7 GiB of 9.7 GiB) in 3m 29s, read: 15.3 MiB/s, write: 15.3 MiB/s
INFO: 29% (2.8 GiB of 9.7 GiB) in 3m 36s, read: 14.9 MiB/s, write: 14.9 MiB/s
INFO: 30% (2.9 GiB of 9.7 GiB) in 3m 43s, read: 14.3 MiB/s, write: 13.7 MiB/s
INFO: 31% (3.0 GiB of 9.7 GiB) in 3m 49s, read: 15.3 MiB/s, write: 15.3 MiB/s
INFO: 32% (3.1 GiB of 9.7 GiB) in 3m 56s, read: 15.4 MiB/s, write: 15.4 MiB/s
INFO: 33% (3.2 GiB of 9.7 GiB) in 4m 3s, read: 14.3 MiB/s, write: 14.3 MiB/s
INFO: 34% (3.3 GiB of 9.7 GiB) in 4m 10s, read: 13.7 MiB/s, write: 13.7 MiB/s
INFO: 35% (3.4 GiB of 9.7 GiB) in 4m 16s, read: 16.0 MiB/s, write: 15.3 MiB/s
INFO: 36% (3.5 GiB of 9.7 GiB) in 4m 22s, read: 16.0 MiB/s, write: 16.0 MiB/s
INFO: 37% (3.6 GiB of 9.7 GiB) in 4m 31s, read: 12.0 MiB/s, write: 12.0 MiB/s
INFO: 38% (3.7 GiB of 9.7 GiB) in 4m 38s, read: 13.7 MiB/s, write: 13.7 MiB/s
INFO: 39% (3.8 GiB of 9.7 GiB) in 4m 45s, read: 14.9 MiB/s, write: 14.9 MiB/s
INFO: 40% (3.9 GiB of 9.7 GiB) in 4m 51s, read: 16.0 MiB/s, write: 13.3 MiB/s
INFO: 41% (4.0 GiB of 9.7 GiB) in 4m 58s, read: 14.9 MiB/s, write: 14.9 MiB/s
INFO: 42% (4.1 GiB of 9.7 GiB) in 5m 4s, read: 14.7 MiB/s, write: 14.7 MiB/s
INFO: 43% (4.2 GiB of 9.7 GiB) in 5m 11s, read: 14.3 MiB/s, write: 14.3 MiB/s
INFO: 44% (4.3 GiB of 9.7 GiB) in 5m 19s, read: 15.0 MiB/s, write: 15.0 MiB/s
INFO: 45% (4.4 GiB of 9.7 GiB) in 5m 24s, read: 17.6 MiB/s, write: 17.6 MiB/s
INFO: 46% (4.5 GiB of 9.7 GiB) in 5m 32s, read: 12.0 MiB/s, write: 12.0 MiB/s
INFO: 47% (4.6 GiB of 9.7 GiB) in 5m 39s, read: 13.7 MiB/s, write: 13.7 MiB/s
INFO: 48% (4.7 GiB of 9.7 GiB) in 5m 45s, read: 17.3 MiB/s, write: 17.3 MiB/s
INFO: 49% (4.8 GiB of 9.7 GiB) in 5m 51s, read: 15.3 MiB/s, write: 15.3 MiB/s
INFO: 50% (4.9 GiB of 9.7 GiB) in 5m 58s, read: 15.4 MiB/s, write: 15.4 MiB/s
INFO: 51% (5.0 GiB of 9.7 GiB) in 6m 5s, read: 15.4 MiB/s, write: 15.4 MiB/s
INFO: 52% (5.0 GiB of 9.7 GiB) in 6m 11s, read: 14.7 MiB/s, write: 14.7 MiB/s
INFO: 53% (5.1 GiB of 9.7 GiB) in 6m 20s, read: 10.7 MiB/s, write: 10.7 MiB/s
INFO: 54% (5.3 GiB of 9.7 GiB) in 6m 27s, read: 16.6 MiB/s, write: 16.6 MiB/s
INFO: 55% (5.3 GiB of 9.7 GiB) in 6m 31s, read: 21.0 MiB/s, write: 21.0 MiB/s
INFO: 56% (5.4 GiB of 9.7 GiB) in 6m 38s, read: 13.1 MiB/s, write: 13.1 MiB/s
INFO: 57% (5.5 GiB of 9.7 GiB) in 6m 45s, read: 14.3 MiB/s, write: 14.3 MiB/s
INFO: 58% (5.6 GiB of 9.7 GiB) in 6m 53s, read: 12.5 MiB/s, write: 12.5 MiB/s
INFO: 59% (5.7 GiB of 9.7 GiB) in 7m 1s, read: 13.5 MiB/s, write: 13.5 MiB/s
INFO: 60% (5.8 GiB of 9.7 GiB) in 7m 11s, read: 10.4 MiB/s, write: 10.4 MiB/s
INFO: 61% (5.9 GiB of 9.7 GiB) in 7m 17s, read: 16.7 MiB/s, write: 16.7 MiB/s
INFO: 62% (6.0 GiB of 9.7 GiB) in 7m 28s, read: 7.6 MiB/s, write: 7.6 MiB/s
INFO: 63% (6.1 GiB of 9.7 GiB) in 7m 37s, read: 12.0 MiB/s, write: 12.0 MiB/s
INFO: 64% (6.2 GiB of 9.7 GiB) in 7m 43s, read: 16.7 MiB/s, write: 16.7 MiB/s
INFO: 65% (6.3 GiB of 9.7 GiB) in 7m 46s, read: 29.3 MiB/s, write: 29.3 MiB/s
INFO: 66% (6.4 GiB of 9.7 GiB) in 7m 53s, read: 16.6 MiB/s, write: 16.6 MiB/s
INFO: 67% (6.5 GiB of 9.7 GiB) in 8m 2s, read: 9.8 MiB/s, write: 9.8 MiB/s
INFO: 68% (6.6 GiB of 9.7 GiB) in 8m 11s, read: 10.7 MiB/s, write: 10.7 MiB/s
INFO: 69% (6.7 GiB of 9.7 GiB) in 8m 17s, read: 17.3 MiB/s, write: 17.3 MiB/s
INFO: 70% (6.8 GiB of 9.7 GiB) in 8m 23s, read: 21.3 MiB/s, write: 21.3 MiB/s
INFO: 71% (6.9 GiB of 9.7 GiB) in 8m 27s, read: 16.0 MiB/s, write: 16.0 MiB/s
INFO: 72% (7.0 GiB of 9.7 GiB) in 8m 42s, read: 6.7 MiB/s, write: 6.7 MiB/s
INFO: 73% (7.1 GiB of 9.7 GiB) in 8m 54s, read: 8.7 MiB/s, write: 8.7 MiB/s
INFO: 74% (7.2 GiB of 9.7 GiB) in 9m 6s, read: 8.7 MiB/s, write: 8.7 MiB/s
INFO: 75% (7.3 GiB of 9.7 GiB) in 9m 13s, read: 14.3 MiB/s, write: 14.3 MiB/s
INFO: 76% (7.4 GiB of 9.7 GiB) in 9m 23s, read: 9.6 MiB/s, write: 9.6 MiB/s
INFO: 77% (7.5 GiB of 9.7 GiB) in 9m 31s, read: 11.5 MiB/s, write: 11.5 MiB/s
INFO: 78% (7.6 GiB of 9.7 GiB) in 9m 41s, read: 10.4 MiB/s, write: 10.4 MiB/s
INFO: 79% (7.7 GiB of 9.7 GiB) in 9m 52s, read: 8.7 MiB/s, write: 8.7 MiB/s
INFO: 80% (7.8 GiB of 9.7 GiB) in 10m 5s, read: 7.4 MiB/s, write: 7.4 MiB/s
INFO: 81% (7.9 GiB of 9.7 GiB) in 10m 13s, read: 14.0 MiB/s, write: 14.0 MiB/s
INFO: 82% (7.9 GiB of 9.7 GiB) in 10m 20s, read: 12.6 MiB/s, write: 12.6 MiB/s
INFO: 83% (8.1 GiB of 9.7 GiB) in 10m 32s, read: 9.3 MiB/s, write: 9.3 MiB/s
INFO: 84% (8.1 GiB of 9.7 GiB) in 10m 38s, read: 16.0 MiB/s, write: 16.0 MiB/s
INFO: 85% (8.2 GiB of 9.7 GiB) in 10m 46s, read: 11.5 MiB/s, write: 11.5 MiB/s
INFO: 86% (8.3 GiB of 9.7 GiB) in 10m 56s, read: 9.6 MiB/s, write: 9.6 MiB/s
INFO: 87% (8.4 GiB of 9.7 GiB) in 11m 6s, read: 10.0 MiB/s, write: 10.0 MiB/s
INFO: 88% (8.5 GiB of 9.7 GiB) in 11m 15s, read: 12.4 MiB/s, write: 12.4 MiB/s
INFO: 89% (8.6 GiB of 9.7 GiB) in 11m 23s, read: 11.0 MiB/s, write: 11.0 MiB/s
INFO: 90% (8.7 GiB of 9.7 GiB) in 11m 31s, read: 13.5 MiB/s, write: 13.5 MiB/s
INFO: 91% (8.8 GiB of 9.7 GiB) in 11m 43s, read: 7.3 MiB/s, write: 7.3 MiB/s
INFO: 92% (8.9 GiB of 9.7 GiB) in 11m 52s, read: 11.6 MiB/s, write: 11.6 MiB/s
INFO: 93% (9.0 GiB of 9.7 GiB) in 12m 2s, read: 10.4 MiB/s, write: 10.4 MiB/s
INFO: 94% (9.1 GiB of 9.7 GiB) in 12m 13s, read: 8.4 MiB/s, write: 8.4 MiB/s
INFO: 95% (9.2 GiB of 9.7 GiB) in 12m 23s, read: 9.6 MiB/s, write: 9.2 MiB/s
INFO: 96% (9.3 GiB of 9.7 GiB) in 12m 34s, read: 9.5 MiB/s, write: 9.5 MiB/s
INFO: 97% (9.4 GiB of 9.7 GiB) in 12m 42s, read: 13.5 MiB/s, write: 13.5 MiB/s
INFO: 98% (9.5 GiB of 9.7 GiB) in 12m 50s, read: 11.0 MiB/s, write: 11.0 MiB/s
INFO: 99% (9.6 GiB of 9.7 GiB) in 13m 1s, read: 9.8 MiB/s, write: 9.8 MiB/s
INFO: 100% (9.7 GiB of 9.7 GiB) in 13m 12s, read: 8.0 MiB/s, write: 8.0 MiB/s
INFO: backup was done incrementally, reused 490.35 GiB (98%)
INFO: transferred 9.69 GiB in 792 seconds (12.5 MiB/s)
INFO: Finished Backup of VM 100 (00:13:47)
INFO: Backup finished at 2020-11-16 12:02:29
INFO: Backup job finished successfully
TASK OK

------------------------------------------------------------------------------

INFO: starting new backup job: vzdump 100 --node prox01 --mode snapshot --storage BKP_NUVEM --remove 0
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-16 14:26:56
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-16T17:26:56Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task '6b66b22a-b1a7-4076-a3f5-79c7d8794206'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: OK (7.9 GiB of 500.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 7.9 GiB dirty of 500.0 GiB total
INFO: 1% (104.0 MiB of 7.9 GiB) in 3s, read: 34.7 MiB/s, write: 34.7 MiB/s
INFO: 2% (164.0 MiB of 7.9 GiB) in 1m 7s, read: 960.0 KiB/s, write: 960.0 KiB/s
INFO: 3% (260.0 MiB of 7.9 GiB) in 3m 46s, read: 618.3 KiB/s, write: 618.3 KiB/s
INFO: 4% (340.0 MiB of 7.9 GiB) in 6m 17s, read: 542.5 KiB/s, write: 542.5 KiB/s
INFO: 5% (412.0 MiB of 7.9 GiB) in 8m 18s, read: 609.3 KiB/s, write: 575.5 KiB/s
INFO: 6% (500.0 MiB of 7.9 GiB) in 11m 32s, read: 464.5 KiB/s, write: 464.5 KiB/s
INFO: 7% (572.0 MiB of 7.9 GiB) in 14m 16s, read: 449.6 KiB/s, write: 424.6 KiB/s
INFO: 8% (660.0 MiB of 7.9 GiB) in 17m 42s, read: 437.4 KiB/s, write: 437.4 KiB/s
INFO: 9% (744.0 MiB of 7.9 GiB) in 20m 18s, read: 551.4 KiB/s, write: 525.1 KiB/s
INFO: 10% (816.0 MiB of 7.9 GiB) in 21m 15s, read: 1.3 MiB/s, write: 1.3 MiB/s
INFO: 11% (900.0 MiB of 7.9 GiB) in 21m 32s, read: 4.9 MiB/s, write: 4.9 MiB/s
INFO: 12% (980.0 MiB of 7.9 GiB) in 24m 28s, read: 465.5 KiB/s, write: 465.5 KiB/s
INFO: 13% (1.1 GiB of 7.9 GiB) in 27m 24s, read: 651.6 KiB/s, write: 651.6 KiB/s
INFO: 14% (1.1 GiB of 7.9 GiB) in 28m 50s, read: 523.9 KiB/s, write: 523.9 KiB/s
INFO: 15% (1.2 GiB of 7.9 GiB) in 31m 35s, read: 546.1 KiB/s, write: 546.1 KiB/s
INFO: 16% (1.3 GiB of 7.9 GiB) in 33m 47s, read: 589.6 KiB/s, write: 589.6 KiB/s
INFO: 17% (1.4 GiB of 7.9 GiB) in 36m 23s, read: 577.6 KiB/s, write: 577.6 KiB/s
INFO: 18% (1.4 GiB of 7.9 GiB) in 39m 16s, read: 497.2 KiB/s, write: 497.2 KiB/s
INFO: 19% (1.5 GiB of 7.9 GiB) in 41m 22s, read: 617.7 KiB/s, write: 617.7 KiB/s
ERROR: interrupted by signal
INFO: aborting backup job
ERROR: Backup of VM 100 failed - interrupted by signal
INFO: Failed at 2020-11-16 15:11:30
ERROR: Backup job failed - interrupted by signal
TASK ERROR: interrupted by signal

-------------------------------------------------------------------------------------------------








()







INFO: starting new backup job: vzdump 100 --storage BKP_NUVEM --remove 0 --mode snapshot --node prox01
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-16 21:43:12
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-17T00:43:12Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task '72ea9686-8a90-45f5-b8c1-312e274401ca'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: created new
INFO: 0% (212.0 MiB of 500.0 GiB) in 3s, read: 70.7 MiB/s, write: 37.3 MiB/s
ERROR: interrupted by signal
INFO: aborting backup job
ERROR: Backup of VM 100 failed - interrupted by signal
INFO: Failed at 2020-11-16 21:55:44
ERROR: Backup job failed - interrupted by signal
TASK ERROR: interrupted by signal

----------------------------------------------------------------------------------



The last backup I canceled, because he already starts to do the full again. Thank you for your help!
 
yeah, there was no bitmap at that point so the VM must have been stopped in-between?
 
Do you speak in the highlighted text?

I stop, because it seems to me that a full backup will start, different from the others that show "incremental".

I did several incremental backups correctly, but then gave this message.



INFO: starting new backup job: vzdump 100 --storage BKP_NUVEM --remove 0 --mode snapshot --node prox01
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-16 21:43:12
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-17T00:43:12Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task '72ea9686-8a90-45f5-b8c1-312e274401ca'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: created new
INFO: 0% (212.0 MiB of 500.0 GiB) in 3s, read: 70.7 MiB/s, write: 37.3 MiB/s

ERROR: interrupted by signal
INFO: aborting backup job
ERROR: Backup of VM 100 failed - interrupted by signal
INFO: Failed at 2020-11-16 21:55:44
ERROR: Backup job failed - interrupted by signal
TASK ERROR: interrupted by signal
 
if the log says a new bitmap was created, that there was none previously, which means this was the first backup after the VM has been started (this time). check the logs - either the VM or the host must have been restarted between that backup and the last incremental one.
 
From what I understand from your answer, it's as if something has broken down and the system has restarted the whole process. How can I force an incremental backup? How can I tell the system to perform an incremental now? Thanks.
 
you can't force a *fast* incremental backup. the backup will *always* be incremental as long as a previous backup exists on the server side, but in the non-fast mode it will need to read and chunk the source data.
 
Dear, I'm getting this message right now. I have 7 backups prior to this one. They are verified. I still don't understand, because the system wants full backup, since everyone else is ok.


INFO: starting new backup job: vzdump 100 --mode snapshot --storage BKP_NUVEM --remove 0 --node prox01
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-21 09:16:28
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-21T12:16:28Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'ac51d64b-f335-4757-b503-61cc73d63499'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: 0% (448.0 MiB of 500.0 GiB) in 3s, read: 149.3 MiB/s, write: 53.3 MiB/s
 
Dear, I'm getting this message right now. I have 7 backups prior to this one. They are verified. I still don't understand, because the system wants full backup, since everyone else is ok.


INFO: starting new backup job: vzdump 100 --mode snapshot --storage BKP_NUVEM --remove 0 --node prox01
INFO: Starting Backup of VM 100 (qemu)
INFO: Backup started at 2020-11-21 09:16:28
INFO: status = running
INFO: VM Name: ubilex
INFO: include disk 'virtio0' 'local-zfs:vm-100-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/100/2020-11-21T12:16:28Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
ERROR: VM 100 qmp command 'guest-fsfreeze-thaw' failed - got timeout
INFO: started backup task 'ac51d64b-f335-4757-b503-61cc73d63499'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: 0% (448.0 MiB of 500.0 GiB) in 3s, read: 149.3 MiB/s, write: 53.3 MiB/s
I only know one thing that can cause the dirty bitmap to be invalid and that happens if i backup to another PBS/Datastore. Do you do any backups inbetween? What happens if you run one directly after the one with invalid bitmap?
 
Folks,

I would like to thank you for the feedback

This backup that happened now was incremental.

As I understand it, he read the file, and reused it.
I made another bakup and it appeared fast incremental.
Now everything is ok.

Thanks.
Sorted out
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!