When I use snapshot backup, the logs suggest that some sort of block-indexing is used to determine what blocks are "dirty" on a disk and perform a fast incremental backup. However if the VM has rebooted recently, that indexing seems to be reset and it checks all blocks.
I have a VM that struggles with snapshot-type backup (sometimes root goes read-only during backup). It has a 5TB data disk, and can take 30 minutes to backup when using the dirty indexing, or over 2 hours if dirty-indexing isn't available.
If I changed the VM to a "Stop" type backup, does that mean I lose the dirty-block indexing? Would "suspend" work better in my case?
I have a VM that struggles with snapshot-type backup (sometimes root goes read-only during backup). It has a 5TB data disk, and can take 30 minutes to backup when using the dirty indexing, or over 2 hours if dirty-indexing isn't available.
If I changed the VM to a "Stop" type backup, does that mean I lose the dirty-block indexing? Would "suspend" work better in my case?
Last edited:
