Hiho!
I've observed that when I set an I/O limit on a backup repo with a Fast Clone capable file system the maintenance setting "Defragment and compact full backup file" of a Backup Copy Job takes very much longer than without having an I/O limit. I've tested it a few times on XFS and ReFS repos and it's reproduceable.
After the copy part from the primary repo has finished there's no noticable I/O on the target repo during the "Defragment and compact full backup file" step. But it still takes (in my case) hours to complete this step. Without the I/O limit this step only takes a few minutes.
It looks like Veeam doesn't take into account that Fast Clone doesn't really shuffle data from and to the repo file system since it's mainly a rearrangement of file system pointers (simplified).
Or have I misunderstood this feature?
Regards
I've observed that when I set an I/O limit on a backup repo with a Fast Clone capable file system the maintenance setting "Defragment and compact full backup file" of a Backup Copy Job takes very much longer than without having an I/O limit. I've tested it a few times on XFS and ReFS repos and it's reproduceable.
After the copy part from the primary repo has finished there's no noticable I/O on the target repo during the "Defragment and compact full backup file" step. But it still takes (in my case) hours to complete this step. Without the I/O limit this step only takes a few minutes.
It looks like Veeam doesn't take into account that Fast Clone doesn't really shuffle data from and to the repo file system since it's mainly a rearrangement of file system pointers (simplified).
Or have I misunderstood this feature?
Regards
Statistics: Posted by lkwjochen — Feb 24, 2025 9:35 am
