Arctera Insight Information Governance Administrator's Guide
- Section I. Getting started
- Introduction to Arctera Insight Information Governance administration
- Configuring Information Governance global settings
- About scanning and event monitoring
- About filtering certain accounts, IP addresses, and paths
- About archiving data
- About Information Governance integration with Data Loss Prevention (DLP)
- Configuring advanced analytics
- About open shares
- About user risk score
- About bulk assignment of custodians
- Configuring Metadata Framework
- Section II. Configuring Information Governance
- Configuring Information Governance product users
- Configuring Information Governance product servers
- About node templates
- About automated alerts for patches and upgrades
- Configuring saved credentials
- Configuring directory service domains
- Adding a directory service domain to Information Governance
- Configuring containers
- Server Pools
- Section III. Configuring native file systems in Information Governance
- Configuring clustered NetApp file server monitoring
- About configuring secure communication between Information Governance and cluster-mode NetApp devices
- Configuring EMC Celerra or VNX monitoring
- Configuring EMC Isilon monitoring
- Configuring EMC Unity VSA file servers
- Configuring Hitachi NAS file server monitoring
- Configuring Windows File Server monitoring
- Configuring Arctera File System (VxFS) file server monitoring
- Configuring monitoring of a generic device
- Managing file servers
- Adding filers
- Adding shares
- Renaming storage devices
- Configuring clustered NetApp file server monitoring
- Section IV. Configuring SharePoint data sources
- Configuring monitoring of SharePoint web applications
- About the Information Governance web service for SharePoint
- Adding web applications
- Adding site collections
- Configuring monitoring of SharePoint Online accounts
- About SharePoint Online account monitoring
- Adding site collections to SharePoint Online accounts
- Configuring monitoring of SharePoint web applications
- Section V. Configuring cloud data sources
- Configuring monitoring of Box accounts
- Configuring OneDrive account monitoring
- Configuring Azure Netapp Files Device
- Managing cloud sources
- Section VI. Configuring Object Storage Sources
- Section VII. Health and monitoring
- Section VIII. Alerts and policies
- Configuring policies
- Managing policies
- Configuring policies
- Section IX. Remediation
- Configuring remediation settings
- Section X. Reference
- Appendix A. Information Governance best practices
- Appendix B. Migrating Information Governance components
- Appendix C. Backing up and restoring data
- Appendix D. Arctera Information Governance health checks
- About Information Governance health checks
- About Information Governance health checks
- Appendix E. Command File Reference
- Appendix F. Arctera Information Governance jobs
- Appendix G. Troubleshooting
- Troubleshooting FPolicy issues on NetApp devices
Purging indexes by date/whitespace for deleted files
It is observed that information about files and folders, which are physically deleted on filers is retained. By using this utility, you can clean access data events for deleted files and folders to reclaim disk space by reducing index.db size. In this utility, you need to provide new option of purge by specified number of days. Access data events associated with the deleted files will be deleted if deletion date is older than given number of days. There is one option, if selected, utility will take a backup of access data events before cleanup at pre-configured location.
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.
After running this utility on an index.db where deleted files are having data in access column; index.db size should reduce as this utility will Vacuum index db after purging is successful.
To identify the targeted indexes for purging based on max deleted files count for each Share, users can execute a DQL report using the template named Calculate deleted files count from the Data Management category. For additional information, refer to the About DQL query templates section in the Information Governance User's Guide.