...
This is just our way of organizing things. If you're wondering, the directory names come from the 1st (a) and 2nd to 4th (0d9) of the filenames, which come from an MD5 hash of the indexed record's properties (name, format, etc.), which we use as an ID to keep track of things. Every record in Voyager has one of these IDs - We don't expect you to use them (except for very specific / debugging searches).
...
Disk Space Required for Indexing
...
When we indexed these sources, we did so completely. This means that we created (150 x 150 pixel) thumbnail and (512 x 512 pixel) preview images for each record. We also retained the default option to Extract Linked Data from the datasources, so we'd pull local copies of the LYR and XML files from MXD and GDB layers where present.
...
...
When indexing was complete, we noted the following storage footprints in the \v0 and \meta directories.
...
...
All told, we're looking at approximately 70 Mb per 1000 index records, but let's round that up to 100 Mb per 1000 records to be conservative. For each record in the index, we need 0.1 Mb (100 kb) of space set aside. You'll notice that the search index requires much less storage than the meta files.
...
Stop the Voyager Search service / system process
Edit the file <VoyagerInstallPath>\server_<version>\app\Voyager.vmoptions
Enter a new path for the Voyager index directory parameter (-Dindex.dir) - This can be an absolute path (to a mapped drive, a relative path (shown), or a UNC to a network share.
Alternatively, you can enter a new path for the entire Voyager data directory parameter (index, meta, and logs etc.) (-Ddata.dir).
...
Metadata File Size Management
...