You can use this technote to specify the location:
http://support.veritas.com/docs/319157
Configuring analytics database locations
Details:
Configuring analytics database locations
When you enable a case for analytics, all the items in the case must be fetched from Enterprise Vault into the customer database, and indexed. This requires a large amount of disk space. Discovery Accelerator lets you define locations to host the analytics table file groups and indexes. You can add more locations when you need more disk space.
The Customer page of the Accelerator Manager Web site lists existing analytics database locations, and lets you add more. Next to each location, check marks in the Table File Group and Full Text Indexes columns show whether the location is used for table files, search indexes, or both.
When you plan and configure analytics database locations, consider the following:
*
The volume of data. The collection and indexing of analytics data can generate very large databases and index files. As a rough guide, collecting one million items that are all 20 kilobytes in size can produce a database that is 40 gigabytes or more in size. However, this can vary from one environment to another.
*
Performance. Host each database location on a physically separate disk. If you have more than one analytics database location, Discovery Accelerator uses them in rotation to spread the data and the disk access requirements.
Each Discovery Accelerator case uses only one location for the search index and one location for the database.
The following examples show two valid configurations for analytics database locations.
To add a database location for analytics
1.
Browse to the Accelerator Manager Web site.
2.
Right-click the appropriate customer, and then click Properties.
3.
Under Database Locations For Analytics, click New Location.
4.
Enter the path to the new database location. Note the following:
*
The database locations must reside on the SQL server, and you must use local paths to refer to them. For example, do not use UNC paths to refer to database locations.
*
The Accelerator Manager Web site does not verify that the specified locations exist. You must ensure that the paths are valid.
5.
Check Table File Group, Full Text Indexes, or both.
6.
Click OK next to the new location.
7.
Repeat steps 3 through 6 if you want to add more database locations.