What happens when closing an Index location and opening another one

Article:TECH55944  |  Created: 2007-01-04  |  Updated: 2013-04-25  |  Article URL http://www.symantec.com/docs/TECH55944
Article Type
Technical Solution


Issue



What happens when closing an Index location and opening another one. (This technical article is for pre Enterprise Vault 9.0 versions. Refer DOC4250 for behavior of Enterprise Vault 10.0 and later versions.)


Solution



When an index location is closed, the index folders in the location continue to be updated.   The new location will be used for the index folders of newly created archives and for rollover indexes.   Closing a location does not cause a rollover.

Example:
There are 200 archives indexing to C:\Indexing and that location is now closed. Those 200 index locations will continue to update from their corresponding archives.  

Once a new index location (D:\Indexing) is created, all newly created archives will create their index folders in that location.    Any rollover indexes is created on this new location as well.

According to the Enterprise Vault Administrators Guide, When closing a location, Indexing service no longer create new indexes there. This does not stop the Indexing service from adding to existing indexes, so the action must be taken before space runs out.

In Figure 1, there is a single index location on the C: drive with seven archive index folders and for this illustration, Folder 1 is the journal archive. Notice that index updates are going to each folder.

Figure 1
 

In Figure 2 a new index location is opened on the D: drive.  This shows what the journal archive would look like once it has rolled over and added two new archives that are created in the new location.

Figure 2
 

The old location will continue to grow as the six indexes there are still active and still receiving updates.  New index folders and rollover index folders will be created and updated in the new location.

Note: Rebuilding an index will NOT force it to be rebuilt in the new index location.  It will rebuild in its original location because the IndexRootPath does not get updated to the new location during a rebuild.

If running out of disk space, perform one of the following options:

Pre-Enterprise Vault 2007                
 
  • Add more space to the existing location.            
  • Move the indexes to a new location with more space.   (See article 273141 in the Related Documents section)
Enterprise Vault 2007 and above
 
  • Add more space to the existing location.
  • Move the indexes to a new location with more space.
  • Move individual indexes to the new location using the Vault Administration Console.

 



Legacy ID



294679


Article URL http://www.symantec.com/docs/TECH55944


Terms of use for this information are found in Legal Notices