cancel
Showing results for 
Search instead for 
Did you mean: 

Index Volume scope

rnt123
Level 5

Hello,

 

I was using the Index Volume Browser, and I got to wondering what is the scope of an Index Volume? I know that the Index location is the actual NTFS path for storing an index, but is the scope of an Index Volume the entire Archive or an archive for an individual mailbox / user?

 

Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

It is important to note that Index Volumes that exist in closed index locations will continue to have data written to them for the life of the associated archive or until the Index Volume rolls over

One slight correction, that is not the case in EV 10.  In EV 10 see the referenced doc, it says this:

"Previous versions of Enterprise Vault w ould allow an index location to be closed. How ever, this simply meant that no new Index Volumes would be created in the closed index location, but additional index data could still be added to existing Index Volumes.

When closing a 64-bit Index location, the location is now actually closed and no further data written to it.."

Enterprise Vault 10.0 - Indexing Design and Implementation Best Practices

Article:DOC4250  |  Created: 2011-06-08  |  Updated: 2012-04-19  |  Article URL http://www.symantec.com/docs/DOC4250

Regards

 

View solution in original post

5 REPLIES 5

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

Can you share what version of EV?

So an archive can have multiple index volumes.  In EV 10 if you close an index location a new index volume will be created that is associated with the archive.  Also, archives for journal mailboxes tend to be quite large, so a new volume is created for those based on defined tresholds. 

HTH,

Tony

A_J1
Level 6
Employee Accredited Certified

Hi,

Each archive will have an associated Index Volume or Volumes. (It is possible for an archive to have multiple index volumes associated with it as the index volume will roll over once it is at capacity) Each Indexing Service allows the creation of multiple Index Locations which determines where Index Volumes are to be created. If there are multiple Index locations open the Indexing Service creates new index Volumes randomly across the open locations in an effort to spread them out across the environment.
 
It is important to note that Index Volumes that exist in closed index locations will continue to have data written to them for the life of the associated archive or until the Index Volume rolls over. After that only updates to the index because of deletions will change the volumes. Additionally, if you move an Index Volume to another EV Server and Index service make sure to move all volumes associated with the archive to keep them grouped together.
 
I hope this Helps...
 
 

A_J1
Level 6
Employee Accredited Certified

If you have any further queries let me know...

JesusWept3
Level 6
Partner Accredited Certified
In EV9 and below closed index root paths would continue to grow, EV 10 closing a path would force a roll over
https://www.linkedin.com/in/alex-allen-turl-07370146

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified

It is important to note that Index Volumes that exist in closed index locations will continue to have data written to them for the life of the associated archive or until the Index Volume rolls over

One slight correction, that is not the case in EV 10.  In EV 10 see the referenced doc, it says this:

"Previous versions of Enterprise Vault w ould allow an index location to be closed. How ever, this simply meant that no new Index Volumes would be created in the closed index location, but additional index data could still be added to existing Index Volumes.

When closing a 64-bit Index location, the location is now actually closed and no further data written to it.."

Enterprise Vault 10.0 - Indexing Design and Implementation Best Practices

Article:DOC4250  |  Created: 2011-06-08  |  Updated: 2012-04-19  |  Article URL http://www.symantec.com/docs/DOC4250

Regards