Tracking Log files remote to UCA server with several paths defined within the Exchange Tracking Logs Data Source in UCA, or too many Exchange Log files are listed 5000+ in each defined Tracking log path.
WORKAROUND 1
E.g. If you have 10 Servers where the Tracking Logs will be collected from, create 10 Exchange Tracking Log Data sources and define 1 path to the Tracking Log files in each Data Source.
2. Create and Configure multiple Exchange Tracking Log data sources, 1 Data Source / Log path per Exchange server.
WORKAROUND 3
UC-Analytics Supports reading of Exchange Tracking Logs that are compressed.
1. Use a script to copy and compress (.zip) the Tracking Logs to local path on the UCA machine with a 4:1 compression level, ensure the files go into paths distinctly named for configuring multiple data sources with 1 path in each data source.
2. Create and Configure multiple Exchange Tracking Log data sources, 1 Data Source and Log path per Exchange Server
**Note: If the Tracking Logs are local to UCA, you may want to create another script that deletes the local UCA Tracking Log directories every 3 days. Creating several Exchange Tracking Log Data Sources with 1 path to each Tracking Log Directory is to take advantage of multiple CPU threads as at this time UCA is not a multi-threaded application.
