When you enable the Data Classification Scan for a File System, a meta database is created. The meta database contains information about the files in the associated volume. The Data Classification service constantly updates the databases to track file additions, volume additions, content update to files, etc. Journals from the FSF driver are used to keep track of the updates to each meta database.
The default location of the meta database is as follows:
Unix |
Windows |
The meta database is located at the root of each mount point, and is named .db.cv. For example: For /home, it would be /home/.DATACLASS_1/.db.cv You can relocate the database to a centralized location. |
On each volume, the meta database is created at the following location: System Volume Information\Bull Calypso \Data Classification It is named as dc_<instance_number>.db For example: On the C drive, it would be C:\System Volume Information\Bull Calypso \Data Classification\dc_<instance_number>.db You cannot relocate the database.
|
The meta databases created by Data Classification usually consume about 5% of the total space on the hard disk. Depending on the type of data and folder layout, the metafiles may consume additional space.
Each Data Classification update record consumes about 256 bytes (this assumes an average short name length of 16 bytes and an average full path length of 256 bytes).
When the volume where Data Classification database resides or the volume monitored by the Data Classification gets Full, free up some space or add more space to the volume. Manually delete the Data Classification database. Restart the Data Classification service to create the new Data Classification database.
During the deployment of the the Data Classification Enabler on a Unix client, a cvdccache directory is created at the specified location. This directory contains the Data Classification Cache.
You can change the location as follows:
/etc/CommVaultRegistry/Galaxy/Instance001/DataClassification/.properties
The dCacheRootDir registry key displays the current location of the Data Classification Cache. Change the value of the registry key to specify the new location for Data Classification Cache. Ensure that the new path, that you have specified, contains the cvdccache directory
Also change the value of the dRawBufferDir registry key to specify the new location for Data Classification Cache. Ensure that the new path, that you have specified, contains the cvdccache/rawbuffer directory.
The Data Classification Enabler and ContinuousDataReplicator use the same location for cache. If you have installed ContinuousDataReplicator, follow the steps given below to change the cache location for ContinuousDataReplicator:
Data Classification database is available on every volume. If you have multiple volumes, perform the following steps to delete the database manually from each volume.
psexec -i -s cmd
This will open a new command prompt window.
System Volume Information\bull \Data Classification
Enter the following in the new command prompt:
C:\System Volume Information\bull\Data Classification>del dc_002.db
where C:\ is the driver where the database is located and dc_002.db is the database to be deleted.
Use the ServiceEnabled registry key to enable or disable the data classification monitoring threads for all volumes on a client computer.
If you want to disable data classification for selected volumes, use the VolumeFilters registry key to provide the list of volumes.
If you are using Data Classification Enabler with the File Archiver and you have created any DataClassSets, you cannot use them after the upgrade.
No. You can only perform interactive install for the Data Classification Enabler. For more information, refer to Deployment - Data Classification Enabler.
Yes, you can use Data Classification Scan method for SnapProtect backups.
For Unix File System iDataAgent, perform the following before Data Classification Scan method for SnapProtect backups:
For Windows File System iDataAgent, ensure that the meta database is located on the same volume for which you are performing the SnapProtect backup.