Enterprise Vault™ Reporting
- About this guide
- Introducing Enterprise Vault Reporting
- How FSA Reporting works
- 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
Adding a file server as an archiving target with FSA Reporting data collection enabled
You can enable FSA Reporting data collection for a file server when you add the file server as an archiving target.
The New File Server wizard takes you through the steps to add the file server. Note the following:
To support FSA Reporting, an Enterprise Vault Directory database must have at least one FSA Reporting database associated with it. The wizard helps you to select an existing FSA Reporting database, or to configure a new database in which to hold the file server's FSA Reporting data.
Before Enterprise Vault creates the first FSA Reporting database, it prompts you for the credentials of a Windows account to use when it accesses FSA Reporting databases.
For non-Windows file servers, the wizard prompts you to select a proxy server to perform the FSA Reporting data collection on the file server.
To add a file server as an archiving target with FSA Reporting enabled
- Make sure that both a forward DNS lookup and a reverse DNS lookup succeed for the file server.
- Start the Enterprise Vault Administration Console. If you are adding a Windows file server, use an account that is a member of the local Administrators group on the file server. If you are adding a non-Windows file server and you want to configure a new proxy server for FSA Reporting, use an account that is a member of the local Administrators group on the proxy server.
- In the Administration Console, expand the Enterprise Vault site until the Targets container is visible.
- Expand the Targets container.
- Right-click the File Servers container, and on the shortcut menu click New and then File Server.
- On the second page of the New File Server wizard, do as follows:
Enter the fully-qualified DNS name of the file server, or click Browse and select the file server.
For a Windows file server, select the option to install the FSA Agent unless the file server already has the latest version of the FSA Agent.
For a non-Windows file server, do not select the option to install the FSA Agent.
- For Celerra/VNX file servers, select whether to use placeholder shortcuts. If you want to use placeholder shortcuts, enter the details of the account on the Celerra/VNX that has permission to use the dhsm feature.
See "Preparing a Celerra/VNX device for FSA" in Setting up File System Archiving.
- On the summary page, click Next to add the file server as an archiving target.
- On the next wizard page the configuration of FSA Reporting begins. Select Enable data collection.
The next wizard pages help you to select an FSA Reporting database in which to hold the FSA Reporting data for the new file server.
If no FSA Reporting databases are associated with the Directory database, the wizard helps you to create an FSA Reporting database.
If one or more FSA Reporting databases are already associated with the Directory database, you can choose to select an existing database, or to create a new one.
- For non-Windows file servers you must select a proxy server to perform the FSA Reporting data collection. You can select an existing proxy server for FSA Reporting if one or more exist, or configure a new proxy server.
If FSA Reporting performs scans on the proxy server, make sure that no scan of the proxy server occurs while you perform this step. If an FSA Reporting scan is in progress, stop the scan or wait for it to finish.
- The final wizard page confirms that the wizard has added the file server successfully, and that the file server is enabled for use.
Specify when to collect FSA Reporting data, and the scope of data collection on this file server. Do one of the following:
Select Use the default settings for FSA Reporting data collection. FSA Reporting then uses the default FSA Reporting data collection settings, which are set on the properties of the File Servers container.
Clear Use the default settings for FSA Reporting data collection and provide the non-default settings for this file server.
The final wizard page also notes that you must do the following before you can use the FSA Reporting reports:
Add the required target volumes and enable them for FSA Reporting data collection, if required.
Install and configure Enterprise Vault Reporting if you have not already done so.
Wait for at least one FSA Reporting scan to complete successfully.
When you enable FSA Reporting data collection for a file server, Enterprise Vault automatically enables data collection for any existing target volumes.
If you add new target volumes you must enable them for data collection, if required.