When an outage between the LSMS and NPAC occurs, the LSMS attempts to resynchronize automatically as soon as the association is reestablished. The NPAC then resends to the LSMS all transactions that were missed by the LSMS.
Whenever association is reestablished between the NPAC and the LSMS, the NPAC and the LSMS automatically resynchronize their databases. The time required for automatic resynchronization between an NPAC and the LSMS is directly proportional to the number of transactions that need to be sent. If you believe you have a lot of subscription version records, you can choose to perform a manual NPAC/LSMS recovery, as described in Downloading Files from an NPAC to the LSMS.
If the NPAC and the LSMS are unable to complete automatic recovery, one of the following notifications will display on the LSMS console window, where either PRIMARY or SECONDARY indicates the NPAC for which recovery is underway:
[Critical] 2018: 99-07-05 12:55:56 NPAC [<PRIMARY|SECONDARY>] Recovery Failed
or
[Critical] 2019: 99 -07-05 12:55:56 NPAC [<PRIMARY|SECONDARY>] Recovery Partial Failure
If you receive one of these messages, perform the procedure described in Downloading Files from an NPAC to the LSMS using the example for performing a bulk download of files from the NPAC.