Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to Install and Configure Enterprise Vault Discovery Accelerator 10.x

Created: 18 Oct 2012 • Updated: 31 Oct 2012 | 10 comments
Language Translations
AmolB's picture
+4 4 Votes
Login to vote

This article explains how to install and configure Enterprise Vault Discovery Accelerator 10.x.

Pre-Requisites:

OS: Win 2008 R2 or above

Microsoft Visual C++ Redistributable: Microsoft Visual C++ 2008 SP1 (x86) Redistributable

Microsoft .NET Framework: Microsoft .NET Framework 3.5 (SP1 or later)

Internet Information Service: IIS7.5, IIS6 Management Compatibility and IIS Windows Authentication

Enterprise Vault: EV10 API Runtime

Along with the EV installables Symantec also ships CA\DA. Binaries of DA are available at the root of the

installation media.To begin installation of DA browse installation media -> Symantec EV Discovery

Accelerator -> Server -> Language Folder -> double click on the MSI and than follow the wizard.

Below are the screenshots which you will come across, at the end of the wizard server side installation of the

Discovery Accelerator will be over. After installation you need to configure DA by entering EV and SQL info

(Details about the configuration is explained below in the article). A client machine (WinXP or Win7) is required

to install DA client from where DA server can be accessed for Discovery.

Installation wizard will not proceed if there is any error in the below enviornment check. 

Warnings can be addressed after innstallation.

Typical install will select all the common features whereas Custom install gives a choice of features to be installed.

You may select a different installation directory by clicking on the Browse button.

With the check box enabled DA launches administration website to configure DA customer.

You can manually launch the website using http:\\localhost\evbaadmin or

http:\\DA server name or IP address\evbaadmin

Launching evbaadmin site will show below page. After entering SQL server name you need to enter

Database name for Discovery Accelerator. For Data & Log File you need to create a folder on the SQL server

and specify path of that folder on the below page. Without importing License file the configuration page will not

proceed further.

To add a customer you need to right click on the DA server name and than select "New Customer" option.

Customer Type has 2 options "Discovery" which is used for Discovery purpose and the other option

is "Custodian Manager" used to sync with Microsoft Active Directory to fetch and maintain historical

changes made to any custodian (AD user account).

Note: You can configure only 1 Custodian Manager per DA server.

To configure a Customer for Discovery you need to fill in the details mentioned on the below page.

Name of the Customer: XYZ

Directory DNS aliases:  Alias of the EV server.

Virtual Directory: Name of the Virtual directory could be same as name of the customer.

IIS server: Discovery Accelerator server name.

Database name: For better administration I prefer specifying the customer name.

Data and Log File folder: Create a folder on the SQL server and specific the same path (Eg: E:\DA_Logs)

Finally enable Analystic Database location and than click on OK.

Installing DA client on a Win7 machine.

Copy DA Client installables from Symantec EV Discovery Accelerator folder located at the

root of the installation media.Double click on the MSI file to kick off the client installation.

Follow the installation wizard, once done launch DA client from Start -> All Programs 

If you have multiple DA servers than manually enter the DA server name and than the client will

show a list of DA customers hosted by the DA server.

After selecting an Instance (DA customer) you are all set to perform Discovery. Through DA client you

can perform a Search, put a Legal Hold on items, Mark & Tag items, you can also Export items to a PST.

Comments 10 CommentsJump to latest comment

Backup_Exec's picture

HI

Excellend & Good one!

Thanks

Sameer

Don't forget to give a "Thumbs Up" or Mark as "Solution" if someones advice has helped you.

0
Login to vote
Muhammad Ejaz's picture

That's great...............................

0
Login to vote
kmouline's picture

Very Nice Article,

Any body can point on where to find Discovery Accelerator Admin/user guide ?

I also need admin/user guide for EV journaling. 

Thank you,

0
Login to vote
doylc's picture

If you've already got an EV enviornment in place, can you install Discovery Accelerator over the top of an existing installation? What is the storage requirements for Discovery Accelerator, can you get the search and exporting benefits from it straight away or will it have to run an index to take note of the content?

We've got around 2000 vaults with a 400GB index.

0
Login to vote
Kenneth Adams's picture

Hello, doylc;

Yes, you can install Discovery Accelerator on top of an existing EV environment and get immediate bennefits.  The storage requirements are really dependent upon how much space would be needed for exported items, so we can't really give you definitive numbers here.

