Veritas Enterprise Vault™ Introduction and Planning
- About this guide
- Introduction
- Overview of Enterprise Vault
- How Enterprise Vault works
- About single instance storage
- About Enterprise Vault indexing
- About Index Server groups
- About Enterprise Vault Administration Console
- About Enterprise Vault sites, Directory, and Directory database
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Enterprise Vault Outlook Add-In
- About IMAP access to Enterprise Vault archives
- About the Enterprise Vault Client for Mac OS X
- About Microsoft Exchange forms
- About OWA Extensions
- About the Office Mail App for OWA 2013 and later and Outlook 2013 and later
- About Enterprise Vault Search Mobile edition
- About Enterprise Vault extensions for Notes
- About Enterprise Vault Web Access components
- About Enterprise Vault monitoring and reporting
- FIPS 140-2 compliance
- Enterprise Vault administration
- About Enterprise Vault administration
- Administration Console configuration of archiving
- Administration accounts and roles
- How to archive PST file contents
- How to archive NSF file contents
- How to export archived items
- Welcome message and other notifications
- About reporting and monitoring in Enterprise Vault
- How to script management tasks
- Checklist of day-to-day management tasks
- Exchange Server archiving
- Exchange Public Folder archiving
- File System Archiving
- About File System Archiving
- About File archiving policies
- About shortcut files with File System Archiving
- About setting up File System Archiving
- File System Archiving in a clustered environment
- The process of File System Archiving
- How File System Archiving handles older versions of archived files
- How File System Archiving synchronizes permissions
- File System Archiving reports
- How to restore files with File System Archiving
- About FSAUtility
- How to back up and scan shortcut files with File System Archiving
- Pass-through recall for placeholder shortcuts with File System Archiving
- File Blocking with File System Archiving
- Retention Folders and File System Archiving
- FSA Reporting
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Enterprise Vault Accelerators
- About the Enterprise Vault Accelerators
- Differences between the Enterprise Vault Accelerators
- About Compliance Accelerator
- About Discovery Accelerator
- Building in resilience
- Planning component installation
- About planning component installation
- About valid computer names for Enterprise Vault servers
- Prerequisites for Enterprise Vault components when planning installation
- Factors to consider when planning deployment of Enterprise Vault components
- Enterprise Vault Directory Service installation planning
- Where to set up the Enterprise Vault Services and Tasks
- How to plan installing Exchange Mailbox Archiving Tasks
- How to plan installing Exchange Journaling Tasks
- How to plan installing Exchange Public Folder Tasks
- How to plan installing Domino Journaling and Mailbox Archiving Tasks
- How to plan installing the Move Archive task
- How to plan installing the Storage Service
- How to plan installing the Indexing Service
- How to plan installing the Shopping Service
- How to plan installing File System Archiving
- How to plan installing SharePoint Archiving
- How to plan installing SMTP Archiving
- How to plan installing Accelerator Services
- Enterprise Vault databases and planning their installation
- Vault store groups and vault stores installation planning
- Administration Console installation
- Installation planning for client components
- Planning your archiving strategy
- About archiving strategies
- Where to define default settings for the Enterprise Vault Site
- How to allow users flexibility
- How to plan the types of items to archive
- How to define your archiving policy for user mailboxes
- How to plan the archiving policy for journal mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan an archiving strategy for FSA
- How to plan a strategy for SharePoint archiving
- How to plan settings for retention categories
- How to plan the automatic deletion of archived items
- How to plan PST migration
- How to plan NSF migration
- How to plan shared archives
- How to plan vault stores and partitions
- How to plan single instance storage
- About Enterprise Vault reports
File System Archiving in a clustered environment
If your Windows file servers are grouped in a cluster, you can make the FSA services that run on them highly available. You must add an FSA resource to the cluster resource group or service group, and configure the FSA resource for high availability. The FSA resource monitors the state of the FSA services on the online node. If a problem occurs with the FSA services on the online node, then the cluster resource group or service group that contains the FSA resource fails over to the next available node.
Figure: Example FSA cluster configuration shows an environment in which three file servers are clustered together.
Note that you can make the FSA Agent services highly available only when there is a shared disk resource.
The FSA clustering feature works with the following cluster software:
Windows Server Failover Clustering (formerly known as Microsoft Cluster Server, or MSCS)
Veritas Cluster Server (VCS)
Refer to the Enterprise Vault Compatibility Charts for details of the supported versions of this software, and the supported versions of Windows. The Compatibility Charts document is available on the Veritas Enterprise Support site at this address:
http://www.veritas.com/docs/000097605
The following cluster types are supported:
Active/passive cluster. To support high availability, the shared cluster resources are made available on one node of the cluster at a time. If a failure on the active cluster node occurs, the shared resources fail over to the passive node and users may continue to connect to the cluster without interruption.
Active/active cluster. To support load balancing and high availability, the cluster resources are split among two or more nodes. Each node in the cluster is the preferred owner of different resources. In the event of a failure of either cluster node, the shared resources on that node fail over to the remaining cluster nodes.
Enterprise Vault supports multiple nodes in any combination of active/passive and active/active. We have validated configurations with up to four nodes.
For guidelines on how to make the FSA Agent services highly available in a clustered environment, see the Setting up File System Archiving manual.