317266

Symantec Enterprise Vault™

Installing and Configuring

8.0

Symantec Information Foundation™

Symantec Enterprise Vault: Installing and Configuring

Legal NoticeCopyright © 2008 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, VERITAS, and Enterprise Vault are trademarks or registeredtrademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Othernames may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation20330 Stevens Creek Blvd.Cupertino, CA 95014

http://www.symantec.com

Chapter 1 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

When to use this guide .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Introducing this guide .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Getting help .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Accessing the Support Web site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Subscribing to Email Notifications .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Accessing telephone and fax support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Product documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Comment on the documentation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Section 1 Enterprise Vault prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 2 Enterprise Vault hardware prerequisites . . . . . . . . . . . . . . . . . . . . . . . 21

Server hardware requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Enterprise Vault server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SQL Server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Additional processing capacity for initial archiving .... . . . . . . . . . . . . . . . . . . 23

Network requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Storage requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Vault stores ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Enterprise Vault indexes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26SQL databases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Cache .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Shopping baskets ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Local storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 3 Enterprise Vault prerequisite software andsettings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

About the Enterprise Vault prerequisite software and settings ... . . . . . . . . . . 31Enterprise Vault Deployment Scanner ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Basic software requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Operating system components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32SQL server software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Contents

Microsoft Data Access Components (MDAC) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Pre-installation tasks for Enterprise Vault server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Creating the Vault Service account ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Creating a SQL login .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Creating Enterprise Vault DNS aliases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Turning off or reconfiguring Windows Firewall in Windows

Server 2008 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 4 Additional requirements for OperationsManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

About additional requirements for Operations Manager ... . . . . . . . . . . . . . . . . . . . 43Where and when to install Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Additional prerequisite software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Additional preinstallation tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 5 Requirements for Enterprise Vault Reporting . . . . . . . . . . . . . . . 47

About requirements for Enterprise Vault Reporting .... . . . . . . . . . . . . . . . . . . . . . . . 47Where and when to install Enterprise Vault Reporting .... . . . . . . . . . . . . . . . . . . . . 47Prerequisites for Enterprise Vault Reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Using Reporting on a 64-bit machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Preinstallation tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 6 Additional requirements for Exchange Serverarchiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

About the requirements for Exchange Server archiving .... . . . . . . . . . . . . . . . . . . . 51Required software on Enterprise Vault server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Pre-installation tasks for Exchange Server archiving .... . . . . . . . . . . . . . . . . . . . . . . 52

The Enterprise Vault system mailbox .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Additional Vault Service account permissions .... . . . . . . . . . . . . . . . . . . . . . . . . . 53Assigning permissions on Microsoft Exchange Server ... . . . . . . . . . . . . . . . . 53Create an Outlook profile on the Enterprise Vault server

computer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Configure Internet Explorer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Enterprise Vault client access with Exchange Server archiving .... . . . . . . . . . 58Prerequisites for Outlook Add-Ins ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58OWA clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Customized shortcuts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Archive search and Archive Explorer in standalone browser ... . . . . . . . 60

Contents4

Prerequisites for OWA ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Prerequisites for RPC over HTTP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

RPC over HTTP with Exchange Server 2003 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62RPC over HTTP with Exchange Server 2007 (Outlook

Anywhere) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 7 Additional prerequisites for Domino Serverarchiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Prerequisites for Domino Server mailbox archiving .... . . . . . . . . . . . . . . . . . . . . . . . . 65Prerequisite software for Enterprise Vault Domino Gateway .... . . . . . 66Prerequisite software for target Domino mail servers ... . . . . . . . . . . . . . . . . 66Prerequisites for Enterprise Vault extensions for Lotus Notes

clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Pre-installation tasks for Domino mailbox archiving .... . . . . . . . . . . . . . . . . 67Register the Enterprise Vault Domino Gateway .... . . . . . . . . . . . . . . . . . . . . . . . 68User ID for Domino mailbox archiving .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Configure the server document for each target Domino mail

