PST Cleanup – The Final Stage of the FlightDeck Approach
Last week we looked at how PST FlightDeck provides a fast and safe ingestion process for transferring user PSTs into new targets such as Office 365. In the final part of our PST FlightDeck blog series, we look at how FlightDeck undertakes a cleanup process to manage items potentially still waiting in the upload area, and ensure that the required files (and the items within them) have all been transferred successfully.
A PST cleanup can be performed either post, or pre-ingestion. We advocate a post-ingestion cleanup to save resources due to the fact fewer write IOPS are required on the FlightDeck Server(s) as the PST-Files have no need to be extended. From our experience, writing/extending the PST files is best avoided in order to ensure the best-possible levels of performance, stability and corruption avoidance.
Let’s look at this process in the context of a typical PST migration project. Say, for example, you have 100 items in a single PST file. You may have put filters into place, which remove items of a certain size, or perhaps some of them have been identified as duplicates during the project. Either way, this can leave you with fewer than 100 items in your newly migrated PST file.
This means that a number of items for that PST file are still residing in the centralized BITS upload location. When configured to, the cleanup module will now move these items to a specific directory to attempt re-ingestion before ascertaining whether it’s now safe to remove them from the upload location, where you want to maximize space for items waiting to be ingested. This can safeguard you against the possible deletion of items that have failed to ingest. Any problem items are easily visible and appropriate rules can be applied to certain items that may need further processes applied to them.
High levels of speed and efficiency with a PST migration, just as with an archive or mailbox migration, is an end-to-end process that can’t rely on any one capability alone. Our approach to the cleanup phase serves to maximize both data safety and migration resources during your project, just as every other part of the process has been continually refined in order to achieve.
More information can be found below, along with the previous parts of this blog series.