About MSDP data integrity checking
Deduplication metadata and data may become inconsistent or corrupted because of disk failures, I/O errors, database corruption, and operational errors. NetBackup checks the integrity of the deduplicated data on a regular basis. NetBackup performs some of the integrity checking when the storage server is idle. Other integrity checking is designed to use few storage server resources so as not to interfere with operations.
The data integrity checking process includes the following checks and actions:
Automatically constrains data loss or corruption to ensure that new backups are intact.
Automatically runs a cyclic redundancy check (CRC) for the data containers.
Automatically collects and cleans up storage garbage.
Automatically recovers the container-based reference database (or parts of the database) if it is corrupt or missing.
Automatically finds storage leaks and fixes them.
NetBackup resolves many integrity issues without user intervention, and some issues are fixed when the next backup runs. However, a severe issue may require intervention by Cohesity Support. In such cases, NetBackup writes a message to the NetBackup Disk Logs report.
The data integrity message code is 1057.
See MSDP event codes and messages.
NetBackup writes the integrity checking activity messages to the NetBackup Deduplication Engine storaged.log file. For cloud LSU, the messages were written toStoraged_<dsid>.log.
You can configure some of the data integrity checking behaviors.
More Information