Enterprise Vault™ Reporting
- About this guide
- Introducing Enterprise Vault Reporting
- Overview of implementing Enterprise Vault Reporting
- Installing Enterprise Vault Reporting
- Configuring Enterprise Vault Reporting
- Configuring FSA Reporting
- Configuring FSA Reporting
- Preparing for an FSA Reporting proxy server
- Adding a file server as an archiving target with FSA Reporting data collection enabled
- Enabling FSA Reporting data collection for an existing target file server
- Enabling or disabling FSA Reporting data collection for a file server target volume
- Setting the defaults for FSA Reporting data collection
- Setting the storage location for FSA Reporting's temporary files
- Verifying the placeholders on Dell EMC Celerra/VNX devices
- Including NetApp filer snapshot folders in FSA Reporting scans
- Checking that the configuration of FSA Reporting was successful
- Accessing the reports
- About accessing Enterprise Vault Reporting's reports
- Administrator roles that provide access to Enterprise Vault Reporting's reports
- Accessing Enterprise Vault Reporting's reports from SQL Server Reporting Services Report Manager
- Accessing Enterprise Vault Reporting's reports from the Administration Console
- Managing FSA Reporting
- Managing FSA Reporting
- Viewing the status of FSA Reporting
- Running an unscheduled FSA Reporting scan on a file server
- Stopping FSA Reporting scans
- Disabling all FSA Reporting data collection
- Changing the default FSA Reporting data collection schedule
- Changing a file server's FSA Reporting database
- Maintaining the FSA Reporting databases
- Changing the FSA Reporting proxy server for a non-Windows file server
- Modifying the FSA Reporting data collection parameters
- Obtaining data for a specific file type in the FSA Reporting reports
- Upgrading the FSA Agent
- Troubleshooting Enterprise Vault Reporting
- Appendix A. Report overviews
- The Enterprise Vault Reporting operation reports
- Archive Quota Usage report
- Archived Items Access report
- Archived Items Access Trends report
- Content Provider Ingest History report
- Content Providers Licensing and Usage Summary report
- Domino Mailbox Archiving Status report
- Domino Server Journal Mailbox Archiving Health report
- Domino Server Journal Mailbox Archiving Trends report
- Enterprise Vault Server 24-hour Health Status report
- Enterprise Vault Server Seven Day Health Status report
- Exchange Mailbox Archiving Status report
- Exchange Server Journal Mailbox Archiving Health report
- Exchange Server Journal Mailbox Archiving Trends report
- IMAP usage report
- Items Archival Rate report
- Move Archive report
- Single Instance Storage Reduction by File Type report
- Single Instance Storage Reduction per Vault Store Group report
- Single Instance Storage Reduction Summary report
- SMTP Provisioning report
- Vault Store Savesets report
- Vault Store Usage by Archive report
- Vault Store Usage by Billing Account report
- Vault Store Usage Summary report
- The FSA Reporting data analysis reports
- Archive Points Space Usage Summary report
- Drive Space Usage on a Server report
- Drive Space Usage Summary report
- Duplicate Files on a Server report
- Duplicate Files Summary report
- File Group Space Usage on a Server report
- File Group Space Usage Summary report
- Inactive Files on a Server by File Group report
- Inactive Files on a Server by User report
- Inactive Files Summary report
- Storage Summary report
- Storage Trends report
- File Space Usage on an Archive Point report
- Largest Files Per Volume report
- Largest Files of a Specified File Type Per Volume report
- Top Duplicate Files Per Volume report
- The Enterprise Vault Reporting operation reports
Setting the storage location for FSA Reporting's temporary files
FSA Reporting creates temporary files on the target file server to hold the data from FSA Reporting scans. On a file server with a large number of files, these temporary files can become very large.
FSA Reporting stores the temporary files by default in the FSAReports subfolder of the Enterprise Vault installation folder. The installation folder is often on drive C, which typically has limited space. If the temporary files fill up all the space on the installation drive, the computer may suffer performance problems or stop responding. If there is likely to be insufficient space for the temporary files on the installation drive, relocate the storage location to a drive that has sufficient free space.
The registry value determines the path to the storage location.
To set the storage location for FSA Reporting's temporary files
- Create a suitable location on a drive that has sufficient free space, and give the Vault Service account write access to the location.
Note:
The path must not exceed 100 characters, including spaces.
- For a Windows file server, start the registry editor on the file server.
For a NetApp filer or a Celerra/VNX device, start the registry editor on the server that acts as the FSA Reporting proxy server.
- Navigate to the following registry key:
On a 32-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \KVS \Enterprise Vault \FSA \ReportingOn a 64-bit installation of Windows:
HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault \FSA \Reporting - Edit the TempFilePath registry value and specify the existing path that you chose in step 1.
The path that you specify with TempFilePath must not exceed 100 characters, including spaces.
Enterprise Vault creates a subfolder named
FSAReportsunder the path that TempFilePath defines, in which to hold the temporary files. - Exit from the registry editor.
- On Windows file servers, restart the Enterprise Vault File Collector service.
For NetApp filers and Celerra/VNX devices, restart the Enterprise Vault Admin service on the Enterprise Vault server on which you have changed the registry value.