3.2.5.3 Data Verification Pull Replication
Data verification pull replication can be initiated manually or via a database verification timer. Data verification pull replication happens in the following phases:
Association setup: The pull partner goes through all the owner NBNS servers one by one. All the active name records owned by the owner NBNS server to be verified are scanned and the maximum version number is determined. Then a NBNS server is selected and an association is set up with it. If the owner NBNS server is one of the configured push partners, then the association will be with the push partner. If the owner NBNS server is not configured as a push partner, and if the configuration allows data verification with non-partner NBNS servers, then the association will be with the owner NBNS server. If the owner NBNS server is not configured as a push partner, and if the configuration only allows verification with push partners, then the association will be with a randomly selected push partner. No persistent association is used in data verification pull replication.
Obtain Name Records: The pull partner then sends a Name Records Request message. The minimum version number in a Name Records Request message is 1, and the maximum version number is the highest version number of all active name records owned by the owner NBNS server.
Update local database: Once the Name Records Response message is received, the pull partner updates all the name records in its database owned by the owner. If any name records are not found in the response message, it is deleted from the local name record database.
An NBNS server MUST stop data verification, if during data verification it retrieves the maximum number of records per verification;<10> it SHOULD continue the verification during the next expiration of the database verification timer.
If data verification pull replication is manually initiated, all owner NBNS servers will be verified. The data verification is not subject to the maximum number of records limitation.