Video Screencast Help

Move EV10 indexes from existing path (seperate file server) to a different file server

Created: 24 Jul 2013 • Updated: 11 Aug 2013 | 4 comments
cl12's picture
This issue has been solved. See solution.

Hi Guys

we are currently running EV 10 on Windows Server 2008 R2, the index locations are currently located on a fileshare resource on a cluster (call this fileshare01), this cluster is decommissioned so we want to update the location within EV to point to the new fileshare resource (call this fileshare02)

the data has been 'moved' to the new location via taking an array level snapshot and presented to the new fileshare resource (so the data is as was !)

i followed what i had done in the past (EV9 <) which is stopping EV services, then updating the SQL DB Indexrootpathentry location to point at the new location then restart of EV services - but this failed to work (i.e. items cannot be pulled back doing searches)

i get the feeling that EV 10 may need further updating to point to this new location

any thoughts ?

C

Operating Systems:

Comments 4 CommentsJump to latest comment

GabeV's picture

Take a look at this TN for EV 10:

http://www.symantec.com/docs/HOWTO59084

It has SQL query that it is a little bit different from EV 9.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

GabeV's picture

Also, if you want to move an index location from one Enterprise Vault server to another, this TN will help:

How to move the Index Location to a Different Location on a Different Server
http://www.symantec.com/docs/HOWTO82325

It's for Enterprise Vault 10 as well.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill

SOLUTION
cl12's picture

Hi

having looked through the docs ... as we're not creating any new indexes and instead just going to update the location of the existing, i'm pretty confident that if we update the IndexRootPathEntry in SQL then run the below to force EV to update

UPDATE IndexingServiceEntry
SET IVSyncNeeded = 2

EV should update the location and all be well ?

C

 

GabeV's picture

Yes. That is correct. Running that update statement should be sufficient to inform Enterprise Vault that it needs to update the paths of the volumes on service startup.

I hope this helps.

“Success is not final, failure is not fatal: it is the courage to continue that counts.”–Winston Churchill