People using FSA Reporting should be aware that there can be an accumulation of .OUT files on the EV server or File Server, and that they might be clumped together and date back a long time. These can take up considerable space. The cause of this is FSA Reporting. What can happen is that if an FSA Reporting scan errors out/fails/crashes the .OUT files don’t get cleaned up.
You can move the location of these temporary files, by doing the following :
Add the following registry key : HKEY_LOCAL_MACHINESOFTWAREKVSEnterprise VaultFSAReportingTempFilePath. “TempFilePath” should specify a folder path on the server under which FSA Reporting stores its temporary data files. FSA Reporting creates a subfolder named FSAReports under the specified path, in which to hold the temporary files.
If there is likely to be insufficient space for the temporary files on the installation drive, relocate the storage location to an existing path on a drive that has sufficient free space.
Note: The value of TempFilePath must not exceed 100 characters, including spaces.
For Windows file servers TempFilePath is located on the file server.
For NetApp and EMC Celerra file servers, TempFilePath is located on the Enterprise Vault server that performs the FSA Reporting file collection.
If you change this value on a Windows file server, restart the Enterprise Vault File Collector service on the file server. If you change this value on an Enterprise Vault server, restart the Enterprise Vault server’s Admin service.