The Microsoft Exchange VSS writer takes a snapshot of the database which is followed by an integrity check. This does not attempt to fix anything, it instead is validating that all of the relevant data such as all of the transaction logs are available and in a good state. If the integrity check fails, it is up to the Exchange team to address the issue.
@Patrick Dijkgraaf
The documentation wording is not the best. I have submitted a Doc MR to remove the “repair” portion and reword that line. Commvault simply leverages the Exchange function to start the consistency check with is similar to a eseutil /k command.
No actual repair is ran against the database and the backup will fail if the consistency check fails.
It can however ensure the consistency of the DB so that you know the backup is valid and help discover potential issues to resolve on the Exchange side.
Note as per MSFT recommendation consistency checks are not enabled by default on DAG configurations. They however can be enabled if desired.
https://documentation.commvault.com/2022e/expert/17098_configuring_consistency_checks_for_exchange_database_backups.html