Prerequisites
A volume consists of:
- Store data in a store directory. Sub-directories containing .mrc files (v2 and lower) or .zz files (v3 and higher). The root of the store path also contains a file called volumeinfo (meta data about the volume)
- Index data in an index directory. Contains Lucene index files.
The volume can be imported/restored without b) index data, but not without a) store data.
The imported volume must be encrypted using exactly the same encryption passphrase as is configured in Configuration->Volumes. If not, the volume will be unreadable and its data will need to be reecrypted.
Import Procedure
Volume Status | Description |
ACTIVE or CLOSED | The volume is recognized. It is most likely readable. |
UNREADABLE | The volume is likely encrypted using a different encryption key. It is necessary to reencrypt the volume. |
UNMOUNTED, NEW | Архива does not have sufficient privileges to read/write from the location. Alternatively, the volume store path is missing a volumeinfo file in the root of the store path. |
No Index Data
If no volume index data is available, the imported volume will need to be reindexed. During the import, choose an empty local directory where the volume index should reside (Архива will create the directory location you specify automatically if not already present). Thereafter, click Save and then, assuming the volume status is either ACTIVE or CLOSED, reindex the newly imported volume.
VolumeInfo Missing
The volumeinfo file is a text file (editable using Notepad or vim) that typically resides in the root of the store path. It contains the unique volume id, created date, closed date, and volume status. It is possible to create a new volumeinfo file, by copying one over from an existing volume, editing using a text editor, and manually changing the ID slightly to another random hex value (one digit can be modified if so desired). Assuming the volume ID was changed, the volume must be reindexed.