By default, ETA stores all networksA network is a visual summary, generated by ETA, of the information in one or more documents. and document collectionsA collection is a container for storing and organising ingested files and documents. Only the textual content is stored in collections, not the original files and documents. in the directories ‘networks’ and ‘collections’ in the <ETA database directory>The directory in which the ETA database is stored, for example, C:\Users\Documents\ETA database., as specified in WEB-INF/config/site-config.xml, under entry <data-directory>.
Note: The database locations configuration is not configurable from the GUI. File system access to the server is required.
You can expand the disk space available to ETA by adding more locations on the file system for ETA datastores.
Configured datastores are listed the System Overview pane.
To view datastore locations:
Each entry shows the path, the total disk space used, the remaining disk space available and the number of collections and networks stored at each datastore. Clicking on the number of collections or networks shows a detailed summary of which networks or collections are present and how much disk space each of them occupies.
If no new collections/networks will be automatically created in a datastore (writeable="false"), a padlock icon is displayed.
To add more datastores:
<root> <ext-data-directory writeable="true" forDocuments="true" forNetworks="true">D:\secondary-db\</ext-data-directory> <ext-data-directory writeable="true" forDocuments="true" forNetworks="true">E:\tertiary-db\</ext-data-directory> </root>
There can be any number of ext-data-directory elements.
writeable is a flag which specifies whether ETA writes to that data store (if it’s set to false, ETA will accept networks or collections found there on startup, but will not add more data there).
forDocuments is a flag which tells ETA that this datastore should be used for document collections.
forNetworks is a flag which tells ETA that this datastore should be used for networks.
ETA accepts an arbitrary number of datastore locations. If there is a choice, any new collection and network will be created in the datastore that has the smallest total disk usage at the time of creation.
If external datastore locations are specified and at least one of them specifies writeable="true", then no new collections or networks will be created under the main storage (as if the main storage became writeable="false").
If ETA is configured to not create any new collections/networks in the datastore (writeable="false") then this process is the only way to populate such a datastore.
If there is more than one datastore with the same ID (for example if data was accidentally copied instead of moved), ETA will not start, to prevent any data loss.
Warning: Do not start the ETA server while the move is in progress. ETA can delete partially-moved databases during startup.
To move a collection or network between two datastores:
The System Overview pane should now confirm that the network or collection is now present in the new datastore.