Veritas Data Insight Administrator's Guide

Set backup location if backup is needed before cleanup. It should not be a shared location as SQLite does not support operation across shared location.

configdb.exe -O -J "matrix.whitespace.backup.directory.path" -j "backup_location"

backup_location is the path where you want to store backup. For example,

configdb.exe -O -J "matrix.whitespace.backup.directory.path" -j "C:\DataInsight\data\indexer"

Trigger index writer to purge access column without backup

idxwriter.exe --indexdir <PATH_TO_INDEX_DIR_OF_MSU> --purge-access-data --purge-access-days <DAYS>

For example,

idxwriter.exe --indexdir C:\DataInsight\data\indexer\default\13\13 --purge-access-data --purge-access-days 60

Result: This will delete content of access column and vacuum index.db to reclaim disk space.

To keep backup of access column; run index writer with additional parameter as below -

idxwriter.exe --indexdir C:\DataInsight\data\indexer\default\13\13 --purge-access-data --purge-access-days 60 --purge-access-with-backup

This will fail if path is not set in the first step. Otherwise, a backup sqlite file whitespace_backup_13_1701862181.sqlite will be created at location mentioned in step 1. Where 13 is the msu_id. It will contain dentry_access_backup and fentry_access_backup tables containing backup of access column for deleted fids.