Does this perhaps mean that Windows is regularly messing around deduping the disks and producing changes which then trigger CBT changes although there have been no actual file changes?
pkelly_sts wrote:So, firstly, does enabling in-VM dedupe create a large incremental at all
pkelly_sts wrote:is it recommended to simply configure the dedupe config with a very old age of files to start deduping and gradually reduce the age over time (e.g. only dedupe any files older than, say, 3yrs initially, then after that has gone over the wire, reduce to older than 2.5yrs, then 2, then 1.5 etc.)
v.Eremin wrote:Your understanding is perfectly correct. Usage of Windows Deduplication (with garbage collection being the main culprit) inside the guest leads to high number of changed blocks. Thus, longer backup time. Thanks.
Thanks for the sharing and tips.
I never run Full backup on my Veeam Backup job since it is running OK with the Reverse Incremental job.
Or shall I convert the Dedupe backup job into Forever Forward Incremental to get better result in disk space saving instead ?
Users browsing this forum: Yahoo [Bot] and 1 guest