![]() ![]() INFO: backup is sparse: 8.00 MiB (0%) total zero data INFO: using fast incremental mode (dirty-bitmap), 44.4 GiB dirty of 256.0 GiB total INFO: virtio0: dirty-bitmap status: OK (44.4 GiB of 256.0 GiB dirty) INFO: issuing guest-agent 'fs-thaw' command INFO: issuing guest-agent 'fs-freeze' command INFO: creating Proxmox Backup Server archive 'vm/201/' ![]() INFO: include disk 'virtio0' 'local-zfs:vm-201-disk-1' 256G ![]() For example, there is a 250 GB Windows 2012 R2 Terminal server with several dozens of users and although during weekends they barely work, I can see in dirty backups some 44 GB of data "changed". While backing ap many Containers take really just seconds, with Windows servers it is obviously heavier job to accomplish. This is NOT a complaint and I am aware it is kind of off topic here, but perhaps others can add their little bits here. I want to share one experience I have no explanation so far. I am down from 4 hrs to 1 hr with daily virtual machines backups. Testing it on two places already some weeks and after understanding the retention setting I say it is a life saver. First A HUGE THANK for absolutely amazing tools, including PBS. ![]()
0 Comments
Leave a Reply. |