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
Checking that the configuration of Enterprise Vault Reporting was successful
After you have configured Enterprise Vault Reporting for the first time, perform the following checks to confirm that the Enterprise Vault configuration was successful.
To check that the configuration of Enterprise Vault Reporting was successful
- If a logon does not exist on all these SQL servers, create it.
Check that the reporting user account has an SQL login on the SQL servers that hold the following databases:
The Enterprise Vault Directory database
The Enterprise Vault Monitoring database
The Enterprise Vault Audit database
All vault store databases
All vault store group fingerprint databases
All FSA Reporting databases, if you have configured FSA Reporting
- Check that the SQL server role EVReportingRole has been added to each Enterprise Vault database, and that this role has been assigned to the reporting user.
- Attempt to access the reports.
See About accessing Enterprise Vault Reporting's reports.
Note that before you can use the data analysis reports you must configure FSA Reporting for one or more target file servers and perform at least one successful FSA Reporting data scan.
If you experience any problems, refer to the Enterprise Vault Reporting troubleshooting documentation.