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
About the FSA Reporting proxy servers for non-Windows file servers
The Enterprise Vault File Collector service cannot run on non-Windows file servers, that is NetApp Filers and Dell EMC Celerra/VNX devices. Another server must act as a proxy to perform the FSA Reporting data collection remotely. We refer to this server as the FSA Reporting proxy server.
When you configure FSA Reporting for a non-Windows file server, you must select a server to act as the FSA Reporting proxy server. You can choose an existing FSA Reporting proxy server if you have already configured one.
Any of the following can act as an FSA Reporting proxy server, subject to the necessary prerequisites:
An Enterprise Vault server in the Enterprise Vault site.
A Windows file server that is configured as a file server archiving target in the Enterprise Vault site.
A Windows server on the network.
See FSA Reporting proxy server requirements.
If you configure several FSA Reporting proxy servers you can use a mix of the proxy server types if you want.
Figure: FSA Reporting proxy server options shows an example configuration that uses all of the FSA Reporting proxy server types.
Note the following:
When a Windows file server or a networked Windows computer acts as an FSA Reporting proxy server, the FSA Agent must reside on the proxy server to provide the File Collector service. When you choose the proxy server, Enterprise Vault prompts you to install the FSA Agent if it is not already present.
Note:
To enable FSA Reporting on NetApp C-Mode filers, you must have the Enterprise Vault 11.0.1 or later FSA Agent installed.
When an Enterprise Vault server acts as a proxy server, a program named
FSAReportingService.exeon the Enterprise Vault server performs the file collector tasks. The Enterprise Vault Admin service starts and governs theFSAReportingService.exeprogram.
Table: Benefits and disadvantages of the FSA Reporting proxy server types lists some factors to consider when you choose the type of proxy server.
Table: Benefits and disadvantages of the FSA Reporting proxy server types
Server type | Benefits | Disadvantages |
|---|---|---|
Enterprise Vault server | Uses the existing Enterprise Vault infrastructure, so you have no additional servers to manage. Does not require the FSA Agent, so no additional installation of the FSA Agent is required. | Adds the proxy server resource demand to the Enterprise Vault server, so may adversely affect the existing Enterprise Vault tasks and applications. |
Windows file server archiving target | Uses the existing Enterprise Vault infrastructure, so you have no additional servers to manage. Useful in a distributed environment with Windows file server archiving targets available locally and centralized Enterprise Vault servers. A local Windows file server archiving target can avoid the need to scan over a wide area network. | Adds the proxy server resource demand to the file server, so may adversely affect the file server's existing tasks and applications. Enterprise Vault applications on the file server may run more slowly. |
Other Windows server on the network | Useful in a distributed environment when there are no Windows file server archiving targets or Enterprise Vault servers available locally. By using a local Windows server you can avoid the need to scan over a wide area network. Does not add the proxy server resource demand to an Enterprise Vault server or Windows file server archiving target. | Additional hardware provision required: another server to manage. Requires a separate installation of the FSA Agent. |
The resource demand on an FSA Reporting proxy server tends to increase with the following:
The number of file servers that you have assigned to the proxy server.
The number of archive points and volumes that require scanning for FSA Reporting.
The number of FSA Reporting scans the proxy server performs concurrently.
If you configure FSA Reporting for several non-Windows file servers in an Enterprise Vault site, you can spread the proxy server load as follows:
Distribute the non-Windows file servers among several FSA Reporting proxy servers.
Assign different proxy servers to the file servers with the most volumes that are enabled for FSA Reporting.
Assign different proxy servers to the file servers that have the same FSA Reporting scan schedule.
Stagger the FSA Reporting scan schedules for the file servers that are assigned to the same proxy server.
We recommend that you use a separate FSA Reporting proxy server for each non-Windows file server, if possible.