Searching is run against existing index volumes of your current archives, with any future archives automatically added (this is configurable).  The DA searches actually pass the search criteria to the EV Index Server's index search engine (or engines if you have both 32 and 64 bit indexes).

Exporting is available once you've run and accepted a search, with the items eligible to be exported being those accepted by the search processing.  Exporting can be done to MSG, PST or HTML files for Microsoft Exchange items, or to Lotus Notes formatted NDF files (both individual files or in a Lotus Notes database file) or HTML files.

We recommend installing DA on its own server that is not performing any EV functions to provide for the best performance.  The DA server needs either the Enterprise Vault binaries (exe and dll files) installed by running the EV setup program and not running the configuration wizard, or it needs the EV-API installed.  We in the CA/DA Support Team recommend the full EV binaries as there have been instances where the EV-API installation fails to register all of the dll files needed for proper operation.  Plus, installing the full EV binaries allows for more processes to be traced in a dtrace when troubleshooting may be needed.

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region

+3
Login to vote
doylc's picture

Thanks Ken.

I guess the issue from our point of view is trying to determine what impact this might have on the existing installation and if we'd suffer a disk hit from DA having to reindex.

With the disk space required I was reading the drive with the EV temp folder needs at least 40GB but a recommended 80GB free. We wouldn't be looking at exporting anymore then 10-20GB worth of emails, that would be a worst case scenario.

Our Journal index is only set to brieft at the moment. We intend on setting this to full, but this would require a full rebuild which would take weeks given when we upgraded to EV 10 and upgraded it's index to 64bit it took around 4 weeks to complete. During a rebuild i'm not sure you can search the index, so we can't have it offline for that amount of time whilst we wait for it to complete.

Because we've only got breif on the index, how does the DA search extract the new information, i.e. where it broadens the index classifications.

Sounds like the safest best would be to install it on a seperate server, run a few searches and monitor the disk usage.

0
Login to vote
doylc's picture

I've managed to get it up and running. The main question I have now is given our Journal index is set to brief and not full, does this mean we're missing out on seaching the majority of the custom attributes or other search criteria DA gives you apposed to the advanced search in EV?

0
Login to vote
Kenneth Adams's picture

Greetings, doylc!

Having your journal index at the Brief level only means you can't search for phrases.  Any other indexable and searchable attribute is still available to you.  For example, with Brief level, you can't search for phrases such as "Discovery Accelerator Administrators Guide", but you could search for the individual words.  Having those individual words on their own lines would have your search criteria look something like this:

 Discovery OR Accelerator OR Administrators OR Guide

If you put all of those words on the same line, the logic changes to something like this:

  (Discovery AND Accelerator) OR (Accelerator AND Administrators) OR (Accelerator AND Guide)

Of course, the actual logic depends on the selection of ALL OF or ANY OF for the criteria field, so the above examples may not be what you actually get.  To see what your search criteria really looks like when passed to the search engine, obtain a dtrace of the EVIndexQueryServer process on the EV Indexing Server while starting a DA search.  Look in the dtrace log for some part of your criteria (in the above example, you could look for any of the 4 words).  The line found would contain the logic of the criteria passed.

As for the disk space on the EV Storage Service server and our recommendation for 40 GB minimum of free space on the drive containing the Vault Service Account's TEMP folder, this recommendation is based on the heavy usage of this TEMP folder during normal archiving operations as well as exporting.  This TEMP folder is where EV puts its temporary files while converting new items to HTML or text prior to archiving, and also when converting from our DVS files into MSG files.  You'll get better performance from your system if the VSA TEMP folder is located off of the system drive (i.e., C:\) and off of a drive that hosts a pagefile.sys file.

Finally, EV 10 has the great feature of being able to search indexes while they are being rebuilt.  Based on your system's configuration, you can rebuild any index volume or entire archive's index and still search the 'old' index volumes until such time as the 'new' index is ready and the system switches to the 'new' index volumes.  I recommend you test this in your environment, though.  Create an archve for  test user's mailbox and archive some items into it.  Then run a search against that archive to be sure you can find items.  Once you've confirmed you can find items, rebuild that archive's index while running another search.  You should be able to find the same items in the original index volume while the new index volume is being prepared and populated.

Ken Adams

Backline Support for CA, DA, ACE, UCE, PSTD, ARMS, EVDC
US Support Region

+3
Login to vote