Open
Description
Recovery/restart records keep track of the last sequence number that was saved in the target database. Assume the source is a huge database and an aggressive filter is defined that eliminates most documents (lets say the first million) from the source. If the service encounters a fatal error before the first recovery record is written, the service restarts processing with sequence number 0 instead of resuming with the last sequence number that didn't pass the filter.