Enterprise Vault™ PST Migration
- About this guide
- Introduction to PST migration
- PST file ownership
- PST migration: scripted
- Output from PST migration
- PST migration: wizard-assisted
- PST migration: Locate and Migrate
- Setting up PST Locate and Migrate
- Configuring the holding folder for PST Locate and Migrate
- Creating and configuring the PST Locator, PST Collector, and PST Migrator tasks
- Migrating PST files using PST Locate and Migrate
- Running the PST Locator task to find domains and computers
- Running the PST Locator task to find PST files
- PowerShell cmdlets for PST migration
- PST migration: client-driven migration
- About client-driven PST migration
- Enabling mailboxes for PST client-driven migration
Improving performance when archiving PST file contents
When Enterprise Vault archives items, it converts the contents to HTML and indexes them. The default conversion timeout for this process is 30 minutes. Enterprise Vault makes three attempts to convert an item, and so can take up to 90 minutes before it fails an item and moves to the next one.
If there are very large or complex items in a PST file, it can take a long time to migrate them all. If you do not need the content of the items to be indexed, you can improve performance by lowering the conversion timeout to a few minutes.
To change the conversion timeout
- On the Storage service computer, set the string registry value ConversionTimeout to the required timeout in minutes. The entry must be under the following registry key:
HKEY_LOCAL_MACHINE \SOFTWARE \Wow6432Node \KVS \Enterprise Vault
- Restart the Storage service.
This change to the conversion timeout also affects normal archiving, so remember to return it to the original value when you have migrated the PSTs.
You can also improve performance by making Enterprise Vault create text versions rather than HTML versions of certain document types. See the Administrator's Guide for instructions on how to control content conversion.