HTML renderings and text extractions have a significant impact on the amount of storage required per file for the Filr appliance. In a small deployment, index files and database files also have an impact on the amount of storage required per file for the Filr appliance.
HTML Renderings: Each time a user renders a file as HTML (either by clicking View Details on the file from the web interface, by clicking View as HTML from the web interface, or by tapping on a file from the mobile app), that rendering occupies additional disk space.
HTML renderings for files in both Personal Storage and files in Net Folders are stored in the /vashare directory in a clustered environment and in the /vastorage directory in a non-clustered environment.
Only one HTML rendering can exist for a single document. If a user views a file as HTML and a rendering already exists, a second rendering is not created.
The amount of space the HTML rendering occupies differs depending on the type of file that is rendered:
Office file renderings (such as Microsoft Office and OpenOffice) require the same amount of disk space as the original file. (For example, a 1 MB file requires an additional 1 MB of disk space for the HTML rendering.)
PDF renderings require approximately 10 times the amount of disk space as the original file. (For example, a 1 MB file requires an additional 10 MB of disk space for the HTML rendering.)
PowerPoint renderings require approximately 3 times the amount of disk space as the original file. (For example, a 1 MB file requires an additional 3 MB of disk space for the HTML rendering.)
If HTML renderings are consuming more than 10 GB of disk space on your system, you can delete all HTML renderings by restarting the Filr appliance.
Text Extractions: When an indexed file is added to Filr (either to Personal Storage or to a Net Folder), text from the file is extracted and added to the search index to be used for searching. By default, each text-extracted file is truncated to 1.1 MB.