Martin Damgaard wrote:Hi Anglerzac, This is excactly how i started noticing the issue. I could confirm this by running a scrubbing job on the server.
That gave a match every time. When eventviewer listed a file as corrupt and unable to repair - Veeam Backup or Validator tool confirmed this.
I highly recommend running some manual scrubs on the volume or/and test ALL archives with the validator tool.
Otherwise your backups might be corrupt, without you noticing it!
(From my understanding Veeam health checks ONLY tests archives up til last full VBK. All earlier backups can only be checked by Validator tool).
Does this issue impact the source and target deduplication features of Veeam described here?
It seems from the discussion that the issue is with OS-level deduplication (which is separate from Veeam source/target deduplication) and only an issue on on backup destination volumes. Is that correct?
Users browsing this forum: Bing [Bot], Google [Bot] and 1 guest