Should We Enable “Storage‑level Corruption Guard / Backup File Health Check” on Backup Copy Jobs to Vault

[TimeKnight]

Hi all,
My coworker and I are trying to clarify best practices around the integrity‑check setting (“Storage‑level corruption guard / Perform backup files health check”) in Backup Copy Jobs that target Veeam Data Cloud Vault. We’re seeing mixed guidance, so we’d really appreciate input from Veeam experts and the community.
Our environment

Primary backups run from our SAN to a Windows Server ReFS repository.

• On all primary backup jobs, we enable Maintenance → Perform backup files health check.

• Our offsite copy is Veeam Data Cloud Vault (VDC‑Vault), using Backup Copy Jobs.

• We do not currently run SureBackup or SureRestore.

• Backup mode is forever‑incremental (no synthetic or active fulls).

• We are currently running Veeam 12.3.

Our question
Since we already run weekly integrity checks (SLCG/BFHC) on all local primary backup jobs:
Should we also enable the “Perform backup files health check” option inside the Backup Copy Jobs that copy to Veeam Data Cloud Vault?
Points we’re debating

• Is there any added value running this on the copy job if the source ReFS chain is already validated?

• Does the copy‑job health check validate anything inside the Vault itself, or only the on‑prem data before upload?

• Is it redundant because VDC‑Vault uses object‑storage durability and integrity mechanisms, and we already run weekly checks on the primary backup jobs?

Thanks in advance — we appreciate any expert insight or references!

[vnikiforov]

Hello, Brian,

It's really a matter of preference, but you may want to enable it on the Backup Copy Job too.

A job's health check only validates the chain in its own target, so your primary jobs check the on-prem ReFS chain and never touch the Vault. Data availability at the backend is essentially guaranteed at the Azure level - please check the details in the provided article, but the copy job's health check is the only thing that actually validates the integrity of the restore points inside the Vault, which the Azure side has no visibility into. Think logical corruption within the backup chain, for example. So no, it isn't redundant.