Veritas Enterprise Vault™ PST Migration

Last Published:
Product(s): Enterprise Vault (12.1)
  1. About this guide
    1.  
      Introducing this guide
    2. Where to get more information about Enterprise Vault
      1.  
        Enterprise Vault training modules
  2. Introduction to PST migration
    1.  
      Introducing PST file migration
    2.  
      Tools for migrating PST files
    3.  
      Feature comparison of PST migration tools
    4.  
      About the Exchange PST Migration policy
    5.  
      Improving performance when archiving PST file contents
    6.  
      Migrating PST files in hosted environments
    7. About the Personal Store Management node
      1.  
        Creating filters
  3. PST file ownership
    1.  
      About PST file ownership
    2.  
      PST file marking to determine PST file ownership
    3. PST message sampling to determine PST file ownership
      1.  
        Configuring message sampling to determine PST file ownership
      2.  
        Results of message sampling
  4. PST migration: scripted
    1.  
      Overview of the scripting mechanism for PST migration
    2.  
      Undertaking the PST migration process using Policy Manager
    3.  
      Preparation for PST scripted migration
    4. Output from PST migration
      1. [PSTcheckpoint] section PST scripted migration
        1.  
          Report mode [PSTcheckpoint] section
        2.  
          Process mode [PSTcheckpoint] section
      2.  
        Enterprise Vault event log for PST scripted migration
    5.  
      Example initialization file for PST scripted migration
  5. PST migration: wizard-assisted
    1.  
      About the PST Migrator wizard
    2.  
      Outline of the wizard-assisted PST migration process
    3.  
      Preparation for the wizard-assisted PST migration process
    4.  
      Migration tips for the wizard-assisted PST migration process
    5.  
      How the wizard-assisted PST migration process affects users
    6.  
      Starting the wizard-assisted PST migration process
  6. PST migration: Locate and Migrate
    1.  
      About Locate and Migrate
    2. Setting up PST Locate and Migrate
      1.  
        Administrator roles required to manage PST Locate and Migrate
      2. Configuring the holding folder for PST Locate and Migrate
        1.  
          Determining the size of the holding folder for PST Locate and Migrate
      3. Creating and configuring the PST Locator, PST Collector, and PST Migrator tasks
        1.  
          How to configure the PST Locator task
        2.  
          How to configure the PST Collector task
        3.  
          How to configure the PST Migrator task
    3. Migrating PST files using PST Locate and Migrate
      1. Running the PST Locator task to find domains and computers
        1.  
          Adding computers for PST searching
        2.  
          Switching off NetApp device identification checks by the PST Locator task
      2.  
        Selecting computers for PST searching
      3.  
        Configuring paths to include or exclude for PST searching
      4. Running the PST Locator task to find PST files
        1.  
          Adding PST files for migration
        2.  
          Editing PST file properties
      5.  
        Running the PST Collector task
      6.  
        Running the PST Migrator task
      7. PowerShell cmdlets for PST migration
        1.  
          About the PST migration cmdlets
        2.  
          Running the PST migration cmdlets
        3.  
          Using Add-EVPstComputer
        4.  
          Using Add-EVPstFile
        5.  
          Adding multiple computers or PST files
    4.  
      Excluding network shares from PST migration using the PstLocatorTask.exe.config file
    5.  
      Troubleshooting PST migration
  7. PST migration: client-driven migration
    1. About client-driven PST migration
      1.  
        Options to configure client-driven PST migration
    2.  
      Preparation for client-driven PST migration
    3.  
      Editing the PST migration messages for client-driven PST migration
    4.  
      Configuring the PST holding folder for PST client-driven migration
    5.  
      Creating a PST Migrator task for PST client-driven migration
    6. Enabling mailboxes for PST client-driven migration
      1.  
        Enabling mailboxes for PST file submission
    7.  
      Permissions required for migrating PST files stored on network drives

Example initialization file for PST scripted migration

The initialization file must be saved as a Unicode file.

Table: Sample initialization file shows a sample initialization file that sets up migrations for five PST files.

Table: Sample initialization file

Initialization file section

Notes

[Directory]

directorycomputername = server2

sitename = server2

  • The directory section is mandatory and must appear at the top of the file.

  • This section contains the name of the Enterprise Vault directory computer and the site name.

[PSTDefaults]

ServerComputerName = server2

PSTLanguage = Western European

MailboxFolder = EVPM PST Migrations

MigrationMode = Report

ShortcutMode = NoShortcuts

IncludeDeletedItems = false

SetPstHidden = false

SetPstReadOnly = false

CompactPst = true

DeletePst = false

CancelMbxAutoArchive = false

  • These default options apply to all PST migrations listed in the following [PST] sections unless overridden in those sections.

  • PST Language is mandatory.

  • There must only one [PSTDefaults] section and it must appear before the individual [PST] sections.

  • MigrationMode=Report specifies that this initialization file is to run in report mode.

  • ShortcutMode=NoShortcuts means that, by default, there will be no shortcuts to the migrated items. Items that cannot be migrated will be left in the PST files, not moved to the mailboxes. You can override this behavior for individual PST files.

[PST]

Filename = E:\Migration\Missing.pst

  • The [PST] sections must appear after the [PSTDefaults] section

  • As a minimum each section must specify the PST filename.

  • If an option is unspecified then Policy Manager uses the value in the [PstDefaults] section.

  • This marked file is missing and will produce an error when Policy Manager runs.

[PST]

Filename = \\server3\temp\marked1.pst

  • This file is on a remote computer.

  • This PST file has been marked by the Enterprise Vault client so that Policy Manager can automatically determine the target archive, the Exchange Server mailbox, and the retention category.

[PST]

Filename = E:\Migration\marked2.pst

MailboxDN = /o=ACME/ou=DEVELOPER/cn=Recipients/cn=JackH

ShortcutMode = MailboxShortcuts

  • This PST file has been marked by the Enterprise Vault client so that Policy Manager can automatically determine the target archive, the Exchange Server mailbox, and the retention category.

  • The MailboxDN setting is overriding the PST marking. This will result in a warning when the initialization file is processed. The file will be processed correctly, using the specified enabled mailbox and that mailbox's default retention category and archive.

  • Policy Manager will create shortcuts to archived items and place them, together with any items that remain in the PST at the end of the migration, into the mailbox.

[PST]

Filename = E:\Migration\marked3.pst

ArchiveName = Jack Henry2

  • This PST file has been marked by the Enterprise Vault client.

  • The ArchiveName setting is overriding the owner entry that the client made. This will result in a warning when the initialization file is processed. The PST file will be processed correctly, using the specified archive and the default retention category from the owning mailbox.

[PST]

ArchiveName = SharedArchive1

Filename = E:\Migration\unmarked.pst

RetentionCategory = Business

  • This file has not been marked by an Enterprise Vault client.

  • You must specify the ArchiveName, PST filename, and RetentionCategory.