Yeah I see the problem, but there is not an easy solution to this other than the obvious fixing the P2P server side crash. The replication process has no way of knowing that these two replications are the same (on the client side it does, but the server side will force the reset to zero as a safety measure). I’ll file a ticket and try to reproduce this. This is my last working day before my winter break but if I can reproduce and fix this soon then it will make it into our 1.4 release.