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
Process mode [PSTcheckpoint] section
The following [PSTcheckpoint] section results from running an initialization file in process mode. The Generation count of 2 shows that these results are from the second run of the file:
[PSTCHECKPOINT] GENERATION = 2 CREATED = 02Oct2008 10:59:36 AM SOURCE = E:\EV\pstmigration\pstlist.ini PSTPROCESSEDCOUNT = 115 PSTFAILEDCOUNT = 0 PSTUNPROCESSEDCOUNT = 3 PSTINCOMPLETECOUNT = 0 PSTPARTIALCOUNT = 0
The following entries are of interest:
PSTPROCESSEDCOUNT = 115 shows that 115 PST files were processed. This is the same initialization file as shown above in the Report mode description. The three problem files have been left with DONOTPROCESS = TRUE entries, so Policy Manager has ignored them.
PSTFAILEDCOUNT = 0 shows that there were no files for which processing could not be tried.
PSTUNPROCESSEDCOUNT = 3 shows that three files were ignored. These are the three files with DONOTPROCESS = TRUE entries.
PSTINCOMPLETECOUNT = 0 shows that no PST files were processed only partially. Policy Manager's processing was not interrupted.
PSTPARTIALCOUNT = 0 shows that there were no PST files with individual items that could not be processed. If there had been such items, Policy Manager would have placed them in the Migration Failed Items folder in the PST files.