Grab our RSS feeds Follow us on Twitter Join our Facebook Group Connect with us on LinkedIn
myITforum.com, Powered by You.
you are not logged in

Articles

Newslinks

Links

Downloads

Site Services

Community Forums

Discussion Lists

Article Search

Newsletter

Web Blogs

FAQs

Live Support

myITforum TV

Take a Poll

Monthly Drawing

myITforum Network

User Group Directory

Our Partners

About Us

Register

Login

BRONZE PARTNER:

BRONZE PARTNER:



Industry News:




  Home : Articles : Security print | email | | Forums |   print | email | | Blogs |   print | email | | Wiki |   print | email | | FAQs |   print | email | Article Search  
Installing and Configuring Enterprise Vault 6.0 SP3 – Part I


Bookmark and Share

By: Alan Maddison
Posted On: 1/3/2007

Introduction
There are many email archiving solutions available on the market today but the market leader in terms of market and mind share is Symantec’s Enterprise Vault. Originally developed by a team at DEC who subsequently purchased the rights to the software and formed a company called KVS the product has been in existence for about six years. As a mature, enterprise class product the functionality offered by Enterprise Vault (EV) is substantial. However, from an IT administrator’s perspective this level of functionality also brings with it a level of complexity which can be daunting. In this article I will describe the basic installation and initial configuration options that you have with Enterprise Vault. In subsequent articles I will cover more of the configuration options for EV modules including Mailbox archiving, File System Archiving and PST Migration.

Installation Pre-requisites
In general the entire class of archiving products available on the market today rely on a number of different technologies particularly some of the key networking and infrastructure technologies provided by Microsoft. This is particularly true of Enterprise Vault which has an extensive list of pre-requisites. In order to successfully deploy EV it is very important that you take care of these requirements. This process was made much simpler with the introduction, in SP2, of Deployment Scanner and I encourage everyone to use this tool to check that you have met the EV requirements prior to beginning configuration of the product.

EV Server configuration requirements:

    Operating System - Windows Server 2000 SP1
    Windows Server 2003 (R2 is supported but the x64 edition is not)

    IIS - 5.0/6.0
    Requires ASP.net and ASP to be enabled within IIS

    MSMQ - 2.0/3.0
    Needs to be installed without AD integration (Workgroup mode)
    Should be moved from system partition to dedicated volume for maximum performance

    MDAC - 2.6 (Windows Server 2003 ships with v2.8)

    MSXML - 3.0 SP2 (Windows Server 2003 ships with v3.0 SP4)

    .NET Framework - 1.1 (Windows Server 2003 ships with v1.1)
    2.0 (Discovery Accelerator and Compliance Accelerator only)

    Outlook - Outlook 2003 only (as of 6.0 SP1)
    Needs to be installed with Collaboration Data Objects (CDO)
    Outlook profile/MAPI needs to initialized on each EV server, i.e. Outlook should be launched a profile created and a mailbox accessed. Typically using the EV system mailbox is ideal.

    Exchange System Manager - Version should match your Exchange Server environment
    The admin tool for Exchange Server needs to be installed on each EV server to ensure that EV can access all MAPI capabilities. You should also ensure that the EV server is configured to use the correct version of MAPI – if you search for mapisvc.inf you should find at least two versions, copy the larger of the two to the OS system32 folder and then run a utility called fixmapi.exe, also in the system32 folder. You will see no output or dialog boxes from this utility.


A quick review of the requirements above clearly shows that Windows Server 2003 is the preferred operating system for EV 6.0 SP3 as it simplifies the additional installations that need to take place in order to meet some of the requirements.


Hardware requirements:

    CPU - Archiving is CPU intensive and generally CPU bound so a multi-processor or multi-core server is preferred.

    Memory - 4GB is recommended although EV can not use more than 4GB and the /3GB switch should not be configured on the EV server as it can lead to Index corruption. Refer to http://seer.support.veritas.com/docs/280896.htm for more information.

    Storage - EV supports multiple hardware platforms for storage including NTFS partitions, NetApp, EMC Centera.

    Best practices would dictate the following volumes:

    MSMQ – requires fast storage, typically this would be direct attached storage (DAS) or Fibre Channel SAN LUNs. The MSMQ storage location should be moved from the default location on the system drive to a dedicated partition. If you intend to aggressively monitor usage the partition size can be relatively small (1GB) however if you do not intend to monitor usage size accordingly (10GB).

    Indexes - requires fast storage, typically this would be direct attached storage (DAS) or Fibre Channel SAN LUNs. There is a ratio between the size of indexes and data archived. Full indexing will require storage equal to 12% of data archived, e.g. 1TB of archived data = 120GB of indexes.

    Storage (archived data) – does not require fast storage, SATA drives are adequate

    Shopping Service – does not require fast storage, SATA drives are adequate

    Auditing (Optional based on configuring auditing within EV) – does not require fast storage, SATA drives are adequate


