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
- Preparing for an FSA Reporting proxy server
- Accessing the 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
- Managing FSA Reporting
- Maintaining the FSA Reporting databases
- Troubleshooting Enterprise Vault Reporting
- Appendix A. Report overviews
- The Enterprise Vault Reporting operation reports
- Archived Items Access Trends report
- The FSA Reporting data analysis reports
- The Enterprise Vault Reporting operation reports
How Enterprise Vault Reporting works
You can use Enterprise Vault Reporting with or without FSA Reporting configured.
Figure: How Enterprise Vault Reporting works: without FSA Reporting illustrates how Enterprise Vault Reporting works when FSA Reporting is not configured.
You access the Enterprise Vault reports from the Microsoft SQL Server Reporting Services Report Manager web application. You must log on to Report Manager with a user account that belongs to a suitable administrator role. The administrator role determines which reports you can access.
Enterprise Vault displays a list of reports that are appropriate for your administrator role. When you select a report, the Enterprise Vault data extension on the Microsoft SQL Server Reporting Services server computer issues a query to obtain the required data from the Enterprise Vault databases. Report Manager then displays the generated report.
You can also access the reports from the Enterprise Vault Administration Console.
Different reports require information from different Enterprise Vault databases. Each of the operation reports requires data from one or more of the following databases:
Vault store databases. A vault store database holds information about each item that is archived in the associated vault store.
Directory database. The Directory database holds Enterprise Vault configuration data for one or more Enterprise Vault sites.
Fingerprint databases. Each fingerprint database holds information about the single instance storage parts for a vault store group.
Monitoring database. This database holds the status information that the Enterprise Vault monitoring agents gather about the Enterprise Vault servers.
Auditing database. This database holds the data that the Enterprise Vault auditing mechanism gathers.
Note:
Enterprise Vault monitoring and auditing must be enabled if you want to use the reports that require data from these databases.
See Enterprise Vault reports that require monitoring or auditing to be enabled.