Enterprise Vault™ Introduction and Planning
- About this guide
- Overview of Enterprise Vault
- How Enterprise Vault works
- About Enterprise Vault indexing
- About Enterprise Vault tasks
- About Enterprise Vault services
- About the Archive Discovery Search Service
- About the Enterprise Vault Outlook Add-In
- About Enterprise Vault Search
- Enterprise Vault administration
- About reporting and monitoring in Enterprise Vault
- Exchange Server archiving
- About Exchange Server archiving and user mailboxes
- Exchange Server and journal mailbox archiving
- Exchange Public Folder archiving
- File System Archiving
- Archiving Microsoft SharePoint servers
- Domino mailbox archiving
- Domino Journal archiving
- SMTP Archiving
- Skype for Business Archiving
- Enterprise Vault Accelerators
- About Compliance Accelerator
- The Compliance Accelerator client application
- About Discovery Accelerator
- Discovery Accelerator client application
- Building in resilience
- About Enterprise Vault and VCS
- About Enterprise Vault and Windows Server Failover Clustering
- About Enterprise Vault building blocks
- Planning component installation
- Where to set up the Enterprise Vault Services and Tasks
- Installation planning for client components
- Planning your archiving strategy
- How to define your archiving policy for user mailboxes
- How to plan the archiving strategy for Exchange public folders
- How to plan settings for retention categories
- How to plan vault stores and partitions
- About Enterprise Vault reports
How to plan PST migration
How you implement the archiving of PST files will depend on the number of files to be archived, your company policy on the use of PST files and whether users have infrequent access to a fast network connection.
There are several ways to import PST files into Enterprise Vault:
Wizard-assisted migration can be used for a small number of PST files.
Scripted migration using Enterprise Vault Policy Manager is ideal for performing bulk migrations of PST files.
Locate and Migrate uses Enterprise Vault Tasks to locate PST files on users' computers, copy them to a central location, and then import them. You can configure specific paths to include or exclude during PST searching. Locate and Migrate is designed to minimize the difficulties of collecting PST file from users' computers and is likely to require least effort on your part.
Client-driven migration is similar to Locate and Migrate but the locating of PST files and sending them to a collection location is done automatically by the user's computer and not by Enterprise Vault Server Tasks. This can be useful if, for example, there are users with laptop computers who are in the office only one or two days a week, thus making it difficult to obtain their PST files by other methods. You can also give users' control over migrating their PST files. Client-driven migration needs to be enabled in the Administration Console.
To aid PST migration you can configure desktop clients so that, when a user starts Outlook, the client writes a marker into each PST file that is listed in the mail profile. When a marked PST file is subsequently imported, the marker indicates the owning mailbox.
PST migration is described in the PST Migration guide.
When planning PST migration, take the following points into consideration:
Do not enable PST migration for all users at the same time. Migrate the PST files for a small group of users and then move onto the next group.
A typical rate of PST migration is 2 GB/hour.
An administrator has to allow each PST file before it can be imported.
It is important that the language setting in the properties for each PST is correct before the PST is imported.