Enterprise Vault™ Installing and Configuring
- About this guide
- Section I. Enterprise Vault requirements
- Enterprise Vault hardware requirements
- Hardware requirements for Enterprise Vault server
- Hardware requirements for SQL Server
- Network requirements for Enterprise Vault
- About the storage requirements for Enterprise Vault
- Storage for vault stores
- Storage for Enterprise Vault indexes
- Storage requirements for SQL databases
- Storage requirements for the Enterprise Vault cache folder
- Local storage requirements for temporary files
- TEMP folder security requirements
- Granting additional users and groups access to the TEMP folder
- Enterprise Vault required software and settings
- About the Enterprise Vault required software and settings
- About valid computer names for Enterprise Vault servers
- About the Enterprise Vault Deployment Scanner
- Basic software requirements for Enterprise Vault
- Best practice settings for Enterprise Vault servers
- Message queue cleanup interval: MessageCleanupInterval
- Message queue message storage limit: MachineQuota
- Disable opportunistic locking: OplocksDisabled
- Disable loopback check: DisableLoopbackCheck
- Disable strict name checking: DisableStrictNameChecking
- Maximum Outlook attachments and recipients: AttachmentMax and RecipientMax
- TCP/IP maximum ports and TCP timed wait delay
- Preinstallation tasks for Enterprise Vault server
- Creating the Vault Service account
- Creating a SQL login account
- About assigning permissions and roles in SQL databases
- Assigning the required SQL Server roles and permissions to an Active Directory group
- Locking down Enterprise Vault SQL databases
- Creating Enterprise Vault DNS aliases
- Turning off or reconfiguring Windows Firewall
- Securing data locations
- About User Account Control (UAC)
- Additional requirements for Operations Manager
- Additional requirements for classification
- Additional requirements for Enterprise Vault Reporting
- Additional requirements for Exchange Server archiving
- About Exchange Server archiving
- Preinstallation tasks for Exchange server archiving
- Installing Outlook on the Enterprise Vault server
- Creating the Enterprise Vault system mailbox
- Removing the restriction on NSPI connections to a Windows Server domain controller
- Creating a user profile on the Enterprise Vault server
- Creating a mailbox for the Vault Service account
- Configuring the Exchange throttling policy on the Vault Service account
- Granting the Vault Service account Send As permission on the system mailboxes
- Assigning Exchange Server permissions to the Vault Service account
- Enterprise Vault client access with Exchange Server archiving
- Additional requirements for Domino Server archiving
- Domino Server archiving requirements for all Enterprise Vault servers
- Requirements for Domino mailbox archiving
- Required software for Enterprise Vault Domino Gateway
- Required software for target Domino mail servers
- Requirements for Enterprise Vault extensions for Notes clients
- Preinstallation tasks for Domino mailbox archiving
- Register the Enterprise Vault Domino Gateway
- Configuring the Internet port on the Enterprise Vault Domino Gateway
- Configuring server security for the Enterprise Vault Domino Gateway
- Configuring Single Sign-On on the Enterprise Vault Domino Gateway
- Clustering Enterprise Vault Domino Gateway servers
- Configuring an alias URL for web connections to the Enterprise Vault Domino Gateway server
- About the user ID for Domino mailbox archiving
- Configuring the server document for each target Domino mail server
- Install and configure Enterprise Vault Domino Gateway
- Requirements for Domino journaling archiving
- Additional requirements for File System Archiving (FSA)
- Additional requirements for SharePoint Server archiving
- Additional requirements for Skype for Business Archiving
- Additional requirements for SMTP Archiving
- Additional requirements for Enterprise Vault Search
- Additional requirements for a standalone Enterprise Vault Administration Console
- Additional requirements for the Archive Discovery Search Service
- Enterprise Vault hardware requirements
- Section II. Installing Enterprise Vault
- Section III. Configuring Enterprise Vault
- About configuring Enterprise Vault
- Running the Enterprise Vault configuration wizard
- Securing Enterprise Vault Web Access components
- Default security for the Enterprise Vault Web Access components
- Customizing the port or protocol for the Enterprise Vault Web Access components
- Customizing authentication for the Enterprise Vault Web Access components
- Customizing security for the Web Access components on client computers
- Encrypting session cookies
- Running the Enterprise Vault Getting Started wizard
- What the Enterprise Vault Getting Started wizard does
- Preparing to run the Enterprise Vault Getting Started wizard
- Running the Enterprise Vault Getting Started wizard
- About the express and custom modes of the Enterprise Vault Getting Started wizard
- About indexing configuration with the Enterprise Vault Getting Started wizard
- About storage configuration with the Enterprise Vault Getting Started wizard
- About policy definition with the Enterprise Vault Getting Started wizard
- About Exchange target configuration with the Enterprise Vault Getting Started wizard
- About Domino target configuration with the Enterprise Vault Getting Started wizard
- About file target configuration with the Enterprise Vault Getting Started wizard
- Planning for the Enterprise Vault Getting Started wizard
- Configuring Enterprise Vault Operations Manager
- Configuring the Archive Discovery Search Service
- Section IV. Initial Enterprise Vault setup
- Initial Enterprise Vault setup
- Setting up storage
- About setting up storage for Enterprise Vault archives
- About Enterprise Vault single instance storage
- About sharing levels and sharing boundaries
- How Enterprise Vault single instance storage works
- About the fingerprint database
- Deletion of SIS parts
- Requirements for Enterprise Vault single instance storage
- About Centera device-level sharing
- About sharing partitions on storage devices that support the Enterprise Vault storage streamer API
- Developing a suitable sharing regime for Enterprise Vault single instance storage
- Creating vault store groups
- About creating vault stores
- About Enterprise Vault safety copies
- Choosing when to remove Enterprise Vault safety copies
- Checking that the partition has been backed up before Enterprise Vault removes safety copies
- Using the archive attribute to determine whether a partition has been backed up
- Using the trigger file mechanism to determine whether a partition has been backed up
- Creating a vault store
- About Enterprise Vault safety copies
- Creating vault store partitions
- Configuring sharing for a vault store group
- Adding index locations
- Setting up Index Server groups
- About Index Server groups
- Do I need to create Index Server groups?
- Do you have more than one Enterprise Vault server?
- Do you use or plan to use journal archiving or File System Archiving?
- Do you use or plan to use Compliance Accelerator or Discovery Accelerator?
- Is the server loading evenly distributed across existing Enterprise Vault servers?
- Are there more than approximately 5,000 mailbox archives per Enterprise Vault server?
- Creating an Index Server group
- Adding an Index Server to an Index Server group
- Removing an Index Server from an Index Server group
- Assigning a vault store to an Index Server group
- Unassigning a vault store from an Index Server group
- Assigning a vault store to a different indexer
- Reviewing the default settings for the site
- Setting up Enterprise Vault Search
- About Enterprise Vault Search
- Defining search policies for Enterprise Vault Search
- Allowing privileged Enterprise Vault Search users to restore items to other users' mailboxes
- Setting up provisioning groups for Enterprise Vault Search
- Creating and configuring Client Access Provisioning tasks for Enterprise Vault Search
- Configuring user browsers for Enterprise Vault Search
- Configuring Enterprise Vault Search for use in Forefront TMG and similar environments
- Setting up Enterprise Vault Search Mobile edition
- Managing metadata stores
- Section V. Clustering Enterprise Vault with VCS
- Introducing clustering with VCS
- Installing and configuring Storage Foundation HA for Windows
- Configuring the VCS service group for Enterprise Vault
- Running the Enterprise Vault Configuration wizard
- Before you run the Enterprise Vault Configuration wizard
- Setting up Enterprise Vault in an active/passive VCS configuration
- About setting up Enterprise Vault in a VCS N+1 configuration
- Implementing an SFW HA-VVR disaster recovery solution with Enterprise Vault
- About installing and configuring SFW HA-VVR with Enterprise Vault
- Overview of the steps for installing and configuring SFW HA-VVR
- Setting up the VCS cluster on the primary site
- Setting up the VCS cluster on the secondary site
- Adding the VVR components for replication
- Adding the GCO components for wide-area recovery
- Troubleshooting clustering with VCS
- Section VI. Clustering Enterprise Vault with Windows Server Failover Clustering
- Introducing clustering with Windows Server Failover Clustering
- About clustering Enterprise Vault with Windows Server Failover Clustering
- Supported Windows Server Failover Clustering configurations
- Required software and restrictions on clustering Enterprise Vault with Windows Server Failover Clustering
- Typical Enterprise Vault configuration in a Windows Server failover cluster
- Control of Enterprise Vault services in a Windows Server failover cluster
- Preparing to cluster with Windows Server Failover Clustering
- Configuring Enterprise Vault in a Windows Server failover cluster
- About configuring Enterprise Vault in a Windows Server failover cluster
- Setting up a new Enterprise Vault installation with Windows Server Failover Clustering support
- Configuring a new Enterprise Vault server with Windows Server Failover Clustering support
- Configuring a failover node in a Windows Server failover cluster
- Troubleshooting configuration of the Enterprise Vault Monitoring database
- Examples of Enterprise Vault installations in various Windows Server Failover Clustering modes
- Converting an existing Enterprise Vault installation to a Windows Server failover cluster
- Modifying an existing Enterprise Vault cluster
- Troubleshooting clustering with Windows Server Failover Clustering
- About this chapter
- Enterprise Vault event messages and the failover cluster log
- Resource ownership and dependencies when configuring Enterprise Vault in a failover clustered environment
- Registry replication on failover clustered nodes
- Viewing the clustered message queues for an Enterprise Vault cluster server
- Starting and stopping Enterprise Vault services in a Windows Server Failover Clustering environment
- Potential failover issue in a Windows Server cluster
- Introducing clustering with Windows Server Failover Clustering
- Appendix A. Automatically preparing an Enterprise Vault server
Developing a suitable sharing regime for Enterprise Vault single instance storage
If you use Enterprise Vault single instance storage, you need to create a sharing regime that meets your organization's data sharing requirements and which is appropriate for your network connection speeds.
Consider what sort of sharing regime you require before you start archiving. There are limits to what you can change:
You can change a vault store's sharing level, but the change does not act retrospectively. For example, if you change a vault store's sharing level from 'share within group' to 'share within vault store', any items already shared within the vault store group remain so.
You cannot move a vault store to another vault store group unless all of the following circumstances apply:
You previously upgraded to Enterprise Vault 8.0.
The vault store is one that Enterprise Vault upgraded to Enterprise Vault 8.0, or one that you created 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 information barriers, also known as "Chinese walls". For example, a datacenter may be required by law or by company policy to keep information separate between its investment, retail, and mergers and acquisitions groups, to avoid conflicts of interest.
You may want to create a separate vault store group for each organizational group in which information must be isolated.
Network connectivity between the appropriate computers must be sufficient to provide acceptable storage and retrieval times. As a minimum we recommend that you limit single instance storage to an environment in which the connections support the expected response time of a 100 Mbps switched Ethernet LAN.
The Enterprise Vault server whose Storage service manages a vault store must have adequate connectivity with the following:
The computers that host the vault store partitions for the vault stores that are 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 takes Enterprise Vault to archive and retrieve the shared items.
If your organization spans several widely-dispersed geographical locations it may 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 speeds across sample network connections. The relevant wizards prompt you to run the connectivity test when you create a new vault store group or partition, or when you configure sharing. The connectivity test can help you create a sharing regime with an acceptable level of performance. To assess performance, the connectivity test measures the average round-trip time for a number of ping requests. If you have disabled ping in your environment, use your own tools to decide if the performance is acceptable. We recommend a round-trip time of one millisecond or less.
If the test results indicate poor connectivity, consider modifying the sharing boundaries or changing the location of your computers to improve connection speeds. If you are willing to accept poorer performance, you can choose to accept poor connectivity test results.
When you create a vault store group, configure its fingerprint database appropriately for the projected sharing requirements.
More Information