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
About the DFS utility
The DFS utility, mxdfsscan.exe
, maps root level DFS paths to actual storage server or share paths. It is used to export the DFS components (roots, root targets, links, and link targets) for all Windows DFS namespaces. The utility finds out physical level storage/filer link for all Domain DFS paths. It takes DFS root UNC path as input, for example\\<DFS domain>\root
. This utility only enumerates online links and skips all offline links. It generates the output in .csv format.
The mxdfsscan.exe
is a command line utility.
mxdfsscan.exe
creates a DFS mapping CSV file with details of DFS servers that must be mapped in the Information Governance configuration. mxdfsscan.exe
lets you specify only a single namespace at a time. You can run the utility twice to get information from two different DFS namespaces and create two different files from the output, for example, test1.csv
and test2.csv
. You can then import settings from test1.csv
and test2.csv
from the Information Governance Management Console
When you import a new DFS mapping file to Information Governance, the old mappings are maintained in Information Governance. For example, if you import mappings from test1.csv
and then from test2.csv
, the mappings from both files are displayed in Information Governance. However, if there are some duplicate mappings (the same DFS link appears twice - whether mapped to the same physical path or a different path), these mappings are not imported. A message is displayed indicating that there are duplicate mappings and hence one or more mappings cannot be imported.