We have a 3 node P2P replication in a ring topology (each node is connected to every other node), A, B, C. Occasionally the connection between A and B is interrupted for a long enough period that the subscription that B has for A gets marked as inactive. However because A is also connected to node C which is then connected to node B I had assumed that B could still go on functioning as normal as all the updates from A could flow to B via C and vice versa.
So when this happens it seems that I am forced to remove B from the topology and reinitialise B from a backup of A or C and re-add the node to the topology. This is a problem for me as the databases are large and backups take up to 12 hours to transfer from one node to the other, essentially putting the node out for nearly a day.
So currently I've increased the transaction retention on the 3 distributors from 3 to 5 days to try and alleviate the issue.
However I would like to know why I can't simply "reinstate" the connection between A and B rather than having to go through all the hassle of restoring B from a backup. If someone can advise if I'm going about this the wrong way that would be much appreciated.
Thank you,
Warren