Depending upon the size of your environment and usage patterns it may be practical to consolidate the storage, shopping service and auditing partitions onto a single set of spindles. In large environments you should not do this. Typically writing to WORM media such as a Centera will require a staging area for file collection. If you are archiving to a Centera then there will be no need for a storage partition.

Other requirements:

    DNS aliases - You must create a CNAME alias within your DNS zone for each EV site and server that you create. Most installations will have a single site. Typically the site alias will point to the first EV server installed in your environment. Each alias that you create for a server will of course point to the physical server for which it was created.

    Exchange Server - 5.5
    2000
    2003 (6.0 SP1 was the first version to support Exchange SP2)

    Exchange OWA Control files - 6.5.7651.25 or earlier

    SQL Server - SQL Server 2000
    SQL Server 2005 (6.0 SP1 was the first version to support 2005)


EV requires a SQL server. It is not best practice to install SQL on the same box as EV but it is supported. The load placed on a SQL server will vary depending on your EV environment but using an existing SQL server is possible. EV does support SQL Named Instances. A single dedicated SQL server with multiple processors will support multiple EV servers. For example, a four way SQL box (16GB of RAM) will typically support at least 10 EV servers.


User requirements:

A typical EV install requires multiple user accounts depending on the exact EV configuration. By far the most important account is the EV Service Account. This account has extensive rights and access to and use of this account should be closely controlled. Another user account that is required by EV is the EV Anonymous Account which is used to control access from the Exchange mailbox (backend) servers and EV servers. In addition EV requires System Mailboxes for each Exchange Server in your environment. In a single server environment there is no reason why you could not use the Service Account mailbox however in a multi-server environment you must have a separate user account in order to ensure EV scales.

    Service Account - Local administrator on each EV server

    Full Exchange Admin rights – typically at the Exchange Admin group or Organization level

    Local administrator on each SQL server used for EV databases – only required during installation – can be removed after EV is installed and configured as the Service Account will be a DB owner

    SQL System Administratorpermissions for Discovery Accelerator scheduled search functionality – not required otherwise

    Local administrator on each file server for File System Archiving
    Full control on each file share for File System Archiving

    Anonymous Account - No special requirements – a normal user account without a mailbox is adequate

    System Mailboxes - No special requirements – you should create a unique user account and mailbox for every Exchange server in your environment

    Registry Entries - The following registry entries should be applied to your EV servers


After installing the pre-requisites on your Enterprise Vault servers and running Deployment Scanner you are ready to begin installation and configuration. The installation will typically only take a few minutes and is launched by running setup.exe from the install media. The steps required for configuration will take longer.

Configuration
The Configuration Wizard is launched from the Enterprise Vault program group which is created during installation. After starting the Configuration Wizard the first screen we see is shown below. If this is the first EV server in your environment you will select the default option of creating a new Vault Directory.







The next step in the process is to enter the information for the account that we will use as the Vault Service account.







Once we have entered the Vault Service Account information we receive confirmation on the rights that are granted to the account.







The next step requires you to enter the name of the SQL server that you intend to use for your EV deployment. The default location is the local machine so be sure to change this if required. You should enter the fully qualified domain name (FQDN) although this is not a requirement.







The next step requires you to enter the physical path on the SQL server where your EV databases will be located. As you can see from the screenshot EV uses the administrative shares on the SQL server to locate the physical path. This is one of the reasons that the EV install requires local admin rights on the SQL server.







The next step takes us through Site creation. You are required to enter a name and description which you will see in the Vault Administration console and a DNS CNAME (alias) for the site. Typically the CNAME will point to the first EV server in your environment.







The next screen requires you to input the DNS alias for the server itself.







The next screen identifies the EV services that will be installed on the server.







The next screen allows you to modify the properties of the EV services. By selecting the service and clicking on the Properties button you can modify some of the parameters associated with each service.







By selecting the service and clicking on the properties button shown above you can configure the properties of each service. The first service to be configured is the Index service. Remove the default index location and point EV to the index partition as shown below.







The next service to be configured is the Storage service. The number of Restore processes and Restore threads should be modified to 2 and 3 respectively for best results.







As the Task Controller service has no properties to modify the final service to configure is the Shopping service shown below. As discussed earlier it is always best to modify the storage location for this service. The actual performance and storage requirements for this service depend entirely on how your users interact with the EV Web application. Many organizations choose not to educate their users on this functionality relying instead on the Outlook EV client. If this is true in your EV deployment usage will be very light.







After configuring the final service and selecting Next the Configuration wizard will display your configuration choices. The wizard will then start the services. It is important to note that by this point you should have copied the license keys for EV into the installation directory, the default location being c:\program files\enterprise vault. The license file should be named <servername>_keys.txt. Services will fail if you attempt to start them before you have created the license key.


Next Steps
You have now completed the installation and service configuration for Enterprise Vault. The next part of this article will discuss Directory/Site configuration, storage configuration, and policy configuration.

  myITforum.com ©2010 | Legal | Privacy