Forum Discussion

-Maurice's avatar
-Maurice
Level 4
12 years ago

Move multiple indexvolumes using "Manage Indexes" "Change location"

Hello community, a few points to the envorinment of my "issue" Environment 4 EV Server each with one Vault Store Version EV 10.0.1 / Exchange 2010   I have one customer which has round 9k...
Configuring
Enterprise Vault
Information Governance
  • Switch's avatar
    Switch
    12 years ago

    The process I outlined is for moving the indexes of all archives in a particular vault store irrespective of the index locations. Even if the indexes are spread across multiple drives, when you query for the FolderName and IndexrootPath from tables IndexVolume and IndexRootPathEntry, you get the list of folders with paths for the particular vault store.

    Then you can use robocopy or similar tools to copy only those folders from the Query results to the new EV server. Then follow the remaining procedure for updating the IndexRootPathEntry, IndexServiceEntry and StorageServiceEntryID.

    I would not suggest the procedure if you are not comfortable with EV SQL databases.

     

    I also think you can further customize the query to indentify the index folders for individual Archive instead of a VaultStore as a whole. I have to check it out in lab whether that is possible, however I can guarantee for all indexes of archives in a particular vault store.

     

    Edit: In the above process, you do not have to copy the index volumes to exact locations on the new servers. If you index is spread across multiple locations, you can copy them to a single location in new server. eg: You current index for that vault store is spread across I:\Index1, I:\Index2, J:\Index1. You have to move them to single location \\newserver\I$\Index1. This makes the update statement simple.

-Maurice's avatar
-Maurice
Level 4
12 years ago

First of all, the reallocation of the index volumes worked as expected using direct updates in the directory database.

As promised, a short update on this with a highlevel description of the tasks I performed.

 

Added a new IndexingLocation to copy the volumes from evserver01 and i set the backupmode for all indexing locations.

Created a SQL query to get the list of index volumes which needs to be moved (this was the most of the work)

This query was then used in a PS script to construct the source volume path and to initiate the copy-item command to copy each indexvolumes to the newly created indexinglocation.

Note: The query used the following values

dbo.IndexVolume.IndexRootPathEntryId, dbo.IndexRootPathEntry.IndexRootPath, dbo.IndexVolume.FolderName

After i checked that the volumes are copied succsessfully the the destination location. Then I used another SQL script to update the IndexRootPathEntryId for these indexing volumes. I triggered a IVSync to update the Metadata on the EVservers on all servers

After this was done, i created a "basic" Index Verify Task to check all the indexing volumes on EVServer02 to doublecheck that everything is fine.

Overall this whole procedure took around less then eight hours, starting from script creation, Lab testing, execution and verify (was started in the evening and completed during the night)

 

Cheers Maurice

PS: PowerShell is just great! It's so powerful and easy to use too.

PPS: I don't like to share these scripts here in public, because you can may damage your environment if you are not aware of - how these scripts and queries are working together and are depended from each other. If you are interested in these scripts and you have a use case, just send me a private message here and I will get in touch with you.