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 the data uploads to the FSA Reporting databases
FSA Reporting can perform data uploads to an FSA Reporting database in parallel. For sites in which large numbers of FSA Reporting scans occur, parallel upload can greatly improve the data upload rate. FSA Reporting uploads the data for each archive point separately.
The data upload threads collect the data from the FSA Reporting scan threads, and then upload the data to the database. By default, FSA Reporting uses up to three data upload threads per file server.
If you suspect that there is a data upload bottleneck, you can increase the number of available data upload threads.
See Modifying the number of available data upload threads.
If FSA Reporting uploads data from large numbers of file servers in parallel you can benefit from configuring multiple FSA Reporting databases.
see "About the FSA Reporting databases" in the Enterprise Vault Reporting guide.