To make customers more comfortable with setting a reasonable number and percentage of ingestion failures, PST Flight Deck introduced a feature called Failback. Failback is designed to be able to ingest items into the desired target that would originally fail during ingestion into that target. As the original content is still being delivered to the customer’s target, Failback enables Operators to set a greater ingestion failure threshold with comfort and without concerns of valued data not being delivered to their users.
PST Flight Deck now offers the possibility to deliver failed items to their respective users. This is accomplished via the Failback feature. This feature is designed to be able to ingest items into the desired target that would originally fail during ingestion into that target. This would permit an Operator to focus on data not available to the users and to raise the failed item threshold to a highly manageable level of failures to investigate.
An Operator may set the number of items or percentage of items as a limit for an acceptable failure rate from each PST file. If I file has a failure rate greater than that configured, the status of that file will be changed to a Partially Ingested status.
There are two ways, a PST file can get its status changed to Partially Ingested:
1) There are items that failed ingestion but the number of Ingestion Failed items is bellow the configured Ingestion threshold -> Failback is performed but fails to successfully ingest the new message. If Failback fails ingestion of any message, the status of the PST file is set to Partially Ingested.
There are a couple of reasons presently identified why a Failback message can’t be ingested.
It there is a need to troubleshoot Ingestion with Failback, please read this KB article:
For more details regarding possible filters, Failback, or other features within the product, please review the PST FlightDeck Administrator Guide