FSA Reporting creates temporary files on the target file server to hold the data from FSA Reporting scans. On a file server with a large number of files, these temporary files can become very large.
FSA Reporting stores the
temporary files by default in the FSAReports
subfolder of the Enterprise Vault
installation folder. The installation folder is often on drive C,
which typically has limited space. If the temporary files fill up
all the space on the installation drive, the computer may suffer
performance problems or stop responding. If there is likely to be
insufficient space for the temporary files on the installation
drive, relocate the storage location to a drive that has sufficient
free space.
The registry value determines the path to the storage location.
To set the storage location for FSA Reporting's temporary files
Create a suitable location on a drive that has sufficient free space, and give the Vault Service account write access to the location.
For an NTFS file server, start the registry editor on the file server.
For a NetApp file server or an EMC Celerra file server, start the registry editor on the Enterprise Vault server that acts as the proxy file server for FSA Reporting file collection.
See Identifying the proxy server for FSA Reporting file collection.
Navigate to the following registry key:
HKEY_LOCAL_MACHINE \Software \KVS \Enterprise Vault \FSA \Reporting
Edit the TempFilePath registry value and specify the existing path that you chose in step 1.
The path that you specify with TempFilePath must not exceed 100 characters, including spaces.
Enterprise Vault creates
a subfolder named FSAReports
under
the path that TempFilePath
defines, in which to hold the temporary files.
On NTFS file servers, restart the Enterprise Vault File Collector service.
For NetApp and Celerra file servers, restart the Enterprise Vault Admin service on the Enterprise Vault server on which you have changed the registry value.