Synchronizing Data Between the Main LSMS and Shadow LSMS

Both NPAC data and locally provisioned data need to be synchronized between the main and shadow LSMS so that the shadow can take over when the main LSMS fails.

• NPAC data synchronization occurs in one of the following ways:
  • With an active shadow, active connections from both main and active shadow to the NPACs allow transmission of the same NPAC data to both LSMSs.
  • With an inactive shadow, NPAC data is synchronized by downloading files from the NPAC to the inactive shadow LSMS.
• Locally provisioned data must be manually entered at both the main LSMS and shadow LSMS.
  Note: When you log in to manually enter any locally provisioned data, always use the same service provider ID (SPID) at both the main LSMS and the shadow LSMS. Locally provisioned data is correlated with a SPID. In order for the data to be the same at the main LSMS and shadow LSMS, it must be entered with the same SPID at both LSMSs. The main LSMS and shadow LSMS must use different NPAC-assigned SPIDs for their association with the NPAC. You can create SPIDs used just for entering data, or you can use the main LSMS’s NPAC-assigned SPID for entering locally provisioned data at both the main LSMS and shadow LSMS.

  For information about manually entering locally provisioned data, refer to the Database Administrator's Guide.