server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Install and configure Enterprise Vault Domino Gateway .... . . . . . . . . . . . . 73Install and configure Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Prerequisites for all Enterprise Vault servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Prerequisites for Domino journal archiving .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Conflict with Microsoft Office 2003 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Domino Journaling databases ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Access for Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Domino Mailing List Groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Client access for Domino journal archiving .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Chapter 8 Additional prerequisites for File System Archiving(FSA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

About the prerequisites for FSA .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Enterprise Vault server requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79About FSA shortcuts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Placeholder shortcut requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80The FSA Agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Preparing file servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Setting the permissions on a NetApp Filer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Client requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

5Contents

Chapter 9 Additional prerequisites for SharePoint Serverarchiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Enterprise Vault server requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85SharePoint Server requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

SharePoint security certificates ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Support for SharePoint 2003 to 2007 gradual migration .... . . . . . . . . . . . . 86

Installing Enterprise Vault SharePoint components ... . . . . . . . . . . . . . . . . . . . . . . . . 88Running the configuration wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Chapter 10 Additional prerequisites for SMTP archiving . . . . . . . . . . . . . . . . 91

About the prerequisites for SMTP archiving .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Microsoft SMTP Server requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Enterprise Vault server and holding area requirements ... . . . . . . . . . . . . . . . . . . . . 92Client access for SMTP archiving .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Chapter 11 Prerequisites for a standalone Enterprise VaultAdministration Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

About the prerequisites for a standalone Enterprise VaultAdministration Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Additional requirements for Exchange Server archiving .... . . . . . . . . . . . . . . . . . . 96What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Section 2 Installing Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Chapter 12 Licenses and license keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Overview of licensing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Obtaining license keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Installing Enterprise Vault license key files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Replacing licenses and installing additional licenses ... . . . . . . . . . . . . . . . . . . . . . 101What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 13 Installing Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Upgrading an existing installation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Before you install Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Installing Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Contents6

Chapter 14 Postinstallation tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Default security for the Web Access application .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Setting up the default authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Customizing security for the Web Access application .... . . . . . . . . . . . . . . . . . . . . 109Customizing the port or protocol for the Web Access

application .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Customizing authentication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Customizing security on the client computers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Using the proxy bypass list ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Explicitly naming the Web Access application computer ... . . . . . . . . . . . 114Enabling remote access to the Web Access application

computer ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Chapter 15 Uninstalling Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Uninstalling Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Reinstalling Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Section 3 Configuring Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Chapter 16 About configuring Enterprise Vault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

About configuring Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Chapter 17 Running the Enterprise Vault configurationwizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

When to run the configuration wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123What the configuration wizard does ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Running the configuration wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Troubleshooting configuration of the Monitoring database ... . . . . . . . . . . . . . 128

Chapter 18 Running the Getting Started wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

When to run the Getting Started wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129What the Getting Started wizard does ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Preparing to run the Getting Started wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Express mode or Custom mode? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Storage configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Policy definition .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Exchange target configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Domino target configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

7Contents

File target configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Chapter 19 Configuring Enterprise Vault OperationsManager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

When to run the Operations Manager Configuration utility ... . . . . . . . . . . . . . 139Running the Operations Manager Configuration utility ... . . . . . . . . . . . . . . . . . . 139Accessing Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Troubleshooting Operations Manager ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 20 Configuring Enterprise Vault Reporting . . . . . . . . . . . . . . . . . . . . . . . 143

When to run the Reporting Configuration utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Running the Reporting Configuration utility ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Postconfiguration steps for Enterprise Vault Reporting .... . . . . . . . . . . . . . . . . . 145Accessing the reports ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Troubleshooting Enterprise Vault Reporting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Section 4 Initial Enterprise Vault setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Chapter 21 Initial Enterprise Vault setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

License keys ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Using the Administration Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Using the Administration Console without an Internetconnection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Setting up the Administration Console to display Japanesecharacters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Starting the Administration Console ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153About administration roles ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Adding services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Creating retention categories ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

Retention category properties ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Chapter 22 Setting up storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

About setting up storage for archives ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159About single instance storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

About sharing levels and sharing boundaries ... . . . . . . . . . . . . . . . . . . . . . . . . . . 162How Enterprise Vault single instance storage works .... . . . . . . . . . . . . . . . 164The fingerprint database ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Requirements for single instance storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Contents8

EMC Centera device-level sharing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Developing a suitable sharing regime .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167About vault stores on upgrade to Enterprise Vault 8.0 ... . . . . . . . . . . . . . . . . . . . . 168Creating vault store groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Creating vault stores ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

About safety copies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Creating a vault store ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Creating partitions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172About partition states ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172About collections and migration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Creating a partition .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Configuring sharing for a vault store group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

Chapter 23 Reviewing the default settings for the site . . . . . . . . . . . . . . . . . . 179

Reviewing the default settings for the site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Setting the Site archiving schedule ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Web Access application settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

What next? ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Section 5 Clustering Enterprise Vault with VERITASCluster Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Chapter 24 Introducing clustering with VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Supported VCS configurations and software .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185About the VCS GenericService agent ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Typical Enterprise Vault configuration in a VCS cluster ... . . . . . . . . . . . . . . . . . . 186Installation order ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Chapter 25 Installing and configuring VERITAS StorageFoundation HA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

About this chapter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Installing and configuring SFW HA ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Managing disk groups and volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

Chapter 26 Configuring the service group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

About configuring the service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Before you begin .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Creating a service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

9Contents

Modifying an existing service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Deleting a service group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Chapter 27 Running the Enterprise Vault Configurationwizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

About the Enterprise Vault Configuration wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . 199Before you begin .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Setting up an active/passive configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Adding cluster support in a first-time Enterprise Vaultinstallation .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Upgrading an existing Enterprise Vault installation to acluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Setting up an N+1 configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206N+1 configuration option 1 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206N+1 configuration option 2 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Disallowing two Enterprise Vault servers on the same node .... . . . . . 210

Chapter 28 Implementing an SFW HA-VVR disaster recoverysolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

About this chapter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213About the SFW HA-VVR disaster recovery solution .... . . . . . . . . . . . . . . . . . . . . . . . 213

Installing and configuring SFW HA-VVR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Setting up the cluster on the primary site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Setting up the cluster on the secondary site ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Adding the VVR components for replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . 216Adding the GCO components for wide-area recovery .... . . . . . . . . . . . . . . . 217

Chapter 29 Troubleshooting clustering with VCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

VCS logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Enterprise Vault Cluster Setup wizard error messages ... . . . . . . . . . . . . . . . . . . . . 220Viewing the clustered message queues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Section 6 Clustering Enterprise Vault withMicrosoftserver clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Chapter 30 Introducing clustering with Microsoft serverclusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

About clustering with Microsoft server clusters ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Note on clustering terminology for Windows 2008 users ... . . . . . . . . . . . . . . . . 226

Contents10

Supported cluster configurations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Required software and restrictions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Clustering existing Enterprise Vault installations .... . . . . . . . . . . . . . . . . . . . 227Typical Enterprise Vault configuration in a Microsoft server

cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Control of services in a clustered environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Enterprise Vault services in a clustered environment .... . . . . . . . . . . . . . . 229Resource groups and resources ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229What happens at failover ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230

Chapter 31 Preparing to cluster with Microsoft serverclusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Preparing to cluster Enterprise Vault ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Setting up the shared disks and volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Setting up the resource groups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Chapter 32 Configuring Enterprise Vault in a Microsoft servercluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

About configuring Enterprise Vault in a Microsoft server cluster ... . . . . . 235Setting up a new Enterprise Vault installation with cluster

support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Configuring a new Enterprise Vault server with cluster

support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Configuring a failover node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Troubleshooting configuration of the Monitoring database ... . . . . . . . 241Configuration examples ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

Converting an existing Enterprise Vault installation to a cluster ... . . . . . . 246Converting an existing Enterprise Vault server to a server with

cluster support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Modifying an existing Enterprise Vault cluster ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Adding a node .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Adding shared storage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

Chapter 33 Troubleshooting clustering with Microsoft serverclusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

About this chapter ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Event logs and the server cluster log .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Resource ownership and dependencies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Registry replication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Viewing the clustered message queues ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Starting and stopping services ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

11Contents

Appendix A Planning for the Getting Started Wizard . . . . . . . . . . . . . . . . . . . . . . 257

Planning for the Getting Started Wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Contents12

About this guide

This chapter includes the following topics:

■ When to use this guide

■ Introducing this guide

■ Getting help

■ Product documentation

■ Comment on the documentation

When to use this guideWork through this guide if you want to perform a new installation of EnterpriseVault.

To upgrade an existing installation of Enterprise Vault, see theUpgradeInstructions file.

Introducing this guideThis manual provides detailed information on installing and configuring EnterpriseVault. Before you install Enterprise Vault, read the Introduction and Planningmanual so that you have an understanding of the various components.

To install and configure Enterprise Vault, you need to know how to administerthe following products:

■ Microsoft Windows Server 2003 or Windows Server 2008

■ Microsoft SQL Server

■ Microsoft Message Queue Server

1Chapter

■ Microsoft Internet Information Services (IIS)

■ Your archive storage hardware and software

If you are going to be using Enterprise Vault with IBM Domino Server, you alsoneed administrative knowledge of IBM Domino Server and the IBM Lotus Notesclient.

If you going to be using Enterprise Vault with Microsoft Exchange Server, youalso need administrative knowledge of Exchange Server and Outlook.

If you going to be using Enterprise Vault with Microsoft Windows SharePointServices and Microsoft SharePoint Portal Server, you need administrativeknowledge of these products.

To use the reporting feature of Enterprise Vault Operations Manager, you needadministrative knowledge of Microsoft SQL Server Reporting Services.

Getting helpSymantec offers a variety of support options:

■ Accessing the Support Web site

■ Subscribing to Email Notifications

■ Accessing telephone and fax support

Accessing the Support Web siteThe Symantec Enterprise Support site(http://www.symantec.com/business/support) lets you do the following:

■ Contact the Support staff and post questions to them.

■ Download the latest patches, upgrades, and utilities.

■ Search the Knowledge Base for answers to technical support questions.

■ Subscribe to automatic email notification of product updates.

■ Find out about training courses.

■ Read current white papers, technical notes, and selected documentation.

Subscribing to Email NotificationsSubscribe to Email Notifications to be informed of software alerts, newly publisheddocumentation, Beta programs, and other services.

About this guideGetting help

14

http://www.symantec.com/business/support

To subscribe to Email Notifications

1 Browse to the Symantec Enterprise Support site(http://www.symantec.com/business/support).

2 Click Sign up forNewsBulletins.

3 On the Email Bulletin Service page, under Sign up for the Email BulletinServicebyselectingyourproductgroupbelow, clickAvailabilityProducts.

Accessing telephone and fax supportTelephone support for Enterprise Vault is available with a valid support contractonly.

To contact us for technical support, dial the appropriate telephone number shownat the Symantec Enterprise Support site. Have your product license informationready for quick navigation to the appropriate support group.

Product documentationTable 1-1 lists the documentation that is available in the Documentation folderof the Enterprise Vault media.

Table 1-1 Enterprise Vault documentation set

CommentsDocument

Provides an overview of Enterprise Vaultfunctionality.

Introduction and Planning

Before you install or upgrade Enterprise Vault,we strongly recommend that you run theDeployment Scanner to check prerequisitesoftware and settings.

Deployment Scanner

Provides detailed information on setting upEnterprise Vault.

Installing and Configuring

Describes how to archive items from MicrosoftExchange user mailboxes, journal mailboxes, andpublic folders.

Setting up Exchange Server Archiving

Describes how to archive items from Domino mailfiles and journal databases.

Setting up Domino Server Archiving

Describes how to archive files that are held onnetwork file servers.

Setting up File System Archiving

15About this guideProduct documentation


Table 1-1 Enterprise Vault documentation set (continued)

CommentsDocument

Describes how to archive documents that are heldon Microsoft SharePoint servers.

Setting up SharePoint Server Archiving

Describes how to archive SMTP messages fromother messaging servers.

Setting up SMTP Archiving

Includes backup and recovery procedures.Administrator’s Guide

A reference document listing registry values withwhich you can modify many aspects of EnterpriseVault behavior.

Registry Values

Describes Enterprise Vault tools and utilities.Utilities

The online help file for the Enterprise VaultAdministration Console.

Administration Console Help

The online help file for the Enterprise VaultOperations Manager.

Operations Manager Help

Includes all the above documentation so that youcan search across all files. To access this file fromwithin the Administration Console, click Help >Help on Enterprise Vault.

Enterprise Vault Help

For the latest information on supported devices and versions of software, see theEnterprise Vault Compatibility Charts book, which is available from this address:

http://entsupport.symantec.com/docs/276547

Comment on the documentationLet us know what you like and dislike about the documentation. Were you able tofind the information you needed quickly? Was the information clearly presented?Report errors and omissions, or tell us what you would find useful in futureversions of our guides and online help.

Please include the following information with your comment:

■ The title and product version of the guide on which you want to comment.

■ The topic (if relevant) on which you want to comment.

■ Your name.

About this guideComment on the documentation

16


Email your comment to [email protected]. Please only use this address tocomment on product documentation.

We appreciate your feedback.

17About this guideComment on the documentation

mailto:[email protected]

About this guideComment on the documentation

18

Enterprise Vaultprerequisites

■ Enterprise Vault hardware prerequisites

■ Enterprise Vault prerequisite software and settings

■ Additional requirements for Operations Manager

■ Requirements for Enterprise Vault Reporting

■ Additional requirements for Exchange Server archiving

■ Additional prerequisites for Domino Server archiving

■ Additional prerequisites for File System Archiving (FSA)

■ Additional prerequisites for SharePoint Server archiving

■ Additional prerequisites for SMTP archiving

■ Prerequisites for a standalone Enterprise Vault Administration Console

1Section

Enterprise Vault hardwareprerequisites


■ Server hardware requirements

■ Network requirements

■ Storage requirements

■ What next?

Server hardware requirementsIn a production Enterprise Vault environment, the following servers are normallyinstalled on separate computers:

■ The Enterprise Vault server

■ The SQL Server

■ The target system that is being archived, for example, Exchange Server

For pilot or demonstration configurations only, some or all of these can be installedon the same computer.

This section describes the minimum hardware requirements for these servers.

Enterprise Vault serverAny computer on which you plan to install Enterprise Vault must be a memberof a domain.

2Chapter

Table 2-1 shows the recommended minimum specifications for a productionEnterprise Vault system.

Table 2-1 Minimum specification for an Enterprise Vault server

Recommended minimumItem

2Number of CPUs

2.8 GHzPower of CPUs

4 GBMemory

It is possible to run Enterprise Vault on a computer with less memory, but this isnot recommended for a production system, as it does not allow for any growth inarchiving requirements. The extra memory is particularly important if users willbe performing large, simultaneous archive searches.

If you are just installing a demonstration Enterprise Vault system, and performanceis not an issue, it is possible to run Enterprise Vault on less than 1 GB, but thecomputer must be configured to have at least 1 GB of page file space.

Enterprise Vault can be run on a multi-processor system with four or eight CPUs,but in order to take advantage of the extra CPU power, the disk system used mustbe able to cope with the increased throughput.

In a small to medium Enterprise Vault environment, the core Enterprise Vaultservices will typically all be installed on the same computer. In larger installations,services such as the Storage and Indexing services can be installed on a separatecomputer.

For information on distributing Enterprise Vault services, see the Introductionand Planning manual.

SQL ServerEnterprise Vault requires a number of SQL databases:

■ The Enterprise Vault Directory database holds the configuration informationfor an Enterprise Vault site

■ Each vault store has a vault store database, which holds configurationinformation for the vault store and details of the items stored in its archives

■ Each vault store group has a fingerprint database, which holds the fingerprintsand other information related to the single instance storage parts that arecreated for Enterprise Vault single instance storage.

Enterprise Vault hardware prerequisitesServer hardware requirements

22

■ The Monitoring database holds monitoring information for the EnterpriseVault site.

■ If you configure FSA Reporting, Enterprise Vault creates an FSA Reportingdatabase to hold the FSA Reporting data.

The SQL Server that manages these databases will typically reside on a differentcomputer from the Enterprise Vault server.

In general, the specification of the SQL Server computer should match that of theEnterprise Vault server. The performance of the SQL Server will also benefit fromextra memory; a minimum of 4 GB is recommended. The amount of memory thatthe SQL Server can use depends on the Windows and SQL Server versions.

Table 2-2 shows the recommended minimum specifications for a production SQLServer.

Table 2-2 Minimum specification for SQL Server

Recommended minimumItem

2Number of CPUs

2.8 GHzPower of CPUs

4 GBMemory

You do not need a separate SQL Server for every Enterprise Vault server. As ageneral rule, one SQL Server can manage up to eight Enterprise Vault servers.

Additional processing capacity for initial archivingIf you have a large backlog of data that you want to archive quickly, when youfirst install Enterprise Vault, you may want to configure additional EnterpriseVault servers for the initial archiving run. When archiving reaches a steady state,the additional Enterprise Vault servers can be redeployed for other purposes.

Network requirementsEnterprise Vault can generate a considerable volume of network traffic. As aminimum we recommend an environment in which the connections support theexpected response time of a 100 Mbps switched Ethernet LAN.

For guidelines on the network traffic you might expect between the variouscomponents under different conditions, contact your Symantec supplier.

23Enterprise Vault hardware prerequisitesNetwork requirements

When you configure sharing with Enterprise Vault single instance storage,Enterprise Vault provides a connectivity test to help you determine whether thenetwork latency is acceptable across the relevant connections.

See “About single instance storage” on page 160.

Storage requirementsStorage is required for the following components of Enterprise Vault:

■ Vault stores, where the archived items are held.

■ Indexes.

■ SQL Server databases:

■ Enterprise Vault Directory database

■ Vault store databases

■ Vault store group fingerprint databases

■ Monitoring database

■ FSA Reporting database, if FSA Reporting is configured

■ Cache for temporary files used by Enterprise Vault.

■ Shopping baskets, which are used by Enterprise Vault for details of items thatare to be restored.

In addition a small amount of local storage is needed on the Enterprise Vaultserver.

This section gives a basic guide to the Enterprise Vault storage requirements.

For full details of all the supported storage devices and software, see the EnterpriseVault Compatibility Charts.

Vault storesThe Enterprise Vault Storage service computer needs access to storage for thevault stores.

Enterprise Vault is very versatile in its use of storage for the vault stores, and isdesigned to operate with various types of storage solution provided by third partysoftware and hardware products. Many storage solutions provide high performancearchiving and retrieval.

The types may be categorized as follows:

■ Local storage

Enterprise Vault hardware prerequisitesStorage requirements

24

■ NTFS (An NTFS volume or a network share that appears on the network as anNTFS volume)

■ SAN

■ NAS

■ CAF (Centera)

The Write Once Read Many (WORM) feature is supported on several devices.

One of the most important factors that will determine the performance ofEnterprise Vault is the speed of the storage device.

Required amount of storage for vault storesWhen an item is archived, it is first compressed and then metadata is added to it.As a general rule, the item is compressed to half its original size and the metadatacomprises approximately 5 KB. When an item is shared, only the metadata isadded.

The following general rules can be used for estimating the amount of storageneeded:

■ Take the total size of items to be archived and halve it.

■ For email items, divide by the average number of recipients.

■ Add 5 KB multiplied by the total number of items

The compression ratio may vary considerably. Office documents tend to compresswell. Other document types, such as ZIP files or JPG files, are already compressedand cannot be compressed further. For this reason, you should always overestimatethe amount of storage needed.

The above general rule applies to most types of archiving, but care needs to betaken with File System Archiving (FSA). For example, if compressed image or mapfiles are archived, then there is no space saving.

For email archiving, growth in the number of mailboxes and the number and sizeof messages must also be taken into consideration. Because of these extra factors,a more conservative method of estimating storage is to assume that space usedby archiving will equal the space used by Exchange Server or Domino Server instoring items.

Migration of archived dataArchived data may in turn be migrated to secondary and tertiary storage systemsthat are managed by hierarchical storage management (HSM) software, such as

25Enterprise Vault hardware prerequisitesStorage requirements

VERITAS NetBackup. Several storage solutions interoperate with Enterprise Vaultto provide integrated data migration.

See the Enterprise Vault Compatibility Charts.

If you plan to migrate archived data, you need additional storage for the migrateddata.

Enterprise Vault indexesThe computer hosting the Enterprise Vault Indexing service requires access toadequate storage for the indexes.

Indexes may be placed on local storage, SAN or NAS. If fast indexing is requiredor searches across a large number of archives, NAS devices may not be suitable.

File systems that use slow storage media as part of their solution, such as opticaldisk, are unsuitable for indexes.

If indexes are stored on NetApp devices, and possibly other NAS systems,opportunistic locking must be turned off for volumes that contain indexes.

As anti-virus software can potentially change data, it is important to exclude theindex locations in your virus checking application.

Required amount of storage for indexesTable 2-3 shows how to calculate the expected sizes of indexes.

Table 2-3 Index size compared to size of original data

Index size as a proportion of original data sizeIndexing type

3%Brief

8%Medium

12%Full

The type of data being archived will also affect the size of indexes. Archiving alarge number of text or HTML files will produce larger indexes. Archiving a largenumber of binary files, such as image files, will produce smaller indexes, as thecontent is not indexed.

There is no sharing of index files.

SQL databasesStorage space is required for the following SQL databases:


26

■ Enterprise Vault Directory database

■ Vault store databases

■ Vault store group fingerprint databases

■ Monitoring database

■ FSA Reporting database, if FSA Reporting is configured

■ Audit database

Storage required for the Directory databaseThe directory database has an initial storage requirement of 10 MB for the datadevice and 25 MB for the transaction log device, making a total initial disk spacerequirement of 35 MB.

To allow for temporary growth and the transaction logs, it is suggested that youmake 5 GB available for the directory database.

Storage required for the vault store databasesEach vault store database has an initial storage requirement of 100 MB for thedata device and 80 MB for the transaction log device, making a total initial diskspace requirement of 180 MB for each vault store database.

Ensure that there is adequate space for database devices to grow as data is added.Transaction logs should be limited to an appropriate size for your back-up andmaintenance plan.

A basic sizing guide for each vault store database is 250 bytes for each itemarchived plus 5 GB for static data, transaction logs and temporary datafluctuations.

Storage required for the fingerprint databasesA vault store group's fingerprint database holds the fingerprint, the storagelocation, and sharing boundary information for each SIS part that is stored in thegroup's vault stores.

The fingerprint database has an initial storage requirement of 244 MB, made upas follows:

■ 132 MB for the primary filegroup

■ 1 MB for each of the 32 non-primary filegroups

■ 80 MB for the transaction log device


The non-primary filegroups hold the SIS part fingerprints and other informationabout the SIS parts. If you share items using Enterprise Vault single instancestorage, the non-primary filegroups may grow very rapidly in size. Ensure thatthere is adequate space for the non-primary filegroups to grow as data is added.

The New Vault Store Group wizard provides the following options for the initialconfiguration of the fingerprint database:

■ A default basic configuration, where Enterprise Vault locates the primaryfilegroup and all the non-primary filegroups on one device.

■ An advanced configuration option, where you can specify separate locationsfor the 32 non-primary SQL filegroups.

To ensure acceptable archiving and retrieval performance, it is important toconfigure the fingerprint database appropriately for the amount of sharing in thevault store group.

For optimal performance, do as follows:

■ Use the advanced configuration option to specify as many locations as possibleon the SQL Server, up to the maximum of 32.

■ Use a separate device for each location. If you specify more than one locationon the same device there is no performance benefit.

Note: To add or change locations after the fingerprint database is configured is aSQL Server administration task.

Limit transaction logs to an appropriate size for your back-up and maintenanceplan.

Storage required for the Monitoring databaseThe Monitoring database has an initial storage requirement of 100 MB for thedata device and 80MB for the transaction log device, making a total initial diskspace requirement of 180 MB.

Ensure that there is adequate space for the database to grow as monitoring datais added.

Storage required for the FSA Reporting databaseIf you configure FSA Reporting, Enterprise Vault creates the FSA Reportingdatabase. This database contains the data that the Enterprise Vault File Collectorservice gathers. This data is used in FSA Reporting’s data analysis reports. TheFSA Reporting database has an initial storage requirement of 100 MB for the data


28

device and 80 MB for the transaction log device. The total initial disk spacerequirement is180 MB.

Ensure that there is adequate space for the database to grow as monitoring datais added.

A batch file is provided to trim the database. The batch file retains recent andtrend-related information.

See "Maintaining the FSA Reporting Database" in the Administrator's Guide.

Storage required for the audit databaseThe audit database is not created until you enable auditing. By default, auditingis disabled.

The initial storage requirement for the audit database is 100 MB for the database,and 80 MB for the transaction log.

You can enable auditing for individual Enterprise Vault servers. The auditingevents for several Enterprise Vault servers in a site can be written to a singleauditing database.

The amount of space required will depend on the number and type of events loggedand the level of detail required.

The Utilities manual describes how to set up auditing.

Limit transaction logs to an appropriate size for your back-up and maintenanceplan. For instructions on how to roll over the audit database, see the SymantecSupport document:

http://seer.entsupport.symantec.com/docs/273274.htm

CacheThe Enterprise Vault Cache is a folder on the Enterprise Vault server thatEnterprise Vault uses to store temporary files. The cache is currently used by PSTMigration, FSA when the target file server is a Celerra file server, and vault cache.

The major use for the cache is to provide temporary storage for vault cache clients.If only a few Enterprise Vault clients use vault cache a location with a minimumof 20GB of free space is probably sufficient. If many clients use vault cache, specifya location with far more free space.

As anti-virus software can potentially change data in the cache, it is importantto exclude the cache location in your virus checking application.


http://seer.entsupport.symantec.com/docs/273274.htm

Shopping basketsSpace is required on the Shopping service computer for shopping baskets. Theseare used by Enterprise Vault for keeping details of items that users requestEnterprise Vault to restore.

The amount of space required depends on the extent to which users restore itemsusing the browser search shopping baskets. As a guide, for each shopping basketallow 4 KB for static data plus 1 KB for each item in a basket.

Local storageA small amount of local storage is needed for temporary files. For example, thelocal temporary area may be used by the Storage service when processing largefiles. Local storage is also required for MSMQ files and for Windows system files.

We recommend that you reassign the TEMP system variable to a drive other thanthe C: drive.

Slow local disks can seriously impact the performance of Enterprise Vault. Youare recommended to allocate separate disks for MSMQ files. The disks need to beset up for maximum speed; for example using RAID 1+0 rather than RAID 5.

During installation Enterprise Vault requires 70 MB of disk space to install all theEnterprise Vault components.

What next?Now check the prerequisite software and settings for core Enterprise Vaultservices.

See the next chapter for details.

Enterprise Vault hardware prerequisitesWhat next?

30

Enterprise Vaultprerequisite software andsettings


■ About the Enterprise Vault prerequisite software and settings

■ Enterprise Vault Deployment Scanner

■ Basic software requirements

■ Pre-installation tasks for Enterprise Vault server

■ What next?

About the Enterprise Vault prerequisite software andsettings

Read this chapter to find out the following:

■ Software prerequisites for core Enterprise Vault components.

■ Tasks that you need to perform before installing Enterprise Vault.

The Enterprise VaultCompatibilityCharts contain details of the supported versionsof prerequisite software.

There are additional prerequisites for other optional Enterprise Vault componentsand the different types of archiving. Ensure that you also review the additionalprerequisite information for your planned installation, as outlined in laterchapters.

3Chapter

There are also prerequisites if you are installing Enterprise Vault in a clusteredenvironment.

Enterprise Vault Deployment ScannerBefore installing Enterprise Vault, you can use Enterprise Vault DeploymentScanner to find out which prerequisites are missing. When you have finishedpreparing your servers for installation, it is advisable to run Deployment Scannerto check that all the prerequisites have been correctly installed.

Enterprise Vault Deployment Scanner is a separate wizard that is supplied on theEnterprise Vault media. When the tool runs, it creates a Reports folder in thefolder in which it is run, and places a report file in the Reports folder.

You can find Deployment Scanner and accompanying documentation in theEnterprise Vault 8.0\Deployment Scanner folder on the Enterprise Vaultmedia.

Windows Installer 3.1 must be installed on your Enterprise Vault servers in orderto install Enterprise Vault Deployment Scanner and the Enterprise Vault servercomponents.

Basic software requirementsThis section describes the operating system and software requirements for thecore Enterprise Vault services.

There may be additional requirements for the different types of archiving.

If required, the Enterprise Vault Administration Console can be installed on aseparate computer.

See “About the prerequisites for a standalone Enterprise Vault AdministrationConsole” on page 95.

As a general rule, it is best to install products in the order in which they werereleased.

Operating system componentsEnterprise Vault server components can be installed on the following operatingsystems:

■ Windows Server 2003 with Service Pack 2 or later.


Enterprise Vault prerequisite software and settingsEnterprise Vault Deployment Scanner

32

If Windows Server 2008 with Service Pack 1 is installed, you must also installthe following mandatory hotfix for IIS:http://support.microsoft.com/kb/949516

For details of supported versions, see the Enterprise Vault Compatibility Charts.

Install Windows with the following options and components:

■ NTFS file system.

■ Microsoft Message Queuing (MSMQ) services.See “Installing MSMQ” on page 33.

■ .NET Framework 2.0.See “Microsoft .NET Framework” on page 34.

■ Internet Information Services (IIS) 6.0 or later.See “Internet Information Services (IIS)” on page 35.

■ Internet Explorer 6.0 or later.

■ MSXML.See “MSXML” on page 37.

Roles-based administrationRoles-based administration uses Microsoft Windows Authorization Manager.Creating and managing roles using the Administration Console requires theAuthorization Manager MMC snapin, which is only available on the following:

■ Windows Server 2003


■ Windows XP Professional, or Windows Vista with the Administration ToolsPack for Windows Server 2003 and Windows Server 2008

You can download the Administration Tools Pack from the following location:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c16ae515-c8f4-47ef-a1e4-a8dcbacff8e3&DisplayLang=en

Installing MSMQEnterprise Vault tasks use MSMQ to communicate with the Storage service. Ifyou want to install Enterprise Vault services on more than one computer in thenetwork, you must configure MSMQ on each computer.

The steps for installing MSMQ on Windows 2003 and 2008 are different. Followthe instructions below for your operating system.

33Enterprise Vault prerequisite software and settingsBasic software requirements

http://support.microsoft.com/kb/949516



Note that Active Directory Integration should not be enabled when installingMSMQ.

To install MSMQ on Windows Server 2003

1 In the Windows Control Panel, double-click Add/Remove Programs.

2 ClickAdd/RemoveWindowsComponents. The Windows Components wizardstarts.

3 Select Application Server and then click Details to open the ApplicationServer window.

4 Check MessageQueuing, and then click Details to display the MessageQueuing dialog box.

5 As installing MSMQ with Active Directory Integration affects the performanceof Enterprise Vault, you are strongly recommended to uncheck ActiveDirectory Integration in the Message Queuing dialog box.

6 Click OK twice to return to the Windows Components wizard.

7 Follow the remaining instructions in the wizard.

To install MSMQ on Windows Server 2008

1 Start Server Manager.

2 Click Features in the left pane.

3 Click AddFeatures in the right pane.

4 When the Add Features wizard starts, clickMessageQueuing, and then clickNext.

Note: The only MSMQ feature that Enterprise Vault requires is MessageQueuing Server.

5 Click Install.

6 Follow the remaining instructions in the wizard.

Microsoft .NET FrameworkYou need to install Microsoft .NET Framework v 2.0 on Enterprise Vault servers.

If necessary, you can download .NET Framework using the link in the Links to

related software folder on the Enterprise Vault media.

Enterprise Vault prerequisite software and settingsBasic software requirements

34

Internet Information Services (IIS)You need to install IIS 6.0 or later on each Enterprise Vault server.

In IIS, you can configure the level of isolation for particular Web applications.For shopping baskets in the Enterprise Vault Web access application to be createdcorrectly, the application needs to run under the predefined Local System account.

The configuration wizard will automatically set the correct isolation and accountsettings. You do not need to configure this.

If you have IIS 6.0 or later installed, the configuration wizard will create a newApplication Pool, EnterpriseVaultAppPool, for the Web access application andassign the Local System account to that pool.

Enabling Active Server Pages and ASP.NET on Windows Server 2003

On Windows Server 2003, you need to enable Active Server Pages and ASP.NETmanually.

To enable Active Server Pages and ASP.NET on Windows Server 2003

1 OpenAdd/RemoveProgramsand selectAdd/RemoveWindowsComponents.

2 Ensure MessageQueuing Services and ASP.NET are selected.

3 To install required components and enable Active Server Pages, selectApplication Server and click Details.

4 Select Internet Information Services (IIS) and click Details.

5 Scroll down to WorldWideWeb Service. Click this and then Details.

6 Select Active Server Pages and click OK.

7 Click OK to close the dialog boxes until you get back to the Windowscomponent list.

8 Click Next to install the additional components.

9 Click Finish.

10 To check that Active Server Page scripts can run, start the IIS Manager byclicking Start, Programs, Administrative Tools, IISManager.

11 Click WebService Extensions.

12 Check that Active Server Pages are Allowed.

Configuring ASP.NET on 64-bit versions of Windows Server 2003

If you are installing Enterprise Vault on a 64-bit version of Windows Server 2003,you need to switch to the 32-bit version of ASP.NET 2.0.

To do this, see the following article in the Microsoft Knowledge Base:

35Enterprise Vault prerequisite software and settingsBasic software requirements

http://support.microsoft.com/?kbid=894435

Enterprise Vault prerequisites for IIS on Windows Server 2008

In Windows Server 2008, if you use the Add Roles Wizard to install IIS, you getthe default installation, which has a minimum set of role services. EnterpriseVault requires the following IIS-related roles services as a minimum:

■ Static Content

■ Default Document

■ Directory Browsing

■ HTTP Errors

■ HTTP Redirection

Common HTTPFeatures

Web Server

■ ASP.NET

■ .NET Extensibility

■ ASP

■ ISAPI Extensions

■ ISAPI Filters

ApplicationDevelopment

■ HTTP Logging

■ Logging Tools

■ Request Monitor

■ Tracing

Health andDiagnostics

■ Basic Authentication

■ Windows Authentication

■ Request Filtering

■ IP and Domain Restrictions

Security

■ Static Content Compression (recommendedfor performance but not mandatory)

Performance

IIS Management ConsoleManagement Tools

IIS Management Scripts and Tools

Management Service

■ IIS 6 Metabase Compatibility

■ IIS 6 WMI Compatibility

■ IIS 6 Scripting Tools

IIS 6 ManagementCompatibility

Enterprise Vault prerequisite software and settingsBasic software requirements

36


MSXMLAll Enterprise Vault server computers require MSXML. This is installedautomatically with Internet Explorer 6.0 and later.

If you are using an earlier version of Internet Explorer, you may need to installMSXML. This is available from a link in the Links to related software folderon the Enterprise Vault media.

SQL server softwareEnterprise Vault supports both SQL Server 2000 and 2005.

Both Windows Authentication mode and with Mixed Mode Authentication aresupported.

The SQL installation must be case-insensitive, as case-sensitive SQL installationsare not supported.

Note that if both Enterprise Vault and SQL Server are installed on the sameWindows Server 2003 computer, you will need at least SQL Server 2000 withService Pack 4. Windows Server 2008 requires SQL Server 2005 SP2 or later.

Microsoft Data Access Components (MDAC)To enable access to the SQL databases, MDAC 2.6 or later must be installed onEnterprise Vault servers. A suitable version is installed automatically with bothWindows Server 2003 and Windows Server 2008 (which changes the name ofMDAC to Windows Data Access Component, or Windows DAC).

If necessary, you can install the software using the link supplied in the Links to

related software folder on the Enterprise Vault media.

Pre-installation tasks for Enterprise Vault serverYou need to perform the tasks described in this section, irrespective of the typesof archiving that you plan to implement.

Creating the Vault Service accountThe Vault Service account is used by Enterprise Vault processes to access theWindows server operating system. The account is shared by all the EnterpriseVault computers in the Enterprise Vault directory. If you are managing multipleEnterprise Vault sites, you can use the same Vault Service account for more thanone Enterprise Vault site.

37Enterprise Vault prerequisite software and settingsPre-installation tasks for Enterprise Vault server

The Vault Service account must be a domain-based Windows security accountthat belongs to the local Administrators group on all computers in the EnterpriseVault directory. The account password must not be blank.

We recommend that you do not make this account a Domain Administrator. It isbetter to assign required permissions explicitly. This section describes the basicpermissions that you need to set for this account. Different types of archivingrequire additional permissions for the Vault Service account. For details of these,see the section on the type of archiving that you are implementing.

If possible, create the account so that it is in the same domain as the EnterpriseVault computers. If it is necessary for the Vault Service account and the EnterpriseVault computers to be in different domains, create the account so that it is in adomain that is trusted by the Enterprise Vault computers’ domain.

Ensure that the Microsoft Message Queue security has been set up to grant theAdministrators group access to the Enterprise Vault queues.

At the time the configuration wizard runs, the Vault Service account must haveaccess to administrative shares on the SQL Server computer. One way to enablethis is to make the Vault Service account a local administrator on the SQL Servercomputer. After the Configuration wizard has been run you can remove this access,if required.

During configuration, you are asked to provide the name and password of theVault Service account. Enterprise Vault automatically grants the account thefollowing advanced user rights:

■ Log On As a Service

■ Act As Part Of The Operating System

■ Debug programs

■ Replace a process-level token

Note that it may take some time for the Vault Service account to be registered inthe Active Directory for the computer that is going to run Enterprise Vault. Theaccount cannot be used until the registration is complete.

You are recommended to be logged in to the Vault Service account when youinstall Enterprise Vault. You must be logged in to the Vault Service account whenyou run the Enterprise Vault configuration wizard.

To create the Vault Service account

1 On the domain controller, click Start > Programs >Administrative Tools >ActiveDirectoryUsers and Computers.

2 In the left-hand pane ofActiveDirectoryUsersandComputers, double-clickthe Domain container.

Enterprise Vault prerequisite software and settingsPre-installation tasks for Enterprise Vault server

38

3 Double-click the Users container.

4 On theActionmenu, clickNew and thenUser. The New Object — User screenis displayed.

5 Complete the New Object — User screen and click Next. The next screen asksfor password details.

6 Enter a password and confirm it. You must set a password; the Vault Serviceaccount password cannot be blank.

7 Select the Password never expires check box.

8 Leave the remaining check boxes clear:

■ Usermust change password at logon

■ User cannot change password

■ Account is disabled

9 Click Next to move to the mailbox server screen.

10 Complete the details and click Next to move to the summary screen.

11 Click Finish to create the new user.

To add the new Vault Service account to the local Administrators group

1 Log on to the Enterprise Vault computer as Administrator.

2 In Control Panel, open Administrative Tools and start the ComputerManagement console.

3 Expand SystemTools and then Local Users andGroups.

4 Select Groups, and then double-click the Administrators group in theright-hand pane.

5 Use Add to add the Vault Service account to this group.

6 Click OK.

7 Repeat these steps on each computer which will have Enterprise Vaultinstalled.

Creating a SQL loginThe Vault Service account must have a SQL login account, with Database Creatorspermission, for the SQL Server.

To create a SQL login account in SQL 2000

1 Start EnterpriseManager for SQL 2000.

2 Expand the SQL Server container.

39Enterprise Vault prerequisite software and settingsPre-installation tasks for Enterprise Vault server

3 Click Security.

4 Right-click Logins and, on the shortcut menu, click NewLogin.

5 Enter or select the name of the Vault Service account. For example,domain\vaultadministrator

6 Check thatWindowsAuthentication is selected and that the correctDomainfor the account has been selected.

7 Under SecurityAccess check that Grant access is selected.

8 On the Server Roles tab, select Database Creators.

9 Click OK.

To create a SQL login account in SQL 2005

1 Start SQL ServerManagement Studio.

2 In the tree, select Security>Logins.

3 Right-click Logins and select NewLogin.

4 Either type in the Vault Service account as domain\username or click Searchand search for the account. In the search dialog, ensure that the correctdomain is entered in the Locations box.

5 Select Windows authentication.

6 In the tree, click Server roles.

7 Select the checkbox beside dbcreator.

8 Click OK.

9 You can check that the Vault Service account has the required permissionsas follows:

■ In the tree, select Security>Server Roles.

■ In the right-hand pane, double-click the dbcreator role.

■ The Vault Service account should be displayed in the membership list.

Creating Enterprise Vault DNS aliasesIt is good practice to create a DNS alias for each Enterprise Vault server computer.You are asked to enter the unqualified alias, for example evserver1, when yourun the Enterprise Vault Configuration wizard. When you configure EnterpriseVault on the first computer in a site, Enterprise Vault automatically creates avault site alias using the DNS alias entered for that computer. The vault site aliasis used by the Enterprise Vault software to refer to the Enterprise Vault site.

Enterprise Vault prerequisite software and settingsPre-installation tasks for Enterprise Vault server

40

The DNS alias must not contain special characters; as defined in RFC-1034, onlythe following characters are permitted: [a-z], [A-Z], [0-9] hypen (-) and period (.).The last character must not be either hypen (-) and period (.).

Using an unqualified DNS alias allows future flexibility if you change the computerthat is running the Enterprise Vault services.

Turning off or reconfiguringWindows Firewall inWindows Server 2008In Windows Server 2008, Windows Firewall is enabled by default. This preventsDistributed COM (DCOM) from working and therefore, because Enterprise Vaultrequires DCOM, you must either turn off Windows Firewall or configure itappropriately.

For guidelines on how to use DCOM with firewalls, see the following article:

http://msdn2.microsoft.com/en-us/library/ms809327.aspx

What next?Ensure that you also review the additional prerequisite information for yourplanned installation.

There are additional prerequisites for other Enterprise Vault components, fordifferent types of archiving, for a standalone Administration Console, and forclustered environments.

41Enterprise Vault prerequisite software and settingsWhat next?

http://msdn2.microsoft.com/en-us/library/ms809327.aspx

Enterprise Vault prerequisite software and settingsWhat next?

42

Additional requirements forOperations Manager


■ About additional requirements for Operations Manager

■ Where and when to install Operations Manager

■ Additional prerequisite software

■ Additional preinstallation tasks

■ What next?

About additional requirements for OperationsManager

Enterprise Vault Operations Manager is a separately installable component. It isa Web application that makes remote monitoring of Enterprise Vault possiblefrom any computer with Internet Explorer 6.0 or later.

This chapter describes where to install Operations Manager, and the additionalpreparation required before installation.

Where and when to install Operations ManagerTo use Operations Manager to monitor the Enterprise Vault servers in anEnterprise Vault site, Operations Manager must be installed on at least oneEnterprise Vault server in that site.

4Chapter

Operations Manager requires Enterprise Vault Services on the same computer.You can install the Operations Manager component at the same time as installingthe Enterprise Vault Services component, or at a later date. You must run theEnterprise Vault configuration wizard to configure the Enterprise Vault Servicesbefore you configure Operations Manager.

Additional prerequisite softwareThe computer on which you install Operations Manager requires the followingsoftware prerequisite in addition to the requirements listed in About the EnterpriseVault prerequisite software and settings:

■ The version of Internet Information Services (IIS) must be IIS 6.0 or later.

IIS must not be locked down.

If you are installing Operations Manager on Windows Server 2003 x64 Editions,you must switch to the 32-bit version of ASP.NET 2.0. To do this, see MicrosoftKnowledge Base article:


Note: You cannot install Operations Manager on a 64-bit edition of WindowsServer running Exchange Server 2007. Exchange Server 2007 requires the 64-bitversion of ASP.NET 2.0.

Additional preinstallation tasksCreate a Windows user account named, say, MonitoringUser, in the ActiveDirectory domain, for Operations Manager to use when accessing the EnterpriseVault databases. This monitoring user account does not require an Exchangemailbox, and it need not be a member of the Windows Administrators group.

When you create the monitoring user account:

■ Select the Password Never Expires option.

■ Leave the remaining check boxes clear (User Must Change Password At Logon,User Cannot Change Password, and Account Is Disabled).

What next?Ensure that you review all the additional prerequisite information for your plannedinstallation.

Additional requirements for Operations ManagerAdditional prerequisite software

44


There are additional prerequisites for other Enterprise Vault components, fordifferent types of archiving, for a standalone Administration Console, and forclustered environments. See the following chapters for details.

If you have reviewed all the prerequisite information, then you can install andconfigure your Enterprise Vault server.

45Additional requirements for Operations ManagerWhat next?

Additional requirements for Operations ManagerWhat next?

46

Requirements forEnterprise Vault Reporting


■ About requirements for Enterprise Vault Reporting

■ Where and when to install Enterprise Vault Reporting

■ Prerequisites for Enterprise Vault Reporting

■ Preinstallation tasks

■ What next?

About requirements for Enterprise Vault ReportingThe Enterprise Vault Reporting feature provides enterprise-level reporting forEnterprise Vault servers, using Microsoft SQL Server Reporting Services as thereporting mechanism. Administrators manage report content and view reportsusing the Reporting Services Report Manager Web application.

This chapter describes where and when to install Enterprise Vault Reporting, andlists the prerequisites and pre-installation tasks for this component.

Where andwhen to install Enterprise Vault ReportingTypically, the Enterprise Vault Reporting component is installed without anyother Enterprise Vault components on a Microsoft SQL Server Reporting Services(SSRS) server, separate from the Enterprise Vault servers. However, if required,and providing the prerequisites are met, you can include the Reporting componentas part of an Enterprise Vault server installation.

5Chapter

After installing Enterprise Vault Reporting you must run the Enterprise VaultReporting Configuration utility to configure Reporting and deploy the reports.

Note: You must only configure Reporting after running the Enterprise Vaultconfiguration utility successfully on at least one computer in the site on whichEnterprise Vault Services are installed.

Prerequisites for Enterprise Vault ReportingYou can install Enterprise Vault Reporting on any machine with the followingprerequisites. The machine does not require any other Enterprise Vaultprerequisites if you are installing the Reporting component only:

■ Microsoft SQL Server 2000 Reporting Services with SP2, or Microsoft SQLServer 2005 Reporting Services (SP1 recommended).

■ IIS registered with ASP.NET 1.1 for SQL Server 2000 Reporting Services SP2,or ASP.NET 2.0 for SQL Server 2005 Reporting Services.

■ A network connection to the computer hosting the Enterprise Vault Directorydatabase. If you are using FSA Reporting, then Enterprise Vault Reportingalso requires access to the FSA Reporting database.

Using Reporting on a 64-bit machineIf you install Enterprise Vault Reporting on a machine with a 64-bit processorrunning the 64-bit version of Microsoft SQL Server 2005 Reporting Services, threeof the Operations Reports covering vault store usage will not be available. Tomake these reports available, you need to install and run the 32-bit version ofSQL Server 2005 Reporting Services.

As a prerequisite, the 32-bit version of SQL Server 2005 Reporting Services requiresthe 32-bit version of ASP.NET on IIS. To run the 32-bit version of ASP.NET, seeMicrosoft Knowledge Base article http://support.microsoft.com/?kbid=894435.

Preinstallation tasksBefore installing the Enterprise Vault Reporting component, you must do thefollowing:

■ Install the required prerequisite software for Enterprise Vault Reporting.See “Prerequisites for Enterprise Vault Reporting” on page 48.

Requirements for Enterprise Vault ReportingPrerequisites for Enterprise Vault Reporting

48


■ Create a Windows user account named, say, ReportingUser, in the ActiveDirectory domain, for Enterprise Vault Reporting to use when accessing theEnterprise Vault databases. This reporting user account does not require amailbox, and it need not be a member of the Windows Administrators group.When you create the reporting user account:

■ Select the Password Never Expires option.

■ Leave the remaining check boxes clear (User Must Change Password AtLogon, User Cannot Change Password, and Account Is Disabled).

■ If you use Microsoft SQL Server Reporting Services 2000, grant the reportinguser account full access on the Temporary ASP.NET Files folder, which istypically C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Temporary

ASP.NET Files.

■ Give the Vault Service account a "Content manager" role on the MicrosoftReporting Services Report Server. Refer to the Microsoft Reporting Servicesdocumentation for instructions on assigning Microsoft SQL Server ReportingServices roles to user accounts.

■ Add the Vault Service account to the Local administrators group on theMicrosoft SQL Server Reporting Services server machine.




49Requirements for Enterprise Vault ReportingWhat next?

Requirements for Enterprise Vault ReportingWhat next?

50

Additional requirements forExchange Server archiving


■ About the requirements for Exchange Server archiving

■ Required software on Enterprise Vault server

■ Pre-installation tasks for Exchange Server archiving

■ Enterprise Vault client access with Exchange Server archiving

■ Prerequisites for OWA

■ Prerequisites for RPC over HTTP

■ What next?

About the requirements for ExchangeServer archivingYou can archive items from mailboxes and public folders on the following targetExchange servers:

■ Exchange 2000 with Service Pack 3

■ Exchange Server 2003

■ Exchange Server 2007 with Mailbox Role installed

This chapter describes the additional preparation required before installing andconfiguring Exchange Server archiving components.

6Chapter

Required software on Enterprise Vault serverFor Exchange Server archiving you must install Outlook 2003 on the EnterpriseVault computer.

Pre-installation tasks for Exchange Server archivingThis section describes the additional tasks that you need to perform beforeinstalling and configuring Exchange Server archiving components.

The Enterprise Vault system mailboxThe Enterprise Vault system mailbox is a mailbox that is used by the ExchangeMailbox, Exchange Journaling, and Exchange Public Folder tasks when connectingto the Exchange Server.

You must create a system mailbox on each Exchange Server that you wantEnterprise Vault to archive.

Note the following restrictions:

■ The Enterprise Vault tasks require exclusive use of this mailbox, so the mailboxmust not be used for any other purpose.

■ The mailbox must not be hidden from address lists.

■ The account must not be disabled

You are prompted for the name of this mailbox whenever you create an ExchangeServer archiving task.

After you create the Enterprise Vault system mailbox, it may take some time forthe mailbox to be available. The amount of time depends on configuration optionsin Exchange System Manager. The mailbox must be available before you add anExchange Server archiving task.

If required, you can make the mailbox available sooner by manually forcing anupdate of Exchange Server 2000 or 2003. This is not required on Exchange Server2007.

To force a manual update of the Exchange Server (2000 or 2003)

1 Click Start > Programs >Microsoft Exchange > SystemManager.

2 In the left-hand pane, double-click the Recipients container.

3 Click Recipient Update Services.

Additional requirements for Exchange Server archivingRequired software on Enterprise Vault server

52

4 In the right-hand pane, right-click the Recipient Update Service for thedomain that contains the Exchange Server computer for which you are addingan archiving task.

5 Click UpdateNow.

The mailbox should be available within a minute or two.

Additional Vault Service account permissionsThe Vault Service account must be a member of the Active Directory domain. Werecommend that you do not make this account a Domain Administrator. It is betterto assign Exchange Server permissions explicitly, as described in this chapter.

Assigning permissions on Microsoft Exchange ServerThe Vault Service account needs to be able to access mailboxes on the ExchangeServers that Enterprise Vault is to archive. You need to grant permissions explicitlyon each Exchange Server, as described in this section. If you later add anotherExchange Server, you need to repeat the procedure on the new server to enablemailbox access for the Vault Service account.

You must have Exchange administration permissions to do the following tasks.

On Microsoft Exchange Server 2007

1 On Exchange Server 2007 with Mailbox Role installed, run adsiedit.msc toconfigure the permissions for the Vault Service account in Active Directory;

adsiedit.msc is included in Windows support tools.

2 Expand the tree as follows:

Configuration[your domain]/CN=Configuration,[yourdomain]/CN=Services/CN=Microsoft Exchange/CN=[your Exchangeorganization]/CN=AdministrativeGroups/CN=ExchangeAdministrativeGroup(FYDIBOHF23SPDLT)/CN=Servers.

3 For each server object representing an Exchange Server 2007 with MailboxRole installed, do the following:

■ Right-click the object and select Properties.

■ Click the Security tab.

■ Add the Vault Service account and grant this account Full Control.

■ Click Apply.

■ Click Advanced.

53Additional requirements for Exchange Server archivingPre-installation tasks for Exchange Server archiving

■ For the permission entry for the Vault Service account:Select the permission entry and click Edit....Change Apply onto to This object and all child objects.Click OK.

■ Click OK to close the Advanced Security Settings window.

■ Click OK and close the Properties window.

4 You must also grant the Vault Service account SendAs permission on theEnterprise Vault system mailbox object (and all child objects).

■ In adsiedit.msc click Domain [your_domain].

■ Locate the mailbox that you created for the Enterprise Vault systemmailbox. This is usually under CN=Users.

■ Right-click the object and select Properties.

■ Click the Security tab.

■ Add the Vault Service account and then add Send as permissions to thisaccount.

■ Click Apply.


■ Close adsiedit.msc.

On Microsoft Exchange Server 2003 and Microsoft Exchange 2000 Server

1 Click Start > Programs >Microsoft Exchange > SystemManager.

2 Expand the Servers container.

3 Right-click your Exchange Server and, on the shortcut menu, clickProperties.

4 Click the Security tab.

5 Click Add.

6 Double-click the Vault Service account to add it to the list.

7 Click OK to go back to the Security tab. The Vault Service account has beenadded to the Name list.

8 In the Name list, click the Vault Service account.

9 In the Permissions list, make sure that all check boxes in the Allow columnare selected. Select any check boxes that are not already selected.

10 Click OK.

Additional requirements for Exchange Server archivingPre-installation tasks for Exchange Server archiving

54

Assigning the permissions at Organization or AdministrativeGroup levelIf required, you can add the permissions at the Organization or AdministrativeGroup level in the Exchange hierarchy. This will enable the permissions to bepropagated automatically to any new Exchange Servers added below the level atwhich the permissions are assigned.

To assign the permissions at Organization or Administrative Group level (ExchangeServer 2000 or 2003)

1 Enable the display of theSecuritypage by configuring theShowSecurityPageregistry setting (see Microsoft Knowledge Base Article 883381).

2 In the left-hand pane of Microsoft Exchange, SystemManager, right-clickyour Exchange Organization or the administrative group that you want, andselect Properties.

3 Select theSecurity tab and set the required permissions for the Vault Serviceaccount, as described in the steps for individual Exchange Servers.

To assign the permissions at Organization or Administrative Group level (ExchangeServer 2007)

1 To assign permissions at Exchange Organization level, expand the tree inadsiedit.msc as follows:

Configuration[your domain]/CN=Configuration,[yourdomain]/CN=Services/CN=Microsoft Exchange/CN=[your Exchangeorganization]

To assign permissions at Administrative Group level, expand the tree asfollows:

Configuration[your domain]/CN=Configuration,[yourdomain]/CN=Services/CN=Microsoft Exchange/CN=[your Exchangeorganization]/CN=AdministrativeGroups/CN=ExchangeAdministrativeGroup(FYDIBOHF23SPDLT)

2 Right-click the object and select Properties.

3 Click the Security tab.

4 Add the Vault Service account and grant this account Full Control.

5 Click Apply.

6 Click Advanced.

7 For the permission entry for the Vault Service account:

■ Select the permission entry and click Edit....


■ Change Apply onto to This object and all child objects.

■ Click OK to exit the Edit window.

■ Click OK to close the Advanced Security Settings window.


8 Close adsiedit.msc.

Assigning permission for managed folder synchronization inExchange Server 2007The Exchange Provisioning task performs synchronization of managed contentsettings in Exchange managed folders from Exchange Server 2007 to EnterpriseVault. To enable the task to synchronize settings, the Exchange View-OnlyAdministrator role must be assigned to the Vault Service account.

For information about archiving from Exchange managed folders, see theAdministrator's Guide.

To assign the Exchange View-Only Administrator role to the Vault Service account

1 Open the Exchange Management Console.

2 If necessary, expand the tree so that Organization Configuration is visible.

3 Right-click Organization Configuration and select AddExchangeAdministrator.

4 On the AddExchangeAdministrator page, select the name of the VaultService account.

5 Select ExchangeView-OnlyAdministrator role.

6 Click Add.

7 On the Completion page, click Finish.

Create an Outlook profile on the Enterprise Vault server computerWhen you install Outlook on the Enterprise Vault server, you must create a profileand connect to an Exchange Server mailbox before you install Enterprise Vault.

Outlook may display an error message about a conflicting program. If Outlookoffers to fix the problem, choose to do so and then follow the instructions given.

See the Administrator’s Guide for information on MAPISVC.INF problems.

Additional requirements for Exchange Server archivingPre-installation tasks for Exchange Server archiving

56

Connecting to Exchange Server 2007If the target server is Exchange Server 2007, it must have a Public Folder storecreated to enable connections from versions of Outlook earlier than Outlook 2007.If you selected the option to support older clients when you installed ExchangeServer 2007, then a Public Folder store will have been created automatically.

If a Public Folder store does not exist on the target Exchange Server 2007, thenyou must create one manually to enable Outlook 2003 on the Enterprise Vaultserver to connect to the Exchange Server.

To create a Public Folder store manually

1 On the Exchange Server open the Exchange Management Shell.

2 Enter the following command:

new-publicfolderdatabase -Name "Public Folders"

-StorageGroup "First Storage Group"

-EdbFilePath "C:\Program Files\Microsoft\ExchangeServer\

Mailbox\First Storage Group\Public Folders.edb"

3 Enter the following command to mount the Public Folder database:

mount-database -Identity "Public Folders"

4 You may need to create an Offline Address Book with Public Folder integrationenabled if you are using clients prior to Outlook 2007.

Configure Internet ExplorerIn Internet Explorer on the Enterprise Vault server, ensure that Microsoft OfficeOutlook is set as the default email application for Internet services.

To set the default email application

1 Start Internet Explorer.

2 Select Internet Options from the Tools menu.

3 Click the Programs tab.

4 In the E-mail box, select Microsoft Office Outlook.

5 Click OK.


Enterprise Vault client access with Exchange Serverarchiving

Users can access and manage items in archives using the following client accessmethods:

■ Enterprise Vault Outlook Add-Ins

■ OWA clients, which require Enterprise Vault Exchange Server extensions forOWA

■ Enterprise Vault customized shortcuts.

■ Enterprise Vault search or Archive Explorer in a browser session.

Prerequisites for Outlook Add-InsEnterprise Vault Outlook Add-Ins provide Enterprise Vault user functionality toOutlook users. From within Outlook, users can archive items manually, and view,copy and delete archived items. Outlook users can also start Archive Explorer andEnterprise Vault Search, within Outlook, to access and manage items stored inarchives.

The following Enterprise Vault Add-Ins are available:

■ Outlook Add-In

■ HTTP-only Outlook Add-In

Before users can send items to an archive from within their Outlook client, oneof the Outlook Add-Ins must be installed on their computers. Install the OutlookAdd-In on user computers after you have configured the Enterprise Vault server.

For any of the Add-Ins, user computers must have the following:

■ Operating system – Windows XP (with Service Pack 2 or later) or WindowsVista (with Service Pack 1 or later). (Currently only 32-bit versions of theseoperating systems are supported).

■ Internet Explorer 6.0 or later, with JavaScripting enabled.This must be installed, even if it is not used.

■ TCP/IP protocol.

■ Mail client – Outlook 2003 or Outlook 2007.Install Internet Explorer before you install the mail client.

■ If you plan to enable vault cache, Background Intelligent Transfer Service(BITS) 2.0 or later must be installed and enabled on users' computers. Thisservice is used by Microsoft Windows Update and is included in Windows XP

Additional requirements for Exchange Server archivingEnterprise Vault client access with Exchange Server archiving

58

Service Pack 2 and Windows Vista. If necessary, it can be downloaded fromthe Microsoft website.

■ If you plan to enable vault cache, and have disabled the expansion of PST fileson users' computers by setting the registry entry, PstDisableGrow, then youneed to request and install the following Outlook hotfix from Microsoft.

■ For Outlook 2003:http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=953671&kbln=en-us

■ For Outlook 2007:http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=953925&kbln=en-us

You will also need to configure the registry setting,PSTDisableGrowAllowAuthenticodeOverrides on users' computers, as describedin the chapter on vault cache in the Setting up Exchange Server Archivingmanual.

■ If you plan to enable the Windows Desktop Search plug-in, then WindowsDesktop Search 3.x or later must be installed on the target desktop computers.The Windows Desktop Search plug-in requires Outlook 2007 or Outlook 2003and Enterprise Vault 7.0 or later, Outlook Add-In or HTTP-only Outlook Add-Ininstalled on the desktop computers.You can download Windows Desktop Search from the following address:http://www.microsoft.com/windows/desktopsearch/downloads/default.mspx

OWA clientsEnterprise Vault functionality can be made available in OWA 2003 and OWA 2007Basic and Premium clients by installing Enterprise Vault OWA server extensionson the Exchange Server. Enterprise Vault functionality available with OWA 2000clients is limited to viewing archived items.

With OWA 2007 and OWA 2003 you can control the functionality of the clientsusing OWA settings on the Advanced page of the Exchange Desktop Policyproperties.

On user desktops, Internet Explorer 6.0 or later is required to support the fullfunctionality available with OWA 2007 and OWA 2003 clients.

You do not need to install Enterprise Vault Add-Ins on user desktop computers.

Customized shortcutsIf you do not want to install the Enterprise Vault Outlook Add-Ins on desktopcomputers, or users do not use Outlook as their email client, you can configureEnterprise Vault customized shortcuts in the Exchange Mailbox Policy. Forexample, users may use Entourage (on Mac computers).

59Additional requirements for Exchange Server archivingEnterprise Vault client access with Exchange Server archiving

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=953671&kbln=en-us

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=953925&kbln=en-us

http://www.microsoft.com/windows/desktopsearch/downloads/default.mspx

Using customized shortcuts, users can view an HTML version of archived items,and start Archive Explorer and archive search in a browser session to access andmanage items stored in archives.

On Windows computers, Internet Explorer 6.0 or later, with Java scripting enabled,must be installed on each user’s desktop computer.

On Mac computers, Entourage email client and Safari browser are supported. Fordetails of supported versions, see the Enterprise Vault Compatibility Charts.

Archive search and Archive Explorer in standalone browserUsers can access Enterprise Vault archives using Archive Explorer or archivesearch in a standalone browser session. Enterprise Vault Add-Ins are not requiredon desktop computers, but you will need to inform users of the URLs to enter intheir browser for Archive Explorer and archive search. These will typically takethe following format:

■ Archive Explorer URL:http://web_server_name/EnterpriseVault/ArchiveExplorerUI.asp

■ Integrated search URL:http://web_server_name/EnterpriseVault/searcho2k.asp

■ Browser search URL:http://web_server_name/EnterpriseVault/search.asp

To use Enterprise Vault browser search or Archive Explorer in a browser session,Internet Explorer 6.0 or later, with Java scripting enabled, must be installed oneach user’s desktop computer.

Note: With Exchange Server Journal archiving, shortcuts are not created in themailbox. The associated archives can be accessed using archive search, but notArchive Explorer.

Prerequisites for OWAYou can configure OWA access to Enterprise Vault after you have set up yourEnterprise Vault server for Exchange Server archiving. The instructions forconfiguring OWA access to Enterprise Vault assume that you have alreadyconfigured OWA on Exchange Servers.

To provide OWA 2000 or OWA 2003 access, install Enterprise Vault OWA 2000or OWA 2003 server extensions on OWA front-end and back-end Exchange Servers.

Additional requirements for Exchange Server archivingPrerequisites for OWA

60

To provide OWA 2007 access, install the Enterprise Vault OWA 2007 Extensionson Exchange Server 2007 with Client Access Server (CAS) role installed.

The following are additional requirements for accessing Enterprise Vault fromOWA clients:

■ If you are running Enterprise Vault on Windows Server 2008, then the followingRole Services must be installed for the Web Server (IIS):

■ IIS Management Scripts and Tools

■ IIS 6 Management Compatibility

■ IP and Domain Restrictions

In addition, the option IPv4 Address and Domain Restrictions in FeatureDelegation must be set to Read/Write. To find this option, open InternetInformation Services (IIS) Manager and click the server object in the navigationpane. Open Feature Delegation and IPv4 Address and Domain Restrictions isincluded in the listed options.

■ If you are running Exchange Server 2003 on OWA servers, Exchange Server2003 Service Pack 1 or later on Windows Server 2003 Service Pack 2 or lateris required.

■ As Enterprise Vault OWA 2003 Extensions modify OWA control files onExchange Server 2003, the version of these files must be one that is supportedby Enterprise Vault.See the Enterprise Vault Compatibility Charts.

■ If the back-end OWA 2000 server computer is running Windows 2000, Windows2000 Service Pack 4 or later is required.

■ MSXML is required on Exchange OWA servers (with the exception of front-endOWA 2000 servers). This is installed automatically with Internet Explorer 6.0and later. If you are using an earlier version of Internet Explorer, you mayneed to install MSXML. This is available from a link in the folder, Links to

related software, on the Enterprise Vault media.

■ On user desktops, Internet Explorer 6.0 or later is required to support the fullfunctionality available with OWA 2003 and OWA 2007 clients.Note that the Enterprise Vault buttons are not available in OWA 2000 clients,which means that you can only view archived items. To be able to archive,restore, and delete archived items from your OWA client and have integratedaccess to Archive Explorer and Search features, you need to use OWA 2003 orOWA 2007.

61Additional requirements for Exchange Server archivingPrerequisites for OWA


Prerequisites for RPC over HTTPEnterprise Vault supports RPC over HTTP access for Outlook users.

RPC over HTTP with Exchange Server 2003Exchange Server 2003 with the RPC over HTTP Windows component is requiredon RPC proxy Exchange Servers.

Client computers require Outlook 2003 with one of the following versions ofWindows:

■ Windows XP Service Pack 2 or later

■ Windows Vista

Outlook Add-Ins (any type) are required on desktop computers.

You can configure RPC over HTTP access to Enterprise Vault after you have setup your Enterprise Vault server for Exchange Server archiving and distributedEnterprise Vault Add-Ins to desktop computers.

You then install and configure Enterprise Vault OWA Extensions on RPC proxyservers and target Exchange Servers. For this reason, the additional prerequisiteslisted for Enterprise Vault OWA 2003 Extensions are also needed if you areconfiguring RPC over HTTP access with Exchange Server 2003.

See “Prerequisites for OWA” on page 60.

See the Setting up Exchange Server Archiving manual for instructions on settingup RPC over HTTP access to Enterprise Vault.

The instructions given assume that you have already configured RPC over HTTPon RPC proxy servers and target Exchange Servers. Users’ computers must alsobe set up to use RPC over HTTP access to the Exchange Server.

RPC over HTTP with Exchange Server 2007 (Outlook Anywhere)On Exchange Server 2007 RPC over HTTP access is called Outlook Anywhere. RPCover HTTP access is provided by Exchange Server 2007 with Client Access Server(CAS) installed. No Enterprise Vault Extensions are required on Exchange Server2007, but you need to configure RPC over HTTP access on the Enterprise Vaultserver.

Outlook on users' computers needs to be configured to use RPC over HTTP, andEnterprise Vault Outlook Add-Ins (any type) need to be installed on users'computers. See the SettingupExchangeServerArchivingmanual for instructions.

Additional requirements for Exchange Server archivingPrerequisites for RPC over HTTP

62

What next?Ensure that you review all the additional prerequisite information for your plannedinstallation. There are additional prerequisites for other Enterprise Vaultcomponents, for different types of archiving, for a standalone AdministrationConsole, and for clustered environments.

See the following chapters for details.


63Additional requirements for Exchange Server archivingWhat next?

Additional requirements for Exchange Server archivingWhat next?

64

Additional prerequisites forDomino Server archiving


■ Prerequisites for Domino Server mailbox archiving

■ Prerequisites for all Enterprise Vault servers

■ Prerequisites for Domino journal archiving

■ What next?

Prerequisites for Domino Server mailbox archivingFor Domino mailbox archiving, you need to configure the following:

■ One or more Enterprise Vault Domino Gateways.The Enterprise Vault Domino Gateway is a Domino server that is customizedby Enterprise Vault configuration. The Enterprise Vault Domino Gatewayprovides the interface between Lotus Notes clients and Enterprise Vault. Allthe major actions on archived data (opening, restoring, deleting and searching)are handled by the Enterprise Vault Domino Gateway.

■ One or more Enterprise Vault servers. An Enterprise Vault server can beco-located with an Enterprise Vault Domino Gateway or installed on a separatecomputer. To ensure control of load balancing, we recommend that youco-locate the Enterprise Vault Domino Gateway and Enterprise Vault server.

■ Target Domino mail servers.

■ Enterprise Vault client extensions for Lotus Notes and Domino Web Access.

7Chapter

This section describes the prerequisite software and settings for Domino mailboxarchiving and the tasks that you need to perform before installing EnterpriseVault.

If you are going to install Enterprise Vault Administration Console on a remotecomputer, then you must also install Lotus Notes 7.0.2 or later on that computerin order to manage Domino user archives.

This section describes the minimum requirements for Domino mailbox archiving.For details of the latest supported software versions, see the Enterprise VaultCompatibility Charts (http://entsupport.symantec.com/docs/276547).

Prerequisite software for Enterprise Vault Domino GatewayThe Enterprise Vault Domino Gateway must be a Windows server that is runningthe following minimum software versions:

■ Domino Server 8.0 and Lotus Notes Client 8.0

■ Domino Server 7.0.2 and Lotus Notes Client 7.0.2

■ Enterprise Vault 8.0

Depending on which versions of Domino Server and Lotus Notes you use, you mayrequire Lotus Hotfixes.

For details of required hotfixes, see the Enterprise Vault Compatibility Charts(http://entsupport.symantec.com/docs/276547).

You will need at least a Domino Messaging server license for each Enterprise VaultDomino Gateway.

Prerequisite software for target Domino mail serversTarget Domino mail servers that you want to archive must be running DominoServer 6.5.4 or later.

For details of the latest supported software versions, see the Enterprise VaultCompatibility Charts (http://entsupport.symantec.com/docs/276547).

Prerequisites for Enterprise Vault extensions for Lotus Notes clientsClient access to archived items from Lotus Notes or Domino Web Access (DWA)clients is provided through changes to the Lotus Notes and DWA mail templates;no application needs to be installed on user workstations. You install the updatedmail templates on target Domino mail servers and DWA servers throughout anorganization.

Additional prerequisites for Domino Server archivingPrerequisites for Domino Server mailbox archiving

66




Users who require Enterprise Vault functionality available in their Lotus Notesclient must have Lotus Notes Client 6.5.4 or later installed on their workstations.

For details of the latest supported software versions, see the Enterprise VaultCompatibility Charts (http://entsupport.symantec.com/docs/276547).

To enable the use of Enterprise Vault integrated search from within Lotus Notesor DWA mail clients, users must have Internet Explorer 6.0 or later installed ontheir workstations, and it must be set as the default Web browser in Lotus Notes.In addition, you need to configure Single Sign-On for the users on the EnterpriseVault Domino Gateway.

See “Configure Single Sign-On” on page 69.

Pre-installation tasks for Domino mailbox archivingYou should have already created the following:

■ The Vault Service account.

■ A SQL login account for the Vault Service account .

■ DNS aliases for the Enterprise Vault server and site.

See “Pre-installation tasks for Enterprise Vault server” on page 37.

You now need to perform the tasks described in this section to set up Dominoserver and Lotus Notes on the Enterprise Vault Domino Gateway computer. Thefollowing steps must be completed before you install Enterprise Vault on thecomputer: This ensures that the Enterprise Vault installation program detectsthat this is a Domino server and will install the extension manager files and otherdatabase files.

■ Use IBM Domino Administrator client to do the following:

■ Register the Domino server that will run on the Enterprise Vault DominoGateway computer, and set up the configuration for this server in theDomino Directory.See “Register the Enterprise Vault Domino Gateway ” on page 68.

■ Identify or create a user ID for the Domino mailbox archiving.See “User ID for Domino mailbox archiving” on page 70.

■ Configure the server documents for the Domino mail servers from whichEnterprise Vault will archive.See “Configure the server document for each target Domino mail server”on page 71.

■ On the computer that will host the Enterprise Vault Domino Gateway, do thefollowing:

67Additional prerequisites for Domino Server archivingPrerequisites for Domino Server mailbox archiving


■ Install Domino server binaries and configure the Domino server.See “Install and configure Enterprise Vault Domino Gateway” on page 73.

■ Install Lotus Notes client binaries and hotfix, and configure the client.See “Prerequisites for all Enterprise Vault servers” on page 75.

After you have completed these tasks, you can install Enterprise Vault and performthe initial configuration.

See “Installing Enterprise Vault” on page 103.

You can then complete the configuration of Domino mailbox archiving. See theSetting up Domino Server Archiving manual for instructions.

Register the Enterprise Vault Domino GatewayThere must be at least one Enterprise Vault Domino Gateway for each Dominodomain to be archived. In a production environment, the Enterprise Vault DominoGateway should not be used as a general mail server.

The Enterprise Vault Domino Gateway can be a partitioned Domino server.

Use IBM Domino Administrator client to register the Enterprise Vault DominoGateway, and configure the server document, as described in this section. If youplan to have several Enterprise Vault Domino Gateway computers in your Dominodomain, then you will need to repeat the following tasks for each Enterprise VaultDomino Gateway.

■ Configure the HTTP port.

■ Configure server security.

■ Add trusted servers.

■ Set up Single Sign-On.

Configure the Internet port for HTTPEnterprise Vault requires the HTTP task to be configured on the Enterprise VaultDomino Gateway. As IIS and the Domino server HTTP task both use port 80,change the port used by the Domino server.

To configure the Internet port for HTTP

1 In Domino Administration client open the server document for the EnterpriseVault Domino Gateway.

2 Select Ports tab and then Internet Ports tab in sub-document.

3 OnWeb tab, set TCP/IP port number to something other than 80; for example,8080.


68

Configure server securityTo configure server security

1 Open the Security page of the server document.

2 In the Programability restrictionsWho can section, ensure that the userwho will sign the mail templates is displayed in the field Sign agents to runon behalf of the invoker of the agent.

3 Scroll down to ServerAccess.

4 Add the user who will sign the mail templates to Createmaster templates.

5 Add the target Domino mail servers to Trusted servers.

6 Click Save and Close.

7 Repeat the above steps for each Enterprise Vault Domino Gateway.

Configure Single Sign-OnTo enable authentication for the archive search feature, you need to set up SingleSign-On on the Enterprise Vault Domino Gateway.

The following procedure assumes that you are not using Internet Sites documents,if you are then use the procedure outlined in the Lotus Domino documentation.

For more detail on how to configure Single Sign-On using Web Configuration, seethe following IBM article:

http://www-1.ibm.com/support/docview.wss?rs=2272&context=SSTJRP&dc=DA400&uid=swg27002760&loc=en_US&cs=UTF-8&lang=en&rss=ct2272lotus

To configure Single Sign-On

1 In the Domino Administrator client go toConfiguration tab and selectServer> All ServerDocuments view. Select (but do not open) the server documentfor the Enterprise Vault Domino Gateway.

2 Click Web and select CreateWeb SSOConfiguration from the drop downbox .

■ In theConfigurationName field, change the default name to EVLtpaToken.

■ In the DNSDomain field, enter the DNS domain of the participatingDomino servers.

■ In the Domino ServerNames field, add all the Enterprise Vault DominoGateways. If you want Single Sign-On to cover DWA users, then you alsoneed to add the target Domino mail servers.





■ Click Keys and in the drop down menu select CreateDomino SSOKey.Click OK.

■ Save and Close the Web SSO Configuration.

3 While the server document for the Enterprise Vault Domino Gateway isselected, click Edit server.

■ Click Internet Protocols tab and then DominoWebEngine sub-tab.

■ Change the SessionAuthentication field to Multiple Servers (SSO).

■ In the WebSSOConfiguration field select EVLtpaToken.

■ Save and close the server document.

User ID for Domino mailbox archivingThe Domino provisioning and mailbox archiving tasks need to access the user’smail databases in order to do the following:

■ Add hidden views.

■ Add or update a hidden Enterprise Vault profile document.

■ Change mail items into shortcuts.

To comply with the Domino security model, this access to Domino mail databasesneeds to be done by an authenticated user using a Lotus Notes ID file. When youconfigure the server document for target Domino mail servers, you will give thisID at least Editor access and Delete Documents and Create shared folders/viewspermissions on mail files to be archived.

See “Granting the Domino archiving user access to mail files ” on page 71.

Later, you specify this ID in the Enterprise Vault Administration Console whenyou are configuring Domino mailbox archiving. The ID details (including thepassword) are encrypted and stored in the Enterprise Vault directory database.

Although you can use any user ID file that has the correct level of access, werecommend that you create a generic user account and grant the user the accesspermissions required.

Creating the Domino archiving userUse the user registration tool in the Domino Administrator client to create ageneric user account. As the user’s person document must contain the Dominodomain name, the user must be a Lotus Notes mail user. It is advisable to give theuser a sensible generic name, for example, Enterprise Vault Domino Archiving.


70

You can prefix the last name with the special character '&' to ensure that the useris only displayed at the end of the address list, for example, Enterprise VaultDomino &Archiving/organization.

Configure the server document for each target Domino mail serverWhen configuring the server document for each of the target Domino mail servers,you will need to do the following:

■ The server document for each target Domino mail server must have EnterpriseVault Domino Gateways added as trusted servers:

■ The signing ID that will be used to sign the Enterprise Vault client templatesalso needs to be given the following permissions:

■ Sign agents to run on behalf of the invoker of the agent, on target Dominomail servers.

■ Create master templates.

■ The Domino archiving user needs to be given access to target user mail files.

■ Optionally, you may want to enable Single Sign-On for DWA users.

To configure the server document for target mail servers

1 Open the Security page of the server document.

2 In the Programability restrictionsWho can section, ensure that the userwho will sign the mail templates is displayed in the field Sign agents to runon behalf of the invoker of the agent .

3 Scroll down to ServerAccess, and add all the Enterprise Vault DominoGateways in the domain as trusted servers.

4 Click Save and Close.

5 Repeat the above steps for each Enterprise Vault target Domino mail server.

Granting the Domino archiving user access to mail filesThe Domino archiving user needs to have at least Editor access and the followingpermissions to all the mail files to be archived:

■ Delete documents

■ Create shared folders/views


Note: If you intend not to archive unread items then the Domino archiving userrequires Manager access to the mail files. This is because Domino requires Manageraccess in order to determine which items are unread.

If Domino administrators have Manager access to all mail files, then you can usethe Manage ACL tool in the Domino Administrator client to add the Dominoarchiving user to all mail databases.

Repeat the following steps for each target Domino mail server.

To add the Domino archiving user to all mail databases

1 In the Domino Administrator client, navigate to the Domino mail server andclick the Files tab.

2 In the tasks pane, click theMail folder to display a list of all the mail databasesin the results pane.

3 Select the first mail database, and then press Shift and End together to selectall the mail databases.

4 Right-click and select Access Control > Manage.

5 ClickAdd and then press the person icon to select the Domino archiving userfrom the Domino directory list. Click OK.

6 When the user is in the ACL dialog box, change the Access field to Editorand the User Type to Person.

7 Select DeleteDocuments and Create shared folders/views.

8 Click OK to add the user to the ACL of all mail databases selected.

Warning: It is very important to set the User Type to Person to prevent any userfrom creating a group within the Domino directory of the same name as theDomino archiving user and granting the group access to all mail databases.

If no user has Manager access to every mail database, then do the following:

■ Place the Domino server administrator’s user name in the Full AccessAdministrators field in the server document.

■ Restart the Domino server.

■ In the Domino Administrator client choose Administration > Full AccessAdministration and complete the procedure described above.

■ If necessary the administrator can then be removed from the Full AccessAdministrators field.


72

Single Sign-OnThe main requirement for Single Sign-On is to enable users to use the EnterpriseVault search feature. However, if Single Sign-On is not configured, DWA userswill need to re-enter authentication details when opening archived items. To avoidthis, you may want to configure Single Sign-On on DWA servers, even if you donot plan to give users access to the Enterprise Vault search feature.

See “Configure Single Sign-On” on page 69.

Install and configure Enterprise Vault Domino GatewayInstall Domino Server binaries on each Enterprise Vault Domino Gatewaycomputer. Select the Messaging Server option when installing.

If you have installed Domino 7.0.2 on the Enterprise Vault Domino Gateway youmust apply a Lotus Hotfix.

See “Prerequisite software for Enterprise Vault Domino Gateway ” on page 66.

The Domino server on the Enterprise Vault Domino Gateway must run under theVault Service account. It is best practice to run the Domino server as a service,but be aware that the server console is not displayed when running a service underan account other than the system account. This is a Microsoft Windows limitation.To see the console, you can connect to it remotely.

If you want to have the server console displayed locally while you are configuringDomino Mailbox archiving , you can run the Domino server as an application asfollows:

■ Log on to the Enterprise Vault Domino Gateway computer using the VaultService account.

■ In Windows Services console, if the Lotus Domino Server service is running,stop it.

■ Disable the Lotus Domino Server service.

■ Start the Lotus Domino Server (by double-clicking the desktop icon or runningDomino program directory\nserver.exe), and select the option to start theserver as a regular application. The Domino server configuration starts.

During Domino server configuration:

■ Supply the Domino Server ID that was created when you registered the Dominoserver on the Enterprise Vault Domino Gateway.

■ Select the option Web Browsers (HTTP Services) on the Internet Services pageto add the HTTP server task.


■ For optimum performance, you can use the Customize button to remove allbut the minimum server tasks. The following Domino server services are theminimum required on the Enterprise Vault Domino Gateway:

■ Indexer (Update)

■ Administration process (AdminP)

■ Domino web server (HTTP)

Note: In a production environment, start the Domino Server on the EnterpriseVault Domino Gateway as a service running under the Vault Service account.

To ensure that Enterprise Vault can configure user mail files for archiving, andsubsequently update the users' mail files with any archiving policy changes, theDomino Directory should replicate frequently to the Enterprise Vault DominoGateway.

To enable DWA users to open those archived MIME items that are signed orencrypted there must be an SSL connection to the Enterprise VaultDominoGateway. In this case, you must configure the Enterprise Vault Domino Gatewayfor SSL. If you do not do this configuration, DWA users receive the following errormessage:

Unable to complete the current operation.

SSL is required for secure mail,

but is not enabled on Domino Server.

Please notify your administrator.

Install and configure Enterprise VaultBefore installing Enterprise Vault, stop the Domino Server on the Enterprise VaultDomino Gateway, if it is running.

You can now install Enterprise Vault on the Enterprise Vault Domino Gatewaycomputer and perform the initial set up tasks.

Enterprise Vault can be co-located with an Enterprise Vault Domino Gateway oron a separate computer. To ensure control of load balancing, we recommend thatyou install Enterprise Vault on the same computer as the Enterprise Vault DominoGateway.

As the Enterprise Vault server will be responsible for Domino mailbox archivingand all client interactions, you can optimize performance by running only theminimum tasks and services on this computer.

The following Enterprise Vault services are required:


74

■ Admin service

■ Directory service

■ Storage service

■ Indexing service

■ Task controller service

See “Installing Enterprise Vault” on page 103.

After you have installed and configured Enterprise Vault, you can set up yourDomino mailbox archiving environment using the Enterprise Vault AdministrationConsole. See the Setting up Domino Server Archiving manual for instructions.

Prerequisites for all Enterprise Vault serversFor all Domino archiving you must install the Lotus Notes client on the EnterpriseVaultDomino Gateway and on every Enterprise Vault server, as follows:

■ Install Lotus Notes 7.0.2 or later client software. For details of the latestsupported software versions, see the Enterprise Vault Compatibility Charts(http://entsupport.symantec.com/docs/276547).

■ During the client installation ensure that you select the single user option.You do not need to install the Domino Administrator client software.

■ Start each Notes client and complete its configuration wizard.

Prerequisites for Domino journal archivingThe Domino Server must be running Lotus Domino Server 6.5.4 or later.

On the Enterprise Vault server that will run the Domino Journaling task, you willneed to install and configure Lotus Notes Client.

During the client installation, select the single user option, and configure theLotus Notes client for a Domino server in your organization.

For full details of all the supported versions of prerequisite software, see theEnterprise Vault Compatibility Charts athttp://entsupport.symantec.com/docs/276547.

Conflict with Microsoft Office 2003If you have a Domino Journaling task and Microsoft Office 2003 on the sameserver, a steady increase in handle usage can lead to out-of-memory errors.

75Additional prerequisites for Domino Server archivingPrerequisites for all Enterprise Vault servers



This is a known issue with Microsoft Office 2003, described in Microsoft supportarticle 841532.

To apply the fix

1 Determine the location of the file Msoxmlmf.dll. The file is in the Officeshared folder, the default location for which is as follows:

C:\Program Files\Common Files\Microsoft Shared\Office11

2 Click Start, click Run.

3 Type regsvr32.exe /u and then the path to Msoxmlmf.dll. For example, ifthe file is in the default location, you might type the following:

regsvr32.exe /u "c:\program files\common files\microsoft

shared\office11\msoxmlmf.dll"

4 Click OK.

Domino Journaling databasesEnterprise Vault will archive from any subfolder of the target Domino server'sData directory. Each subfolder, which must already exist, must be an immediatesubfolder of the Data directory, and not lower down the folder structure. Otherwise,the Domino Journaling task fails to find any databases to archive.

By default Enterprise Vault archives from all Domino Journaling databases thatare in the subfolder and use the STDMailJournaling template. You can use aregistry value to specify other templates to use. See the Setting upDomino ServerArchiving manual for instructions.

The normal Enterprise Vault configuration is to retain the original item until thevault store that contains the archived item has been backed up. Enterprise Vaultthen deletes the original item. The Domino Database Management method mustnot interfere with this Enterprise Vault process, which means that the Purge andCompact method (specified in the Journaling section of the server configurationdocument) is unsuitable, because there is the potential to lose items that have,for some reason, not been archived.

Thus, the Domino Journaling database must have its Database Managementmethod set to one of the following in the Journaling section of the serverconfiguration document:

■ Periodic Rollover or Size Rollover. If you choose either of these options inDomino 6.5.n, Domino does not create the rollover databases in the samedirectory as the initial database. This means that you must manually move

Additional prerequisites for Domino Server archivingPrerequisites for Domino journal archiving

76

rollover databases into the Domino journal directory in order for them to bearchived.

■ None. If you select this method the database will continue to grow, so werecommend that you compact the journal directory each night.

Configure Domino Journaling so that the Journaling database is in a subfolder ofthe server’s Data directory. If Domino Journaling is already configured, you mayneed to move the Journaling database and update the server configurationdocument.

Support for clustered Domino journal databasesEnterprise Vault can archive from Domino journal databases on Domino Serversthat are clustered using Domino application clustering.

To support clustered journal databases, the following requirements must besatisfied:

■ Each Domino Server in the cluster should be independently journaling to alocal database.

■ Mail journaling databases should not be configured to replicate to other Dominoservers in the cluster. This includes both cluster replication and scheduledreplication.

■ Enterprise Vault should be configured to archive from the Domino journaldatabases on each server in the cluster.

Access for Enterprise VaultWhen you configure Enterprise Vault to archive a Domino Journaling locationyou must supply at least one Lotus Notes ID file. Enterprise Vault requires threelevels of access, to domain, server, and journaling location. You can use a differentID file for each level or, for simplicity, a single ID file.

The access levels are as follows:

■ Access to the Domino domain. This is provided by the ID file of a user who isenabled for Lotus Mail and whose account is in the same domain as the server.This account must have read access to the Domino Directory.

■ Access to the Domino server. This is provided by the ID file of a user who hasaccess to the Domino server and its directories.By default, Enterprise Vault will use the same ID file as is used to access thedomain.

■ Access to the Domino Journaling location — This is provided by the ID file ofa user who has Editor, Designer, or Manager access to the journaling databases,

77Additional prerequisites for Domino Server archivingPrerequisites for Domino journal archiving

and also has the Delete Documents permission. If the database is encrypted,this ID file must be the one that was used to encrypt the database.By default, Enterprise Vault will use the same ID file as is used to access theserver. If you do not specify a file for server access, Enterprise Vault will usethe same ID file as is used to access the domain.

To configure access for Enterprise Vault

◆ Create suitable ID files and place them in the Lotus Notes data folder on theEnterprise Vault server that will run the Domino Journaling task. By default,this is C:\Program Files\lotus\notes\data.

Domino Mailing List GroupsTo ensure the expansion of Domino mailing list groups when using EnterpriseVault Compliance Accelerator Journaling Connector, it is important that you setthe Mail Domain field explicitly when configuring Domino mailing list groups.

Client access for Domino journal archivingDomino Server journal archives can be searched using Enterprise Vault browsersearch. These archives cannot be accessed using Archive Explorer.

To use Enterprise Vault browser search, Internet Explorer 6.0 or later, with Javascripting enabled, must be installed on the user’s desktop computer.



If your Enterprise Vault server is already set up, then configure Domino Serverarchiving using the Enterprise Vault Administration Console.

Additional prerequisites for Domino Server archivingWhat next?

78

Additional prerequisites forFile SystemArchiving (FSA)


■ About the prerequisites for FSA

■ Enterprise Vault server requirements

■ About FSA shortcuts

■ The FSA Agent

■ Preparing file servers

■ Client requirements

■ What next?

About the prerequisites for FSAThis chapter describes the additional software and settings required for FileSystem Archiving (FSA).

For full details of all the supported versions of prerequisite products, see theEnterprise Vault Compatibility Charts.

Enterprise Vault server requirementsIf you are implementing FSA but not Exchange Server archiving, you do not needto install Outlook on the Enterprise Vault server. However, if you need to accessfiles that have been archived using a previous version of Enterprise Vault, thenOutlook is still required on the Enterprise Vault server.

8Chapter

An Enterprise Vault Storage service is required on the Enterprise Vault serverthat hosts FSA.

Internet Explorer 6.0 or later is required on the Enterprise Vault server computerthat is to host FSA.

About FSA shortcutsWhen a file is archived, Enterprise Vault can, optionally, leave one of the followingtypes of shortcut in its place:

■ A placeholder shortcut. This is a special file that appears exactly as the originalfile but, when opened, forces Enterprise Vault to fetch the archived file. APlaceholder service needs to be configured to create these shortcuts.

■ An internet (URL) shortcut. This is a .url text file containing a hypertext linkto the archived file. The Placeholder service is not required to create theseshortcuts.

Enterprise Vault cannot create placeholders for certain legacy files. This isparticularly true of files that have extended attributes because they were previouslystored in an HPFS (OS/2) file system.

Placeholder shortcut requirementsEnterprise Vault supports the creation of placeholder shortcuts on the followingfile system types:

■ NTFS.The FSA Agent must be installed on each NTFS file server to provide thePlaceholder service.See “The FSA Agent” on page 81.Each disk on which placeholder shortcuts are required must be an NTFS device;it is not sufficient to use a non-NTFS device that appears on the network asan NTFS device.The Enterprise Vault server uses CIFS when accessing the file system, forexample, to archive files.

■ NetApp Filer with Data ONTAP 7.0 or later.The Placeholder service for NetApp Filer devices runs on the Enterprise Vaultserver computer and accesses the NetApp Filer using CIFS.

■ EMC Celerra.The Placeholder service for EMC Celerra file systems runs on the EnterpriseVault server and accesses the EMC Celerra file system using CIFS.

Additional prerequisites for File System Archiving (FSA)About FSA shortcuts

80

Before installing and configuring FSA, ensure that the target file system that youwant to archive is supported.


The FSA AgentThe FSA Agent must be installed on NTFS file servers on which you wish to doany of the following:

■ Use Placeholder shortcuts

■ Implement File Blocking

■ Gather data for FSA Reporting's reports

For details of the prerequisite versions and service packs of the Windows operatingsystem on the file server, see the Compatibility Charts.

The other prerequisites for the FSA Agent on the file server are as follows:

■ Windows Installer 3.1

■ Internet Explorer 6.0 or later

■ .NET 2.0

Instructions for installing the FSA Agent are included in the instructions forinstalling and configuring FSA on NTFS file servers.

See Settng up File System Archiving.

The FSA Agent can be used in a clustered environment. See Setting up File SystemArchiving for instructions.

Preparing file serversFor placeholder shortcut creation on a Windows platform, the Vault Serviceaccount must have the following access rights:

■ Local administrator rights on the file server

■ Full control on the share that is configured as the target volume

Optionally the Vault Service account also requires browse permissions on thetarget folders, and on any folders in the paths to the target folders. If these optionalpermissions are not set, the administrator is unable to browse in the AdministratorConsole for the target folder, and so must specify the path by typing it in.

The remainder of this section gives instructions on how to prepare NetApp Filerdevices for archiving.

81Additional prerequisites for File System Archiving (FSA)The FSA Agent

For instructions on how to prepare an EMC Celerra device, see Setting up FileSystem Archiving.

Setting the permissions on a NetApp FilerBefore configuring a NetApp Filer for archiving, you must give the Vault Serviceaccount administrative permissions on the file server.

To set the permissions on a NetApp Filer

1 Add the Vault Service account as an Administrator on the NetApp filer byfollowing these steps in the order listed:

■ Log on to a Windows server as a user who already has administrativerights on the NetApp filer.

■ On the Windows desktop, right-click MyComputer and then, on theshortcut menu, click Manage.

■ In Computer Management, select Connect toanothercomputer from theAction menu and then enter the name of the NetApp filer.

2 Expand Local Users andGroups and click Groups.

3 In the right pane, right-clickAdministrators and then, on the shortcut menu,click Add toGroup.

4 Click Add to add the Vault Service account to the list of group members.

Client requirementsThe following client access to archived items is available with FSA:

■ If shortcuts are created in the item’s original location, users can access anarchived item simply by double-clicking the shortcut on the file server.

■ If shortcuts are not created, users can access the archived items in the archivesusing archive search or Archive Explorer.

To use Enterprise Vault browser search or Archive Explorer, Internet Explorer6.0 or later, with Java scripting enabled, must be installed on each user’s desktopcomputer.


Additional prerequisites for File System Archiving (FSA)Client requirements

82



If your Enterprise Vault server is already set up, then configure File SystemArchiving using the Enterprise Vault Administration Console.

83Additional prerequisites for File System Archiving (FSA)What next?

Additional prerequisites for File System Archiving (FSA)What next?

84

Additional prerequisites forSharePoint Server archiving


■ Enterprise Vault server requirements

■ SharePoint Server requirements

■ Installing Enterprise Vault SharePoint components

■ Running the configuration wizard

■ What next?

Enterprise Vault server requirementsInternet Explorer 6.0 or later is required on the computer that hosts the EnterpriseVault Storage Service; typically this would be the Enterprise Vault server computer.

If you have a new Enterprise Vault installation that includes SharePoint Serverarchiving, but not Exchange Server archiving, you do not need to install Outlookon the Enterprise Vault server. However, if you need to access documents thathave been archived using a previous version of Enterprise Vault, then Outlook isstill required on the Enterprise Vault server.

SharePoint Server requirementsThe prerequisite software and settings for the SharePoint Servers to be archivedare as follows:

■ The version of Microsoft SharePoint products must be at least one of thefollowing:

9Chapter

■ Microsoft Windows SharePoint Services 2.0 with Service Pack 1

■ Microsoft SharePoint Portal Server 2003 with Service Pack 1

■ Microsoft Windows SharePoint Services 3.0 (WSS 3.0)

■ Microsoft Office SharePoint Server 2007 (MOSS 2007)

■ Ensure that the Vault Service account is either a member of the SharePointadministration group for the SharePoint virtual servers or has localadministrator privileges on the SharePoint computer.

■ The account under which the Enterprise Vault SharePoint task runs (typicallythe Vault Service account) must have full access to target site collections andtheir content. When archiving from SharePoint 3.0 sites, the account musthave Site Collection Administrator privileges on the target SharePoint sitecollections.

■ SharePoint Servers must be running either Windows Server 2003 with ServicePack 2 or later, or Windows Server 2008 with Service Pack 1 or later. If WindowsServer 2008 with Service Pack 1 is installed, you must also install the followingmandatory hotfix for IIS:http://support.microsoft.com/kb/949516

For full details of all the supported versions of prerequisite products, see theEnterprise Vault Compatibility Charts.

SharePoint security certificatesThe certificate used by the SharePoint virtual server or Web Application musthave the same name as the SharePoint URL. For example, if the Sharepoint URLis https://sharepoint, then the name of the certificate used when issuing acertificate request must be sharepoint.

If the names do not match, Enterprise Vault will not be able to validate theSharePoint site when you try to configure it in the Administration Console.

Support for SharePoint 2003 to 2007 gradual migrationEnterprise Vault supports gradual migration from SharePoint 2003 to SharePoint2007.

When installing Enterprise Vault in an environment that is being graduallyupgraded to SharePoint 2007, and you want sites to be archived while they arepending migration, do the following:

■ Install and configure Enterprise Vault with SharePoint Server 2003.

■ Upgrade SharePoint Server to SharePoint 2007.

Additional prerequisites for SharePoint Server archivingSharePoint Server requirements

86


The following information provides an overview of the steps. Detailed instructionsare given in later sections in this manual.

To install and configure Enterprise Vault with SharePoint 2003

1 Install Enterprise Vault on the Enterprise Vault server.

2 Install the Enterprise Vault SharePoint components on the SharePoint server.

3 Run the Enterprise Vault configuration tool on the SharePoint server.

4 Run the Enterprise Vault Administration Console on the Enterprise Vaultserver and configure SharePoint sites for archiving.

5 Return to the SharePoint Server and install the Enterprise Vault Web Partsand the Archive Version History link.

6 Check that archiving is working correctly.

Upgrade SharePoint Server to SharePoint Server 2007

1 Upgrade SharePoint Server 2003 to 2007.

2 Repeat the installation of the Enterprise Vault SharePoint components onthe SharePoint server.

3 Install the Enterprise Vault Web Parts and the Archive Version History linkagain.

4 Ensure that the account that the SharePoint task runs under is a SiteCollection Administrator on the target SharePoint site collections.

The migration is now complete.

About migrated and unmigrated sitesUnmigrated sites should continue to be archived using the redirected URL.Migrated sites should continue to be archived from the normal URL. You can alsoconfigure newly created SharePoint 2007 sites for archiving.

The following example shows the use of redirection during the gradual migrationprocess.

Before upgrade:

■ SharePoint site URL: http://sharepoint/sites/site1

■ Enterprise Vault target URL: http://sharepoint/sites/site1

■ Enterprise Vault will archive site URL: http://sharepoint/sites/site1

After upgrade, before site is migrated:

■ SharePoint site URL: http://sharepoint/sites/site1 is redirected tohttp://sharepoint:8003/sites/site1

87Additional prerequisites for SharePoint Server archivingSharePoint Server requirements

■ Enterprise Vault target URL is unchanged: http://sharepoint/sites/site1

■ Enterprise Vault will archive unmigrated site at redirected URL:http://sharepoint:8003/sites/site1

After upgrade, when site has been migrated:

■ SharePoint site URL: http://sharepoint/sites/site1 - no redirection

■ Enterprise Vault target URL is still unchanged: http://sharepoint/sites/site1

■ Enterprise Vault will archive migrated site URL: http://sharepoint/sites/site1

Installing Enterprise Vault SharePoint componentsThis section describes how to install the Enterprise Vault SharePoint componentson SharePoint Servers.

To install the Enterprise Vault components on your SharePoint server

1 Log on to the SharePoint Server as an account that has local administratorpermissions.

2 Load the Enterprise Vault media on your SharePoint Server computer.

3 Open the Symantec Enterprise Vault 8.0 folder.

4 Open the Server folder.

5 Double-click SETUP.EXE to start the installation.

6 Work through the installation wizard until you reach theSelectComponentsto Install screen.

7 Select Microsoft SharePoint Components. If you are installing only theEnterprise Vault SharePoint components on this computer, clear the checkboxes for other Enterprise Vault components.

8 Click Next.

9 Work through the remainder of the setup wizard.

Running the configuration wizardAfter the installation wizard has finished, you need to run the configurationwizard.

The SharePoint configuration wizard asks for details of the Vault Service accountand configures the Enterprise Vault Admin service to log on using this account.

Additional prerequisites for SharePoint Server archivingInstalling Enterprise Vault SharePoint components

88

To configure Enterprise Vault components on the SharePoint Server

1 Click Start > Programs > Enterprise Vault > SharePoint Configuration tostart the configuration wizard.

2 Click Next to continue.

3 You are prompted for details of the account that Enterprise Vault serviceswill use. Enter the details of the Vault Service account.

You must use the format domain_name\username when you specify theaccount. Alternatively, use the Browse button to browse for the account.

Enter the password for the account and confirm it.

4 Click Next.

A warning message is displayed if the account you are using does not havesufficient privileges to validate the password (see SharePoint Serverrequirements).

Click Yes to continue.

5 On the last screen of the configuration wizard clickFinish to exit the program.




If your Enterprise Vault server is already set up, then configure SharePoint Serverarchiving using the Enterprise Vault Administration Console.

89Additional prerequisites for SharePoint Server archivingWhat next?

Additional prerequisites for SharePoint Server archivingWhat next?

90

Additional prerequisites forSMTP archiving


■ About the prerequisites for SMTP archiving

■ Microsoft SMTP Server requirements

■ Enterprise Vault server and holding area requirements

■ Client access for SMTP archiving

■ What next?

About the prerequisites for SMTP archivingThis chapter describes the additional prerequisites for SMTP archiving.

As SMTP archiving uses FSA to store the messages, ensure that the FSAprerequisites are also satisfied.

See “About the prerequisites for FSA” on page 79.

Ensure that you use supported versions of prerequisite products.


Microsoft SMTP Server requirementsWhen the gateway mail server receives the message, it should relay the messageon to its destination and send a blind copy to the Microsoft SMTP Server that willbe used for Enterprise Vault SMTP archiving

10Chapter

As Microsoft SMTP Server is included in IIS, install IIS on the Microsoft SMTPServer computer, and configure an SMTP virtual server.

The following software versions are required on the Microsoft SMTP Servercomputer:

■ Windows Server 2003 with Service Pack 2 or later, or Windows Server 2008with Service Pack 1 or later. If Windows Server 2008 with Service Pack 1 isinstalled, you must also install the following mandatory hotfix for IIS:http://support.microsoft.com/kb/949516

■ IIS 6.0 or later

For instructions on how to configure Microsoft SMTP Server, see the Microsoftdocumentation.

As the Microsoft SMTP Server is the destination messaging server for any SMTPmessages to be archived by Enterprise Vault, configure the required domainaddresses in DNS.

All messages sent to SMTP archiving are stored; it does not perform any filtering.For this reason, only SMTP messages should be sent to this server, and notExchange MAPI messages. We recommend that you do not install SMTP archivingon a server that is running Microsoft Exchange Server.

Although you can install the Microsoft SMTP Server on the same computer asEnterprise Vault, it is more common to install it on a separate computer. You mustnot configure this server to relay messages to other messaging servers; it shouldonly receive messages for archiving.

EnterpriseVault server andholdingarea requirementsIf you are implementing SMTP archiving, but not Exchange Server archiving, youdo not need to install Outlook on the Enterprise Vault server.

Internet Explorer 6.0 or later is required on the computer that hosts the EnterpriseVault Storage Service; typically this would be the Enterprise Vault server computer.

As Enterprise Vault uses FSA to archive the messages, ensure that the EnterpriseVault server and the holding area file server satisfy FSA prerequisites.

See “About the prerequisites for FSA” on page 79.

Client access for SMTP archivingUsers can find and retrieve archived SMTP messages using Enterprise Vaultbrowser search or Archive Explorer, which they can run from a browser.

Additional prerequisites for SMTP archivingEnterprise Vault server and holding area requirements

92


To view messages in their original format, users must have Outlook Expressinstalled.

To use Enterprise Vault browser search or Archive Explorer, Internet Explorer6.0 or later, with Java scripting enabled, must be installed on the user’s desktopcomputer.




If your Enterprise Vault server is already set up, then configure SMTP archiving.

93Additional prerequisites for SMTP archivingWhat next?

Additional prerequisites for SMTP archivingWhat next?

94

Prerequisites for astandaloneEnterprise VaultAdministration Console


■ About the prerequisites for a standalone Enterprise Vault AdministrationConsole

■ Additional requirements for Exchange Server archiving

■ What next?

About the prerequisites for a standalone EnterpriseVault Administration Console

If required, the Enterprise Vault Administration Console can be installed on aseparate computer that has the following prerequisite software:

■ One of the following versions of Windows:

■ Windows XP Professional with Service Pack 2 or later.

■ Windows Vista. (For roles-based administration functionality, you need toinstall Service Pack 1).


■ Windows Server 2008 with Service Pack 1 or later.If Windows Server 2008 with Service Pack 1 is installed, you must alsoinstall the following mandatory hotfix for IIS:http://support.microsoft.com/kb/949516

11Chapter


■ MDAC 2.6 or later. A suitable version is installed automatically with bothWindows Server 2003 and Windows Server 2008 (which changes the name ofMDAC to Windows Data Access Component, or Windows DAC).

■ IIS 6.0 or later.

■ Microsoft .NET Framework v 2.0.

■ The Administration Tools Pack is required on Windows XP Professional orWindows Vista.

Additional requirements for Exchange Serverarchiving

If Enterprise Vault is configured to archive Exchange Servers, the followingsoftware is also required on the remote Administration Console computer:

■ Exchange System Manager for Exchange 2000 or Exchange Server 2003. Theversion you will require depends on the operating system running on theEnterprise Vault computer and the version of Exchange being managed.See the Enterprise Vault Compatibility Charts.

■ Outlook 2003.


If you have reviewed all the prerequisite information, then you can install andconfigure the Administration Console.

See “Before you install Enterprise Vault” on page 103.

Prerequisites for a standalone Enterprise Vault Administration ConsoleAdditional requirements for Exchange Server archiving

96

Installing Enterprise Vault

■ Licenses and license keys

■ Installing Enterprise Vault

■ Postinstallation tasks

■ Uninstalling Enterprise Vault

2Section

Licenses and license keys


■ Overview of licensing

■ Obtaining license keys

■ Installing Enterprise Vault license key files

■ Replacing licenses and installing additional licenses

■ What next?

Overview of licensingEnterprise Vault uses the Enterprise Licensing System (ELS). To run the associatedEnterprise Vault services, you must install a license key file that covers theEnterprise Vault features that you want to implement.

The following types of Enterprise Vault license are available:

■ Production license. This license comprises a product base license and anyadditional feature licenses. When the license file is installed, the functionalityof Enterprise Vault depends on the feature licenses that you have purchased.Production licenses generally do not have an expiry date.

■ Trialware license. With this 30 day license, the full functionality of EnterpriseVault is available, but the functionality is time-limited, as defined by the key.When the license expires, the software continues to run in restricted, read-onlymode, which allows archived items to be viewed and retrieved, but no itemscan be archived. Enterprise Vault tasks will not start, and you cannot migratethe contents of personal folder (PST) files to Enterprise Vault.

■ Temporary licenses. Temporary licenses are available for 10 day to 90 dayduration.

12Chapter

When the license expires, the software continues to run in restricted, read-onlymode, which allows archived items to be viewed and retrieved, but no itemscan be archived. Enterprise Vault tasks will not start, and you cannot migratethe contents of personal folder (PST) files to Enterprise Vault.

Obtaining license keysFor information on how to purchase Enterprise Vault licenses, see SymantecEnterprise Vault Licensing Information at the following address on the SymantecWeb site:

http://www.symantec.com/enterprise/products/licensing.jsp?pcid=1018&pvid=322_1

The following Enterprise Vault features, which are mentioned in this guide, requirelicenses:

■ Enterprise Vault core services

■ Exchange Server mailbox archiving

■ Exchange Server journal archiving

■ Domino Server mailbox archiving

■ Domino Server journal archiving

■ Exchange Server public folder archiving

■ Migrating PST files

■ NSF migration wizard

■ SharePoint Server archiving

■ Archive Explorer

■ Vault Cache

■ File System Archiving (FSA)

■ SMTP archiving

■ Policy Manager (EVPM)

■ Custom filters and properties

■ Migrating collected Enterprise Vault files

Note that other Enterprise Vault tools and features that are not mentioned in thisguide may also need licenses.

Licenses and license keysObtaining license keys

100

After you have purchased licenses and received your License Certificate, VoucherDocument, or Upgrade Notification, you need go to the Symantec Licensing Portalat the following address:

https://licensing.symantec.com/acctmgmt/index.jsp

to register and generate your license key file. You will need the serial number onthe license document or notification in order to generate a Symantec LicensingPortal account.

When you have generated a license key file, you download a zipped anddigitally-signed ELS license file. The ELS license file has a unique name and theextension .slf. Each license file can contain the license keys for several EnterpriseVault features.

For information about generating license key files, contact Symantec CustomerCare at the following address:


Installing Enterprise Vault license key filesSave this file in a temporary location on each Enterprise Vault server computer.

The Enterprise Vault installation wizard prompts for the location of your ELSlicense file, and copies the file to the top-level Enterprise Vault folder (typicallyC:\Program Files\Enterprise Vault).

When the Enterprise Vault Admin service is started, it installs the licenses. Duringthis process, it creates a new folder called Installed Licenses under theEnterprise Vault folder, and moves the license file into the folder. As this folderwill contain all the ELS license files successfully installed by the Enterprise VaultAdmin service, it provides a useful backup repository for all your Enterprise Vaultlicenses.

When the Admin service installs a license, it writes a license information reportmessage to the event log.

You can continue Enterprise Vault installation without an ELS license file, butEnterprise Vault will operate in restricted, read-only mode until you obtain andinstall a new ELS license.

Replacing licenses and installing additional licensesFollow the instructions in this section if you have already installed EnterpriseVault and subsequently want to install additional license files or replace existinglicense files.

101Licenses and license keysInstalling Enterprise Vault license key files

https://licensing.symantec.com/acctmgmt/index.jsp

http://www.symantec.com/enterprise/support/index.jsp

To replace a license or install an additional license

1 Place the new .slf license file in the Enterprise Vault folder (typicallyC:\Program Files\Enterprise Vault).

2 Restart the Enterprise Vault Admin service.

3 The service moves any license files it finds in the Enterprise Vault folder tothe Installed Licenses folder under the Enterprise Vault folder.

4 The Admin service writes a license information report message to the eventlog.

5 For a multi-server Enterprise Vault deployment, you must repeat the stepson each Enterprise Vault server.

What next?You can augment your Enterprise Vault functionality by obtaining additionalappropriate licenses and keys from your supplier and then installing the newkeys.

If you have obtained temporary or trialware licenses, the license keys will expireat the end of the license period and Enterprise Vault will revert to running inrestricted, read-only mode. The features will be enabled when you install newproduction license keys.

Licenses and license keysWhat next?

102

Installing Enterprise Vault


■ Upgrading an existing installation

■ Before you install Enterprise Vault

■ Installing Enterprise Vault

■ What next?

Upgrading an existing installationThis chapter describes how to perform a new installation of Enterprise Vault.

To upgrade an existing installation of Enterprise Vault, see theUpgradeInstructions file.

Before you install Enterprise VaultCheck that all the prerequisites for your planned installation have been fulfilled.

Run the Deployment Scanner on the computers on which you plan to installEnterprise Vault.

See “Enterprise Vault Deployment Scanner” on page 32.

Installing Enterprise VaultPerform the following steps to install the required Enterprise Vault components.

13Chapter

To install Enterprise Vault

1 Log in to the Vault Service account to install Enterprise Vault.

2 Load the Enterprise Vault media.

3 Open the Symantec Enterprise Vault 8.0 folder.

4 Double-click the ReadMeFirst file to display the ReadMe text and read itbefore continuing with the installation.

5 Open the Server folder.

6 Double-click SETUP.EXE to start the installation.

7 Install the required Enterprise Vault components for this computer.

The core components for an Enterprise Vault server are as follows:

■ Enterprise Vault Services.Installs all the core Enterprise Vault services. After the installation, youmust configure the services before using them. This is done when you runthe Enterprise Vault configuration wizard.See “About configuring Enterprise Vault” on page 121.

■ Administration Console.Installs the Administration Console. This is a snap-in to the MicrosoftManagement Console (MMC) that enables you to manage Enterprise Vault.This component also installs the Enterprise Vault configuration wizard,and the PST Migrator and NSF Migrator wizards.If you want to install a standalone Administration Console on a remotesystem, then select this component only.

A number of other components can be installed as required, if theirprerequisites are met. Some of these components are listed only if certainsoftware is present:

■ SMTP Archiving Components, Exchange Server Extensions, and MicrosoftSharePoint components are usually installed on computers other thanthe Enterprise Vault server. For details, see the appropriate sectionelsewhere in this manual.

■ Enterprise Vault Operations Manager must be installed on at least oneEnterprise Vault server in your site if you wish to use it to monitor theEnterprise Vault servers in that site.

■ Enterprise Vault Reporting is listed for selection only if Microsoft SQLServer Reporting Services (SSRS) are installed on the computer. EnterpriseVault Reporting can be installed on an Enterprise Vault server, but is moretypically installed on a separate server running SSRS.

Installing Enterprise VaultInstalling Enterprise Vault

104

8 If Lotus Domino is installed, the installation lists the Domino partitions thatare available. The installation installs the Enterprise VaultDomino Gatewaysoftware in each partition that you added to the Selected Partitions list.

To add a partition to the Selected Partitions list:

■ Click the partition name.

■ Click Add.

The installation also removes the Enterprise Vault Domino Gateway softwarefrom each partition that is in the Domino Server Partitions list.

9 At the end of installation, you may be instructed to restart your computer.

What next?You must run the appropriate configuration programs to configure the EnterpriseVault components you have installed.

See “About configuring Enterprise Vault” on page 121.

You must perform the postinstallation tasks described in the next chapter beforeyou start the Enterprise Vault Administration Console.

If the installation was unable to configure the security for the Web accessapplication, you must configure it manually.

105Installing Enterprise VaultWhat next?

Installing Enterprise VaultWhat next?

106

Postinstallation tasks


■ Default security for the Web Access application

■ Customizing security for the Web Access application

■ Customizing security on the client computers

■ What next?

Default security for the Web Access applicationThe Enterprise Vault installation automatically configures access to the WebAccess application using HTTP over TCP port 80.

Both Basic authentication and Integrated Windows authentication are configuredautomatically.

The authentication that is automatically set up affects users when they log in tothe Web Access application, as follows:

■ A user logging in with a browser that supports Integrated WindowsAuthentication, such as Internet Explorer, must supply domain name andusername separately:Username: usernamePassword: passwordDomain: domainThis domain can never be defaulted.An Internet Explorer user with suitably-customized browser settings does notneed to supply logon details manually because the logon is automatic; InternetExplorer automatically uses the details of the account to which the user iscurrently logged on.See “Customizing security on the client computers” on page 112.

14Chapter

■ A user logging in to the Web Access application with a browser that does notsupport Integrated Windows Authentication, must supply both domain nameand username in response to a single username prompt:Username: domain\usernamePassword: passwordIt is possible for you to set up a default domain.See “Customizing authentication” on page 110.

For other Web Access application security options, see Customizing security forthe Web Access application.

Setting up the default authenticationThe installation automatically configures Basic authentication and IntegratedWindows Authentication for the Enterprise Vault Web Access application. Whenyou installed Enterprise Vault, if there was no message saying that setup couldnot set alias security, the authentication described in this section has alreadybeen applied to your system.

The Enterprise Vault Web Access application is always installed on the samecomputer as Internet Information Server (IIS).

To set up the default authentication

1 Log in to the IIS computer as Administrator.

2 ClickStart>Programs>AdministrativeTools>InternetServicesManager.

3 Expand the container for the Enterprise Vault Web Access applicationcomputer.

4 Expand the DefaultWeb Site container.

5 Right-click the EnterpriseVault folder and, on the shortcut menu, clickProperties.

6 Click the Directory Security tab.

7 In the Anonymous access and authentication control section, click Edit.

8 Clear the Anonymous access check box.

9 Select Basic authentication. A security message appears, warning abouttransmitting passwords without encryption. Click Yes to continue.

Note the following:

■ If all clients will be using Internet Explorer, you can clear Basicauthentication. If any clients will be using other Web browsers, makesure that Basic authentication is selected.

Postinstallation tasksDefault security for the Web Access application

108

■ Do not add a domain name inBasicauthentication unless you also createa WebApp.ini file as described in Setting up a default domain in the WebAccess application.

10 Select the IntegratedWindowsAuthentication check box.

11 Click OK.

12 Click the Virtual Directory tab.

13 The path to the Web Access application is now set up.

14 Click Configuration.

15 Click the AppOptions tab.

16 Increase the ASPScript Timeout. A value of 900 seconds is normallysufficient.

This increase in the ASP script timeout is so that users can restore basketscontaining large numbers of items.

17 Click OK.

Customizing security for theWeb Access applicationYou can change the port or protocol that is used to access the Web Accessapplication. For example, you may want connections to the application to be madeusing HTTPS.

See “Customizing the port or protocol for the Web Access application” on page 109.

You can also customize the amount of information that users need to providewhen logging on to the Web Access application.

See “Customizing authentication” on page 110.

Customizing the port or protocol for the Web Access applicationYou can change the port or protocol that is used to access the Web Accessapplication. For example, you may want connections to the application to be madeusing HTTPS.

Note: If you change the port after items have been archived, existing shortcutswill no longer work. Shortcuts in Outlook and Lotus Notes can be updated withthe new protocol or port information using Synchronize mailboxes in theEnterprise Vault Administration Console, but customized shortcuts, FSA shortcutsand SharePoint shortcuts cannot be updated.

109Postinstallation tasksCustomizing security for the Web Access application

Before you change the Web Access application port or protocol in Enterprise Vault,you must first make the required changes to the default Web site in IIS for eachserver in the Enterprise Vault site. Bear in mind that changing the protocol orport for the default Web site will affect all virtual directories in the Web site,including the FSAReporting virtual directory.

When you have made the necessary changes in IIS, change the Web Accessapplication port or protocol settings on the General tab of the Site properties inthe Administration Console.

If the Enterprise Vault site uses FSA Reporting, you must then perform someadditional steps. Otherwise the status of FSA Reporting is shown as Off in theAdministration Console. Perform the following steps on each Enterprise Vaultserver and on each file server in the Site.

Additional steps for FSA Reporting after you change the port or protocol

1 Log on as the FSA Reporting user. The FSA Reporting user is the Windowsuser account that you specified for FSA Reporting to use when you ran theFSA Reporting Configuration wizard.

2 Open Internet Explorer and select Tools > Internet Options.

3 If you chose to use an SSL port, click the Advanced tab and under Securitymake sure that Check for server certificate revocation is not selected.

4 Click the Security tab and select the Local intranet zone. Then click CustomLevel to display the Security Settings. Under UserAuthentication, makesure that Prompt for user name and password is not selected.

5 Repeat steps 1 to 4 on each Enterprise Vault server and on each file serverin the Site.

Customizing authenticationThe standard security for the Web Access application means that users mustprovide domain name, user name, and password whenever they start the WebAccess application.

This section describes various levels of automatic authentication that you can setup for the users. If none of these methods is acceptable to you, the defaultauthentication enables users to log on by supplying domain, username, andpassword.

Using a default domain with basic authenticationWith only Basic authentication configured, users must provide a domain namewhen logging on to the Web Access application. For example, a user in domain

Postinstallation tasksCustomizing security for the Web Access application

110

myDomain with a username of Rogers must specify myDomain\Rogers whenlogging on to the Web Access application.

It is possible for IIS and Enterprise Vault to use a default domain for Basicauthentication. In this case, users in the default domain do not need to specify adomain name when starting the Web Access application. Users in other domainsmust still specify a domain name.

Setting up a default domain in IIS

You can set up IIS so that it uses a default domain for Basic authentication. Howyou do this depends on the version of IIS that you have installed.

Note that the default domain does not work unless you also define it for the WebAccess application.

See “Setting up a default domain in the Web Access application” on page 112.

To set up a default domain in IIS 6.0

1 Start Internet Information Services (IIS) Manager.

2 Expand the Web Sites container for the Enterprise Vault Web Accessapplication computer.

3 Expand the DefaultWeb Site container.

4 Right-click the EnterpriseVault folder, and then click Properties.

5 In the EnterpriseVault Properties dialog box, click the Directory Securitytab.

6 In the Authentication and access control section, click Edit.

7 In the Authentication Methods dialog box, uncheckEnableanonymousaccess.

8 Check Basic authentication.

9 To set the default domain, do the following:

■ Click Select.

■ Enter the name of the domain that contains the majority of user accountsthat will be using the Web Access application.

■ Click OK.If there is a prompt about inheritance overrides, click SelectAll and thenOK.

To set up a default domain in IIS 7.0

1 Start Internet Information Services (IIS) Manager.

2 Expand the Sites container for the Enterprise Vault Web Access applicationcomputer.

111Postinstallation tasksCustomizing security for the Web Access application

3 Click the EnterpriseVault folder.

4 Double-click Authentication in the IIS area at the right.

5 Ensure thatAnonymousAuthentication is disabled andBasicAuthenticationis enabled.

6 To set the default domain, do the following:

■ Right-click BasicAuthentication, and then click Edit.

■ Enter the name of the domain that contains the majority of the useraccounts that will be using the Web Access application.

■ Click OK.

Setting up a default domain in the Web Access application

Note that the default domain does not work unless you also define it in IIS.

See “Setting up a default domain in IIS” on page 111.

To set up theWebAccess application so that it uses the same default authorizationdomain as you have set up in IIS

1 Use a text editor to create an initialization file called WebApp.ini, containingthe following line:

Domain=DomainName

where DomainName is the name of the domain that you have specified in IISfor Basic authentication. Note that entries in this file are case-sensitive.

For example, to use a domain called myDomain, the line to use is as follows:

Domain=myDomain

2 Save the file in the Enterprise Vault program folder, normally C:\Program

Files\Enterprise Vault, on the computer that runs the Web Accessapplication.

Customizing security on the client computersOn user computers, you can configure Internet Explorer so that users areautomatically logged on to the Web Access application, without receiving a logonprompt. Essentially, you must configure Internet Explorer so that it trusts theWeb Access application computer.

For this to work, you must also be using the Integrated Windows Authentication,as described in Setting up the default authentication.

Postinstallation tasksCustomizing security on the client computers

112

To make Internet Explorer log on automatically, you may need to modify theInternet Explorer Internet Options on each client computer. The settings aresaved in the Windows registry, so you can save them for rollout to many clientcomputers.

There are many possible ways for you to configure Internet Explorer security,some of which may not be acceptable to you. The following methods are describedhere:

■ Using the proxy bypass list

■ Explicitly naming the Web Access application computer

See the Internet Explorer help if you need more information on configuringbrowser security.

Using the proxy bypass listNote that you must be using a proxy server before you can use the proxy bypasslist.

To configure Internet Explorer to use the proxy bypass list

1 In Internet Explorer, click Tools and then Internet Options.

2 Click the Security tab and then click the Local Intranet zone.

3 Click Sites and then select Include all sites that bypass the proxy server.

4 Click OK.

5 Click CustomLevel.

6 Under Logon, select Automatic logon only in Intranet zone.

7 Click OK.

8 Click the Connections tab, and click LANSettings.

9 Check that a proxy server is being used.

10 If either of the Automatic configuration settings is selected, you must makesure that the Web Access application computer is in the automaticconfiguration exceptions list.

11 If neither of the Automatic configuration settings is selected, click Use aproxy server and then Advanced. If there is no existing entry that includesthe Web Access application computer, specify the Web Access applicationcomputer in the Exceptions list.

113Postinstallation tasksCustomizing security on the client computers

Explicitly naming the Web Access application computerThis section describes how to add the Web Access application computer to theInternet Explorer local intranet zone. Once you have set up the security, userswill not need to log on to search archives or to view or restore archived items.

It is possible to configure users’ desktops so that they automatically add the WebAccess application computer to the Internet Explorer local intranet zone. See theAdministrator’s Guide more details.

To configure Internet Explorer to trust the Web Access application computer

1 In Internet Explorer, click Tools and then click Internet Options.

2 Click the Security tab and then click the Local Intranet zone.

3 Click CustomLevel.

4 Under Logon, select Automatic logon only in Intranet zone and then clickOK.

5 Click Sites and then Advanced.

6 In the Add thisWeb site to the zone box, enter the fully-qualified domainname of the Web Access application computer and then click Add. Forexample, vault.company.com.

7 In the Add thisWeb site to the zone box, enter the computer name, withoutthe DNS domain, of the Web Access application computer and then clickAdd.

8 Click OK.

Enabling remote access to the Web Access application computerYou may need to grant users of the Enterprise Vault Web Access application accessto the IIS computer, using the local IIS computer accounts database, not thedomain accounts database.

Note: If the IIS computer is a domain controller, there is no local accounts database,only a domain accounts database. If you continue with these instructions whenthe IIS computer is a domain controller, you will make changes to the securityaccess of the domain accounts database. This will affect all computers within thedomain, not just the IIS computer. If you do not want to affect the whole domain,you should ensure that you run IIS on a non-domain controller.

To grant access

1 Click Start > Programs > Administrative Tools > Local Security Policy.

2 In the Local Security Policy window, expand the Local Policies container.

Postinstallation tasksCustomizing security on the client computers

114

3 Click UserRightsAssignment.

4 Set up Basic authentication access by following the steps below in the orderlisted:

■ In the right-hand pane, right-click Allow log on locally and then, on theshortcut menu, click Properties.

■ Check that the Users group appears in the Local Security Setting list.

5 Set up Integrated Windows Authentication access by following the stepsbelow in the order listed:

■ With UserRightsAssignment still selected in the left pane of the LocalSecurity Policy window, right-click Access this computer from thenetwork in the right pane and then, on the shortcut menu, clickProperties.

■ Check that the Users group appears in the Local Security Setting list.If you do not want to add the Users group, see the other options below.

By default, the Users group includes Domain Users. If the Users group doesnot include Domain Users, or if some Web Access application users are in adifferent domain, you must do one of the following:

■ Add the Web Access application users to the Users group.

■ Add the Web Access application users to some other group and then grantthe access right to that group.

■ Grant the access right to each Web Access application user’s account.

The Enterprise Vault Web Access application is now set up and ready to beused by users in the same domain as IIS.

What next?You have now completed the post-installation tasks.

Ensure that you have the required Enterprise Vault licenses installed.

If you have not yet run the Enterprise Vault configuration wizard, you can run itnow.

If you have already run the Enterprise Vault configuration wizard, then start toset up your Enterprise Vault server using the Administration Console.

115Postinstallation tasksWhat next?

Postinstallation tasksWhat next?

116

Uninstalling EnterpriseVault


■ Uninstalling Enterprise Vault

■ Reinstalling Enterprise Vault

Uninstalling Enterprise VaultNote the following before you proceed:

■ If you uninstall Enterprise Vault on the primary Enterprise Vault server thatis associated with the Directory database, the Directory database will also beremoved.

■ If you uninstall Enterprise Vault on a secondary Enterprise Vault server, theDirectory database will not be removed.

■ If you are uninstalling Enterprise Vault on a secondary Enterprise Vault server,and you want to preserve the Directory database, first backup the databaseand then close down the primary Enterprise Vault server computer, beforeuninstalling Enterprise Vault on the secondary Enterprise Vault servercomputer.

■ If an Enterprise Vault service has data associated with it, you cannot use theEnterprise Vault Administration Console to remove that service.

15Chapter

To uninstall Enterprise Vault

1 From the Windows Control Panel, select Add/Remove Programs.

2 From the list of programs, select Enterprise Vault, and then clickAdd/Remove.

You are asked to confirm that you want to remove Enterprise Vault from yoursystem.

3 Click Yes.

The uninstaller stops Enterprise Vault services that are still running. It thenremoves all Enterprise Vault Services and Enterprise Vault software fromyour system. The uninstaller does not delete data.

Reinstalling Enterprise VaultIf you want to reinstall Enterprise Vault on the computer, perform the followingsteps.

To reinstall Enterprise Vault

1 Re-run the Setup program. You do not have to select the same installationfolder for Enterprise Vault that you previously selected.

2 Run the Enterprise Vault configuration wizard. When this program promptsyou for a Directory Computer, give the same name as for the previousinstallation. The configuration wizard automatically creates the same servicesas the computer had before.

If you do not want to reinstall Enterprise Vault, delete the Enterprise Vaultdata manually.

Uninstalling Enterprise VaultReinstalling Enterprise Vault

118

Configuring Enterprise Vault

■ About configuring Enterprise Vault

■ Running the Enterprise Vault configuration wizard

■ Running the Getting Started wizard

■ Configuring Enterprise Vault Operations Manager

■ Configuring Enterprise Vault Reporting

3Section

About configuringEnterprise Vault


■ About configuring Enterprise Vault

About configuring Enterprise VaultOn completion of the Enterprise Vault installation program, you may need to runone or more configuration programs, depending on which Enterprise Vaultcomponents you installed.

If you have upgraded, follow the instructions in Upgrading to Enterprise Vault8.0.

For a new Enterprise Vault installation, do as follows:

■ If you installed the Enterprise Vault Services component, run the EnterpriseVault configuration wizard before running any other configuration programs.See “When to run the configuration wizard” on page 123.

■ If you installed the Enterprise Vault Operations Manager component, configureEnterprise Vault Operations Manager.See “When to run the Operations Manager Configuration utility” on page 139.

■ If you installed the Enterprise Vault Reporting component, configure EnterpriseVault Reporting.See “When to run the Reporting Configuration utility” on page 143.

■ If you installed only the Administration Console component, you do not needto run any configuration program.

■ If you installed components for specific archiving implementations such asExchange, Domino, SharePoint or SMTP, you may need to perform separate

16Chapter

configuration steps for those components. See the relevant section elsewherein this manual.

About configuring Enterprise VaultAbout configuring Enterprise Vault

122

Running the EnterpriseVault configuration wizard


■ When to run the configuration wizard

■ What the configuration wizard does

■ Running the configuration wizard

■ Troubleshooting configuration of the Monitoring database

When to run the configuration wizardRun the configuration wizard either immediately after installation (after restartingyour computer if prompted), or after performing the postinstallation tasks forthe Web access application, described in the previous chapter.

Note the following:

■ If you run the configuration wizard immediately after the installation,remember that there are some additional tasks that you need to do beforeusers can use Enterprise Vault. See the previous chapter for details.

■ If you exit from the configuration wizard before configuration is complete,you can run the configuration wizard again and have the option to delete theDirectory database. Once you have successfully completed the configurationwizard, you cannot run it again on the same computer.

What the configuration wizard doesThe configuration wizard lets you do the following:

17Chapter

■ Select which SQL Server you want to use for the Enterprise Vault Directorydatabase

■ Create the Enterprise Vault Directory database

■ Create the Enterprise Vault Monitoring database

■ Create an Enterprise Vault site

■ Add the computer to the site

■ Select the Enterprise Vault services you want to run on the computer

■ Choose the storage areas to use for Enterprise Vault data

Some tasks, such as adding a service or assigning storage areas for the data, canalso be done using the Enterprise Vault Administration Console. However, thefollowing tasks can only be done using the configuration wizard:

■ Creating a new Enterprise Vault Directory

■ Creating a new Enterprise Vault site

■ Adding a new Enterprise Vault server

Running the configuration wizard

Note: These instructions apply to a non-clustered environment. If you areconfiguring Enterprise Vault in a Veritas Cluster Server or Microsoft Server Clusterenvironment, see instead the appropriate clustering section in this manual.

You may be starting the configuration wizard after restarting your computer orafter completing the Installation Program.

Follow the instructions below to run the configuration wizard on the firstEnterprise Vault server in your site. When you are using the configuration wizardto configure Enterprise Vault on subsequent computers, refer to the online Helpif you are unsure about how to proceed.

If during the running of the configuration wizard you receive an error related tothe configuring of the Enterprise Vault Monitoring database, complete theconfiguration wizard and then refer to the troubleshooting information for theMonitoring database.

See “Troubleshooting configuration of the Monitoring database” on page 128.

Running the Enterprise Vault configuration wizardRunning the configuration wizard

124

To run the configuration wizard

1 ClickStart>Programs>EnterpriseVault>EnterpriseVaultConfiguration.

The Configuration wizard starts. The first screen asks whether you want tocreate a new Enterprise Vault Directory database.

2 Click Yes and then Next.

The wizard asks you to select the language you want Enterprise Vault to usewhen populating the default settings in the Administration Console.

3 Select the required language and then Next.

The wizard asks for details of an account for Enterprise Vault services to use.

4 Enter the details of the Vault Service account that you created earlier.

See “Creating the Vault Service account” on page 37.

You must use the format domain_name\username when you specify theaccount. Alternatively, browse for the Vault Service account.

Enter the password for the Vault Service account and confirm it.

5 Click Next.

A warning message is displayed if the account you are using does not havesufficient privileges to validate the password to the Vault Service account.Click Yes to continue.

A message tells you that the Vault Service account has been added to the localAdministrators group. Click OK to close the message.

A second message notifies you that the account will be given the advanceduser rights, LogOnAs a Service and Act as Part of theOperating System,Debug programs, and Replace a process-level token. Click OK to close themessage.

The configuration wizard creates the Directory service and then the nextscreen asks for the location of the SQL Server that you want to use for theDirectory database.

6 Enter the location of the SQL Server that you want to use. You can specify aSQL Server instance if required.

7 Click Next.

The wizard shows the default locations for the Directory database files andtransaction log.

8 Change the locations if necessary.

If you have specified that SQL Server is on a remote computer, the paths forthe data file and transaction log file must be valid on that remote computer.

125Running the Enterprise Vault configuration wizardRunning the configuration wizard

9 Click Next.

The wizard creates the Directory database. The next screen asks for thelocation of the SQL Server that you want to use for the Monitoring database.

10 Enter the location of the SQL Server that you want to use. You can specify aSQL Server instance if required.

Leave StartMonitoring immediately selected to begin monitoring as soonas the configuration is complete on this Enterprise Vault server.

11 Click Next.

The next screen shows default locations on the SQL server for the Monitoringdatabase files and transaction log.

12 Change the locations if necessary.

If you have specified that SQL Server is on a remote computer, the paths forthe data file and transaction log file must be valid on that remote computer.

Do not specify paths that are on the root of a file system, such as C: or C:\.

13 Click Next.

The wizard creates the Monitoring database.

The next screen asks for details of the new Enterprise Vault site.

14 Enter a name and description for the new Enterprise Vault site.

15 Click Next.

The next screen asks for a DNS alias for current computer.

The value you enter must be an unqualified DNS alias for this computer, forexample, evserver1. A fully-qualified DNS name (for example,evserver1.mycompany.local) is not permitted.

If this is the first computer added to the site, the DNS alias entered willautomatically be used as the vault site alias.

See “Creating Enterprise Vault DNS aliases” on page 40.

16 Enter a DNS alias for the current computer and click Next.

17 Click Next to add the computer to the Enterprise Vault site.

An information screen lists software that is installed on your computer. Basedon this list, the wizard automatically selects Enterprise Vault services to addto your computer.

18 Click Next. The list shows the services that will be added to your computer.

19 Check the list of services. If there are services in the that you do not need,you can remove them now.

Running the Enterprise Vault configuration wizardRunning the configuration wizard

126

20 To add additional services to this computer, click Add and select the servicethat you want to add.

21 Once you have the correct list of services, click Properties for each serviceand review the settings. Change the settings as necessary.

22 When you have finished reviewing the services’ properties, click Next.

The default storage locations for the Shopping service and the Indexingservice are displayed.

23 Check that the storage locations are suitable. ClickBack if you want to changethem.

Note the following points:

■ You must ensure that the default index storage location is on an accessibledevice and that the Vault Service account can write to it.

■ With Exchange Server archiving, Enterprise Vault adds information aboutthe index storage location to the Directory database when you enablemailboxes. You cannot easily change the index storage location formailboxes after you have enabled them. However, you can use theAdministration Console to change the index storage location, or addfurther locations, before you enable any mailboxes.

24 If you do not want to change the default locations for the Indexing andShopping services, click Next.

If you do want to change the locations, click Back, select the service that youwant to modify and click Properties to change the location.

The next screen asks for details of the service mailbox.

25 An information page is displayed.

Click Next to continue and start the services.

26 The services that you have added are listed.

Click Next to start the Enterprise Vault services. If any of the service doesnot start immediately, continue to click Next until they have all started.

The services will not start unless you have installed the appropriate licensekeys.

If you do not have the license keys yet, you can continue configuringEnterprise Vault using the Administration Console, but you cannot run theservices until the license keys have been installed.

27 The final screen of the wizard gives you the following options:

127Running the Enterprise Vault configuration wizardRunning the configuration wizard

Run the Enterprise Vault Getting Started Wizard. Choose this option toset up archiving as quickly as possible. The wizard provides both expressand custom options for maximum flexibility.

■

■ Run the Enterprise Vault Administration Console. Choose this option ifyou are already familiar with the Administration Console and familiarwith setting up archiving.

■ Just close the wizard. Choose this option to close the Configuration Wizard.You can then use the Enterprise Vault Start menu options to run theEnterprise Vault Getting Started Wizard or the Administration Console.

28 Click Finish to exit from the configuration wizard.

Note:Remember that you can run the configuration wizard successfully only onceon a computer. If you exit the configuration wizard after successfully configuringEnterprise Vault, you cannot run the wizard again. To do any further setup ormanagement of the Enterprise Vault components, other than that related toEnterprise Vault Operations Manager or Enterprise Vault Reporting, you mustuse the Administration Console.

Troubleshooting configuration of the Monitoringdatabase

If while running the configuration wizard you receive errors indicating that theconfiguration of the Enterprise Vault Monitoring database has failed, completethe configuration wizard and then run the Monitoring Configuration utility toconfigure the Monitoring database and the Monitoring agents manually.

For information on how to do this, see the following TechNote on the EnterpriseVault Support Web site:


The TechNote also describes how to troubleshoot issues with Monitoring agents.

Running the Enterprise Vault configuration wizardTroubleshooting configuration of the Monitoring database

128


Running theGetting Startedwizard


■ When to run the Getting Started wizard

■ What the Getting Started wizard does

■ Preparing to run the Getting Started wizard

■ Express mode or Custom mode?

■ What next?

When to run the Getting Started wizardYou can run the Getting Started wizard immediately after you complete theConfiguration wizard as part of a new installation of Enterprise Vault.

If you exit from the Getting Started wizard before the end of the wizard, you canrun the wizard again. When you have successfully completed the Getting Startedwizard you cannot run it again on the same computer. You can run the GettingStarted wizard on other computers in the site.

To run the Getting Started wizard:

◆ Do one of the following:

■ Select the Run the Enterprise Vault Getting StartedWizard option onthe last page of the Configuration wizard.

■ On the Windows Start menu, click All Programs > Enterprise Vault >Enterprise Vault Getting StartedWizard.

18Chapter

What the Getting Started wizard doesThe Enterprise Vault Getting Started Wizard enables you to configure archivingas quickly as possible.

The wizard helps you do the following, as appropriate:

■ Create archiving policies for Exchange Server, Domino, and File SystemArchiving

■ Set up storage locations

■ Create retention categories

You can choose to run sections of the wizard in express mode or in custom mode,as follows:

■ In express mode, the wizard does not ask many questions. Instead, it appliesas many default settings as possible. Later, you can use the AdministrationConsole to make changes to the settings, if required.

■ In custom mode, the wizard you have the flexibility to change the defaultsettings.

Note: In Express mode the Getting Started wizard asks you to specify a local disk.The wizard then configures Enterprise Vault to use that disk for all storage. Ifyou want to configure remote storage or to configure a different local storageconfiguration then you must select custom mode for storage configuration.

Preparing to run the Getting Started wizardThe Getting Started wizard checks the Enterprise Vault license keys to determinewhich options to present to you. Before you run the Getting Started wizard youmust have installed your license keys.

See “Overview of licensing” on page 99.

You can run the Enterprise Vault Deployment Scanner to create a report thatshows whether the Enterprise Vault prerequisite configuration is correct.

See theDeploymentScannermanual in the Documentation folder of the EnterpriseVault media.

To run the Deployment Scanner:

◆ On the Windows Start menu, click All Programs > Enterprise Vault >Deployment Scanner.

Running the Getting Started wizardWhat the Getting Started wizard does

130

Express mode or Custom mode?The Getting Started wizard enables you to select Express mode or Custom modeto configure each of the following:

■ Storage configuration

■ Policy definition

■ Exchange target configuration

■ Domino target configuration

■ File target configuration

This section helps you to decide whether to use Express mode or Custom modefor each configuration section.

■ In Express mode, the wizard does not ask many questions. Instead, the wizardapplies default settings so that you can configure Enterprise Vault as quicklyas possible. Later, you can use the Administration Console to make changesto the settings, if required.

■ Custom mode enables you to specify settings in detail.

If the Express mode configuration is close to what you need you can use Expressmode and then make small changes in the Administration Console.

In Custom mode you can make any changes you require but it can to a long timeto go through all options. You may prefer to accept the default options and thenmake changes in the Administration Console.

There is a planning sheet that lists the Getting Started wizard's Express-modechoices. You can use the sheet to record your own requirements and then lateruse the Administration Console to make the required changes.

See “Planning for the Getting Started Wizard” on page 257.

Storage configurationIn Express mode the Getting Started wizard configures all storage locally on theserver.

See “About setting up storage for archives” on page 159.

The wizard sets up the following:

■ A vault store group

■ A vault store

■ A vault store partition

131Running the Getting Started wizardExpress mode or Custom mode?

■ The Enterprise Vault server cache

■ Indexes

■ Shopping baskets (if a Shopping service is present)

Select the Custom option for storage configuration if you want to do either of thefollowing:

■ Configure remote storage.

■ Use a different SQL Server for vault stores from the one that you specified inthe configuration program.

■ Configure the structure of the vault store group's fingerprint database.

Storage configuration information youmust supply in ExpressmodeFor the Express storage configuration you must specify which volume to use tostore Enterprise Vault data. This information is used when Enterprise Vault createsthe following storage locations:

■ Cache location: <volume>\EVStorage\Cache

■ Index locations: <volume>\EVStorage\Index

■ Shopping location: <volume>\EVStorage\Cache\Shopping

Note:As anti-virus software can potentially change data, it is important to excludethe cache and index locations in your virus checking application.

Automatic configuration in Express modeThis section lists the settings that the Getting Started wizard automaticallyconfigures when you choose Express mode for Storage Configuration.

Table 18-1 shows the Vault Store Group settings that the wizard creates in Expressmode.

Table 18-1 Vault Store Group settings in Express mode

DescriptionItem

"Express Vault Store Group". If the namealready exists a number is appended to makethe name unique. For example, "ExpressVault Store Group_1".

Name

Running the Getting Started wizardExpress mode or Custom mode?

132

Table 18-1 Vault Store Group settings in Express mode (continued)

DescriptionItem

The same as the Vault Store Group name.Description

The same SQL Server as was specified in theConfiguration program for the EnterpriseVault Directory database.

SQL Server name for fingerprint database

The default database folder for theEnterprise Vault Directory computer.

Folder for all fingerprint database filegroups.

The default log folder for the EnterpriseVault Directory computer.

Folder for fingerprint database log

Table 18-2 shows the Vault Store settings that the wizard creates in Express mode.

Table 18-2 Vault Store settings in Express mode

DescriptionItem

"Express Vault Store". If the name alreadyexists a number is appended to make thename unique. For example, "Express VaultStore_1".

Name

The same as the vault store name.Description


SQL Server

Set to 'Share within Vault Store'.Sharing

Set to 'After backup (immediate forJournaling)'.

Remove safety copy

Set to 'Use Site setting'.Limit archive usage

Table 18-3 shows the Vault Store partition settings that the wizard creates inExpress mode.


Table 18-3 Vault Store partition settings in Express mode

DescriptionItem

"Express Vault Store Ptn1". If the namealready exists a number is appended to makethe name unique. For example, "ExpressVault Ptn2".

Name

Partition of Vault Store [Vault_store_name]Description

Open.State

NTFS volume.Device type

Destination device does not perform datadeduplication.

Data deduplication

Destination device does not perform datacompression.

Data compression

Not enabled.Partition rollover

Use the archive attribute.How to check that items have been secured

Not enabled.Use collection files

Not enabled.Migrate files

Policy definitionA policy defines which documents are to be archived and how they are to bearchived.

Enterprise Vault creates policies automatically. The Getting Started wizard usesthe default Enterprise Vault policies. The default policies in Express mode andCustom mode are the same.

You can use the Administration Console to modify all policy settings later, ifrequired.

Exchange target configurationIf you choose to configure Exchange Server targets, the Getting Started wizardsearches the network for instances of Exchange Server. You can then select theExchange Server computers for which you want to configure archiving.

For the Exchange Server that you select you must do the following:

■ Specify whether to configure mailbox archiving or journal archiving, or both.


134

■ If you choose to configure mailbox archiving you must specify a system mailboxon that server that Enterprise Vault can use to log on.

■ If you choose to configure journal archiving you must specify which journalmailboxes to archive and specify the journal archive to use for each mailbox.The wizard enables you to create new archives, if required.

Table 18-4 shows the Exchange provisioning group settings that the wizard createsin Express mode.

Table 18-4 Exchange provisioning group settings in Express mode

DescriptionItem

'Express Provisioning Group'. If you haveselected 'Storage configuration' theprovisioning group uses a new vault storethat the wizard creates. If you have notselected 'Storage configuration', the wizarduses an existing vault store.

Provisioning group name

'Whole Exchange Server organization'Provisioning group scope

'Default Exchange Desktop Policy'Desktop policy

'Default Exchange Mailbox Policy'Mailbox policy

'Default Exchange PST migration Policy'PST migration policy

'Default Retention Category'Default retention category

The Indexing service on the currentEnterprise Vault server, if any. If there is noIndexing service then the wizard selects anIndexing service on another server.

Indexing service

Domino target configurationIf you choose to configure Domino targets, the Getting Started wizard searchesthe network for Domino servers. You can then select the Domino servers for whichyou want to configure archiving. For each Domino server you can specify whetherto configure mailbox archiving or journal archiving, or both. The Getting Startedwizard then configures archiving appropriately.

For the Express Domino configuration you must provide the following:

■ ID file name. Enterprise Vault uses the ID file as the default ID file for allEnterprise Vault operations that require an ID file. The wizard lists Domino


ID files that are in the Lotus Notes data folder, which by default is C:\ProgramFiles\lotus\notes\data.You must place the ID file that you want to use in the data folder so that youcan select it in the wizard.

■ ID file password. The password for the ID file.

■ The names of the Domino servers for which you want to configure mailboxarchiving.

■ The names of the Domino servers for which you want to configure journalarchiving.

■ The retention category to use when archiving from a Domino target.

Table 18-5 shows the Domino provisioning group settings that the wizard createsin Express mode.

Table 18-5 Domino provisioning group settings in Express mode

DescriptionItem

'Express Provisioning Group'. If the namealready exists a number is appended to makethe name unique. For example, "ExpressProvisioning Group_1".

Provisioning group name

If you have selected 'Storage configuration'the provisioning group uses a new vaultstore that the wizard creates. If you have notselected 'Storage configuration', the wizardselects an existing vault store.

Vault store

'All Organizational Units'Provisioning group scope

'Default Domino Desktop Policy' If this policyis not available the wizard selects the firstpolicy that is available, alphabetically.

Desktop policy

'Default Domino Mailbox Policy'. If thispolicy is not available the wizard selects thefirst policy that is available, alphabetically.

Mailbox policy

'Default Retention Category'Default retention category

The Indexing service on the currentEnterprise Vault server, if any. If there is noIndexing service then an Indexing serviceon another server.

Indexing service


136

Table 18-6 Vault Store settings in Express mode

DescriptionItem

The Vault store that was created in thecurrent run of the wizard, if any. If thewizard did not create a vault store the firstvault store with an open partition is used.

Name

The same description as for the vault storename.

Description


SQL Server

Set to 'Share within Vault Store'.Sharing

Set to 'After backup (immediate forJournaling)'.

Remove safety copy

Set to 'Use Site setting'.Limit archive usage

File target configurationThe Getting Started wizard enables you to configure archiving for the file serversthat you specify.

You can install the Enterprise Vault FSA Agent on each file server. You need toinstall the FSA agent if you require placeholder shortcuts, File Blocking, or needto obtain data for FSA Reporting.

What next?When you have completed the Getting Started wizard you can use theAdministration Console to make any changes to the configuration that you mayrequire.

137Running the Getting Started wizardWhat next?

Running the Getting Started wizardWhat next?

138

Configuring EnterpriseVault Operations Manager


■ When to run the Operations Manager Configuration utility

■ Running the Operations Manager Configuration utility

■ Accessing Operations Manager

■ Troubleshooting Operations Manager

When to run the Operations Manager Configurationutility

Run the Enterprise Vault Operations Manager Configuration utility after installingOperations Manager on a server, but only after the server has been successfullyconfigured using the Enterprise Vault configuration wizard.

You can rerun the Operations Manager Configuration utility if the configurationfails for some reason and you need to repeat it. You can also rerun the utility ifyou need to change the details of the monitoring user account. In this case, besure to rerun the utility on all servers on which Operations Manager is installed.

Running theOperationsManagerConfigurationutilityRun the Operations Manager Configuration utility to configure Operations Managerfor the first time, or to change the details of the monitoring user account.

19Chapter

To run the Operations Manager Configuration utility

1 Ensure you are logged in under the Vault Service account.

2 Click Start > Programs > Enterprise Vault >OperationsManagerConfiguration.

The Operations Manager Configuration utility starts.

3 Provide the details of the monitoring user account you have created forOperations Manager to run under.

Enter the Active Directory domain, the user name, and the password for themonitoring user account.

4 Click Configure to run the utility.

The utility gives the account the required permissions, and adds the user tothe EnterpriseVaultDirectory database as the monitoring user.

5 When the utility has finished, click OK on the displayed dialog to quit theutility.

Note: If you ran this utility to update the details of the monitoring user account,remember to rerun the utility on any other Enterprise Vault server with OperationsManager installed.

You can now try accessing Operations Manager to confirm it has been successfullyinstalled and configured.

Accessing Operations ManagerIf you have installed the Enterprise Vault Operations Manager Web applicationon at least one Enterprise Vault server in an Enterprise Vault site, you can use itto monitor the site’s Enterprise Vault servers.

After configuring Operations Manager, try accessing it to confirm the configurationhas been successful.

Configuring Enterprise Vault Operations ManagerAccessing Operations Manager

140

To access Enterprise Vault Operations Manager

1 Enter the following URL in Internet Explorer 6.0 or later:

http://host_ipaddress/MonitoringWebApp/default.aspx

wherehost_ipaddress is the IP address of the computer hosting an EnterpriseVault server on which the Enterprise Vault Operations Manager Webapplication feature is installed.

Alternatively, if you are accessing Operations Manager from the computeron which it is installed, you can use the following URL, which does not requirethe next step:

http://localhost/MonitoringWebApp/default.aspx

2 In the Connect to <IPAddress> dialog, enter the user name and passwordof an account in the host computer’s domain. Then click OK.

Note: Any user other than the Vault Service account must be assigned to asuitable role to access Operations Manager. Users can view only the tabs andtables in Operations Manager that are applicable to the role to which theyare assigned.

See "Roles-based administration" in the Administrator's Guide.

If the user credentials are valid, Operations Manager displays its Site Summarypage.

Troubleshooting Operations ManagerIf you see an error page when attempting to access Enterprise Vault OperationsManager, ensure that you have done the following and then try to access theapplication again:

■ Confirm that you have satisfied all the pre-installation steps described in Aboutadditional requirements for Operations Manager.

■ Check that IIS 6 is not locked down.

■ Ensure that Integrated Windows Authentication is enabled for the default Website in IIS 6, then restart IIS.

If this does not solve the problem, see the following TechNote on the EnterpriseVault Support Web site: http://entsupport.symantec.com/docs/288138.

141Configuring Enterprise Vault Operations ManagerTroubleshooting Operations Manager


The TechNote provides detailed troubleshooting information related to installingand using Operations Manager.

Configuring Enterprise Vault Operations ManagerTroubleshooting Operations Manager

142

Configuring EnterpriseVault Reporting


■ When to run the Reporting Configuration utility

■ Running the Reporting Configuration utility

■ Postconfiguration steps for Enterprise Vault Reporting

■ Accessing the reports

■ Troubleshooting Enterprise Vault Reporting

When to run the Reporting Configuration utilityRun the Reporting Configuration utility after installing the Enterprise VaultReporting component.

Note: You must only configure Reporting after you have successfully run theEnterprise Vault configuration wizard to configure at least one Enterprise Vaultserver in the site.

You must also run the Reporting Configuration utility after upgrading EnterpriseVault, to deploy any new and upgraded reports.

You can rerun the Reporting Configuration utility if the configuration fails forsome reason and you need to repeat it.

You can also rerun the Reporting Configuration utility if you need to change thedetails of the reporting user account, or to specify a change in the location of theDirectory database SQL server.

20Chapter

Running the Reporting Configuration utilityRun the Reporting Configuration utility to configure Enterprise Vault Reporting,to deploy upgraded reports after an upgrade, or to change the Reporting dataaccess settings.

To run the Reporting Configuration utility

1 Ensure you are logged in under the Vault Service account.

2 Click Start > Programs > Enterprise Vault >Reporting Configuration.

The Reporting Configuration utility starts.

3 Choose one of the configuration options:

■ ConfigureReporting and deploy or upgrade reports. Select this optionto do either of the following:

■ Configure Reporting and deploy the reports on this server.

■ Deploy new and upgraded Enterprise Vault reports, after performingan upgrade of Enterprise Vault.

■ Reconfigure data access settings for Reporting. Select this option tochange the details of the reporting user account, or to specify a changein the location of the SQL server for the Enterprise Vault Directorydatabase.

4 Provide the details of the reporting user account you have created forReporting to run under:

Enter the Active Directory domain, the user name, and the password for thereporting user account.

5 Enter the following details, where required:

■ If you are using Microsoft SQL Server Reporting Services 2005, select theMicrosoft SQL Server Reporting Services instance on which you want todeploy the reports. To deploy the reports on the default instance, selectthe instance name MSSQLSERVER.

■ Select the language you want the reports to use.

■ Select the Directory database SQL Server. If the server does not appearin the list, type in the name of the server.

6 Click Configure or Reconfigure to run the utility.

7 When the utility has finished, click OK on the displayed dialog to quit theutility.

Configuring Enterprise Vault ReportingRunning the Reporting Configuration utility

144

Now follow the postconfiguration steps for Enterprise Vault Reporting, if you areconfiguring Reporting for the first time.

Postconfiguration steps for Enterprise VaultReporting

Perform the following steps to ensure that the Enterprise Vault reports areaccessible:

■ Check that the reporting user account has an SQL logon on all the SQL serversused for:

■ The Enterprise Vault Directory database

■ The Enterprise Vault Monitoring database

■ The Enterprise Vault Audit database

■ All vault store databases

■ All vault store group fingerprint databases

■ The FSA Reporting database, if you have configured FSA Reporting.

If a logon does not exist on all these SQL servers, create it.

■ Check that the SQL server role EVReportingRole has been added to eachEnterprise Vault database, and that this role has been assigned to the reportinguser.

■ Assign to a suitable role any user account other than the Vault Service accountthat requires access to the reports. Note that different roles have access todifferent reports. Only the Vault Service account and the Power Administratorhave access to all reports.See "Roles-based administration" in the Administrator's Guide.

■ Some reports rely on Enterprise Vault Monitoring or Enterprise Vault Auditingbeing enabled in order to provide the source data. Monitoring may be enabledor disabled from the Enterprise Vault configuration wizard, or from theEnterprise Vault Operations Manager Web application, if it is installed. Auditingmay be enabled from the Administration Console, as described in theAdministrator's Guide.

Note: Enterprise Vault Reporting consists of two sets of reports. The OperationReports should now be available. If you want to access the Data Analysis Reportsyou must first configure FSA Reporting.

See "Configuring and running FSA Reporting" in the Administrator's Guide.

145Configuring Enterprise Vault ReportingPostconfiguration steps for Enterprise Vault Reporting

You can now attempt to access the reports to confirm that you have successfullyinstalled and configured Enterprise VaultReporting.

Accessing the reportsTo confirm that Enterprise Vault Reporting has been installed and configuredsuccessfully, try accessing the reports as follows.

Note:These instructions explain only how to access the Enterprise Vault Reportingreports. For more details of the content of the reports and how to view them, see"Using Enterprise Vault Reporting" in the Administrator’s Guide.

To access the Enterprise Vault Reporting reports

1 Enter the following URL in your Web browser:

http://host_name/reportmgr_Webapp_name/

where:

■ host_name is the fully qualified host name of the computer hosting theMicrosoft SQL Server Reporting Services Report Manager Web application.

■ reportmgr_Webapp_name is the name of the Microsoft Reporting ServicesReport Manager Web application.

For example:

http://alderaan.evdomain.com/Reports/

or

http://alderaan.evdomain.com/Reports$MyInstance/

where MyInstance is the Reporting Services instance name.

2 Enter the credentials of a user account that has been assigned to a role thatpermits access to the required reports.

See “Postconfiguration steps for Enterprise Vault Reporting” on page 145.

3 From the Report Manager Web application Home page, select SymantecEnterprise Vault > language, where language is the language you want touse for the reports.

4 To access the Operation Reports, select OperationReports.

Configuring Enterprise Vault ReportingAccessing the reports

146

5 Select the required report from the list of available reports on the OperationReports page.

Note: You can view only those reports for which your role provides access.

6 If you have configured FSA Reporting, you can also access the Data AnalysisReports.

Note: To access the Data Analysis Reports you must first have configuredFSA Reporting.

See “Postconfiguration steps for Enterprise Vault Reporting” on page 145.

To access the Data Analysis Reports, select DataAnalysis Reports.

For detailed information on using the reports, see "Using Enterprise VaultReporting" in the Administrator's Guide.

Note: Do not change the names of any of the Enterprise Vault Reporting reports.If you change the report names, you will not be able to access the reports fromthe built-in links within the reports.

Troubleshooting Enterprise Vault ReportingIf you have problems with installing Enterprise Vault Reporting, or when accessingor viewing its reports, see the following TechNote on the Enterprise Vault SupportWeb site: http://entsupport.symantec.com/docs/288139.

This TechNote gives detailed troubleshooting information for Enterprise VaultReporting.

147Configuring Enterprise Vault ReportingTroubleshooting Enterprise Vault Reporting


Configuring Enterprise Vault ReportingTroubleshooting Enterprise Vault Reporting

148

Initial Enterprise Vault setup

■ Initial Enterprise Vault setup

■ Setting up storage

■ Reviewing the default settings for the site

4Section

Initial Enterprise Vaultsetup


■ License keys

■ Using the Administration Console

■ Adding services

■ Creating retention categories

■ What next?

License keysAt the end of the configuration wizard you were asked to start the EnterpriseVault services. These services will not start until you have installed the appropriatelicense keys.

Using the Administration ConsoleThe Enterprise Vault Administration Console is a snap-in for MicrosoftManagement Console (MMC). MMC provides a common framework foradministrative tools that gives them all a similar look and feel. It is possible tocustomize an MMC snap-in so that it includes the exact functionality needed bya particular administrator.

The Administration Console enables you to manage the Enterprise Vault sites,services, archiving tasks, policies and targets.

21Chapter

If people are using separate administration consoles at the same time to makechanges to Enterprise Vault, the changes made by one person are not necessarilyshown in the other consoles. You are recommended to avoid using multipleconsoles simultaneously when managing Enterprise Vault. If you do use multipleconsoles, press F5 to refresh the Administration Console display before you makeany changes.

Using the Administration Console without an Internet connectionEnterprise Vault files are digitally signed with a VeriSign certificate.

By default Windows checks when a file is accessed whether the file's digitalcertificate has been revoked. If an Enterprise Vault server does not have an Internetconnection the Administration Console pauses repeatedly while Windows triesto check the digital certificate.

If you use Enterprise Vault on a server without an Internet connection, you canprevent Windows from checking whether the certificate has been revoked. Youturn off the Internet Explorer setting "Check for publisher's certificate revocation"for every account that runs an Enterprise Vault service.

If you configure Enterprise Vault to use the Vault Service account to run allservices then you change the setting for the Vault Service account. If you configureEnterprise Vault to use other accounts to run services then you must change thesetting in those accounts.

Do the following on every Enterprise Vault server

1 Log on to an Enterprise Vault server as an account that runs Enterprise Vaultservices on that server.

2 In the Windows Control Panel, double-click Internet Options.

3 In Internet Options click the Advanced tab.

4 In the Security section, clear Check for publisher's certificate revocation.

5 Click OK.

6 Repeat this procedure on every Enterprise Vault server for every accountthat runs Enterprise Vault services.

Setting up the Administration Console to display Japanese charactersIf your Enterprise Vault installation is going to have Japanese users (eitherJapanese administrators or Outlook users who have a Japanese version of theEnterprise Vault User Extensions), you must set up the Administration Consoleso that it can display Japanese characters.

The Japanese characters are used when displaying the following:

Initial Enterprise Vault setupUsing the Administration Console

152

■ Exchange Server mailbox names

■ Archive names and descriptions

■ The Web access application system message

■ Retention category names and descriptions

Follow the steps below on each computer that is to run the Administration Console.

To set up the Administration Console to display Japanese characters

1 Start the registry editor and navigate to the following key:

HKEY_LOCAL_MACHINE

\SOFTWARE

\KVS

\Enterprise Vault

\Admin

2 Add the following registry string values:

SHIFTJISSecondaryFontCharSet

12SecondaryFontSize

MS UI GothicSecondaryFontFace

3 Check that the MS UI Gothic font is installed:

On Windows 2003:

■ In the Windows Control Panel, double-click Regional and LanguageOptions.

■ In Regional and LanguageOptions, click the Languages tab.

■ Under Supplemental languagesupport, select Install files forEastAsianlanguages.

■ Click OK.

The values given here work well but, if you want to experiment with other settings,you can change the fonts while the Administration Console is running.

Starting the Administration ConsoleTo use the Administration Console initially, you should log in as the Vault Serviceaccount. You can then assign roles to other administrators, to enable them to

153Initial Enterprise Vault setupUsing the Administration Console

perform the required Enterprise Vault management tasks using the AdministrationConsole.

To start the Administration Console

■ On the Windows Start menu, click Programs > Enterprise Vault >Administration Console.MMC starts and loads the Administration Console snap-in.The left pane of the main Administration Console shows you the hierarchy ofcomponents that make up your Enterprise Vault site. The right pane showsyou the contents of whatever you select in the hierarchy.

To get help

◆ Do one of the following:

■ To access online help for Enterprise Vault, clickHelp>HelponEnterpriseVault. This online help includes Enterprise Vault manuals.

■ To find out more about MMC, click Help >Help onMMC in the MMCwindow. The MMC help appears.

To refresh the screen

◆ Press F5 to force a refresh at any time.

About administration rolesEnterprise Vault provides the following mechanisms that you can use to controlthe access administrators have to the Administration Console:

■ Roles-based administration. Many administrative tasks do not require all thepermissions that are associated with the Vault Service account. Roles-basedadministration enables you provide individual Enterprise Vault administratorswith exactly the permissions required to perform their individualadministrative tasks.You can assign individuals or groups to roles that match their responsibilitiesand they are then able to perform the tasks that are included in those roles.Because the permissions are associated with roles, rather than with individualadministrators, you can control the role permissions without having to editthe permissions for each administrator.

■ Admin permissions. You can grant or deny access to the following containersin the Administration Console tree:

■ File Server

■ Exchange Server

■ SharePoint Virtual Server

Initial Enterprise Vault setupUsing the Administration Console

154

■ Enterprise Vault Server

You can control access by assigning roles, or by using admin permissions, or both.

When you install or upgrade to Enterprise Vault 8.0 only the Vault Service accounthas access the Administration Console. You can restrict the tasks administratorscan perform by assigning roles and you can further restrict access by using adminpermissions to restrict administrators to managing specific Administration Consolecontainers.

Roles-based administration enables you to use Microsoft Authorization Managerto configure the various administrator roles. All such configuration is performedusing the Vault Service account.

See “Roles-based administration” on page 33.

For instructions on setting up roles-based administration, see theAdministrator’sGuide.

Adding servicesUse the Administration Console to add the following core Enterprise Vault services:

■ Indexing service.

■ Storage service

■ Shopping service

■ Task Controller service.

When creating services, you may be prompted for the password of the VaultService account.

The index storage location is on an accessible device to which the Vault Serviceaccount has write access.

When you add archiving tasks, such as Exchange Mailbox or File System archivingtasks, they will run under the control of the Task Controller service. If you stopthe Task Controller service, all tasks running under the control of this servicewill also stop.

The same instructions can be repeated to add each of these services.

To add a service

1 In the left pane, expand the Enterprise Vault site hierarchy until theEnterprise Vault Servers container is visible.

2 Expand the Enterprise Vault Servers container.

155Initial Enterprise Vault setupAdding services

3 Right-click the name of the computer to which you want to add the serviceand, on the shortcut menu, click New and then Service.

The Add Service dialog box appears, listing the services you can add.

4 Click the service that you want to add.

5 Click Add.

Creating retention categoriesYou may have decided during planning that you wanted more retention categoriesthan the ones predefined in Enterprise Vault. If this is the case, you must createyour own retention categories. Alternatively, you can edit the predefined retentioncategories to suit your needs.

If you configure Enterprise Vault to archive from Exchange managed folders, itcan automatically synchronize managed content settings to managed folderretention categories. Enterprise Vault creates managed folder retention categoriesautomatically. For more information, see the Administrator's Guide.

To create a new retention category

1 Expand the Enterprise Vault site hierarchy until Retention Categories isvisible.

2 Right-click Retention Categories.

3 From the shortcut menu, select New>Retention Category.

The NewRetention Category wizard starts.

4 Work through the wizard. ClickHelp on any of the wizard screens if you needmore information.

Retention category propertiesBy assigning a retention category to items at the time they are archived, it ispossible to categorize stored items. This categorization makes it easier to retrieveitems because it is possible to search by category.

A retention category also specifies the minimum amount of time after its lastmodification date that an item must be retained. This length of time is the retentionperiod. For mail messages, the retention period is the time since the message wasreceived. For documents, it is the time since the document was last modified.

With Exchange Server archiving, users can select retention categories for mailboxfolders or items so that, when archiving occurs, items are stored with theappropriate retention category.

Initial Enterprise Vault setupCreating retention categories

156

If you later modify a retention category, the changes are retrospective. Forexample, if you have a retention category called Customer Accounts with aretention period of 5 years and you change the retention period to 10 years, itemsthat have been already archived with the Customer Accounts retention categoryare retained for a minimum of 10 years.

Enterprise Vault can automatically delete expired items. See the Administrator'sGuide for more details.

A retention category has the following properties:

You can modify the retention category name as needed. The new nameis used immediately, so users of the Web access application mustsearch using the new name to find items stored with this retentioncategory.

Name

This is a description of the retention category. Make sure that thedescription you give here is meaningful to users.

Description

This is the minimum amount of time to retain an item that has beenarchived using this retention category.

The period runs from the date the item last changed, not from thedate that the item is stored in an archive, as follows:

■ For mail messages, the date is the date that the message wasreceived.

■ For documents, the date is the date the document was last modified.

Retention period

Select this if you want items never to expire.Retain itemsforever

Select this to prevent users deleting items that have been archivedusing this retention category. This protection applies during theretention period, and also after the retention period has expired. Inother words, while this option remains selected, users can never deleteitems that have been stored using this retention category.

This setting affects only those items that are stored in archives. Itdoes not affect items that are still on archiving target servers.

Prevent deletion ofarchived items inthis category

Check this to prevent users using this category when archiving newitems. The category is still available to users when they are searchingfor items that have already been archived.

Enterprise Vault does not allow the site default retention category tobe hidden from users. If you hide the site default retention category,Enterprise Vault automatically chooses another retention categoryand makes it the site default.

Hide this categoryfrom users

157Initial Enterprise Vault setupCreating retention categories

To prevent unintentional changes, check this to lock all the retentioncategory settings.

Lock thisRetentionCategory

Select one of the following:

■ Inherit from Site settings. The retention period is inherited fromthe Site default retention category settings.

■ Modified date. The retention period is based on the date when theitem was last modified. For mail messages, a retention period thatis based on the Modified date is the time since the message wassent or received. For documents, it is the time since the documentwas last modified.

■ Archived date. The retention period is the time since the item wasarchived.

Base expiry on

For your notes. Edit this text as necessary. This text is visible only toEnterprise Vault administrators.

AdministrativeNote

What next?See the following chapter for instructions on how to set up storage for archives.

Initial Enterprise Vault setupWhat next?

158

Setting up storage


■ About setting up storage for archives

■ About single instance storage

■ Developing a suitable sharing regime

■ About vault stores on upgrade to Enterprise Vault 8.0

■ Creating vault store groups

■ Creating vault stores

■ Creating partitions

■ Configuring sharing for a vault store group

■ What next?

About setting up storage for archivesBefore you set up storage for your archives, consider whether you want to useEnterprise Vault's optimized single instance storage. Single instance storage cangreatly reduce your storage requirements by sharing the common parts of archiveditems. However, it can increase the network traffic between the Enterprise Vaultservers and the storage devices that host the partitions.

If you intend to use single instance storage, you need to decide on a sharing regimethat is appropriate for your requirements and compatible with your networkconnection speeds.

■ See “About single instance storage” on page 160.

■ See “Developing a suitable sharing regime” on page 167.

22Chapter

Note: A new vault store group is configured by default to use Enterprise Vaultsingle instance storage. The only exception is the Default Upgrade Group thatEnterprise Vault creates if you upgrade to Enterprise Vault 8.0.

For Enterprise Vault to be able to create archives, you must create a vault storegroup that contains a vault store and at least one vault store partition:

■ A vault store group is a container for vault stores. It defines the outer boundaryfor sharing items in Enterprise Vault single instance storage.See “Creating vault store groups” on page 169.

■ A vault store is a logical entity to which an Enterprise Vault Storage servicearchives items. Each vault store has its own vault store database. The vaultstore database holds information about the archives in the vault store and allthe items that are stored in each archive.See “Creating vault stores” on page 170.

■ A vault store partition is a physical location where Enterprise Vault storesarchived data. Each vault store must contain at least one partition. Partitionscan be placed on different physical disks and on various types of storagemedium. As the data in a vault store grows, you can create more partitions toprovide additional capacity. You can configure the partitions so that archivingrolls over from one partition to another when certain criteria are met.See “Creating partitions” on page 172.

To configure Enterprise Vault single instance storage for a vault store group, youmust run the Configure Sharing wizard on the group.

See “Configuring sharing for a vault store group” on page 175.

About single instance storageEnterprise Vault's optimized single instance storage can provide a significantreduction in the storage space that is required for archived items. Enterprise Vaultidentifies the shareable parts (SIS parts) of an item, such as a message attachmentor the contents of a document. It stores each SIS part separately, and only oncewithin a sharing boundary. A sharing boundary can include one or more vaultstores within a vault store group. When Enterprise Vault identifies a SIS part thatit has already stored in the target vault store's sharing boundary, it referencesthe stored SIS part file instead of archiving the SIS part again.

Enterprise Vault applies a minimum size threshold for SIS parts. The size thresholdenables Enterprise Vault to balance the likely storage savings against the resourcesthat are required to create, archive, and retrieve the SIS parts.

Setting up storageAbout single instance storage

160

Enterprise Vault single instance storage can save storage space in a number ofways:

■ Enterprise Vault shares the SIS parts between all the vault stores within asharing boundary. For example, if you use separate vault stores for journalingand mailbox archiving, Enterprise Vault can share the SIS parts between thevault stores.

■ If a number of separate messages with the same attachment are sent to multiplerecipients, Enterprise Vault stores the attachment only once within a sharingboundary. .

■ Enterprise Vault identifies a SIS part from the content, not the file name. Iftwo messages both have the same file attachment, Enterprise Vault can sharethe attachments, even if they have different file names.

■ Enterprise Vault can share the identical SIS parts that result from differenttypes of archiving, such an Exchange message attachment that is also storedas a file on a file server.

If you upgrade to Enterprise Vault 8.0, Enterprise Vault creates a Default UpgradeGroup for each Enterprise Vault site, and places the site's existing vault stores inthat group. The Default Upgrade Group does not use single instance storage untilyou configure sharing for it.

See “About vault stores on upgrade to Enterprise Vault 8.0” on page 168.

In any other vault store group, a new vault store uses Enterprise Vault singleinstance storage by default. The vault store shares only the SIS parts of the itemsthat are archived within itself, by default. It does not share the SIS parts of theitems that are archived to other vault stores in the vault store group.

You can run the Configure Sharing wizard on a vault store group to extend sharingbetween vault stores, or to turn off Enterprise Vault single instance storage if youwant.

Note: Enterprise Vault single instance storage is not performed when items arestored to partitions that are hosted on EMC Centera devices. Enterprise Vaultprovides a separate device-level sharing option to take advantage of the sharingcapabilities of EMC Centera devices.

See “EMC Centera device-level sharing” on page 166.

For more information on Enterprise Vault single instance storage, see the followingtopics:

■ See “About sharing levels and sharing boundaries” on page 162.

■ See “How Enterprise Vault single instance storage works” on page 164.

161Setting up storageAbout single instance storage

■ See “The fingerprint database” on page 165.

■ See “Requirements for single instance storage” on page 166.

■ See “Developing a suitable sharing regime” on page 167.

About sharing levels and sharing boundariesWhen you configure sharing for a vault store group, you set a sharing level foreach vault store in the group. The sharing levels determine the boundaries forsingle instance storage sharing in the group.

Table 22-1 Vault store sharing levels

Effect on sharingVault store's sharing level

The vault store shares SIS parts with all the other vaultstores in the vault store group that have this sharing level.

Share within group

The vault store shares SIS parts only within itself.Share within vault store

Enterprise Vault does not perform single instance storagefor this vault store.

No sharing

A vault store group can therefore contain one or more sharing boundaries. Eachsharing boundary contains one or more vault stores that share the SIS parts thatresult from Enterprise Vault single instance storage.

Figure 22-1 shows an example vault store group that contains five vault stores:


162

Figure 22-1 Sharing boundaries in a vault store group

Sharing boundary

Vault store 1

Sharing level:Share withingroup

Vault store 3


Vault store 4


Vault store 5

Sharing level:No sharing

Vault store group

Sharing boundary

Vault store 2

Sharing level:Share withinvault store

■ Vault stores 1, 3, and 4 all have the sharing level "Share within group". Thesevault stores are within the same sharing boundary. Enterprise Vault sharesSIS parts across the three vault stores for the items that it archives to thesevault stores.

■ Vault store 2 has the sharing level "Share within vault store", so it has its ownsharing boundary. Enterprise Vault shares SIS parts within the vault store forthe items that it archives to this vault store.

■ Vault store 5 has the sharing level "No sharing". The vault store is not includedin any sharing boundary. Enterprise Vault does not perform Enterprise Vaultsingle instance storage on the items that it archives to this vault store.

Note that a vault store group can have only one sharing boundary that containsmultiple vault stores. For example, in Figure 22-1 you cannot configure two newvault stores to share SIS parts across each other and not with the existing vaultstores. You can instead create the new vault stores in another vault store group.


Note:Enterprise Vault assigns a sharing level of "Share within vault store" to newvault stores. An exception to this rule applies to the Default Upgrade Group, whichEnterprise Vault created if you upgraded to Enterprise Vault 8.0. If you do notconfigure sharing for the Default Upgrade Group, Enterprise Vault assigns asharing level of "No sharing" to new vault stores in that group. See “About vaultstores on upgrade to Enterprise Vault 8.0” on page 168.

To change the sharing level for a vault store, run the Configure Sharing wizardon the vault store group after you have created a partition for the vault store.

How Enterprise Vault single instance storage worksEnterprise Vault archives an item using single instance storage if both of thefollowing conditions apply:

■ The target vault store has a sharing level of "Share within vault store" or "Sharewithin group".

■ The current open partition is not hosted on an EMC Centera device.

Enterprise Vault archives an item for single instance storage as follows:

■ It identifies the parts of an item that are suitable for sharing, such as largemessage attachments. These parts are referred to as SIS parts. EnterpriseVault uses a minimum size threshold for SIS parts, to balance the likely storagesavings against the resources that are required to create, archive, and retrievethem.

■ It generates a digital fingerprint to each SIS part. The fingerprint is acryptographic, hash-based identifier that is determined by the contents of theSIS part.

■ For each SIS part, Enterprise Vault accesses the vault store group's fingerprintdatabase to determine whether a SIS part with the same fingerprint is alreadystored within the vault store's sharing boundary. A SIS part with the samefingerprint indicates an identical SIS part.

■ If an identical SIS part is not already stored within the sharing boundary,Enterprise Vault stores the SIS part and saves the SIS part's fingerprintinformation in the fingerprint database.

■ If an identical SIS part is already stored within the sharing boundary,Enterprise Vault references the stored SIS part. It does not store the SISpart again.

■ It stores the remainder of the item (the item minus any SIS parts) as the residualsaveset file. The residual saveset file holds Enterprise Vault metadata about


164

the item and unique information about it, such as the file name if it is adocument or attachment, and follow up flags if it is a message.

When Enterprise Vault receives a request to restore an archived item, itreconstitutes the item from the item's residual saveset file and SIS part files.

If an item's target vault store has a sharing level of "no sharing" or the targetpartition is hosted on an EMC Centera device, then Enterprise Vault does not usesingle instance storage. It archives the item with its Enterprise Vault metadataas a single saveset file.

The fingerprint databaseA vault store group's fingerprint database holds information about each SIS partthat is stored in the vault store group. The information includes the SIS part'sdigital fingerprint, the name of the partition in which the SIS part is stored, andin which sharing boundary the SIS part is shared.

When you create a vault store group, Enterprise Vault creates a fingerprintdatabase for that vault store group.

The New Vault Store Group wizard provides the following options for configuringthe fingerprint database's SQL filegroups:

■ A basic configuration, where Enterprise Vault locates the primary filegroupand all the non-primary filegroups on one device.

■ An option to configure additional locations for the 32 non-primary filegroups.The non-primary filegroups can grow rapidly in size when you use singleinstance storage. For best performance you need to spread the non-primaryfilegroups across multiple locations.

For optimal performance, do as follows:

■ Select the option to configure additional locations for the non-primaryfilegroups.

■ Specify as many locations as possible for the non-primary filegroups on theSQL Server, up to the maximum of 32.

■ Specify a separate device for each location. If you specify more than onelocation on the same device there is no performance benefit.

Note: To add or change locations after the fingerprint database is configured is aSQL Server administration task. See your Microsoft SQL Server documentationfor details.


Requirements for single instance storageEnterprise Vault single instance storage places some additional requirements ona system, as follows:

■ Storage space for the fingerprint database. When you use Enterprise Vaultsingle instance storage the fingerprint database may grow very rapidly. Toensure acceptable archiving and retrieval performance, it is important toconfigure the fingerprint database appropriately for the amount of sharing inthe vault store group.See “Creating vault store groups” on page 169.

■ Network connectivity requirements. An Enterprise Vault server communicateswith the following computers when it stores or retrieves items using EnterpriseVault single instance storage:

■ The computers that host the vault store partitions for the vault stores thatare within the vault store's sharing boundary.

■ The computer that hosts the vault store group's fingerprint database.

Network connection speeds must be fast enough across these connections toprovide acceptable storage and retrieval times.See “Developing a suitable sharing regime” on page 167.

EMC Centera device-level sharingYou can configure a partition for an EMC Centera device to take advantage of theCentera's device-level sharing, if required. Enterprise Vault then stores theshareable parts of a saveset as separate data blobs, so that the Centera device isable to share them.

The New Partition wizard includes an option to enable device-level sharing whenyou create a partition and specify an EMC Centera device.

See “Creating partitions” on page 172.

You can also enable device-level sharing from the General tab of the partitionproperties.

Partitions for EMC Centera do not take part in Enterprise Vault single instancestorage sharing. If you create a partition for EMC Centera in a vault store that isconfigured for sharing, the partition is ignored for the purposes of EnterpriseVault single instance storage sharing.


166

Developing a suitable sharing regimeIf you use Enterprise Vault single instance storage, you need to create a sharingregime that meets your organization's data sharing requirements and which isappropriate for your network connection speeds.

Consider what sort of sharing regime you require before you start archiving. Thereare limits to what you can change:

■ You can change a vault store's sharing level, but the change does not actretrospectively. For example, if you change a vault store's sharing level from'share within group' to 'share within vault store', any items already sharedwithin the vault store group remain so.

■ You cannot move a vault store to another vault store group unless all of thefollowing circumstances apply:

■ You upgraded to Enterprise Vault 8.0.

■ The vault store is one that Enterprise Vault upgraded, or one that youcreated in the Default Upgrade Group.

■ The vault store's sharing level is "No sharing" and has never been changed.

When deciding how to set up single instance storage, consider the following:

■ You may need to keep parts of your organization separated with informationbarriers, also known as "Chinese walls". For example, a datacenter may berequired by law or by company policy to keep information separate betweenits investment, retail, and mergers and acquisitions groups, to avoid conflictsof interest.You may want to create a separate vault store group for each organizationalgroup in which information must be isolated.

■ Network connectivity between the appropriate computers must be sufficientto provide acceptable storage and retrieval times. As a minimum we recommendthat you limit single instance storage to an environment in which theconnections support the expected response time of a 100 Mbps switchedEthernet LAN.The Enterprise Vault server whose Storage service manages a vault store musthave adequate connectivity with the following:

■ The computers that host the vault store partitions for the vault stores thatare within the vault store's sharing boundary.

■ The computer that hosts the vault store group's fingerprint database.

The slower the connection speeds between these computers, the longer it takesEnterprise Vault to archive and retrieve the shared items.

167Setting up storageDeveloping a suitable sharing regime

If your organization spans several widely-dispersed geographical locations itmay be appropriate to create separate vault store groups for each location.Remember to locate the fingerprint databases locally.Enterprise Vault provides a connectivity test to estimate connection speedsacross sample network connections. The relevant wizards prompt you to runthe connectivity test when you create a new vault store group or partition, orwhen you configure sharing. The connectivity test can help you create a sharingregime with an acceptable level of performance. To assess performance, theconnectivity test measures the average round-trip time for a number of pingrequests. If you have disabled ping in your environment, use your own toolsto decide if the performance is acceptable. We recommend a round-trip timeof 1 millisecond or less.If the test results indicate poor connectivity, consider modifying the sharingboundaries or changing the location of your computers to improve connectionspeeds. If you are willing to accept poorer performance, you can choose toaccept poor connectivity test results.

■ When you create a vault store group, configure its fingerprint databaseappropriately for the projected sharing requirements.See “Creating vault store groups” on page 169.

Note: If you upgrade to Enterprise Vault 8.0, Enterprise Vault places all yourexisting vault stores in a vault store group named the Default Upgrade Group.The Default Upgrade Group does not use single instance storage until you configuresharing for it.

See “About vault stores on upgrade to Enterprise Vault 8.0” on page 168.

About vault stores on upgrade to Enterprise Vault 8.0If you upgrade to Enterprise Vault 8.0, Enterprise Vault does the following foreach Enterprise Vault site:

■ It creates a vault store group named the Default Upgrade Group, without afingerprint database.

■ It places the site's existing vault stores into the Default Upgrade Group.

■ It sets the sharing level of each existing vault store to "No sharing".

If you add a vault store to the Default Upgrade Group, Enterprise Vault sets itssharing level to "No sharing", unless you configure sharing for the group.

Note that Enterprise Vault does not use single instance storage in the DefaultUpgrade Group unless you configure sharing for that group. No sharing occurs

Setting up storageAbout vault stores on upgrade to Enterprise Vault 8.0

168

even if your vault stores were configured to use single instance storage beforethe upgrade.

Before you configure sharing for the Default Upgrade Group, consider what sortof sharing regime you require. Remember that you can only a move vault storeto a different vault store group if the vault store has not participated in EnterpriseVault 8.0 single instance storage sharing.

To configure sharing in the Default Upgrade Group, run the Configure Sharingwizard. The wizard prompts you to create a fingerprint database for the groupbefore you configure the sharing levels.

See “Configuring sharing for a vault store group” on page 175.

Note: Ensure that you then back up the fingerprint database.

See "Enterprise Vault backup procedures" in the Administrator's Guide.

Creating vault store groupsVault stores are grouped within vault store groups. If you use Enterprise Vaultsingle instance storage, a vault store group forms an outer boundary for thesharing of SIS parts.

Before you start creating vault store groups and vault stores, consider what sortof sharing regime is compatible with your organization's structure and networkconnection speeds.

See “Developing a suitable sharing regime” on page 167.

You can create a vault store group using the New Vault Store Group wizard, asfollows.

To create a vault store group

1 In the left pane of the Administration Console, expand the Enterprise Vaultsite hierarchy until Vault StoreGroups is visible.

2 Right-click Vault StoreGroups and then click New > Vault StoreGroup.

The New Vault Store Group wizard starts.

3 Work through the wizard. You need to provide the following information:

■ A name for the Vault Store Group.

■ The SQL server that is to host and manage the group's fingerprint database.

■ The locations for the fingerprint database's SQL filegroups.

169Setting up storageCreating vault store groups

The New Vault Store Group wizard provides the following options forconfiguring the filegroups:

■ A basic configuration, where Enterprise Vault locates the primary filegroupand all the non-primary filegroups on one device.

■ An option to configure additional locations for the 32 non-primaryfilegroups. The non-primary filegroups can grow rapidly in size when youuse single instance storage. For best performance, spread the non-primaryfilegroups across multiple locations.

For optimal performance do as follows:

■ Select the option Configure additional locations for non-primaryfilegroups.

■ Specify as many locations as possible for the non-primary filegroups onthe SQL Server, up to the maximum of 32.

■ Specify a separate device for each location. If you specify more than onelocation on the same device there is no performance benefit.

Note: To add or change locations after the fingerprint database is configuredis a SQL Server administration task. See your Microsoft SQL Serverdocumentation for details.

When the vault store group has been created, the New Vault Store wizard takesyou through the steps to create a vault store.

See “Creating vault stores” on page 170.

Creating vault storesWhen you create a vault store you must specify an Enterprise Vault Storage serviceto manage it, and a location for the SQL vault store database.

The vault store database holds information about the archives in the vault storeand all the items that are stored in each archive. For example, when an archiveditem has been backed up, this fact is reflected in the information that is held inthe vault store database.

About safety copiesEnterprise Vault can be configured to retain archived items, until the vault storepartition in which they are archived has been backed up. During the time betweenarchiving and removal, the original items are treated as safety copies by Enterprise

Setting up storageCreating vault stores

170

Vault. When the vault store partition has been backed up, Enterprise Vault canremove the safety copies. It also creates shortcuts and placeholders at this timeif it is configured to do so.

During the creation of each vault store, choose from the following settings tocontrol how Enterprise Vault manages safety copies:

■ Never. Enterprise Vault does not remove safety copies, even after they havebeen backed up.

■ After backup. Enterprise Vault does not remove safety copies until the partitionthat contains the archived items has been backed up.

■ After backup (immediate for journaling). This option is the same as the Afterbackup option except for journal items which are removed immediately afterthey are archived.

■ Immediately after archive. All original items are removed as soon as they havebeen archived.

If you select the After backup option or the After backup (immediate for journaling)option, Enterprise Vault much check that the partition has backed up before itremoves safety copies.

Choose from the following options:

■ Use the archive attribute. Files on the partition whose archive attributes arecleared are considered backed up and Enterprise Vault removes thecorresponding safety copies. This option is appropriate only if your backupsoftware clears archive attributes after backup.

■ Check for a trigger file. A partition is considered backed up when EnterpriseVault finds a trigger file on the partition. Typically, this trigger file is placedon the partition by your backup software. When you choose this option, youcan also configure how often the partition is checked for the presence of atrigger file. For more information, see the Administrator’s Guide.

Creating a vault storeYou can create a vault store using the New Vault Store wizard, as follows.

To create a vault store

1 If you created a vault store group using the New Vault Store Group wizard,the New Vault Store wizard starts automatically . Go to step 5.


3 Expand the Vault StoreGroups container to show the existing vault storegroups.

171Setting up storageCreating vault stores

4 Right-click the vault store group in which you want to create the vault store,and then click New>Vault Store.

The New Vault Store wizard starts.

5 The New Vault Store wizard takes you through the steps to create a vaultstore.

You need to provide the following information:

■ The name of the computer that hosts the Storage service that the vaultstore is to use.

■ The name of the vault store. The name can contain letters, numbers, andspaces.

■ The SQL server that is to create and manage the vault store database, andthe locations for the database files.

■ When safety copies of items are to be removed.

Note:Enterprise Vault assigns a sharing level of "Share within vault store" to newvault stores. An exception to this rule applies to the Default Upgrade Group, whichEnterprise Vault created if you upgraded to Enterprise Vault 8.0. If you do notconfigure sharing for the Default Upgrade Group, Enterprise Vault assigns asharing level of "No sharing" to new vault stores in that group.

To change the sharing level for a vault store, run the Configure Sharing wizardon the vault store group after you have created a partition for the vault store.

When the vault store has been created, the New Partition wizard takes you throughthe steps to create a partition for the vault store.

See “Creating partitions” on page 172.

Creating partitionsPartitions can be placed on different physical disks and on various types of storagemedium. For example, you can create partitions on local NTFS volumes, NetAppdevices, or EMC Centera devices. For a full list of supported devices, see theEnterprise Vault Compatibility Charts.

About partition statesAs the data in a vault store grows, you can create more partitions to provideadditional capacity. Each vault store can contain only one open partition andEnterprise Vault archives data into this partition while it remains open.

Setting up storageCreating partitions

172

There are two approaches to the management of open vault store partitions:

■ You can manually change the open partition in a vault store. For example,when the disk that hosts the open partition reaches capacity, you can closethe partition and open a partition on another disk.

■ The automatic partition rollover feature which lets you configure partitionssuch that archiving rolls over from one partition to another when certaincriteria are met. For example, you can configure a partition to roll over whenthe disk that hosts the open partition has only 5% free space. You can alsoconfigure partitions to roll over on a date that you set. For more information,see the Administrator’s Guide.

To support both these features, during the creation of partitions, you can chooseany one of these initial states:

■ Select Closed to create a closed partition. If there is an existing open partition,it is not affected by this choice. You can open the new partition at any time byediting its properties.

■ Select Open to create an open partition. Each vault store can have only oneopen partition. If there is an existing open partition in the vault store, it isautomatically closed and items are archived to this new partition.

■ Select Ready to create a new partition that is available for partition rollover.

About collections and migrationWhere vault store partitions are held on non-WORM devices other than EMCCentera, you can configure and schedule the collection and migration of the filesthat are stored in the partition.

Collection involves collecting multiple small files into much larger collection files(.CAB files). Collection may give you a significant improvement in backup times.Collection is not recommended on devices that perform deduplication, as it causesloss of deduplication.

Migration involves moving the collection files onto longer term storage devices.For example, you may want to migrate older collections to cheaper, slower storage.

If you choose to use collection files you can configure the collection criteria, andoptionally provide details of how and when to migrate the collection files tosecondary storage. See the Administration Console help for details on settingthese options.

Other storage devices have been integrated with Enterprise Vault to enable themigration of data files. Supported devices are listed in the Enterprise VaultCompatibility Charts.

173Setting up storageCreating partitions

For instructions on how to configure migration to the supported storage devices,see the migration articles on the Symantec support knowledge base.

Note that collection is handled differently on EMC Centera devices, as follows:

■ Centera collection files are used instead of CAB files.

■ Files are collected as soon as they are archived, not according to a schedule.

Creating a partitionYou can create a vault store using the New Vault Store wizard, as follows.

In an environment that uses Enterprise Vault single instance storage, the networkconnection speeds must be adequate to support sharing. If you intend to use singleinstance storage in the vault store, run the connectivity test when the NewPartition wizard prompts you. The connectivity test helps to determine whetherthe connection speeds are adequate for sharing.


To create a partition

1 If you created a vault store using the New Vault Store wizard, the NewPartition wizard starts automatically. Go to step 6.



4 Expand the vault store group that contains the vault store for which you wantto create the partition.

5 Right-click the vault store in which you want to create the partition, and thenclick New>Partition.

The New Partition wizard starts.

6 The New Partition wizard takes you through the steps to create a partition.

You need to provide the following information:

■ The partition name and description.

■ Whether the new partition should be created closed, open or ready. Therecan only be one open partition. If you create an open partition, any existingopen partition is closed.

■ The type of device on which the partition is to be created. Select therequired type of storage device from the drop-down list. The additionalinformation that you need to provide depends on which device you select.

Setting up storageCreating partitions

174

For help with the options, see the Administration Console help for thewizard pages.

■ The location on the device for the vault store. The location can be enteredas a UNC path or a path starting with a drive letter.

■ The storage settings that are used by the storage device. Enterprise Vaultuses this information to help optimize data storage. For more details, seethe Administration Console help for the wizard pages.With the exception of the storage mode, you can change the storagesettings later from the Volume tab of the partition's properties.

Note: If you change the storage settings on the device at a later date, youmust update the related storage settings on the Volume tab of thepartition's properties to reflect the new behavior.

■ For partitions on EMC Centera devices, whether to enable device-levelsharing.

■ Partition rollover criteria if you choose to enable the feature for thispartition.

Note: Although you can create ready partitions on EMC Centera devices,you cannot enable onward rollover from a Centera-hosted partition.

■ Whether to use Security ACLs. This option does not apply to Centeradevices. It is usual to create a vault store partition with security ACLs inthe folders in the partition. Some optical devices, however, do not allowEnterprise Vault to add the ACLs.

■ How to check whether items have been secured.

■ Whether to use file collection software. If you choose to use collectionfiles you can configure the collection criteria, and optionally providedetails of how and when to migrate the collection files to secondarystorage.

Configuring sharing for a vault store groupTo change the sharing levels for the vault stores in a vault store group, you mustrun the Configure Sharing wizard on the vault store group.

175Setting up storageConfiguring sharing for a vault store group

Note: You can rerun the Configure Sharing wizard at any time, but changes youmake to the vault store sharing levels do not act retrospectively.


To configure sharing for a vault store group



3 Right-click the vault store group for which you want to configure sharing,and on the shortcut menu click Properties.

4 Click the Sharing tab.

The Sharing tab lists the vault stores in the vault store group, and their currentsharing levels.

5 Click Configure Sharing.

The Configure Sharing wizard starts.

6 In the special case of the Default Upgrade Group, Enterprise Vault helps youto configure a fingerprint database for the group, if one does not exist already.

7 The Configure Sharing wizard takes you through the steps to configure thesharing levels for the vault stores in the vault store group.

If you change one or more vault store sharing levels to Sharewithin vaultstore or Sharewithin group, the wizard prompts you to run a connectivitytest before the wizard makes any changes. The connectivity test helps todetermine whether the network connectivity is sufficient to support thesharing configuration you have selected.

The wizard makes no changes until you click Finish on the final page of thewizard.

If the connectivity test shows poor results you may want to do one of thefollowing:

■ ClickBack, modify the vault store sharing levels and rerun the connectivitytest .

■ Click Cancel to discard your changes.

For more information on the connectivity test, see the Administration Consolehelp for the Configure Sharing wizard.

Setting up storageConfiguring sharing for a vault store group

176

What next?Go to the next chapter and follow the instructions to review the default settingsfor the site.

177Setting up storageWhat next?

Setting up storageWhat next?

178

Reviewing the defaultsettings for the site


■ Reviewing the default settings for the site

■ What next?

Reviewing the default settings for the siteCheck the default settings configured in the Enterprise Vault site properties.

To display the site settings

1 In the Administration Console, expand the contents of the left pane until theEnterprise Vault site is visible.

2 Right-click the Enterprise Vault site and then, on the shortcut menu, clickProperties.

Alternatively, select the site and click the Review site properties button onthe toolbar.

3 Click Help on any of the Site Properties screens for further information.

4 Site properties include the following settings. Note that you can overridesome of these at a lower level. For example, you can override the site archivingschedule for a particular task by setting the schedule in the task properties.The indexing level can also be set at policy and archive level and the defaultretention category can be set at policy level (and at Provisioning Group levelfor Exchange Server mailbox archiving).

23Chapter

■ The vault site alias and description.

■ Whether users can delete items from their archive.

■ The protocol and port to use for the Web Access application.

■ PST holding area details.

■ A system message for users, if required.

■ A system message for administrators, if required.

General

■ The default retention category.

■ The default indexing level.

Archiving Defaults

■ The schedule for running storage expiry to delete fromarchives any items that are older than the retention periodassigned.

Storage Expiry

■ If required, you can set limits on the size of archives.Archive UsageLimit

■ The schedule for running automatic, background archiving.Site Schedule

■ Performance counters for monitoring Enterprise Vault.Monitoring

5 Click Help on any of the site properties screens for further information.

Setting the Site archiving scheduleEach archiving task or service runs according to a schedule that you define. Thepossible schedules for each task are as follows:

■ The default schedule, which is the one that you set in the site properties. Thisschedule applies to all archiving tasks in your Enterprise Vault site.

■ The task's own schedule, which is the one that you set by editing its properties.You edit this schedule if you want to provide specific settings for that task,overriding those in the site properties.

To edit the default schedule for the site

1 In the left pane of the Administration Console, expand the Enterprise Vaultsite hierarchy until the name of the site is visible.

2 Right-click the site name and then click Properties.

3 Click the Site Schedule tab.

4 Modify the schedule as required. The online help gives detailed instructionson using the schedule page.

Reviewing the default settings for the siteReviewing the default settings for the site

180

Web Access application settingsOn the General page of site properties, the protocol and port for accessing theEnterprise Vault Web Access application can be set.

The default URL for the Web Access application is set to /EnterpriseVault, whichis the name of the virtual directory in IIS for the Web Access application. Whena client contacts the Web Access application to access an archive, Enterprise Vaultcreates the full URL dynamically.

In a default configuration, the Web Access application is accessed using HTTPover port 80. The full URL for the Web Access application is then:

http://FQDN/EnterpriseVault

where FQDN is the fully qualified domain name of the Enterprise Vault server thathosts the Storage service for the user's archive.

If your IIS computer requires a different port or secured connections, then youcan set the required values using the options Use TCP Port or Use HTTPS on SSLPort.

Note: If you change the protocol or port that is used to access the Web Accessapplication after items have been archived, existing shortcuts will no longer work.

See Customizing security for the Web Access application in Installing andConfiguring.

What next?Go to the appropriate Setting up manual for further setup instructions for thetype of archiving that you want to implement.

Table 23-1 on page 181. lists the Setting up manuals.

Table 23-1 Enterprise Vault documentation set

CommentsDocument

Describes how to archive items from MicrosoftExchange user mailboxes, journal mailboxes, andpublic folders.

Setting up Exchange Server Archiving

Describes how to archive items from Domino mailfiles and journal databases.

Setting up Domino Server Archiving

181Reviewing the default settings for the siteWhat next?

ms-its:Installing_and_Configuring.chm::/IC_129.htm

Table 23-1 Enterprise Vault documentation set (continued)

CommentsDocument

Describes how to archive files that are held onnetwork file servers.

Setting up File System Archiving

Describes how to archive documents that are heldon Microsoft SharePoint servers.

Setting up SharePoint Server Archiving

Describes how to archive SMTP messages fromother messaging servers.

Setting up SMTP Archiving

Reviewing the default settings for the siteWhat next?

182

Clustering Enterprise Vaultwith VERITAS Cluster Server

■ Introducing clustering with VCS

■ Installing and configuring VERITAS Storage Foundation HA

■ Configuring the service group

■ Running the Enterprise Vault Configuration wizard

■ Implementing an SFW HA-VVR disaster recovery solution

■ Troubleshooting clustering with VCS

5Section

Introducing clustering withVCS


■ Supported VCS configurations and software

■ About the VCS GenericService agent

■ Typical Enterprise Vault configuration in a VCS cluster

■ Installation order

Supported VCS configurations and softwareBoth active/passive and N+1 configurations are supported, but active/activeconfigurations are not.

In an active/passive configuration, a dedicated spare server is available for eachEnterprise Vault server, ready and waiting for the primary server to go down. Inan N+1 configuration, there is a computer for each Enterprise Vault server andthen one or more spare servers waiting for any of the active servers to fail over.

The following software must be installed:

■ VERITAS Storage Foundation HA for Windows, version 4.3 MP1 or later

■ Enterprise Vault


Note that Compliance Accelerator and Discovery Accelerator are not supportedwithin a cluster. However, an unclustered Compliance Accelerator or DiscoveryAccelerator can reference a clustered Enterprise Vault virtual server.

24Chapter

About the VCS GenericService agentVCS uses the GenericService agent to monitor the Enterprise Vault services ondifferent nodes based on the information in the Enterprise Vault Directorydatabase.

The agent brings online the following services, monitors their status, and takesthem offline:

■ Admin service

■ Directory service

■ Indexing service

■ Shopping service

■ Storage service

■ Task Controller service

See the VERITAS Cluster Server Bundled Agents Reference Guide for detailedinformation on the GenericService agent, including the resource type definitions,attribute definitions, and sample configurations.

The GenericService agent detects an application failure if a configured service isnot running. When this happens, the Enterprise Vault service group is failed overto the next available system in the service group’s system list, and the servicesare started on the new system. This ensures continuous availability for the datathat Enterprise Vault is managing and archiving.

Typical EnterpriseVault configuration in aVCS clusterFigure 24-1 illustrates a typical configuration.

Introducing clustering with VCSAbout the VCS GenericService agent

186

Figure 24-1 Active/passive failover configuration

VCS private network

Shared disks/cluster disk groups

System 1 System 2

EnterpriseVault data

Public network

SQL Server

Here, the volumes for the Enterprise Vault services data are configured in a clusterdisk group on shared storage. The Enterprise Vault virtual server is configuredon the active node (System 1). If System 1 fails, System 2 becomes the active node,and the Enterprise Vault virtual server comes online on System 2.

Installation orderThe order in which you install and configure the various components in a clusteredenvironment is important, as follows:

■ Ensure that all prerequisite components have been installed on each of thecluster nodes

■ Complete the installation and configuration of VERITAS Storage FoundationHA with VCS

■ Install Enterprise Vault Server components on all the nodes in the cluster

■ Configure disk groups and volumes

■ Configure the Enterprise Vault service group

■ Run the Enterprise Vault cluster configuration wizard

■ Test that the nodes in the cluster fail over correctly

187Introducing clustering with VCSInstallation order

Introducing clustering with VCSInstallation order

188

Installing and configuringVERITAS StorageFoundation HA


■ About this chapter

■ Installing and configuring SFW HA

■ Managing disk groups and volumes

About this chapterThis chapter outlines the steps required to install and configure VERITAS StorageFoundation HA for Windows (SFW HA) with Enterprise Vault.

You can also implement a disaster recovery solution.

See “About the SFW HA-VVR disaster recovery solution” on page 213.

Installing and configuring SFW HAExcept where noted, you can get detailed instructions on how to perform the stepsoutlined in this section from theVERITASStorageFoundationandHighAvailabilitySolutions Guide.

To install and configure SFW HA

1 Install SFW HA 4.3 or later on each node that is to be a part of the cluster.There are several stages to this process:

25Chapter

■ Review the product installation requirements, disk space requirements,and requirements for SFW HA.

■ Configure the network and storage.

■ Install SFW HA.

2 If you have installed SFW HA 4.3, upgrade to 4.3 MP1. For detailedinstructions, see the VERITAS Storage Foundation and High AvailabilitySolutions 4.3 Maintenance Pack (MP) 1 Release Notes.

3 Configure the cluster by running the VCS Configuration wizard.

4 Install Enterprise Vault on all systems in the cluster.

5 Configure the disk group and volumes from the first node.

You must create shared volumes to store the following:

■ Indexing service data

■ Shopping service data

■ Vault store partitions

■ PST holding folders

■ EMC Centera staging areas

We also recommend that you create separate volumes to store the MSMQand registry replication data.

6 Mount the volumes on the system where you will configure the EnterpriseVault service group.

See “Managing disk groups and volumes” on page 190.

7 Configure the Enterprise Vault service group.

See “About configuring the service group” on page 193.

8 Run the Enterprise Vault Configuration wizard to create the Enterprise Vaultservices and resources.

See “About the Enterprise Vault Configuration wizard” on page 199.

9 Verify the cluster configuration and test the failover capability.

Managing disk groups and volumesThis section describes how to perform the following activities:

■ Importing a dynamic disk group

■ Mounting a shared volume

Installing and configuring VERITAS Storage Foundation HAManaging disk groups and volumes

190

■ Unmounting a volume and deporting a disk group

While you set up an SFW HA environment, keep the following points in mind:

■ You must mount the volumes on the system where you will configure theEnterprise Vault service group.

■ When a disk group is initially created, it is imported on the node where it iscreated.

■ A disk group can be imported on one node only at a time.

■ To move a disk group from one node to another, unmount the volumes in thegroup, deport the group from its current node, import it to a new node, andmount the volumes.

To import a dynamic disk group

1 Start the VERITAS Enterprise Administrator.

2 Right-click a disk name in the dynamic disk group or the dynamic disk groupname in the tree view, and then click Import DynamicDiskGroup on thecontext menu.

3 Follow the on-screen instructions.

To mount a volume

1 If you have yet to do so, open the VERITAS Enterprise Administrator andimport the dynamic disk group.

2 Right-click the volume, and then click File System>ChangeDrive Letterand Path.

3 In the Drive Letter and Paths dialog box, click Add.

4 Select one of the following options, depending on whether you want to assigna drive letter to the volume or mount it as a folder.

Click Assign aDrive Letter, and then choose therequired letter.

To assign a drive letter.

Click Mount as an emptyNTFS folder, and then clickBrowse to locate an empty folder on the shared disk.

To mount the volume as afolder.

5 Click OK.

To unmount a volume and deport the dynamic disk group

1 In the VERITAS Enterprise Administrator, right-click the volume and thenclick File System>ChangeDrive Letter and Path.

2 In the Drive Letter and Paths dialog box, click Remove.

191Installing and configuring VERITAS Storage Foundation HAManaging disk groups and volumes

3 Click OK.

4 Right-click the disk, and then click Deport DynamicGroup.

5 Click Yes to confirm that you want to deport the disk group.

Installing and configuring VERITAS Storage Foundation HAManaging disk groups and volumes

192

Configuring the servicegroup


■ About configuring the service group

■ Before you begin

■ Creating a service group

■ Modifying an existing service group

■ Deleting a service group

About configuring the service groupIn VCS, a service group represents a virtual server. Each service group containsa set of resources, which you can bring online or offline when a group fails overto another node in the cluster. You can arrange a combination of these resourcesto make a complete Enterprise Vault server.

These resources include the following:

■ IP address

■ Computer name (Lanman resource)

■ MSMQ

■ Disk/storage (MountV and DiskGroup resources)

■ Service resources

Before you can configure Enterprise Vault in a cluster, you must configure aservice group to represent the Enterprise Vault server. VCS provides several ways

26Chapter

to configure a service group, including the Enterprise Vault Cluster Setup wizard,Cluster Manager (both Java Console and Web Console), and the command line.This chapter describes how to configure a service group with the Enterprise VaultCluster Setup wizard.

Before you beginBefore you configure an Enterprise Vault service group, do the following:

■ Verify your DNS server settings. You must ensure that a static DNS entry mapsthe virtual IP address with the virtual server name. Refer to the appropriateDNS document for more information.

■ Verify that the Command Server is running on all systems in the cluster.

■ Verify that the VERITAS High Availability Daemon (HAD) is running on thesystem from where you will run the Enterprise Vault Cluster Setup wizard.

■ Ensure that you have Cluster Administrator privileges. You must also be aLocal Administrator on the node where you run the wizard.

■ Verify that MSMQ is installed locally on each node.

■ Mount the shared volumes that you have created to store the following:






Unmount the volumes from other nodes in the cluster.

Creating a service groupNote that the Enterprise Vault Cluster Setup wizard is available from the WindowsStart menu if you install Enterprise Vault after you install VCS. If you installEnterprise Vault first, you must separately install the wizard. To do this, locateand run the file Enterprise Vault Cluster Setup Wizard.msi.

To create the service group

1 Start the Enterprise Vault Cluster Setup Wizard.

2 Review the information in the Welcome page, and then click Next to displaythe Wizard Options page.

Configuring the service groupBefore you begin

194

3 Click Create service group, and then click Next to display the Service GroupConfiguration page.

4 In the ServiceGroupName box, type a name for the group, such as EVGRP1.

5 Move to the SystemsinPriorityOrder box those systems on which you wantto configure the service group.

If you want to change the priority of the systems in the Systems in PriorityOrder box, click a system and then click the up-arrow or down-arrow button.

6 Click Next to validate the configuration and display the Virtual ServerConfiguration page.

7 Complete the fields by following these steps in the order listed:

■ In the Virtual ServerName box, type the server name that you mappedto the virtual IP address when you set up the static DNS entry.

■ In the Virtual IP address box, type the address that you mapped to thevirtual server. This should be in the same subnet as the current computer,but it should not currently be in use on the network.

■ Enter the subnet mask to which the virtual server belongs.

■ For each system in the cluster, select the public network adapter name.The wizard lists all the TCP/IP-enabled adapters on the system, includingthe private network adapters if they are TCP/IP enabled. Be sure to selectthe adapters to assign to the public network, and not those assigned tothe private network.

■ Click Advanced to specify details for the Lanman resource.You must select the distinguished name of the organizational unit for thevirtual server. By default, the Lanman resource adds the virtual server tothe default container Computers.The user account for VCS Helper service must have adequate privilegeson the specified container to create and update computer accounts.

8 In the Virtual Server Configuration page, clickNext to display the MSMQ andRegRep Directory Details page.

This page enables you to virtualize the MSMQ resource so that it can beaccessed using its virtual name. This resource also ensures that the queuestate is maintained after failover.

9 Complete the fields as follows:

■ In the MSMQDirectory field, enter the path to the required directory.

195Configuring the service groupCreating a service group

■ In theReplicationDirectory field, enter the path to the registry replicationdirectory. The replication data contains a list of the registry keys toreplicate.

We recommend that you configure the MSMQ and replication directories ondifferent volumes.

10 Click Next to display the Storage Location Details page.

This page lets you select the volumes that you want to configure for EnterpriseVault services.

A volume is available for selection only if you have configured it on the shareddisk. The available volumes do not include those that you selected in theprevious page of the wizard, when specifying the storage locations for MSMQand registry replication.

11 In the Available Volumes box, select each volume on which you haveconfigured the services and then click the right-arrow button to move it tothe Selected Volumes box. You must select the volumes that you configuredfor each of the following:






12 Click Next to display the Service Group Summary page.

13 Review your configuration. If you want to modify an attribute name for anyreason, follow these steps in the order listed:

■ Click the resource, and then click the attribute that you want to modify.

■ Click the Edit icon at the end of the table row.

■ In the Edit Attribute dialog box, enter the attribute values.

■ Click OK.

■ Repeat the procedure for each resource and attribute.

14 Click Next to display the Completion page.

15 Click Bring the service group online, and then click Finish.

When you have finished adding the service group, check that it can fail overbetween nodes without error.

Configuring the service groupCreating a service group

196

Modifying an existing service groupTable 26-1 lists the items that you can modify in a service group.

Table 26-1 Modifiable service group items

NotesItem

You can add nodes to or remove them from the cluster. If you want toremove a node, make sure that it is not the active one.

System list

You can add or remove volumes. If you remove a volume on which anEnterprise Vault service is configured, the service ceases to be highlyavailable and is not monitored.

Volumes

You can change the virtual IP address if the service group is offline.You cannot change the virtual server name, which is fixed when youcreate the service group.

Virtual IP

You can modify an Enterprise Vault service group in several ways, including theEnterprise Vault Cluster Setup Wizard, Cluster Manager (both Java Console andWeb Console), and the command line. The following steps describe how to modifythe service group with the Enterprise Vault Cluster Setup Wizard.

Before you proceed, note the following:

■ You must run the wizard from a node on which the service group is online.You can then use the wizard to add resources to or remove them from theconfiguration.

■ You must take the service group partially offline to change the resourceattributes. However, the MountV and VMDg resources for the service groupshould be online on the node where you run the wizard and offline on all othernodes. Mount all the volumes created to store Storage service data (vaultstores), registry replication information, Shopping service data, Indexing dataand MSMQ data.

■ If you want to modify the system list or volumes, the service group must beonline.

To modify an existing service group

1 Start the Enterprise Vault Cluster Setup Wizard.


197Configuring the service groupModifying an existing service group

3 Click Modify service group, and then click Next.

4 Follow the instructions to modify the service group.

Note that if you add a system to an online service group, any resources withlocal attributes may briefly have a status of UNKNOWN. After you add thenew node to the group, run the Enterprise Vault Configuration Wizard onthis node to configure the Enterprise Vault services for it.

Deleting a service groupFollow the steps below to delete a service group with the Enterprise Vault ClusterSetup wizard.

To delete an Enterprise Vault service group

1 On the Windows Start menu, click All Programs >VERITAS >VERITASCluster Server > Enterprise Vault Cluster SetupWizard.


3 Click Delete service group, and then click Next.

4 In the Service Group Summary page, click Next.

5 When the wizard prompts you to confirm that you want to delete the servicegroup, click Yes.

6 Click Finish.

Configuring the service groupDeleting a service group

198

Running the EnterpriseVault Configuration wizard


■ About the Enterprise Vault Configuration wizard

■ Before you begin

■ Setting up an active/passive configuration

■ Setting up an N+1 configuration

About the Enterprise Vault Configuration wizardThe Enterprise Vault Configuration wizard provides options for setting upEnterprise Vault in a cluster. This chapter describes the options that you mustselect to do this.

Before you beginBefore you run the Enterprise Vault Configuration wizard, ensure the following:

■ The Enterprise Vault service group exists and is online on the node from whichyou want to run the wizard.See “About configuring the service group” on page 193.

■ You have installed SFW HA 4.3 MP1 or later.

27Chapter

Setting up an active/passive configurationAs well as describing how to set up cluster support in a first-time installation ofEnterprise Vault, this section describes how to upgrade an existing, standardinstallation of Enterprise Vault to a clustered environment.

Adding cluster support in a first-time Enterprise Vault installationYou must run the Enterprise Vault Configuration wizard on each node of thecluster. On the first node, choose the option to create a new Enterprise Vaultserver with cluster support. On each additional node, choose the option to addthis node as a failover node for an existing clustered server.

Note: If during the running of the configuration wizard you receive an error relatedto the configuring of the Enterprise Vault Monitoring database, complete theconfiguration wizard and refer to Troubleshooting configuration of the Monitoringdatabase.

To create a new Enterprise Vault server with cluster support

1 On the Windows Start menu, click All Programs > Enterprise Vault >Enterprise Vault Configuration).

The first page of the wizard appears.

2 Click Create a newEnterprise Vault serverwith cluster support, and thenclick Next.


When the wizard prompts you for the computer DNS alias, enter anunqualified DNS alias that points to the virtual server name.

In addition, take care to review the storage locations for the Indexing andShopping services, when the wizard prompts you to do so.

4 In the Finish page, clickBringall theresourcesonline, and then clickFinish.

5 After you have configured the server on the first node, run the wizard fromeach additional node that you want to configure as a failover node.

Note that the path to the Enterprise Vault program folder must be the sameon all nodes in the cluster. This is typically C:\Program Files\Enterprise

Vault. If the path varies from one node to another, problems can occur duringfailover.

Running the Enterprise Vault Configuration wizardSetting up an active/passive configuration

200

To add a failover node for an existing clustered server

1 On the Windows Start menu, click All Programs > Enterprise Vault >Enterprise Vault Configuration.

2 Click Add this node as a failover node for an existing clustered server, andthen click Next.


When the wizard prompts you for the name of the service group to whichyou want to add the node, select the name of the service group that you chosefor the first node.

4 In the summary page, review the information, and then click Next.

The wizard informs you that it will create the Enterprise Vault service groupon the new node.

5 In the Finish page, click Finish to exit the wizard.

6 Check that you can bring the resources online on the failover node. You cando this with Cluster Explorer, by clicking Switch To on the context menu.

Troubleshooting configuration of the Monitoring databaseIf during the running of the configuration wizard you receive errors indicatingthat configuring of the Enterprise Vault Monitoring database has failed, completethe configuration wizard and then run the Monitoring Configuration Utility toconfigure the Monitoring database and the Monitoring agents manually.

For information on how to do this, see the following Enterprise Vault TechNoteon the Symantec Support Web site: http://entsupport.symantec.com/docs/287449.

201Running the Enterprise Vault Configuration wizardSetting up an active/passive configuration



Upgrading an existing Enterprise Vault installation to a clusterThere are two types of Enterprise Vault installation that you can upgrade to acluster: a single, non-clustered Enterprise Vault server, and a building blocksconfiguration that contains multiple Enterprise Vault servers. To be eligible forupgrade to a cluster, the Enterprise Vault installation must have the followingfeatures:

■ Enterprise Vault should already be configured in a non-clustered configuration,and it must not already be part of a cluster.

■ Enterprise Vault servers must be configured using unqualified DNS aliasesrather than fully qualified names.

■ The Enterprise Vault server must have a full set of Indexing, Shopping, TaskController and Storage services. However, it must not contain the SharePointPortal Server 2001 service, as this is not supported in a cluster.

■ In a building blocks environment, an Enterprise Vault server that is hostingservices must not be running in failover mode.

To upgrade an existing installation to a clustered Enterprise Vault environment

1 Run the Enterprise Vault Cluster Setup wizard to create an Enterprise Vaultcluster service group and add to the group the server that you are going toconfigure.

2 Ensure that the following items are all on highly-available shared storagedevices.






If they are not, correct the locations in the Enterprise Vault Directory databaseand then move the associated data to the new locations.

See “Moving data to highly-available locations” on page 203.

3 On the WindowsStartmenu, clickAllPrograms>EnterpriseVault>Convertto Cluster.

4 Read the introductory information, and then click Next.


202

5 When the following page appears, check All locations are highly availablestorage devices, and then click Next.

6 If the wizard detects that there are messages in the Enterprise Vault MSMQqueues, choose whether to proceed with the conversion without migratingthem to the clustered MSMQ queues.

Wait until the queues have cleared and then rerun the Convert to Clusterwizard. Any messages that are still in the queues are ignored in the newcluster. To accelerate the process of clearing the queues, stop the TaskController service and ensure that File System Archiving is not performingan archiving run.

7 When the wizard prompts you to choose a service group in which to createthe cluster resources for each Enterprise Vault service, select the group thatyou created earlier.

8 Click Next to create the cluster resources, and then review the list of actionsthat the wizard has carried out.

9 Click Finish to close the wizard.

10 Using the DNS snap-in to the Microsoft Management Console (MMC), changethe computer name alias to point to the virtual server name rather than thelocal name.

11 Use VERITAS Cluster Manager to bring the resources in the cluster online.

Moving data to highly-available locationsIn outline, the procedure for moving the data to highly-available locations is asfollows:

■ Stop the Indexing, Shopping, Storage, and Task Controller services.

■ Make a backup copy of the Enterprise Vault Directory database and data files.

■ Use the Vault Administration Console or run a SQL query against the EnterpriseVault directory to move the data, as described below.


■ Move the contents of this location to a highly availablelocation.

■ Update the database using SQL to point at the newlocation.

The SQL to view the current location is as follows:

SELECT *FROM IndexRootPathEntryWHERE (IndexRootPathEntryId = '<ID FROMLOG FILE>')

The SQL to update the location is as follows:

UPDATE IndexRootPathEntrySET IndexRootPath = '<THE NEW LOCATION>'WHERE (IndexRootPathEntryId = '<ID FROMLOG FILE>')

IndexRootPathEntry[IndexRootPath]

■ Move the pool entry authorization (.pea) file to a highlyavailable location.

■ Use the Vault Administration Console to view theproperties of the EMC Centera partition and then, on theConnection tab, edit the Pool Entry Authorization FileLocation box to point at the new location.

PartitionEntry[AccountName]




SELECT *FROM PartitionEntryWHERE (PartitionEntryId = '<ID FROM LOGFILE>')


UPDATE PartitionEntrySET PartitionRootPath = ‘<THE NEWLOCATION>’WHERE (PartitionEntryId = '<ID FROM LOGFILE>')

PartitionEntry [PartitionRootPath]


204

■ Move the secondary storage files to a highly availablelocation.



SELECT *FROM PartitionEntryINNER JOIN Locations ONPartitionEntry.SecondaryLocation =Locations.LocationIdentityWHERE (PartitionEntry.PartitionEntryId =‘<ID FROM LOG FILE>')


UPDATE LocationsSET Location = '<NEW LOCATION>'WHERE LocationIdentity =(SELECT SecondaryLocation FROM PartitionEntryWHERE PartitionEntryId = ‘<ID FROM LOGFILE>')

PartitionEntry/Locations[SecondaryLocation]






UPDATE PartitionEntrySET StagingRootPath = ‘<THE NEW LOCATION>’WHERE (PartitionEntryId = '<ID FROM LOGFILE>')

PartitionEntry [StagingRootPath]


1 Move the contents of the location to a highly availablelocation.

2 Use the Vault Administration Console to view theproperties of the PST Migrator Task and update theTemporary files folder.

PSTMigratorTask [MigrationDirectory]


■ Use the Vault Administration Console to edit theShopping service location to the new highly availablelocation.

ShoppingServiceEntry[ShoppingRootPath]

■ Move the contents of the location to a highly availablelocation.

■ Use the Vault Administration Console to view the siteproperties and update the PST Holding Folder propertyto point at the new location.

SiteEntry [PSTHoldingDirectory]

Setting up an N+1 configurationAs a cheaper alternative to setting up an active/passive cluster, you can set up anN+1 configuration in which there is a single spare node for the cluster.

There are two basic types of N+1 configurations:

■ The clustered Enterprise Vault servers run on two nodes, and there is a sharedspare node.

■ The two Enterprise Vault servers are configured to run on any of the threenodes in the cluster.

The following sections describe how to set up Enterprise Vault in these twoconfigurations.

N+1 configuration option 1Figure 27-1 illustrates a configuration in which there is a spare node in additionto the two nodes on which the Enterprise Vault servers are running.

Running the Enterprise Vault Configuration wizardSetting up an N+1 configuration

206

Figure 27-1 N+1 configuration option 1

NODEAEVSERVER1

NODEB(EVSERVER2)

NODEC(SPARE)

Shared Disk

Shared Disk

You configure the service group for EVSERVER1 to run on both NODEA andNODEC, and the service group for EVSERVER2 to run on both NODEB and NODEC.EVSERVER1 and EVSERVER2 are both virtual computer names from the servicegroup.

To set up this N+1 configuration



2 On either NODEA or NODEC, run the Enterprise Vault Cluster Setup wizardand create a service group called EVSERVER1 for these two nodes.

3 On either NODEB or NODEC, run the Enterprise Vault Cluster Setup wizardand create a service group called EVSERVER2 for these two nodes.

207Running the Enterprise Vault Configuration wizardSetting up an N+1 configuration

4 Take the actions described below on NODEA and NODEB, depending onwhether you are performing a first-time installation of Enterprise Vault orupgrading an existing installation.

Upgrade installationNew installationNode

Run the Convert to Cluster wizard.Choose to create the service resourcesin the EVSERVER1 service group.

Run the Enterprise VaultConfiguration wizard. Choose toconfigure a new Enterprise Vaultserver with cluster group forEVSERVER1.

NODEA



NODEB

5 On NODEC, run the Enterprise Vault Configuration wizard and choose to addthis node as a failover node for an existing clustered server. Select eitherservice group.

When you bring the service groups online on NODEA and NODEB, ClusterExplorer may falsely indicate a problem with the GenericService resources(their icons in the left pane may have question marks). This is because VCSassumes that each resource is simultaneously online on two nodes. You canignore this situation.

N+1 configuration option 2The second option involves configuring both EVSERVER1 and EVSERVER2 to runon any of three nodes. This has the advantage that if NODEB fails, the servermoves to NODEC. NODEB can then be brought back online and act as a failoverserver for EVSERVER1 and EVSERVER2.


208

Figure 27-2 N+1 configuration option 2

NODEA

NODEB NODEC

Shared Diskfor EVSERVER1


To set up this N+1 configuration



2 With the Enterprise Vault Cluster Setup wizard, create a service group forEVSERVER1 that contains nodes NODEA, NODEB, and NODEC.

3 With the Enterprise Vault Cluster Setup wizard, create a service group forEVSERVER2 that contains nodes NODEA, NODEB, and NODEC.


4 Take the actions described below on NODEA and NODEB, depending onwhether you are performing a first-time installation of Enterprise Vault orupgrading an existing installation.

Upgrade installationNew installationNode



NODEA



NODEB

5 On NODEC, run the Enterprise Vault Configuration wizard and choose to addthis node as a failover node for an existing clustered server. Select eitherservice group.

Notice that the only difference in configuration between this option andoption 1 is that, when you create the service groups, you must select all thenodes rather than a subset of the nodes.

You can take a similar approach if you require your system to have more thanone spare server (N+2, N+3, N+4, and so on). In each case, you must configurea node for each Enterprise Vault server and then add the spare nodes asfailover nodes.

Disallowing two Enterprise Vault servers on the same nodeYou cannot run multiple Enterprise Vault service groups on the same node in acluster. When configuring the cluster in an N+x configuration, you can stop thisfrom happening by setting the Limits and Prerequisites attributes for every node,as described below.

For more information on these steps, see the VERITAS Cluster ServerAdministrator’s Guide.

To prevent two Enterprise Vault servers from running on the same node

1 Use VERITAS Cluster Manager to log on to the cluster.

2 Click anywhere in the Cluster Monitor panel to open Cluster Explorer.

3 For each node in the cluster, perform the following steps in the order listed:


210

In the configuration tree at the left, click the node whose attributes youwant to edit.

■

■ In the View panel, click the Properties tab.

■ Click Show all attributes to open the Attributes View dialog box.

■ Find the Limits attribute.

■ Click the Edit icon at the right of the row.

■ In the Edit Attribute dialog box, add a key called EnterpriseVault andgive it a value of 1.

■ Click OK to close the dialog box and return to the Attributes View dialogbox.

■ Repeat for the Prerequisites attribute on each Enterprise Vault servicegroup.

When both the Limits and Prerequisites attributes have a key calledEnterpriseVault with a value of 1, two Enterprise Vault servers cannot runon the same node.



212

Implementing an SFWHA-VVR disaster recoverysolution



■ About the SFW HA-VVR disaster recovery solution

About this chapterThis chapter describes how to install and configure SFW HA-VVR with EnterpriseVault. The steps are similar to those documented in the VERITAS StorageFoundation and High Availability Solutions Guide.

About the SFW HA-VVR disaster recovery solutionIn this scenario,there is a source host on the primary site and a destination hoston the secondary site. The application data is stored on the primary site andreplicated to the secondary site by using the VERITAS Volume Replicator (VVR).The primary site provides data and services during normal operation. If a disasteroccurs on the primary site and its data is destroyed, a secondary host can takeover the role of the primary host to make the data accessible. The application canbe restarted on that host.

Figure 28-1 shows an SFW HA-VVR configuration.

28Chapter

Figure 28-1 SFW HA-VVR configuration

Data

Secondary site

DB Log

Original VolumesReplicatorLog

Data

Replicated VolumesReplicatorLog

Primary Site

System1 System2 System1 System2

Internet

DB Log

This example has one disk group on each site for the application. Note that a VVRreplicator log is needed on each site. If there are multiple disk groups, an additionalreplicator log is required for each one.

Installing and configuring SFW HA-VVRTo install and configure SFW HA-VVR, complete the following tasks in the orderspecified:

■ Set up the cluster on the primary site.

■ Set up the cluster on the secondary site.

■ Add the VVR components for replication.

■ Add the Global Cluster Option (GCO) components for wide-area recovery.

The following sections describe these tasks in detail.

Implementing an SFW HA-VVR disaster recovery solutionAbout the SFW HA-VVR disaster recovery solution

214

Setting up the cluster on the primary siteComplete the following steps to set up the cluster on the primary site. Exceptwhere noted, you can obtain more information on how to perform these stepsfrom the VERITAS Storage Foundation and High Availability Solutions Guide.

To set up the cluster on the primary site

1 Install SFW HA 4.3 or later on each node that is to be a part of the cluster onthe primary site. There are several stages to this process:

■ Review the product installation requirements, disk space requirements,and requirements for SFW HA.

■ Install Windows and configure the network settings.

■ Install SFW HA on the primary site. Be sure to select the VVR and GCOoptions during the installation.

■ Using the VVR Security Service Configuration wizard, configure theVERITAS Volume Replicator Security Service (VxSAS).



4 Install Enterprise Vault.

5 Configure the disk group and volumes. You must create shared volumes tostore the following:






We also recommend that you create separate volumes to store the MSMQand registry replication data.

6 Configure the VCS service group at the primary site.

See “About configuring the service group” on page 193.

See “About the Enterprise Vault Configuration wizard” on page 199.

7 Verify the cluster configuration, and test the failover capability.

215Implementing an SFW HA-VVR disaster recovery solutionAbout the SFW HA-VVR disaster recovery solution

Setting up the cluster on the secondary siteThe process of setting up a cluster on the secondary site is similar to that on theprimary site. Except where noted, you can obtain more information on how toperform these steps from the VERITAS Storage Foundation andHigh AvailabilitySolutions Guide.

To set up the cluster on the secondary site

1 Create a parallel environment on the secondary site.



4 Install Enterprise Vault.

5 Configure the disk groups and volumes on the secondary site.

The disk group and volume setup on the secondary site must be identical tothat on the primary site. The disks, disk groups, and volumes must be thesame sizes, have the same names, and must be of the same type.

6 Configure the VCS service group at the secondary site, taking care to specifythe same service group name that you specified on the primary site.

7 Verify the cluster configuration, and test the failover capability.

Adding the VVR components for replicationThis section provides information on configuring the VVR components forreplication. You can obtain more information on how to perform these steps fromthe VERITAS Storage Foundation and High Availability Solutions Guide.

To add the VVR components for replication

1 Create a replicator log volume at each site.

2 Set up the replicated data sets for VVR on the hosts for the primary andsecondary sites. Note that the Setup Replicated Data Set wizard lets youconfigure replicated data sets for both sites.

3 Create the VVR RVG service group.

You must run the Volume Replicator Agent Configuration wizard from thesystem that contains the application service group.


216

Adding the GCO components for wide-area recoveryYou require the Global Cluster Option (GCO) components to manage globalclustering for wide-area disaster recovery. For information on how to performthe steps below, see the VERITAS Storage Foundation and High AvailabilitySolutions Guide.

To add the GCO components for wide-area recovery

1 Ensure that your environment meets the requirements for global clusteroperations.

2 Link clusters by adding a remote cluster.

3 Convert the local service group to a global group.

4 Perform additional global cluster administration tasks.

217Implementing an SFW HA-VVR disaster recovery solutionAbout the SFW HA-VVR disaster recovery solution


218

Troubleshooting clusteringwith VCS


■ VCS logging

■ Enterprise Vault Cluster Setup wizard error messages

■ Viewing the clustered message queues

VCS loggingVCS generates two error message logs: the engine logs and the agent logs. Log filenames are appended by letters, where A indicates the first log file, B the second,C the third, and so on; for example, agent_A.txt.

The agent log is located at %VCS_HOME%\log (typically c:\Program

Files\VERITAS\cluster server\log). The format of agent log messages is asfollows:

Timestamp Mnemonic Severity Message_ID Message_Text

where:

Shows the date and time when the message was logged.Timestamp

Identifies the product (for example, VCS).Mnemonic

Indicates the severity of the error, which can be CRITICAL, ERROR,WARNING, NOTICE, or INFO. CRITICAL messages are the most severe,whereas INFO messages are the least severe.

Severity

29Chapter

Is the unique numeric ID of the error message. The prefix V-16 denotesVCS.

Message_ID

Is the message generated by VCS.Message_Text

For example, a typical agent log message looks like this:

2006/01/24 11:04:17 VCS ERROR V-16-10051-6026 GenericService:

CLSEV1-EnterpriseVaultAdminService:monitor:

The LanmanResName attribute has not been configured.

Enterprise Vault Cluster Setupwizard errormessagesTable 29-1 describes some messages that you may see when you run the EnterpriseVault Cluster Setup wizard.

Table 29-1 Enterprise Vault Cluster Setup wizard error messages

ExplanationMessage

Only users who are members of the localadministrator’s group can run this wizard.

Access Denied. You must have Administratorprivileges to run the wizard.

Verify that the VCS service has started andis running on the local machine.

VCS not running on the local machine. Eitherthe service has not been started or it is in astale state.

The wizard verifies that MSMQ is installedand configured on all the nodes. The errormessage is shown if MSMQ is not installedon one node or the configuration is different.

To resolve the problem, verify that MSMQhas been installed and configured beforeproceeding with the Enterprise Vault ClusterSetup wizard.

MSMQ is not configured properly.

The wizard verifies that the MSMQ resourcetype is installed on the system. This resourcetype is installed with the 4.3 MP1.

The required resource type MSMQ is notinstalled on this system.

Troubleshooting clustering with VCSEnterprise Vault Cluster Setup wizard error messages

220

Viewing the clustered message queuesIn a clustered Enterprise Vault installation the Computer Management snap-indoes not show Enterprise Vault message queues by default: it shows only queuesfor the local computer.

To view the clustered message queues for an Enterprise Vault virtual server

1 Ensure the Enterprise Vault virtual server is online on the node you want toview the queues from.

2 Open a command prompt window and change to the Enterprise Vaultinstallation folder, typically C:\Program Files\Enterprise Vault.


ClusterCompMgmt

This launches the Computer Management snap-in with the environmentvariables set so that it displays the clustered message queues.

4 Expand Services andApplications, then expand MessageQueuing. TheEnterprise Vault virtual server queues are listed under Private Queues.

221Troubleshooting clustering with VCSViewing the clustered message queues

Troubleshooting clustering with VCSViewing the clustered message queues

222

Clustering Enterprise VaultwithMicrosoft server clusters

■ Introducing clustering with Microsoft server clusters

■ Preparing to cluster with Microsoft server clusters

■ Configuring Enterprise Vault in a Microsoft server cluster

■ Troubleshooting clustering with Microsoft server clusters

6Section

Introducing clustering withMicrosoft server clusters


■ About clustering with Microsoft server clusters

■ Note on clustering terminology for Windows 2008 users

■ Supported cluster configurations

■ Required software and restrictions

■ Typical Enterprise Vault configuration in a Microsoft server cluster

■ Control of services in a clustered environment

About clustering with Microsoft server clustersYou can cluster Enterprise Vault in a Microsoft server cluster on Windows2003/2008 Enterprise or Datacenter Edition, to provide a high availability solutionfor Enterprise Vault. If you are setting up Enterprise Vault in an environmentwhere Microsoft Exchange and SQL server are clustered, you may want to clusterEnterprise Vault to ensure that you can meet your service level agreements,recovery times, and recovery point objectives.

High availability is provided by creating an Enterprise Vault virtual server thatcan fail over between physical nodes in the cluster. When Enterprise Vault servicesare running on a virtual server they operate with virtual IP addresses, a virtualcomputer name, virtual Microsoft Message Queues, and highly available shareddisks. When a failure occurs, the cluster software can move the virtual server’sresources to a different physical node in the cluster.

30Chapter

To cluster Enterprise Vault in a Microsoft server cluster, you need a workingknowledge of Microsoft server clusters. For detailed information on Microsoftserver clusters, see your Microsoft documentation.

Note on clustering terminology for Windows 2008users

With Windows 2008, Microsoft has changed the terminology with which it refersto some important parts of clustering.

Table 30-1 shows the terms that are used in Windows 2003 clustering and theirWindows 2008 counterparts. This manual uses the Windows 2003 terminologythroughout.

Table 30-1 Windows 2003/2008 terminology

Windows 2008 termWindows 2003 term

ClusterCluster Group

Microsoft Failover ClusterMicrosoft Server Cluster

Client Access PointNetwork Name

Storage DevicePhysical Disk

Service or ApplicationResource Group

Supported cluster configurationsAn Enterprise Vault cluster consists of:

■ One or more primary nodes, each normally hosting an Enterprise Vault virtualserver.

■ One or more failover nodes: standbys that can take over the job of hosting anEnterprise Vault virtual server if a primary node fails.

Enterprise Vault does not permit "active/active" cluster configurations. That is,only one Enterprise Vault virtual server can run on a clustered node at any onetime. You can configure Enterprise Vault in any operation mode that adheres tothis restriction, such as:

■ An active/passive failover pair: a primary node with a dedicated failover node.

■ N+1 (hot standby server): two or more primary nodes share a single failovernode. Only one node failure can be accommodated at any one time.

Introducing clustering with Microsoft server clustersNote on clustering terminology for Windows 2008 users

226

■ N+M: an extension of the hot standby concept with N primary nodes and Mfailover nodes. Only M node failures can be accommodated at one time.

■ N+M ‘any-to-any’: identical to N+M, except that there is no need to fail backto the original node after a failover. When the original node becomes availableagain, it can operate as a failover node.

Required software and restrictionsYou must install Windows Server 2003/2008 Enterprise Edition or DatacenterEdition on each primary and failover node. Each node must be running the sameoperating system.

Note the following restrictions:

■ A clustered Enterprise Vault server cannot contain the SharePoint PortalServer 2001 Service. However, SharePoint 2003 runs as an Enterprise Vaulttask and is unaffected by this restriction.

■ Compliance Accelerator and Discovery Accelerator are not supported withina cluster. However, an unclustered Compliance Accelerator or DiscoveryAccelerator can reference a clustered Enterprise Vault virtual server.

Clustering existing Enterprise Vault installationsIf you have an existing Enterprise Vault 7.0 or later installation then, subject tocertain restrictions, you can use the Enterprise Vault Convert to Cluster wizardto convert the Enterprise Vault servers to servers with cluster support. Theconversion requires you to move the Enterprise Vault data manually to highlyavailable locations.

See “Converting an existing Enterprise Vault installation to a cluster” on page 246.

Typical Enterprise Vault configuration in a Microsoftserver cluster

Figure 30-1 illustrates a typical configuration.

227Introducing clustering with Microsoft server clustersRequired software and restrictions

Figure 30-1 Enterprise Vault in an active/passive failover pair configuration

Shared storage

NODEA NODEB

EnterpriseVault data

Public network

Private cluster network

SQL Server

In this example:

■ NODEA and NODEB are the two Enterprise Vault nodes in the Microsoft servercluster. NODEA is the primary node. NODEB is the failover node.

■ The SQL server and Microsoft Exchange may also be configured in the cluster:this does not affect Enterprise Vault.

■ The volumes for the Enterprise Vault services data are configured on sharedstorage.

■ The Enterprise Vault virtual server is configured on the primary node, NODEA.If NODEA fails, the virtual server’s resources fail over to NODEB, and thevirtual server comes online on NODEB.

See “Configuration examples” on page 241.

Control of services in a clustered environmentThe following overview describes how in a clustered environment a common setof Enterprise Vault services are controlled by an Enterprise Vault virtual server.See the following chapters for instructions on how to set up the cluster andconfigure Enterprise Vault.

Introducing clustering with Microsoft server clustersControl of services in a clustered environment

228

Enterprise Vault services in a clustered environmentWhether you configure Enterprise Vault as a server with cluster support, or as afailover node for an existing clustered server, the Configuration wizard installsthe following set of Enterprise Vault services on the node:

■ Directory Service

■ Index Service

■ Shopping Service

■ Storage Service

■ Task Controller Service

An Admin Service is already present from when Enterprise Vault was installed.The presence of this set of services is mandatory on each node, to ensure a commonconfiguration on all nodes in the cluster. You cannot remove Enterprise Vaultservices in a clustered configuration.

The Configuration wizard sets the Enterprise Vault services to manual startup,to enable the cluster software to start and stop them as required.

Note: In a clustered configuration, you cannot start or stop services using theAdministration Console or the EVService utility. If you stop a service usingWindows Service Control manager, the cluster software assumes this is due to asystem failure, and will restart the service or initiate a failover. To start or stopEnterprise Vault services safely, use only Cluster Administrator or the Windowscommand line utility cluster.exe.

See “Starting and stopping services” on page 255.

Resource groups and resourcesBefore configuring an Enterprise Vault server as a server with cluster support,you must create a cluster resource group, which will become the Enterprise Vaultvirtual server. The Enterprise Vault Configuration wizard adds the followingEnterprise Vault service resources to the resource group, to control and monitorthe equivalent Enterprise Vault services on the active node:

■ Admin Service resource

■ Directory Service resource

■ Index Service resource

■ Shopping Service resource

229Introducing clustering with Microsoft server clustersControl of services in a clustered environment

■ Storage Service resource

■ Task Controller Service resource

The Configuration wizard also adds one more resource to the group: an EnterpriseVault Server Instance resource. All the other Enterprise Vault resources in thegroup are configured to be dependent on this resource, directly or indirectly. Itspurpose is to prevent failovers to nodes already running Enterprise Vault, avoidingan active/active operation mode.

What happens at failoverIf an active node fails, the Enterprise Vault virtual server attempts to fail over tothe next available node in the resource group’s preferred node list, assuming allthe resources have that node as a possible owner. The Server Instance resourcefails over first, provided the failover node is not already running an EnterpriseVault virtual server. The remaining resources then fail over in order of dependency.The resources start the Enterprise Vault services on the failover node, ensuringcontinuing availability for the data that Enterprise Vault is managing andarchiving.

Introducing clustering with Microsoft server clustersControl of services in a clustered environment

230

Preparing to cluster withMicrosoft server clusters


■ Preparing to cluster Enterprise Vault

■ Setting up the shared disks and volumes

■ Setting up the resource groups

Preparing to cluster Enterprise VaultThis chapter describes the preparations you must take before you can cluster anew or existing Enterprise Vault installation in a Microsoft server cluster.

Note: The information in this chapter provides only an overview of the tasks youneed to perform. For general information on how to configure a Microsoft servercluster, refer to your Microsoft documentation.

To prepare for clustering with Microsoft server clusters

1 Decide on the operation mode for your cluster, including:

■ The number of primary nodes (each normally hosting an Enterprise Vaultvirtual server).

■ The number of failover nodes.

■ Which nodes are to be the preferred owners of each virtual server.

2 Ensure that your setup meets the requirements.

See “Required software and restrictions” on page 227.

31Chapter

3 Set up the shared disks and volumes for the cluster.

See “Setting up the shared disks and volumes” on page 232.

4 Use Cluster Administrator to create the cluster and to add the primary andfailover nodes.

5 Set up a resource group, including the prerequisite resources, for eachEnterprise Vault virtual server you require.

See “Setting up the resource groups” on page 233.

6 Create a static DNS host entry and an alias entry for each Enterprise Vaultvirtual server. For example, you might create a virtual server host entryEVSERVER1, and an alias entry EVSERVER1Alias, pointing at EVSERVER1.

For information on creating DNS settings, refer to your DNS documentation.

Setting up the shared disks and volumesYou must set up shared storage and volumes for the cluster, ready to accept theshared data. Each Enterprise Vault virtual server requires one or more volumesin which to store the following:

■ MSMQ data

■ Indexing Service data

■ Storage Service data (vault store partitions)

■ Shopping Service data



It is good practice for MSMQ data, Indexing Service data and Storage Service datato each have a separate physical disk resource. Placing them on the same drivesmay result in degraded performance.

For example, if you are setting up two Enterprise Vault virtual servers, EVSERVER1and EVSERVER2, you might allocate the shared storage for the cluster as follows:

■ Volume Q: Quorum dataCluster Group

■ Volume I: MSMQ data

■ Volume J: Index data

■ Volume K: Vault store data

■ Volume L: PST holding folders, Shopping service data, stagingareas

EVServer1

Preparing to cluster with Microsoft server clustersSetting up the shared disks and volumes

232

■ Volume M: MSMQ data

■ Volume N: Index data

■ Volume O: Vault store data

■ Volume P: PST holding folders, Shopping service data, stagingareas

EVServer2

Note the following when setting up the shared disks and volumes:

■ You must configure the storage for different resource groups on differentphysical disks, since only one server can connect to a physical disk at a time.

■ Configure shared disks and volumes such that the required nodes will be ableto access to the clustered disk resources on failover. For example, in a 2+1configuration, the failover node must have access to the quorum data volume,plus all the volumes used by both virtual servers.

Setting up the resource groupsYou must create and configure a resource group for each virtual server that thecluster is to support. For example, for an N+M cluster, you require N resourcegroups.

Note: You do not require a separate IP address resource in Windows 2008, as youcreate the required address automatically when you add a Client Access Point(network name).

Table 31-1 Prerequisite resources for Enterprise Vault resource groups

ParametersDependenciesResource type

Specify the required diskvolume.

NonePhysical Disk or VolumeManager Disk Group.

(Configure one disk resourcefor each volume you have setup for use by this virtualserver.)

■ Specify the IP address forthe virtual server.

■ Specify the publicnetwork.

■ Enable NetBIOS for thisaddress.

NoneIP Address

233Preparing to cluster with Microsoft server clustersSetting up the resource groups

Table 31-1 Prerequisite resources for Enterprise Vault resource groups(continued)

ParametersDependenciesResource type

■ Use the group name asthe network name.

■ We recommend that youselect the "DNSRegistration MustSucceed" check box.

■ You must select the"Enable KerberosAuthentication" checkbox. This is required bythe Message Queuingresource.

IP Address resourceNetwork name

None■ The Physical Diskresource for this virtualserver’s MSMQ data

■ The Network Nameresource

Message Queuing

To set up a resource group

1 Use Cluster Administrator to create and name the resource group.

2 In the Properties of the resource group, specify the nodes that are to be thepreferred owners of this resource group. List the nodes in the preferred order,according to your chosen operation mode.

3 Add the prerequisite resources to the resource group. Add one resource ofeach resource type listed in the following table, except where noted. Werecommend you use the following naming format for the resources:

groupname-resourcetype

For example, if you named a resource group EV1 and you are adding a physicaldisk resource, name the resource EV1-PhysicalDisk. Later, the EnterpriseVault Configuration wizard adds Enterprise Vault service resources to theresource group using this naming format.

Specify the required nodes as possible owners for each resource, accordingto your chosen operation mode.

When you have finished setting up the resource group, check that it can fail overbetween nodes without error.

Preparing to cluster with Microsoft server clustersSetting up the resource groups

234

Configuring EnterpriseVault in a Microsoft servercluster


■ About configuring Enterprise Vault in a Microsoft server cluster

■ Setting up a new Enterprise Vault installation with cluster support

■ Converting an existing Enterprise Vault installation to a cluster

■ Modifying an existing Enterprise Vault cluster

About configuring Enterprise Vault in a Microsoftserver cluster

This chapter describes:

■ Setting up a new Enterprise Vault installation with cluster support.

■ Converting an existing Enterprise Vault installation to a cluster.

■ Modifying an existing Enterprise Vault cluster to add another Enterprise Vaultclustered server or failover node, or to add more shared storage.

Before proceeding, you must have performed the preparatory steps for clustering.

See “Preparing to cluster Enterprise Vault” on page 231.

32Chapter

Setting up a new Enterprise Vault installation withcluster support

This section describes how to set up a first-time Enterprise Vault installation asa cluster.

Note: If during the running of the configuration wizard you receive an error relatedto the configuring of the Enterprise Vault Monitoring database, complete theconfiguration wizard and refer to Troubleshooting configuration of the Monitoringdatabase.

To set up a new Enterprise Vault installation with cluster support

1 Install Enterprise Vault on all the nodes that are to run Enterprise Vault, bothprimary and failover, but do not run the Enterprise Vault Configurationwizard on any node at this stage. For instructions on installing EnterpriseVault, see Sections I and II of this manual.

2 Configure the Enterprise Vault servers that are to act as clustered servers.

See “Configuring a new Enterprise Vault server with cluster support”on page 236.

3 Configure Enterprise Vault on the nodes that are to act as failover nodes.

See “Configuring a failover node” on page 240.

4 Test the cluster to ensure the failovers work as planned.

Configuring a new Enterprise Vault server with cluster supportPerform one of the following procedures on a newly installed Enterprise Vaultserver to configure it as an Enterprise Vault server with cluster support. Choosethe appropriate procedure depending on which of the following you want to do:

■ Create an Enterprise Vault Directory on the Enterprise Vault server. This ismandatory for the first Enterprise Vault server you configure. The Directoryis a container for Enterprise Vault Sites, which define common settings forEnterprise Vault servers. Every Enterprise Vault server must belong to justone Site. The configuration process creates a new Site in the new Directoryand adds the Enterprise Vault server to that Site. It also creates a Directorydatabase on the SQL server you specify.

■ Join an Enterprise Vault Directory on another Enterprise Vault server (typicallya previously configured Enterprise Vault virtual server). You can add theEnterprise Vault server to an existing Enterprise Vault Site in the Directory,

Configuring Enterprise Vault in a Microsoft server clusterSetting up a new Enterprise Vault installation with cluster support

236

or create a new Site in the Directory and add the Enterprise Vault server tothat.

To configure an Enterprise Vault serverwith cluster support, creating an EnterpriseVault Directory on the server

1 Use Cluster Administrator to ensure that a suitable resource group youprepared earlier is online on the Enterprise Vault server node.

2 On the node’s Windows Start menu, click All Programs > Enterprise Vault> Enterprise Vault Configuration. The first page of the Enterprise VaultConfiguration wizard appears.

3 Click Create a newEnterprise Vault serverwith Cluster support, and thenclick Next.

4 The wizard lists the resource groups that are currently online on this node.Select the prepared resource group and click Next.

5 On the next Wizard page, select Yes to choose the option to create anEnterprise Vault Directory on this computer. Then click Next.

6 Select the language you want Enterprise Vault to use when populating thedefault settings in the Administration Console. Then click Next.

7 The wizard asks for details of the Vault Service account. This is the accountyou created earlier as part of the preinstallation tasks for Enterprise Vault.Use the format domain_name\username, for example cluster\vaultadmin.Alternatively, use the ... button to browse for the account.

Enter the password details and then click Next.

The wizard then displays a couple of messages relating to the Vault Serviceaccount having been granted user rights on the computer, and the creationof the Directory Service.

8 When prompted, enter the location of the SQL Server to use for the EnterpriseVault Directory database and click Next.

9 The wizard prompts you to enter the locations for the Enterprise VaultDirectory database and transaction log. For performance reasons it is goodpractice to place these on separate disks. If default locations are shown,change them if they are incorrect. If you specified a SQL server on a remotecomputer, the paths must be valid paths on that computer, such as\\DC\C$\Program Files\Microsoft SQL Server\MSSQL\Data.

Then click Next.

237Configuring Enterprise Vault in a Microsoft server clusterSetting up a new Enterprise Vault installation with cluster support

10 When prompted, enter the location of the SQL Server to use for the EnterpriseVault Monitoring database. Leave StartMonitoring immediately selectedto begin monitoring as soon as the configuration is complete on this EnterpriseVault server. Then click Next.

11 The wizard prompts you to enter the locations for the Enterprise VaultMonitoring database and transaction log. For performance reasons it is goodpractice to place these on separate disks. If default locations are shown,change them if they are incorrect. If you specified a SQL server on a remotecomputer, the paths must be valid paths on that computer.

Then click Next.

12 The wizard then prompts you for a name and description for the new VaultSite.

A Vault Site alias is created automatically. This will be the DNS alias for theEnterprise Vault resource group you selected in step 4.


14 The wizard confirms the Enterprise Vault Site and Enterprise Vault Directorycomputer you have selected. It prompts you to specify the DNSAlias for thecomputer you are currently configuring.

Enter the unqualified DNS alias for the Enterprise Vault resource group thatyou selected in step 4, and clickNext to update the Enterprise Vault Directory.

15 The wizard lists the Enterprise Vault services that are to be added to thiscomputer. Click Next to add the services.

16 The wizard lists the Enterprise Vault services that it has now added, givingyou the option to check their properties. Note that in a cluster configurationyou are not allowed to add or remove services. Click Next to continue.

17 The wizard displays the storage locations for the Indexing and Shoppingservices. These locations default to the first disk resource in the selectedresource group. If the locations are suitable, clickNext. If you want to specifydifferent storage locations, click Back and edit the properties of the service.The wizard displays a warning if you try to modify these to a local locationsuch as C:\Shopping.

18 The Configuration wizard indicates that it needs to create cluster resourcesfor each of the Enterprise Vault services. If you wish, select Bring resourcesonline to allow Enterprise Vault to bring the resources online in the cluster.Alternatively you bring the resources online later using Cluster Administrator.

19 The final wizard page displays a list of the actions the wizard has performed,and the results. Click Finish to exit the wizard.


238

To configure an Enterprise Vault server with cluster support, joining an EnterpriseVault Directory on another computer



3 Click Create a newEnterprise Vault serverwith Cluster support, and thenclick Next.

4 The wizard lists the resource groups that are currently online on this node.Select the prepared resource group and click Next.

5 On the next wizard page, select No to join an Enterprise Vault Directory onanother Enterprise Vault server, and specify the DNS alias for the remoteEnterprise Vault server. This should be the unqualified DNS alias for anEnterprise Vault virtual server that you previously configured into the cluster.

Click Next and continue.

6 On the next wizard page, do one of the following:

■ Select the option to create a new Vault Site in the remote Enterprise VaultDirectory.

■ Click Next and continue from step 7.

■ Or select the option to join an existing Vault Site in the remote EnterpriseVault Directory, and select a Vault Site from the list displayed.

■ Then click Next and continue from step 10.

7 The wizard then prompts you for a name and description for the new VaultSite.

8 The vault site alias, which is created automatically when the first EnterpriseVault server is added to the site, will be the DNS alias for the remote EnterpriseVault server you specified in step 5.


10 The wizard confirms the Enterprise Vault Site and Enterprise Vault Directorycomputer you have selected. It prompts you to specify the DNSAlias for thecomputer you are currently configuring.

11 Enter the unqualified DNS alias for the Enterprise Vault resource group youselected in step 4.

12 Click Next to update the Enterprise Vault Directory.


13 The wizard lists the Enterprise Vault services that are to be added to thiscomputer. Click Next to add the services.

14 The wizard lists the Enterprise Vault services that it has now added, givingyou the option to check their properties. Note that in a cluster configurationyou are not allowed to add or remove services. Click Next to continue.

15 The wizard displays the storage locations for the Indexing and Shoppingservices. These locations default to the first disk resource in the selectedresource group. If the locations are suitable, clickNext. If you want to specifydifferent storage locations, click Back and edit the properties of the service.The wizard displays a warning if you try to modify these to a local locationsuch as C:\Shopping.

16 The Configuration wizard indicates that it needs to create cluster resourcesfor each of the Enterprise Vault services. If you wish, select Bring resourcesonline to allow Enterprise Vault to bring the resources online in the cluster.Alternatively you bring the resources online later using Cluster Administrator.


Configuring a failover nodePerform this procedure on the nodes that are to act as failover nodes.

To configure a failover node


2 Click Configure thenodeasa failovernode foranexistingclusteredserver,and then click Next.

3 The wizard prompts you for the name of the resource group for which youwant to add the node as a failover node. Select any resource group that isconfigured to fail over to this node. The resource group must be online onone of the nodes that you have configured as an Enterprise Vault primarynode, and its resources must all have the failover node as a possible owner.Select the name of the resource group, and then click Next.

4 On the next wizard page, enter the password for the Vault Service account,and then click Next.


240

5 The next wizard page lists the actions the wizard will take if you proceed. Tocontinue clickNext, then click and then clickOK to confirm the actions taken.


Troubleshooting configuration of the Monitoring databaseIf during the running of the configuration wizard you receive errors indicatingthat configuring the Enterprise Vault Monitoring database has failed, completethe configuration wizard and then run the Monitoring Configuration Utility toconfigure the Monitoring database and the Monitoring agents manually.

For information on how to do this, see the following Enterprise Vault TechNoteon the Symantec Support Web site: http://entsupport.symantec.com/docs/287449.


Configuration examplesThese examples describe how to set up first-time installations of Enterprise Vaultin various cluster operation modes.

Active/passive failover pairThis example describes setting up a new Enterprise Vault installation of an"active/passive" failover pair.

Figure 32-1 illustrates a single failover pair, consisting of a primary node, NODEA,running the Enterprise Vault virtual server EVSERVER1, plus a dedicated failovernode, NODEB.



Figure 32-1 Failover pair configuration

NODEAEVSERVER1(Primary Node)

NODEB(Failover Node)

Shared Disk

To set up this failover pair

1 Prepare for clustering Enterprise Vault as follows:

■ Create a node for the primary server (NODEA).

■ Create a node for the failover server (NODEB).

■ Create a resource group EVSERVER1 for the virtual server, with thepreferred owners set to NODEA followed by NODEB.

■ Add the prerequisite resources to resource group, ensuring that they haveNODEA and NODEB as their possible owners.

■ Create a DNS entry for the virtual server.

2 Install Enterprise Vault on NODEA and NODEB, without running theEnterprise Vault Configuration wizard.

3 On NODEA, run the Enterprise Vault Configuration wizard and choose toconfigure a new Enterprise Vault server with cluster support. SelectEVSERVER1 as the resource group in which to create the Enterprise Vaultservice resources. A Vault Site alias will be created automatically.

4 On NODEB, run the Enterprise Vault Configuration wizard and choose toconfigure a failover node for an existing clustered server. Select EVSERVER1as the resource group for which you want to add this node as a failover node.

5 Test the failover from NODEA to NODEB.


242

2+1 configuration without "any-to-any"Figure 32-2 illustrates a configuration in which there is a single spare node inaddition to the two nodes on which the Enterprise Vault servers are running.

Figure 32-2 2+1 configuration without "any-to-any" support

NODEAEVSERVER1

NODEB(EVSERVER2)

NODEC(SPARE)

Shared Disk

Shared Disk

If either NODEA or NODEB fails, the virtual Enterprise Vault server running onthat node can fail over to NODEC. This is not an "any-to-any" configuration so ifa node fails the resources must be moved back after the node is recovered, in orderto return to high availability.

To set up this 2+1 configuration

1 Prepare for clustering as follows:

■ Add three nodes to the cluster (NODEA, NODEB, NODEC).

■ Create two resource groups (EVSERVER1, EVSERVER2), and add theprerequisite resources to each group.


■ Configure the groups and resources so that the following nodes are thepreferred owners, in the order shown:

NODEA, NODECEVSERVER1

NODEB, NODECEVSERVER2

■ Create DNS entries for the virtual servers EVSERVER1 and EVSERVER2.

2 Install Enterprise Vault on NODEA, NODEB, and NODEC, but do not run theEnterprise Vault Configuration wizard.

3 On NODEA, run the Enterprise Vault Configuration wizard and choose toconfigure a new Enterprise Vault server with cluster support. SelectEVSERVER1 as the resource group in which to create the Enterprise Vaultservice resources. A Vault Site alias will be created automatically using thevirtual server alias.

4 On NODEB, run the Enterprise Vault Configuration wizard and choose toconfigure a new Enterprise Vault server with cluster support. SelectEVSERVER2 as the resource group in which to create the Enterprise Vaultservice resources. A Vault Site alias will be created automatically using thevirtual server alias.

5 On NODEC, run the Enterprise Vault Configuration wizard, and choose toconfigure a failover node for the existing clustered server. Select eitherEVSERVER1 or EVSERVER2 as the resource group for which you want to addthis node as a failover node.

6 Test the cluster to confirm that if NODEA fails, the EVSERVER1 resourcesfail over successfully to NODEC. Then return the EVSERVER1 resources toNODEA and confirm that if NODEB fails, the EVSERVER2 resources fail oversuccessfully to NODEC.

2+1 configuration "any-to-any"This second option for a 2+1 operation mode involves configuring the EnterpriseVault virtual servers EVSERVER1 and EVSERVER2 to run on any of the threenodes. This has the advantage that, for example, if NODEA fails and EVSERVER1fails over to NODEC, you can bring NODEA back online to act as the failover nodefor EVSERVER1 and EVSERVER2.


244

Figure 32-3 2+1 "any-to-any" configuration

NODEA

NODEB NODEC



You can extend the setup process for an N+M configuration with any number ofprimary and failover nodes, up to the total of 8 clustered nodes supported byMicrosoft server clusters.

To set up this 2+1 any-to-any configuration

1 Prepare for clustering as follows:

■ Add three nodes to the cluster (NODEA, NODEB, NODEC).

■ Create two resource groups (EVSERVER1, EVSERVER2), and add theprerequisite resources to each group.

■ Configure the groups and resources so that the following nodes are thepreferred owners, in the order shown:

NODEA, NODEC, NODEBEVSERVER1

NODEB, NODEC, NODEAEVSERVER2

2 Follow steps 2 to 5 of the 2+1 configuration without "any-to-any" support.


3 See “2+1 configuration without "any-to-any"” on page 243.

4 Test the cluster to confirm that if an active node fails, the virtual server failsover to the appropriate node.

5 For example, if you have configured the preferred owners of the resourcegroups as suggested in step 1:

■ Confirm that if NODEA fails, EVSERVER1 fails over successfully to NODEC.

■ Then bring NODEA back online as the spare node and confirm that ifNODEB fails, EVSERVER2 fails over to NODEA.

Converting an existing Enterprise Vault installationto a cluster

There are two types of Enterprise Vault installation that you can convert to aMicrosoft server cluster: a single, non-clustered Enterprise Vault server, and abuilding blocks configuration that contains multiple Enterprise Vault servers,provided no server is running in failover mode.

To be eligible for conversion to a cluster, the existing Enterprise Vault installationmust meet the following conditions:

■ Enterprise Vault should already be configured in a non-clustered configuration,and it must not already be part of a cluster.

■ Enterprise Vault must be configured using DNS aliases rather than fullyqualified node names.

■ The Enterprise Vault server must have a full set of Indexing, Shopping, TaskController, and Storage services. However, it must not contain the SharePointPortal Server 2001 service, as this is not supported in a cluster.

Note that Compliance Accelerator and Discovery Accelerator are not supportedwithin a cluster. However, an unclustered Compliance Accelerator or DiscoveryAccelerator can reference a clustered Enterprise Vault virtual server.

You can cluster an existing Enterprise Vault installation in any of the operationmodes previously described. Note that:

■ You can configure a combination of new and existing Enterprise Vault serversas virtual servers, if required.

■ You must perform a new installation of Enterprise Vault on the nodes that areto act as failover nodes.

Configuring Enterprise Vault in a Microsoft server clusterConverting an existing Enterprise Vault installation to a cluster

246

To convert an existing Enterprise Vault installation to a cluster

1 Prepare for clustering.

See “Preparing to cluster Enterprise Vault” on page 231.

2 Install Enterprise Vault on the failover nodes and, if required, on anyadditional primary nodes you are adding to the existing installation. Do notrun the Enterprise Vault Configuration wizard on any node at this stage. Forinstructions on installing Enterprise Vault, see Sections I and II of this manual.

3 Convert your existing Enterprise Vault servers to servers with cluster support.

See “Converting an existing Enterprise Vault server to a server with clustersupport” on page 247.

4 If you are adding any new Enterprise Vault servers, configure the newEnterprise Vault servers as servers with cluster support.

See “Configuring a new Enterprise Vault server with cluster support”on page 236.

5 Configure Enterprise Vault on the failover nodes.

See “Configuring a failover node” on page 240.

6 Test the cluster to ensure the failovers work as planned.

Converting an existing Enterprise Vault server to a server with clustersupport

This section describes how to convert an existing Enterprise Vault server to aserver with cluster support, including moving data to highly-available locations.

To convert an existing Enterprise Vault server to a server with cluster support

1 Ensure that the following items are all on highly-available shared storagedevices.






If they are not, correct the locations in the Enterprise Vault Directory databaseand then move the associated data to the new locations.

247Configuring Enterprise Vault in a Microsoft server clusterConverting an existing Enterprise Vault installation to a cluster

See “Moving data to highly-available locations” on page 249.


3 On the Windows Start menu, clickAllPrograms>EnterpriseVault>Convertto Cluster. The first page of the Enterprise Vault Convert to Cluster wizardappears. Click Next to continue.

4 The wizard makes a number of checks relating to the suitability of theinstallation for conversion to a cluster. It then displays a warning reminderthat when the wizard has successfully completed you must update the DNSalias or Hosts file entry that is currently pointing at the physical node, sothat it points at the virtual server name.

5 The wizard then displays a list of the current file locations for the EnterpriseVault services and partitions. You must confirm that these locations are allon highly-available shared storage devices before continuing. Either selectthe check box to confirm high-availability, and clickNext to continue, or clickCancel to exit from the wizard and move the required data to highly-availablelocations before running the wizard again.

6 If the wizard detects that there are messages in the Enterprise Vault MSMQqueues, it displays a page indicating the name of each queue and the numberof messages on it. The wizard cannot move these messages to the clusteredmessage queues due to permissions constraints. We recommend you cancelfrom the wizard and leave the services running in a non-clusteredenvironment until Enterprise Vault has cleared the message queues. You canthen re-run the Convert to Cluster wizard. If you continue without doing this,the messages remain on the node-specific queues and are not processed. Ifyou want to continue without clearing the queues, select the Continueconverting configuration to a cluster check box and click Next.

7 The wizard lists the resource groups that are currently online on this node.Select the required resource group and click Next.

8 The wizard creates the necessary resources, updates the Enterprise Vaultservices to manual startup, and updates the Directory database tables toremove the local computer name from the computer entry table and themessage queue names. The final wizard page displays a list of the actions thewizard has performed, and the results. Click Finish to exit the wizard.

9 If you have not already done so, manually update the DNS alias to point atthe virtual server name rather than the local node name.

10 Bring the virtual server resources online using Cluster Administrator.


248

Moving data to highly-available locationsIn outline, the procedure for moving the data to highly-available locations is asfollows:

■ Stop the Indexing, Shopping, Storage, and Task Controller services.

■ Make a backup copy of the Enterprise Vault Directory database and data files.

■ Use the Enterprise Vault Administration Console or run a SQL query againstthe Enterprise Vault Directory to move the data, as described below.

■ Move the contents of this location to a highly available location.

■ Update the database using SQL to point at the new location.


SELECT *FROM IndexRootPathEntryWHERE (IndexRootPathEntryId = '<ID FROMLOG FILE>')


UPDATE IndexRootPathEntrySET IndexRootPath = '<THE NEW LOCATION>'WHERE (IndexRootPathEntryId = '<ID FROMLOG FILE>')

IndexRootPathEntry[IndexRootPath]

■ Move the pool entry authorization (.pea) file to a highlyavailable location.

■ Use the Enterprise Vault Administration Console to view theproperties of the EMC Centera partition and then, on theConnection tab, edit the Pool Entry Authorization File Locationbox to point at the new location.

PartitionEntry[AccountName]

249Configuring Enterprise Vault in a Microsoft server clusterConverting an existing Enterprise Vault installation to a cluster






UPDATE PartitionEntrySET PartitionRootPath = ‘<THE NEWLOCATION>’WHERE (PartitionEntryId = '<ID FROM LOGFILE>')

PartitionEntry[PartitionRootPath]

■ Move the secondary storage files to a highly available location.



SELECT *FROM PartitionEntryINNER JOIN Locations ONPartitionEntry.SecondaryLocation =Locations.LocationIdentityWHERE (PartitionEntry.PartitionEntryId =‘<ID FROM LOG FILE>')


UPDATE LocationsSET Location = '<NEW LOCATION>'WHERE LocationIdentity =(SELECT SecondaryLocation FROMPartitionEntryWHERE PartitionEntryId = ‘<ID FROM LOGFILE>')

PartitionEntry/Locations[SecondaryLocation]


250






UPDATE PartitionEntrySET StagingRootPath = ‘<THE NEW LOCATION>’WHERE (PartitionEntryId = '<ID FROM LOGFILE>')

PartitionEntry[StagingRootPath]

■ Move the contents of the location to a highly available location.

■ Use the Enterprise Vault Administration Console to view theproperties of the PST Migrator Task and update the Temporaryfiles folder.

PSTMigratorTask[MigrationDirectory]


■ Use the Enterprise Vault Administration Console to edit theShopping service location to the new highly available location.

ShoppingServiceEntry[ShoppingRootPath]

■ Move the contents of the location to a highly available location.

■ Use the Enterprise Vault Administration Console to view thesite properties and update the PST Holding Folder property topoint at the new location.

SiteEntry[PSTHoldingDirectory]

Modifying an existing Enterprise Vault clusterThis section describes how to modify an existing Enterprise Vault cluster to dothe following:

■ Add a node to host a new Enterprise Vault virtual server or to act as a failovernode.

■ Add shared storage for a virtual server.

Adding a nodeYou may want to add a node to an existing Enterprise Vault cluster to host a newEnterprise Vault virtual server or to act as a failover node.

251Configuring Enterprise Vault in a Microsoft server clusterModifying an existing Enterprise Vault cluster

To add a node to an existing cluster

1 Share the required disk volumes on the new node.

2 Use Cluster Administrator to add the node to the cluster.

3 If you are adding a new Enterprise Vault virtual server, prepare a new resourcegroup and add the prerequisite resources.

See “Setting up the resource groups” on page 233.

4 Specify the new node as a possible owner of all resources in all the resourcegroups that are required to run on it.

5 Add the new node at a suitable position in the preferred owners list of anyresource group that is required to run on it.

6 Install Enterprise Vault on the node.

7 Run the Enterprise Vault Configuration wizard and choose either Create anewEnterprise Vault serverwith Cluster support, or Configure the nodeas a failover node for an existing clustered server, as required.

8 Test the modified cluster to confirm that failovers to or from the new nodework as planned.

Adding shared storageYou may want to add shared storage to an existing Enterprise Vault cluster, toprovide more storage for a virtual server.

To add shared storage to an existing Enterprise Vault cluster

1 Set up the additional shared disks and volumes, sharing the volumes on thenodes that require access to them.

2 For the virtual server that is to use the new storage:

■ Add a Physical Disk resource to the resource group for each new volume.Make the Physical Disk resource dependent on the Enterprise VaultServerInstance resource.

■ Change the Properties of theAdminServiceresource to add a dependencyon each new Physical Disk resource.

3 Specify the required nodes as possible owners for the new Physical Diskresources, according to your cluster operation mode.

4 Test the modified cluster to confirm that the Enterprise Vault virtual servercan access the new shared storage successfully before and after failover.

Configuring Enterprise Vault in a Microsoft server clusterModifying an existing Enterprise Vault cluster

252

Troubleshooting clusteringwith Microsoft serverclusters



■ Event logs and the server cluster log

■ Resource ownership and dependencies

■ Registry replication

■ Viewing the clustered message queues

■ Starting and stopping services

About this chapterThis chapter describes how to troubleshoot problems with Enterprise Vault in aMicrosoft server cluster.

Note: For information on backing up and recovering a clustered Enterprise Vaultenvironment, see the Administrator’s Guide.

33Chapter

Event logs and the server cluster logThere are no specific Enterprise Vault event messages for clustering, but EnterpriseVault continues to write messages to the standard Application and EnterpriseVault event logs, so check these for errors.

If any Microsoft server cluster resources fail to come online, check the event logsand also the Microsoft server cluster log text file, typicallyC:\WINDOWS\Cluster\cluster.log.

To see the operations related to Enterprise Vault, search for ‘Enterprise Vault’.

Resource ownership and dependenciesResource ownership must be set up correctly to avoid problems when configuringEnterprise Vault in a cluster. The Configuration wizard only lists a resource groupfor selection if every resource in the group has the node on which you are runningthe wizard listed as a possible owner.

Resource ownership and resource dependencies must also be set up correctly toensure failovers work as planned.

Table 31-1 describes the dependencies you must set for the prerequisite resources.

Enterprise Vault Configuration wizard sets up the dependencies for the EnterpriseVault service resources and the Server Instance resource when it adds them tothe resource group.

If you add a shared disk to an existing cluster you must ensure you set up the diskresource and dependencies correctly.

See “Adding shared storage” on page 252.

Registry replicationAs part of configuring the virtual server, the Configuration wizard sets up aregistry checkpoint on the Admin service resource, to provide the required registryreplication on the clustered nodes.

If you suspect problems with registry entries related to an Enterprise Vault virtualserver, view the checkpoint to confirm it is set up correctly. Enter the followingcommand using the Windows command line utility cluster:

cluster resource EnterpriseVaultAdminService /check

where EnterpriseVaultAdminService is the name of the Admin service resource,for example EVSERVER1-EnterpriseVaultAdminService.

Troubleshooting clustering with Microsoft server clustersEvent logs and the server cluster log

254

You should see listed one checkpoint for the Admin service resource:Software\KVS\Enterprise Vault.

Viewing the clustered message queuesIn a clustered Enterprise Vault installation the Computer Management snap-indoes not show Enterprise Vault message queues by default: it shows only queuesfor the local computer.

To view the clustered message queues for an Enterprise Vault virtual server

1 Ensure the Enterprise Vault virtual server is online on the node you want toview the queues from.

2 Open a command prompt window and change to the Enterprise Vaultinstallation folder, typically C:\Program Files\Enterprise Vault.


ClusterCompMgmt

This launches the Computer Management snap-in with the environmentvariables set so that it displays the clustered message queues.

4 Expand Services andApplications, then expand MessageQueuing. TheEnterprise Vault virtual server queues are listed under Private Queues.

Starting and stopping servicesIn a clustered environment the clustering software must have control of theEnterprise Vault services. To allow this, the Enterprise Vault Configuration wizardsets the startup of these services to manual. Do not attempt to change the startupto automatic.

If a service starts or stops outside of the control of the cluster software, the clustersoftware assumes this is due to a change in system condition. For example, if aservice stops, the cluster software assumes a failure, and will attempt to restartthe service or initiate a failover.

You should not attempt to start or stop Enterprise Vault services, except throughthe cluster software in one of the following ways:

■ Use Cluster Administrator to bring the associated service resource online oroffline.

■ Or use the Windows command line utility cluster. For the syntax of thiscommand, open a command prompt window and enter:

255Troubleshooting clustering with Microsoft server clustersViewing the clustered message queues

cluster /?

For more details, see, for example, the following TechNet article:

http://technet2.microsoft.com/WindowsServer/en/librar

y/8da99e1e-619f-4deb-acf0-cd8d61ac2ed01033.mspx

To help prevent the starting and stopping of services by other means, EnterpriseVault behaves as follows in a clustered configuration:

■ The Enterprise Vault Administration Console buttons for starting and stoppingservices are unavailable.

■ You cannot start or stop services using the EVService utility. However, youcan continue to use EVService to control tasks.

■ Enterprise Vault blocks attempts to start Enterprise Vault services using theWindows Service Control Manager, and logs an event message. However,Enterprise Vault cannot block the stopping of services using Windows ServiceControl Manager, so be careful to avoid this.

Troubleshooting clustering with Microsoft server clustersStarting and stopping services

256

Planning for the GettingStarted Wizard

This appendix includes the following topics:

■ Planning for the Getting Started Wizard

Planning for the Getting Started WizardThis section lists the choices that the Getting Started wizard makes automaticallywhen you run it in Express mode. In Express mode, the Getting Started wizarddoes not ask many questions. Instead, the wizard applies as many default settingsas possible. Later, you can use the Administration Console to make changes tothe settings, if required.

This section lists the choices that the wizard makes in Express mode and showsall the options that are available within the Administration Console. There is alsospace for you to note down your preferred selection.

Table A-1 shows the Vault Store Group settings that the wizard creates in Expressmode.

AAppendix

Table A-1 Vault Store Group settings in Express mode

Your choiceAdministrationConsole possiblevalues

Wizard's valueItem

Edit as required."Express Vault Store Group".If the name already exists anumber is appended to makethe name unique. Forexample, "Express Vault StoreGroup_1".

Name

Edit as required.The same as the Vault StoreGroup name.

Description

Cannot change.The same SQL Server as wasspecified in the Configurationprogram for the EnterpriseVault Directory database.

SQL Serverforfingerprintdatabase

Cannot change.The default database folderfor the Enterprise VaultDirectory computer.

Folder forallfingerprintdatabasefilegroups

Cannot be changed.The default log folder for theEnterprise Vault Directorycomputer.

Folder forfingerprintdatabase log

Table A-2 shows the Vault Store settings that the wizard creates in Express mode.

Table A-2 Vault Store settings in Express mode


Wizard's valueItem

Edit as required."Express Vault Store". If thename already exists a numberis appended to make the nameunique. For example, "ExpressVault Store_1".

Name

Edit as required.The same as the vault storename.

Description

Planning for the Getting Started WizardPlanning for the Getting Started Wizard

258

Table A-2 Vault Store settings in Express mode (continued)


Wizard's valueItem

Can be changed toanother SQL Server.

The same SQL Server as wasspecified in the Configurationprogram for the EnterpriseVault Directory database.

SQL Server

'No sharing'; 'Sharewithin Vault Store';'Share within group'.

'Share within Vault Store'.Sharing

'Never'; 'After backup;'After backup(immediate forJournaling)';Immediately afterarchive'.

'After backup (immediate forJournaling)'.

Removesafetycopies

'Disabled'; 'Enabled';'Use Site setting'.

'Use Site setting'.Limitarchiveusage

Table A-3 shows the Vault Store partition settings that the wizard creates inExpress mode.

Table A-3 Vault Store partition settings in Express mode


Wizard's valueItem

Edit as required."Express Vault Store Ptn1". Ifthe name already exists anumber is appended to makethe name unique. Forexample, "Express VaultPtn2".

Name

Edit as required.Partition of Vault Store[Vault_store_name]

Description

'Closed'; 'Open';'Ready'.

Open.State

Cannot change.NTFS volume.Device type

259Planning for the Getting Started WizardPlanning for the Getting Started Wizard

Table A-3 Vault Store partition settings in Express mode (continued)


Wizard's valueItem

Device performs datadeduplication; Devicedoes not perform datadeduplication.

Destination device does notperform data deduplication.

Datadeduplication

Device performs datacompression; Devicedoes not perform datacompression.

Destination device does notperform data compression.

Datacompression

'Not Enabled'; 'Enabledbased on volume';'Enabled based ontime'; 'Enabled basedon time or volume'.

Not enabled.Partitionrollover

'Use the archiveattribute'; 'Check for atrigger file'.

Use the archive attribute.How tocheck thatitems havebeensecured

Use collection files; Donot use collecitionfiles.

Not enabled.Usecollectionfiles

Enabled; Not enabled.Not enabled.Migratefiles

Table A-4 shows the Exchange provisioning group settings that the wizard createsin Express mode.


260

Table A-4 Exchange provisioning group settings in Express mode


Wizard's valueItem

Edit as required.'Express Provisioning Group'.If you have selected 'Storageconfiguration' theprovisioning group uses a newvault store that the wizardcreates. If you have notselected 'Storageconfiguration', the wizarduses an existing vault store.

Provisioninggroup name

'Windows group';'Windows user';'Distribution group';'Organizational Unit';'LDAP query'; 'WholeExchangeOrganization'.

'Whole ExchangeOrganization'

Provisioninggroup scope

Edit as required.'Default Exchange DesktopPolicy'

Desktoppolicy

Edit as required.'Default Exchange MailboxPolicy'

Mailboxpolicy

Edit as required.'Default Exchange PSTmigration Policy'

PSTmigrationpolicy

Edit as required.'Default Retention Category'Defaultretentioncategory

Edit as required.The Indexing service on thecurrent Enterprise Vaultserver, if any. If there is noIndexing service then thewizard selects an Indexingservice on another server.

Indexingservice

Table A-5 shows the Domino provisioning group settings that the wizard createsin Express mode.


Table A-5 Domino provisioning group settings in Express mode


Wizard's valueItem

Edit as required.'Express Provisioning Group'.If the name already exists anumber is appended to makethe name unique. Forexample, "ExpressProvisioning Group_1".

Provisioninggroup name

Edit as required.If you have selected 'Storageconfiguration' theprovisioning group uses anew vault store that thewizard creates. If you havenot selected 'Storageconfiguration', the wizardselects an existing vault store.

Vault store

'Directory Group';'Mailbox';'Organizational Unit';'Corporate Hierarchy'.

'All Organizational Units'Provisioninggroup scope

Edit as required.'Default Domino DesktopPolicy'. If this policy is notavailable the wizard selectsthe first policy that isavailable, alphabetically.

Desktoppolicy

Edit as required.'Default Domino MailboxPolicy'. If this policy is notavailable the wizard selectsthe first policy that isavailable, alphabetically.

Mailboxpolicy

Edit as required.'Default Retention Category'Defaultretentioncategory

Edit as required.The Indexing service on thecurrent Enterprise Vaultserver, if any. If there is noIndexing service then thewizard selects an Indexingservice on another server.

Indexingservice


262

Table A-6 shows the Vault Store settings that the wizard creates in Express mode.

Table A-6 Vault Store settings in Express mode


Wizard's valueItem

Edit as required.The Vault store that wascreated in the current run ofthe wizard, if any. If thewizard did not create a vaultstore the first vault store withan open partition is used.

Name

Edit as required.The same description as forthe vault store name.

Description

Can be changed toanother SQL Server

The same SQL Server as wasspecified in the Configurationprogram for the EnterpriseVault Directory database.

SQL Server


'Share within Vault Store'.Sharing


'After backup (immediate forJournaling)'.

Removesafetycopies

'Disabled'; 'Enabled';'Use Site setting'.

'Use Site setting'.Limitarchiveusage



264

Aactive/passive failover configuration 186Admin permissions 154Administration Console

Japanese fonts 152Using 151

agent configurationmodifying 197

Assigning administrator roles 155Authorization Manager 155

CClient computer

customizing security 113Clustering

Microsoft server clusters 225VERITAS Cluster Server 185

Collection 173computer

adding new 124configuration

modifying using wizard 197typical setup 186

Configuration Program 151configuration wizard 123configuration wizards

Exchange Server Configuration 194configurations

active/passive failover 186Configure sharing 175

DDefault domain

with basic authentication 110Default Upgrade Group 168Device-level sharing

EMC Centera 166DNS alias 40Domino Journaling

configuring access for Enterprise Vault 77

Domino Journaling (continued)configuring the journaling databases 76Database Management 76

EEMC Centera

Device-level sharing 166Enterprise Vault

configuring 121installing 103, 117

Enterprise Vault Operations Manageraccessing 140configuring 139requirements 43

Enterprise Vault Reportingaccessing 146configuring 143requirements 47

Enterprise Vault sitecreating new 124

Entourage clients 59Exchange

supported versions 185Exchange agent

about 186configuring using wizard 194supported services 186troubleshooting 219typical setup 186

Exchange clusteractive/passive setup 186

Exchange cluster configurationActive/Passive failover 186

Exchange permissions 53Exchange Service agent 186Exchange service group

modifying 197

FFingerprint database 165

Index

Fingerprint Databasesdisk space requirements 27

Fontsin Administration Console 152

FSA Reporting databasedisk space requirements 28

HHTTPS support 181

IInternet Explorer

for users 58

JJapanese fonts

in Administration Console 152

LLicense keys 99

obtaining 100Licenses 99

MMAC clients 59MDAC version 37Microsoft .NET Framework 35Microsoft Authorization Manager 155Microsoft server clusters 225

configuring 235Microsoft SQL Server

setting up 78Migration 173Monitoring database

disk space requirements 28troubleshooting 128

MSMQsetting up 78

NNetApp Filer

setting permissions on 82

OOperations Manager

accessing 140

Operations Manager (continued)configuring 139requirements 43

Outlook Add-Ins 58requirements 58

Outlook versionsfor users 58

OWA client support 59

PPartition

creating 172permissions

for Vault Service account [permissionsVault Site] 53

Production license defined 99PstDisableGrow 58

RReporting

accessing 146configuring 143requirements 47

Retention Categorycreating new 156

Rolesassigning administrator 155

Roles-based administration 154

SSafari browser support 60Safety copy

about 170Saveset files 164Security

on client computers 113security

for Web Access application [securityWeb] 107

service groupmodifying 197

Servicesconfiguring 126starting during configuration 127

Sharing levels 162Sharing regime 167Single instance storage

about 160

Index266

Single instance storage (continued)Default Upgrade Group 168developing a suitable sharing regime 167how it works 164requirements 166sharing boundaries 162sharing levels 162

SMTP ArchivingMAPI messages 92relaying 92where to install SMTP server 92

SQL loginfor Vault Service account 39

Storagesetting up 159

Storage requirements 24Support contact information 14supported services 186supported versions 185

TTCP/IP

required on client computers 58Temporary license

defined 99Trialware license

defined 99troubleshooting

Exchange service agent 220troubleshooting information 219

VVault Directory

creating new 124Vault Directory Database

disk space requirements 27Vault Service account 53

permissions 53requirements 38SQL login 39

Vault Site aliascreating 40

Vault storecreating 170on upgrade to Enterprise Vault 8.0 168

Vault Store Databasedisk space requirements 27

Vault store groupconfigure sharing for 175creating 169

Vault store groupsDefault Upgrade Group 168

Vault StoresOverview 160, 170

VCS 185VERITAS Cluster Server 185

WWeb Access application

application pool 35basic authentication 110customizing security for 109https support 181setting up security 107specifying a port 181

Windows Desktop Search 59wizards

Exchange Server Configuration 194

267Index

317266

Documents

Transcript of 317266