The File Share Connector enables Records Management to manage the lifecycle of documents stored in network file shares.
For the File Share Connector to be able to effectively manage network file shares, the file shares should be located within the same Local Area Network and, if possible, on the same machine where the File Share Connector is installed.
File Share Connector Architecture
What comprises the solution...
.NET-based Windows Service for crawling and classification
.NET-based Windows Server for retention action execution
Services are configured by adding a list of file share paths to be managed
Each managed path provided is recursively monitored and crawled using File System Watchers and File Enumeration
How scaling works...
Each managed path represent a single application thread
Managed paths must not overlap
Application can be installed to multiple servers to form a cluster
Application supports failover, not load distribution
Managed paths can be divided amongst multiple clusters
When to scale...
When CPU utilization is consistently above 90% for extended durations, a new cluster should be created and managed paths should be divided amongst the available clusters
When Memory Pressure is consistently above 80% for extended durations, a new cluster should be created and managed paths should be divided amongst the available clusters
General Sizing Guidelines...
(Total # Files / 10,000,000) = # Managed Paths
Ceiling(# Managed Paths / 10) = # Servers
Topics for Installation and Configuration of the File Share Connector