Veritas Enterprise Vault™ PST Migration
- About this guide
- Introduction to PST migration
- PST file ownership
- PST migration: scripted
- PST migration: wizard-assisted
- PST migration: Locate and Migrate
- Setting up PST Locate and Migrate
- Migrating PST files using PST Locate and Migrate
- PST migration: client-driven migration
- About client-driven PST migration
- Enabling mailboxes for PST client-driven migration
Report mode [PSTcheckpoint] section
The following [PSTcheckpoint] section results from running an initialization file in report mode. The Generation count of 1 shows that these results are from the first run of the file:
[PSTCHECKPOINT] GENERATION = 1 CREATED = 02Oct2008 10:58:02 AM SOURCE = E:\EV\pstmigration\pstlist.ini PSTPROCESSEDCOUNT = 118 PSTNOTREADYCOUNT = 3 PSTWARNINGCOUNT = 2
The following entries are of interest:
PSTPROCESSEDCOUNT = 118 shows that the file contains references to 118 PST files.
PSTNOTREADYCOUNT = 3 shows that there are three files with problems. The Report_Error entries in the individual [PST] sections give you more information. Policy Manager automatically adds DONOTPROCESS = TRUE to each of these [PST] sections.
PSTWARNINGCOUNT = 2 shows that there are two files with warnings. In this case, these are both marked PST files whose markings are intentionally being overridden. The Report_Error entries in the individual [PST] sections gives more information.
Because Policy Manager has added the DONOTPROCESS = TRUE entries to each of the problem PST files, you could run this new initialization file in process mode immediately, leaving the problem PSTs to be addressed later. Alternatively, you could fix the problems, remove the DONOTPROCESS = TRUE entries, and then run the file again in either report mode or process mode.