Added: a seeding capability for checkpoints on the startup of the replicator. It will only attempt to seed (1) if there is no stored checkpoint and (2) if there is something to seed with. If not, it will fall back to the current ICheckpointStore behavior, usually starting from Position.Start. Currently there's either the option to not seed (none) or to seed from a chaser.chk file (chaser). The rationale is that, if you mount the backup a server or cluster was restored from, the chaser.chk file contains the position to resume replication from, thus acting as the seed of a checkpoint store. This change is currently only useful for ESDB to ESDB replication.
Added: a seeding capability for checkpoints on the startup of the replicator. It will only attempt to seed (1) if there is no stored checkpoint and (2) if there is something to seed with. If not, it will fall back to the current
ICheckpointStore
behavior, usually starting fromPosition.Start
. Currently there's either the option to not seed (none
) or to seed from achaser.chk
file (chaser
). The rationale is that, if you mount the backup a server or cluster was restored from, thechaser.chk
file contains the position to resume replication from, thus acting as the seed of a checkpoint store. This change is currently only useful for ESDB to ESDB replication.