Hi,
I would like to ask about the mechanism of the backup. Here is the backup log for example:
What I wonder here is 'fs-freeze' is called right after 'fs-thaw'. I understand 'fs-freeze' will freeze the file system on the VM to increase consistency. However, 'fs-thaw' is called right after that, BEFORE doing backing up. The time between 2 command is just a few seconds. I thought 'fs-thaw' must be called AFTER doing backup, right?
I would like to ask about the mechanism of the backup. Here is the backup log for example:
Code:
()
INFO: starting new backup job: vzdump 101 --prune-backups 'keep-daily=30,keep-last=36' --storage PB022-DS4 --mailnotification failure --quiet 1 --notes-template '{{cluster}}, {{guestname}}, {{node}}, {{vmid}}' --mailto help@fruitcloud.net --mode snapshot
INFO: Starting Backup of VM 101 (qemu)
INFO: Backup started at 2023-03-02 17:00:03
INFO: status = running
INFO: VM Name: BaltFresh
INFO: include disk 'virtio0' 'disk2:101/vm-101-disk-0.qcow2' 170G
INFO: include disk 'virtio1' 'disk2:101/vm-101-disk-1.qcow2' 120G
INFO: exclude disk 'virtio2' 'disk2:101/vm-101-disk-2.qcow2' (backup=no)
INFO: include disk 'virtio3' 'disk2:101/vm-101-disk-3.qcow2' 200G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/101/2023-03-02T14:00:03Z'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '53e4c9b1-c0ba-46b7-b716-1c6c95ca4732'
INFO: resuming VM again
INFO: virtio0: dirty-bitmap status: OK (27.7 GiB of 170.0 GiB dirty)
INFO: virtio1: dirty-bitmap status: OK (14.0 GiB of 120.0 GiB dirty)
INFO: virtio3: dirty-bitmap status: OK (128.0 MiB of 200.0 GiB dirty)
INFO: using fast incremental mode (dirty-bitmap), 41.8 GiB dirty of 490.0 GiB total
INFO: 2% (1.1 GiB of 41.8 GiB) in 3s, read: 373.3 MiB/s, write: 373.3 MiB/s
INFO: 3% (1.4 GiB of 41.8 GiB) in 37s, read: 9.9 MiB/s, write: 9.8 MiB/s
INFO: 5% (2.2 GiB of 41.8 GiB) in 40s, read: 264.0 MiB/s, write: 262.7 MiB/s
INFO: 7% (3.0 GiB of 41.8 GiB) in 43s, read: 281.3 MiB/s, write: 278.7 MiB/s
INFO: 8% (3.6 GiB of 41.8 GiB) in 57s, read: 40.0 MiB/s, write: 40.0 MiB/s
INFO: 10% (4.6 GiB of 41.8 GiB) in 1m, read: 345.3 MiB/s, write: 344.0 MiB/s
INFO: 11% (5.0 GiB of 41.8 GiB) in 1m 3s, read: 136.0 MiB/s, write: 136.0 MiB/s
INFO: 12% (5.3 GiB of 41.8 GiB) in 1m 36s, read: 8.6 MiB/s, write: 8.6 MiB/s
INFO: 14% (6.1 GiB of 41.8 GiB) in 1m 39s, read: 300.0 MiB/s, write: 297.3 MiB/s
INFO: 17% (7.2 GiB of 41.8 GiB) in 1m 42s, read: 354.7 MiB/s, write: 350.7 MiB/s
INFO: 20% (8.5 GiB of 41.8 GiB) in 1m 45s, read: 452.0 MiB/s, write: 452.0 MiB/s
INFO: 23% (9.8 GiB of 41.8 GiB) in 1m 48s, read: 440.0 MiB/s, write: 440.0 MiB/s
INFO: 25% (10.9 GiB of 41.8 GiB) in 1m 51s, read: 369.3 MiB/s, write: 369.3 MiB/s
INFO: 28% (11.8 GiB of 41.8 GiB) in 1m 54s, read: 333.3 MiB/s, write: 333.3 MiB/s
INFO: 30% (12.7 GiB of 41.8 GiB) in 1m 57s, read: 285.3 MiB/s, write: 285.3 MiB/s
INFO: 32% (13.6 GiB of 41.8 GiB) in 2m, read: 321.3 MiB/s, write: 321.3 MiB/s
INFO: 35% (14.9 GiB of 41.8 GiB) in 2m 3s, read: 438.7 MiB/s, write: 438.7 MiB/s
INFO: 37% (15.8 GiB of 41.8 GiB) in 2m 6s, read: 320.0 MiB/s, write: 320.0 MiB/s
INFO: 40% (17.1 GiB of 41.8 GiB) in 2m 9s, read: 424.0 MiB/s, write: 421.3 MiB/s
INFO: 42% (17.8 GiB of 41.8 GiB) in 2m 12s, read: 252.0 MiB/s, write: 248.0 MiB/s
INFO: 43% (18.1 GiB of 41.8 GiB) in 3m 55s, read: 2.4 MiB/s, write: 2.3 MiB/s
INFO: 44% (18.4 GiB of 41.8 GiB) in 4m 1s, read: 58.0 MiB/s, write: 56.0 MiB/s
INFO: 45% (19.0 GiB of 41.8 GiB) in 4m 7s, read: 104.0 MiB/s, write: 101.3 MiB/s
INFO: 46% (19.3 GiB of 41.8 GiB) in 4m 10s, read: 81.3 MiB/s, write: 80.0 MiB/s
INFO: 47% (19.7 GiB of 41.8 GiB) in 4m 16s, read: 70.0 MiB/s, write: 69.3 MiB/s
INFO: 48% (20.2 GiB of 41.8 GiB) in 4m 27s, read: 52.7 MiB/s, write: 51.6 MiB/s
INFO: 49% (20.7 GiB of 41.8 GiB) in 4m 30s, read: 149.3 MiB/s, write: 144.0 MiB/s
INFO: 50% (21.0 GiB of 41.8 GiB) in 4m 39s, read: 42.2 MiB/s, write: 41.8 MiB/s
INFO: 51% (21.4 GiB of 41.8 GiB) in 4m 42s, read: 113.3 MiB/s, write: 112.0 MiB/s
INFO: 52% (21.8 GiB of 41.8 GiB) in 4m 52s, read: 47.2 MiB/s, write: 46.8 MiB/s
INFO: 53% (22.2 GiB of 41.8 GiB) in 4m 57s, read: 77.6 MiB/s, write: 76.0 MiB/s
INFO: 54% (22.6 GiB of 41.8 GiB) in 5m 11s, read: 31.7 MiB/s, write: 30.9 MiB/s
INFO: 55% (23.0 GiB of 41.8 GiB) in 5m 18s, read: 58.3 MiB/s, write: 57.7 MiB/s
INFO: 56% (23.5 GiB of 41.8 GiB) in 5m 26s, read: 52.0 MiB/s, write: 49.5 MiB/s
INFO: 57% (23.9 GiB of 41.8 GiB) in 5m 40s, read: 30.6 MiB/s, write: 30.0 MiB/s
INFO: 58% (24.3 GiB of 41.8 GiB) in 6m 14s, read: 12.7 MiB/s, write: 12.2 MiB/s
INFO: 59% (24.7 GiB of 41.8 GiB) in 6m 29s, read: 28.8 MiB/s, write: 28.5 MiB/s
INFO: 60% (25.1 GiB of 41.8 GiB) in 6m 48s, read: 23.4 MiB/s, write: 23.2 MiB/s
INFO: 61% (25.6 GiB of 41.8 GiB) in 7m 15s, read: 17.6 MiB/s, write: 17.5 MiB/s
INFO: 62% (26.1 GiB of 41.8 GiB) in 7m 27s, read: 44.7 MiB/s, write: 43.3 MiB/s
INFO: 63% (26.7 GiB of 41.8 GiB) in 7m 30s, read: 180.0 MiB/s, write: 180.0 MiB/s
INFO: 64% (27.0 GiB of 41.8 GiB) in 7m 33s, read: 100.0 MiB/s, write: 98.7 MiB/s
INFO: 65% (27.3 GiB of 41.8 GiB) in 7m 37s, read: 84.0 MiB/s, write: 84.0 MiB/s
INFO: 66% (27.6 GiB of 41.8 GiB) in 7m 41s, read: 93.0 MiB/s, write: 93.0 MiB/s
INFO: 67% (28.2 GiB of 41.8 GiB) in 7m 44s, read: 186.7 MiB/s, write: 185.3 MiB/s
INFO: 68% (28.6 GiB of 41.8 GiB) in 7m 48s, read: 95.0 MiB/s, write: 94.0 MiB/s
INFO: 69% (29.1 GiB of 41.8 GiB) in 7m 51s, read: 180.0 MiB/s, write: 173.3 MiB/s
INFO: 70% (29.5 GiB of 41.8 GiB) in 7m 54s, read: 137.3 MiB/s, write: 134.7 MiB/s
INFO: 71% (29.8 GiB of 41.8 GiB) in 7m 59s, read: 65.6 MiB/s, write: 64.8 MiB/s
INFO: 72% (30.1 GiB of 41.8 GiB) in 8m 2s, read: 112.0 MiB/s, write: 110.7 MiB/s
INFO: 73% (30.6 GiB of 41.8 GiB) in 8m 6s, read: 120.0 MiB/s, write: 120.0 MiB/s
INFO: 74% (31.0 GiB of 41.8 GiB) in 8m 9s, read: 122.7 MiB/s, write: 120.0 MiB/s
INFO: 75% (31.5 GiB of 41.8 GiB) in 8m 12s, read: 170.7 MiB/s, write: 168.0 MiB/s
INFO: 76% (31.9 GiB of 41.8 GiB) in 8m 15s, read: 150.7 MiB/s, write: 148.0 MiB/s
INFO: 77% (32.2 GiB of 41.8 GiB) in 8m 18s, read: 102.7 MiB/s, write: 101.3 MiB/s
INFO: 78% (32.8 GiB of 41.8 GiB) in 8m 25s, read: 78.3 MiB/s, write: 77.1 MiB/s
INFO: 79% (33.2 GiB of 41.8 GiB) in 8m 28s, read: 149.3 MiB/s, write: 146.7 MiB/s
INFO: 80% (33.7 GiB of 41.8 GiB) in 8m 36s, read: 61.5 MiB/s, write: 61.0 MiB/s
INFO: 81% (34.0 GiB of 41.8 GiB) in 8m 40s, read: 81.0 MiB/s, write: 81.0 MiB/s
INFO: 82% (34.6 GiB of 41.8 GiB) in 8m 43s, read: 198.7 MiB/s, write: 197.3 MiB/s
INFO: 83% (35.0 GiB of 41.8 GiB) in 8m 46s, read: 136.0 MiB/s, write: 136.0 MiB/s
INFO: 84% (35.4 GiB of 41.8 GiB) in 8m 49s, read: 145.3 MiB/s, write: 141.3 MiB/s
INFO: 86% (36.2 GiB of 41.8 GiB) in 8m 52s, read: 293.3 MiB/s, write: 292.0 MiB/s
INFO: 87% (36.8 GiB of 41.8 GiB) in 8m 55s, read: 174.7 MiB/s, write: 174.7 MiB/s
INFO: 88% (37.0 GiB of 41.8 GiB) in 8m 58s, read: 82.7 MiB/s, write: 82.7 MiB/s
INFO: 90% (37.8 GiB of 41.8 GiB) in 9m 1s, read: 284.0 MiB/s, write: 284.0 MiB/s
INFO: 91% (38.1 GiB of 41.8 GiB) in 9m 4s, read: 92.0 MiB/s, write: 92.0 MiB/s
INFO: 92% (38.9 GiB of 41.8 GiB) in 9m 7s, read: 261.3 MiB/s, write: 260.0 MiB/s
INFO: 94% (39.3 GiB of 41.8 GiB) in 9m 10s, read: 160.0 MiB/s, write: 160.0 MiB/s
INFO: 95% (39.9 GiB of 41.8 GiB) in 9m 17s, read: 80.0 MiB/s, write: 77.1 MiB/s
INFO: 96% (40.4 GiB of 41.8 GiB) in 9m 21s, read: 127.0 MiB/s, write: 126.0 MiB/s
INFO: 97% (41.0 GiB of 41.8 GiB) in 9m 24s, read: 204.0 MiB/s, write: 202.7 MiB/s
INFO: 100% (41.8 GiB of 41.8 GiB) in 9m 27s, read: 290.7 MiB/s, write: 288.0 MiB/s
INFO: backup is sparse: 8.00 MiB (0%) total zero data
INFO: backup was done incrementally, reused 448.56 GiB (91%)
INFO: transferred 41.83 GiB in 813 seconds (52.7 MiB/s)
INFO: adding notes to backup
storing login ticket failed: $XDG_RUNTIME_DIR must be set
INFO: prune older backups with retention: keep-daily=30, keep-last=36
INFO: running 'proxmox-backup-client prune' for 'vm/101'
storing login ticket failed: $XDG_RUNTIME_DIR must be set
INFO: pruned 1 backup(s) not covered by keep-retention policy
INFO: Finished Backup of VM 101 (00:13:39)
INFO: Backup finished at 2023-03-02 17:13:42
storing login ticket failed: $XDG_RUNTIME_DIR must be set
INFO: Backup job finished successfully
TASK OKWhat I wonder here is 'fs-freeze' is called right after 'fs-thaw'. I understand 'fs-freeze' will freeze the file system on the VM to increase consistency. However, 'fs-thaw' is called right after that, BEFORE doing backing up. The time between 2 command is just a few seconds. I thought 'fs-thaw' must be called AFTER doing backup, right?
