MSDP data integrity checking configuration parameters
The configuration file parameters that control the deduplication data integrity checking are in two different configuration files, as follows:
The contentrouter.cfg file.
The parameters are described in Table: The contentrouter.cfg file parameters for data integrity checking.
The spa.cfg file.
The parameters are described in Table: The contentrouter.cfg file parameters for data integrity checking.
Those files reside in the following directories:
UNIX: storage_path/etc/puredisk
Windows: storage_path\etc\puredisk
Warning:
Cohesity recommends that you do not disable the data integrity checking. If you do so, NetBackup cannot find and repair or report data corruption.
See About MSDP data integrity checking.
Table: The contentrouter.cfg file parameters for data integrity checking
Setting | Default | Description |
|---|---|---|
|
EnableCRCCheck |
true |
Enable or disable cyclic redundancy checking (CRC) of the data container files. The possible values are true or false. CRC occurs only when no backup, restore, or queue processing jobs are running. |
|
CRCCheckSleepSeconds |
5 |
The time in seconds to sleep between checking containers. The longer the sleep interval, the more time it takes to check containers. |
|
CRCCheckBatchNum |
40 |
The number of containers to check each time. The greater the number of containers, the less time it takes to check all containers, but the more system resources it takes. |
|
ShutdownCRWhenError |
false |
Stops the NetBackup Deduplication Manager when a data loss is discovered. This parameter is reserved for debugging purposes by Cohesity Support Representatives. The possible values are true or false. |
|
GarbageCheckRemainDCCount |
100 |
The number of containers from failed jobs not to check for garbage. A failed backup or replication job still produces data containers. Because failed jobs are retried, retaining those containers means NetBackup does not have to send the fingerprint information again. As a result, retried jobs consume less time and fewer system resources than when first run. |
CRCDaysToRaiseCriticalDataScannedNotification | 7 | A critical event is generated if the data is not scanned for CRC on local LSU within a specified number of days. This parameter must be added as a new entry under DataCheck for initial use. |
EnableCRCDataScanNotification | true | Disable the CRC notifications for local LSU. This parameter must be added as a new entry under DataCheck for initial use. For example, EnableCRCDataScanNotification=false |
Table: spa.cfg file parameters for data integrity checking
Setting | Default | Description |
|---|---|---|
|
EnableDataCheck |
true |
Enable or disable data consistency checking. The possible values are True or False. |
|
DataCheckDays |
14 |
The number of days to check the data for consistency. The greater the number of days, the fewer the objects that are checked each day. The greater the number of days equals fewer storage server resources consumed each day. |
|
EnableDataCheckAlert |
true |
Enable or disable alerts. If true, NetBackup writes a message to the Disk Logs report when it detects a lost data segment. |