A Local File Store maps to one or more base directories known as mount points. A file store consists of one or more mount points in which files are stored, which can be extended while pure runs with no down time. A file store is somewhat similar to a Volume Group in LVM. It is possible to define an arbitrary number of file stores to best suit the storage requirements of the pure installation
When files are uploaded to Pure they are stored in a temporary file storage at first and then distributed to all storages with matching filters. If no store with matching filters is found the default file storage is used.
System stores
Two system stores are configured by default, the Local file storage and Temporary file storage. These stores can not be deleted, but the storage system can be configured to store files in other locations.
This is configured in Administrator > Storage > File storage.
Local file storage
The "local" storage of files. By default Pure is configured to use S3 storage as default location for files. This can be changed to use your local file system and also be expanded with an additional path, for example to expand the current storage space.
Temporary file storage
The default storage for temporary files. This this is where new files are stored until the Preserved Content Update Job moves them to their correct destination.
Deleting a mount point
If a store has more than one mount point it is possible to remove a mount point by scheduling it for delete. The synchronization job will move all files from the deleted mount point to other mount points, and delete it when it's empty.
Editing a mount point
The location of mount points can be edited. This can be used if the pure instance have been moved or copied to another server.
Pure will not move existing files to the new location, but assume that they have been manually copied.
License
A license text can be enabled for a store. The license will be displayed when users adds files to content that matches the storage filters.