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 the Office Mail App for OWA 2013 and later and Outlook 2013 and later
- About Enterprise Vault extensions for Notes
- About Enterprise Vault Search
- 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
- Single Sign-On for Enterprise Vault Search
- 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
- Retention Folders and File System Archiving
- FSA Reporting
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Microsoft Teams Archiving
- Skype for Business 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
Vault store groups and vault stores installation planning
Vault stores are contained in vault store groups. A vault store group defines the outer boundary for sharing items in Enterprise Vault single instance storage.
See About single instance storage.
A vault store can comprise one or more partitions. A vault store partition resides on a storage device. When you set up Enterprise Vault, you specify on which device each partition is created.
If a partition is created on an NTFS volume set, it must be contained within a single NTFS volume set, and cannot span volume sets. Bear in mind that a volume set can contain multiple physical disks, so your partition can be spread over more than one disk. There can be more than one partition on an NTFS volume set. If you need to create or extend NTFS volume sets to accommodate the partition, use the Windows Administrative Tools.
The amount of space you will require for your vault stores depends on the following:
The average size of items that you anticipate archiving.
The number of items you anticipate archiving in a day to that vault store.
The reduction in archive storage space due to single instance storage.
The reduction in storage space due to compression of files.
How often you anticipate archiving items from the Archiving Target.
How long you anticipate archived items remaining in the vault store.
Note:
For assistance with storage sizing, contact your Veritas supplier.
The first two items in this list give you some idea of the amount of space that you would need in the vault store for one day, before any savings due to single instance storage or compression.
Single instance storage and compression can provide significant savings in storage space.
If you use expiry to delete archived items automatically at the end of their retention period, then the amount of space required will not increase as much over longer periods.
If you set up an aggressive archiving policy that archives items from the archiving targets after about two weeks, users are likely to want to access those items frequently. Keep the archived items online in the vault store for a period of time so users can easily restore them. You will need adequate online space to accommodate the data in the vault stores.
If, on the other hand, you set up archiving so that items are not archived from the archiving targets for about six months or a year, users are much less likely to want to access the archived items. You could then almost immediately move the archived items from the vault stores to secondary storage.
You can select a default vault store for archives when creating archiving targets.
For Exchange mailbox archiving, you can select a different vault store at provisioning group, Exchange Server or Enterprise Vault server level. For public folder archiving, you can select a different vault store at Exchange Server or Enterprise Vault server level. For Domino mailbox archiving, you can select a different vault store at provisioning group or Domino Server level.
The vault store selected will be used for automatically-enabled archives associated with the target. Similarly, for SharePoint archiving, the vault store selected for a target will be used for any auto-enabled site collection archives associated with the target.
The vault store databases do not need to be on the same computer as the vault stores. The databases are managed using SQL Enterprise Manager.
See Enterprise Vault databases and planning their installation.