The filestore is where the binaries are physically stored.
Artifactory provides the following options to store binaries:
Local file system stores binaries with redundancy, using a binary provider that manages the synchronization of files between cluster nodes according to the defined redundancy settings.
Cloud storage is done using Amazon S3, Microsoft Azure, and Google Cloud Storage.
Network File System (NFS)
For more information, see Filestore Configuration.
Binary Storage
While Artifactory can use a Networked File System (NFS) for its binary storage, you should not install the application itself on an NFS. The Artifactory application needs very fast, reliable access to its configuration files. Any latency from an NFS will result in poor performance when the application fails to read these files. Therefore, install Artifactory on a local disk mounted directly to the host.
To use an NFS to store binaries, use the file-system binarystore.xml configuration with the additional <baseDataDir> setting.
Working with Very Large Storage
In most cases, our recommendation for storage is at least 3 times the total size of stored artifacts, in order to accommodate system backups.
However, when working with a very large volume of artifacts, the recommendation may vary greatly according to the specific setup of your system. Therefore, when working with over 10 TB of stored artifacts, contact JFrog support, who will work with you to provide a recommendation for storage that is customized to your specific setup.
Allocated storage space may vary
Xray downloads and then deletes fetched artifacts after indexing. However, in order to have more parallel indexing processes, and thereby more temporary files at the same time would require more space.
This is especially applicable for large BLOBs such as Docker images.