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 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
- 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
- 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
How to export archived items
Enterprise Vault provides Administrators with a wizard to export archived items.
You cannot use the wizard to export Enterprise Vault Domino archives. If you want to export items from Domino archives, see the description of Domino Archive Exporter in the Utilities guide.
The wizard enables you to export the following:
Archives to PST files.
Archives to their original Exchange Server mailboxes.
A single archive to any Exchange Server mailbox.
You can export the following archive types:
Exchange Server mailbox and journal archives.
File system archives.
Shared archives. (Shared archives are special archives that you can create and enable several users to access. These archives do not contain folders.)
You can filter the output by date and by Retention Category. So, for example, you could export items less than a year old that were archived with a Retention Category of "Business".
When you export archives to PST files you can then import them back into Enterprise Vault. This is useful if, for example, you are moving a mailbox to a different Enterprise Vault site and want to move its archived items too.
When you select the option for EML to MSG conversion, the export will convert EML messages to MSG messages and then add them to one or more PST files, depending on the number and size of the messages. After a successful export run, the contents of the PST file(s) can be natively previewed in Microsoft Outlook.
EML to MSG conversion is available for IMAP, SMTP, Instant Messaging, Fax, and Bloomberg message types.
Caution:
The EML to MSG conversion is a time-consuming process. The time taken can be minimized by planning the export runs in batches. During testing of the EML to MSG conversion, export rates of approximately 10,000 messages per hour were seen, based on an average message size of 300KB. This estimate may be conservatively used to plan exports batch runs, so they complete within an acceptable time frame.