Two indexes location

You can define multiple index locations and they all we be used.

On your move question,

If I'm not mistaken as long as they are for the same archive connection you shouldn't have an issue moving them and changing the index location.

Use Copy instead of move, test the functionality and then you can delete once everything tests properly.

Thanks for answer. Both indexes are under same archive connection. The thing is, that we have one disc for indexes almost full and messages stays in Message centre, event though second disc for indexes has more, than 1TB free space.

In EventLog is many events related with this, like:

* Unable to write to the repository storage. (0x86040F2A) [ExAsArchive.exe, ExASRecvMsg.cpp(157).CExASRecvMsg::StoreMsg]

* Unable to continue processing this job. (0x86040B1B) [ExShortcutJBC.exe, CExJBMBoxTasks.cpp(1136).CExJBMBoxTasks::ProcessMessages]

>Attribute Cmptd not found

* The dispatcher thread received an error from the the Job Business Component (JBC): ExShortcutJBC.CoExShortcutJBC, HR: 0x86040B1B. (0x86040906) [ExJobDispatcher.exe, ExJobThread.cpp(1373).CExJobThread::Run]

Test connection to storage pool passed successfully. Other services works also without any problem. Is there any way, how to force EMC to use second index disc? Or is there anything else, what can cause this?

For this issue i will suggest you to engage support.

Basically since original drive would have fallen below watermark all data would be sitting in unpack_area section of message center now causing other jobs e.g. journaling to fail because those jobs write to message center.

Go to index dropdir folder and see which year month files belong to. They most probably will be having 201409 in it. If that is the case do following.

1. Stop jounaling Jobs.

2. Stop index service on your native arvhive servers.

3.from index share1 that fell below threshold copy 201409 to index share2.

4. Similerlary move all files with 201409 in their name from dropdir of index share1 to dropdir of index share2

5. Start index servie back.

6. Keep an eye on emc event logs to make sure no errors ae thrown.

7. As indexer will index data you should get space back in message center.

8. It may take some time though.

I assumed that you already added s3cond index location akready through sourceone adMin console.

If any doubt you can work with support for peace of mind.

Best regards,

Rajan Katwal

Sent from mobile device.

Please ignore typing mistakes.

Since you are in the state of receiving errors already, as Rajan suggested, getting support involved to help you straighten this out with be the best path at this point.