PST Flight Deck 9.2 - Administration Guide

Ramp-Up

The Ramp-up phase implies growing the wave sizes until waves are keeping the system busy with available disk space and mostly completing them in the desired wave interval. Setting the Migration Priority for a wave of users enables them for migration. Commonly, a unique priority value would be set per migration wave. Daily monitoring is required at this point of the migration. Monitoring should consist of the environment, the active wave(s), and those users’ files until mostly completed. Remediation and reprocessing of some PST files or items may be required for the wave to fully complete. In addition, module tuning to achieve more performance within the limitations of the environment should also be performed during the initial monitoring and growth of migration waves.

Migration

You do not have to wait for a wave to be entirely completed prior to starting the next wave. The goal of an efficient migration project should be to minimize backlog but ensure enough work to have the environment persistently working. This typical bottleneck in a migration work flow is typically the extraction module but could be other areas if certain environmental factors dictate it. Keeping a system busy requires persistent uploads and consistent ingestion to ensure there is enough work to keep the system working at its fullest capacity without running out of available disk space.

Wrap Up

As users complete, an Operator may choose to move their migration priority to a disabled value. This permits control over future discoveries for the user. Backup files are frequently kept for a determined period of time after a user has completed the migration. This location, and all other module’s storage locations will need to have content removed when appropriate. When a user or the migration completes, it is recommended that those users have the DisablePST registry key set on their workstations to reduce the re-introduction of PST files after a user’s source files have been removed.

Stages of a Migration

During a migration, both users and files are progressing through a workflow. Each stage of the process has specific results indicating what has happened to the file. Stages are used to describe the phases of this process so that an individual can tell the status of a user or a file at a glance.

The user workflow stage is complex and are calculated by the server on an hourly schedule. The displayed status may not correctly reflect the current status of the user. This is normally not an issue as the status of a user does not change that fast. Below is a list of stages used to describe the status of a user:

File stages are current, up to the minute, for a specific file. The following are the stages of file processing:

The primary goal of a PST Flight Deck is to move PST files from a dispersed location and ingest them into a centralized location. Files are considered “Complete” when the need to ingest the file has been satisfied. This is most commonly due to complementing a successful ingestion of a file, however can also be achieved by a file being in a status that does not get ingested (Deleting, Not a PST File…..). Files or users can be considered “Complete” but still have modules in the workflow that have not competed.