When performing any migration, it is important to identify and realize that some items may not be migrated successfully. Large migration projects may include the migration of millions of items, and for a number of reasons some those items may not reach their final target. The number of failed items in a migration project is frequently a fraction of a percent of the total number of items processed by the migration solution.
Below is a list of commonly identified reasons that items may fail to migrate successfully using PST Flight Deck:
- Requests timing out.
- Items too large.
- Throttling denials.
- Target unavailability.
- Item unavailable or corrupt in the source PST.
- Unsupported items by the target due to size, type, or other properties.
As items can fail for any number of reasons, it is important to be able to account for the failures within a migration. During a migration, items may fail to migrate due to a dependency of the migration utility and not the utility itself. These types of failures are frequently logged through a migration utility despite the failure being independent of the solution.
Although issue remediation is a specific task, the following remediation process can be used to work through failed items in PST Flight Deck:
- Backup\remove\rename historic FD logging or enable FD logging so new logs are created.
- Re-Ingest failed items from the Clean-up directory*.
- Monitor for progress until PST has re-cleared the applicable Ingest module.
- If large number of items fail ingestion again, review applicable ingest worker log for root cause of failure.
- Make configuration changes to accommodate any logged failures, wherever possible.
- Re-Ingest again if corrective action was taken or issue was thought to be temporary in nature.
- Make organizational decision about actions to be taken for remaining failed items
- Examples of options remaining for failed items within PST files may be to retain them, dispose of them, or use an alternate means to ingest them…..
*Re-Ingest location can be changed to multiple directories but is most commonly configured for the Clean-Up directory to reprocess items which have failed.
Depending on the size of your migration, it may not be reasonable to review all items which fail to migrate. It is suggested in instances where the volume of failures is high but the overall percentage of failed items is low to review a random sampling of failed items for best results considering resource constraints.
For information on how to configure FD to retain failed items please reference the FD Admin Guide.
Should you have questions or concerns related to any of the failures discovered, please prepare logging collected from a re-ingestion using the instructions above and start a ticket related to any single failure that was identified as a concern by emailing email@example.com