Enterprise Vault™ FSA Reporting Deployment Guidelines
- Deploying FSA Reporting with Enterprise Vault
- About deploying FSA Reporting with Enterprise Vault
- Assumptions, notes, and recommended settings
- Guidelines for deploying FSA Reporting
- Changing the number of simultaneous target volume scans
- Managing the data uploads to the FSA Reporting databases
- Changing the storage location for scan data on an Enterprise Vault server
About deploying FSA Reporting with Enterprise Vault
This technical note contains important information about the deployment of FSA Reporting in an environment that uses Enterprise Vault 9.0 or later.
We recommend that you install or upgrade to the latest available service pack for your version of Enterprise Vault, if you intend to use FSA Reporting.
You must install a compatible version of the FSA Agent on any Windows file servers on which you run FSA Reporting, and on any servers (other than Enterprise Vault servers) that act as FSA Reporting proxy servers. For information on compatible versions of the FSA Agent see the following technical note on the Veritas Support website:
https://www.veritas.com/docs/100030221.
This FSA Reporting deployment guidelines technical note provides advice on:
The factors that affect how many file servers you should attempt to scan simultaneously.
How to configure Enterprise Vault for improved performance with FSA Reporting.
Managing data uploads to the FSA Reporting database, and temporary data storage on the Enterprise Vault server.
Note:
The figures that are quoted in this technical note are based on practical experience, but they can only provide approximate guidelines. Every customer has different needs and different environments. Many factors influence the performance of an archiving system, including the type and size of data that is archived, the file types, and so on. In addition, most systems expect growth in both volume and size of data. These factors lead to the need to be very cautious when you deploy a system.