Veritas Enterprise Vault™ PST Migration
- About this guide
- Introduction to PST migration
- PST file ownership
- PST migration: scripted
- PST migration: wizard-assisted
- About the PST Migrator wizard
- Outline of the wizard-assisted PST migration process
- Preparation for the wizard-assisted PST migration process
- Migration tips for the wizard-assisted PST migration process
- How the wizard-assisted PST migration process affects users
- Starting the wizard-assisted PST migration process
- PST migration: Locate and Migrate
- About Locate and Migrate
- Setting up PST Locate and Migrate
- Migrating PST files using PST Locate and Migrate
- Excluding network shares from PST migration using the PstLocatorTask.exe.config file
- Troubleshooting PST migration
- PST migration: client-driven migration
- About client-driven PST migration
- Preparation for client-driven PST migration
- Editing the PST migration messages for client-driven PST migration
- Configuring the PST holding folder for PST client-driven migration
- Creating a PST Migrator task for PST client-driven migration
- Enabling mailboxes for PST client-driven migration
- Permissions required for migrating PST files stored on network drives
Results of message sampling
Depending on how you have configured message sampling, you can get any of the following results.
Table: Results of message sampling details the behavior of Enterprise Vault with respect to message sampling.
Table: Results of message sampling
Message sampling | Resulting action | PST migration status |
|---|---|---|
Message sampling successfully identifies the owner. | Enterprise Vault matches the email address or display name with the available Exchange mailbox user, and assigns the archive of that user to the PST file so that items are migrated to that archive. | The PST file state changes to Do not migrate. If the percentage of associated messages matches the configured criteria for the change of migration state, the PST file state changes to Ready to copy. |
Message sampling has identified a probable owner, but the number of associated messages does not meet the configured ownership criteria. | - | The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state. |
Message sampling has identified multiple possible owners. For example, the PST file has 2 owners with 50% associated messages each or 3 owners with 33.3% associated messages each. | Enterprise Vault displays this information in the More details section in the properties page of the PST file. | The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state. |
Message sampling has identified the owner, but the associated archive is not found. This may happen in case the PST file is from outside the network or the user's mailbox is not enabled for archiving. | Enterprise Vault displays this information in the More details section in the properties page of the PST file. | The PST file remains in the Not Ready state. If you have specified a default archive to store PST files that have no owners identified, the PST file is assigned to the default archive and the state changes to Do not migrate. If the PST file is in the Not Ready state, you can manually assign the correct archive and change the state. |