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
Guidelines for deploying FSA Reporting
Follow these guidelines for all FSA Reporting deployments.
Note:
There are additional guidelines if you use FSA Reporting with non-Windows file servers. See Additional guidelines for NetApp and Dell EMC Celerra file servers.
If you have more than nine file servers on which you want to run FSA Reporting scans, we recommend that you stagger the scan start times so that Enterprise Vault scans no more than nine file servers concurrently.
By default, FSA Reporting performs up to five simultaneous target volume scans on a file server. As an approximate guide, this default value is suitable if each target volume contains no more than the following:
5000 archive points
4 million archived files
40 million files
If your target volumes exceed one or more of these values, we recommend that you reduce the number of simultaneous target volume scans.
See Changing the number of simultaneous target volume scans.
From Enterprise Vault 9.0 onwards you can configure multiple FSA Reporting databases to provide scalability. FSA Reporting can upload the data faster from multiple file servers if there are multiple FSA Reporting databases. For more information, see "About the FSA Reporting databases" in the Enterprise Vault Reporting guide.
To improve performance in any configuration, we recommend that you use a dedicated SQL Server or SQL Server instance for the FSA Reporting databases.
In configurations where a large number of scans occur, the scans can take longer to complete if there is limited disk space in the folder where the Enterprise Vault server stores the scan data and metadata XML temporary files. If necessary, you can use a registry value to specify a different location that has more space.
See Changing the storage location for scan data on an Enterprise Vault server.