Warn in Import Existing Data to not use index path that another instance is using

It is very easy for customers to end up with two instances running on the same box, but have both using the same search index directory. Very bad!

All they have to do is take a copy of their database and use it for the new instance.

In the absence of a proper solution such as something like JRA-11623, could we put some scary warnings in the Import Existing Data page, saying to make sure that the index path is not being used by another instance, for example, one that you may have exported data from?

I know this won't capture the case when the customer uses database management tools to copy the database. For that we'll need a proper solution.

Cheers,
Ian