Enterprise Vault™ Introduction and Planning
- About this guide
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Archive Discovery Search Service
- About the Enterprise Vault Outlook Add-In
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- About Exchange Server archiving and user mailboxes
- Exchange Server and journal mailbox archiving
- Exchange Public Folder archiving
- File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- The Compliance Accelerator client application
- About Discovery Accelerator
- Discovery Accelerator client application
- Building in resilience
- About Enterprise Vault and VCS
- About Enterprise Vault and Windows Server Failover Clustering
- About Enterprise Vault building blocks
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
FSA Reporting provides summary reports on the active data on your file servers, and on the data that has been archived from them. FSA Reporting's reports include data on a wide range of items including the following:
The number of archived files for each file server, and the space used and saved as a result of archiving. You can also view the 10 largest files in a volume.
Active and archived space usage by different file groups, per server and per archive point.
Numbers of unaccessed or duplicated files, and the space they are occupying.
Used and free space on the drives of each file server.
Many of the reports can provide either an overall view for all file servers with FSA Reporting configured, or a detailed view for a named file server.
In order to access FSA Reporting's reports, the Enterprise Vault Reporting component must be installed and configured on a computer with the required prerequisites, including Microsoft SQL Server Reporting Services. You use the SQL Server Reporting Services Report Manager web application to view the reports.
You must also configure FSA Reporting for each file server target for which you want to obtain reports. The Administration Console provides wizards to help you do the following:
The first time that you configure a file server target for FSA Reporting, a wizard helps you to set up an FSA Reporting database to hold the FSA Reporting scan data.
When you configure another file server target for FSA Reporting, you can assign the file server to an existing FSA Reporting database, or create another database. Multiple FSA Reporting databases can provide scalability if you obtain FSA Reporting data for many file servers.
For a Windows file server, install the FSA Agent on the file server if the agent is not already present
For a non-Windows file server, that is NetApp Filers and Dell EMC Celerra/VNX devices, select another server to act as the FSA Reporting proxy server. The FSA Reporting proxy server gathers the FSA Reporting data for one or more non-Windows file servers.
Any of the following can act as an FSA Reporting proxy server, subject to some additional prerequisites:
An Enterprise Vault server in the Enterprise Vault site.
A Windows server that is configured as a file server archiving target in the Enterprise Vault site.
A Windows server on the network.
To enable FSA Reporting on NetApp C-Mode filers, you must have the Enterprise Vault 11.0.1 or later FSA Agent installed.
For more information, see the Reporting guide.