Fixes issue where batch insertion on existing db would delete indexes

When doing batch insertion on an existing database containing indexes,
those indexes, or rather the configuration for them (as well as the
existence of them from the dbs POV) would be deleted if not used in this
second batch insertion. I.e. any index configuration would be overwritten
with whatever this second batch insertion did.

Problem being that the existing index configuration wasn't read (the call
to indexStore.start()) so when shutting down in the end and writing the
index configuration, any existing would be lost.

Fixes #527
Merge pull request #662 from tinwelint/fix-527

Fixes issue where batch insertion on existing db would delete indexes