B&R the right way

[rickslick]

If I take a backup from an old pgedge system , and then restore it on another pgedge cluster ( 2 node replication empty system) , then the partner of the destination cluster (which is replicating frm the node where restore was run ) is complaining about no replication origin. Sync breaks ie subscritption from the partner is a continues worker error exit thread

Backup size approx 11 gb
spock main branch line is being used for testing

2025-07-21 07:26:28.253 UTC [299] LOG:  SPOCK: caught exception after replay queue overrun - forcing apply worker restart
2025-07-21 07:26:28.253 UTC [299] ERROR:  StartTransactionCommand: unexpected state STARTED
2025-07-21 07:26:28.253 UTC [299] LOG:  apply worker [299] at slot 2 generation 1 exiting with error
2025-07-21 07:26:28.253 UTC [299] FATAL:  no replication origin is configured
2025-07-21 07:26:28.256 UTC [44] LOG:  background worker "spock apply 16388:2979946351" (PID 299) exited with exit code 1
2025-07-21 07:26:28.269 UTC [2654] LOG:  SPOCK sub_n1_n2: connected

what is the recommended approach for B&R .

[mason-sharp]

Which version of Spock are you using? Are you trying to add a node and following this procedure?

[rickslick]

@mason-sharp the system is already in place and replication is verified. We had an old backup and wanted to restore this in the 2 node replication system. As soon we apply the restore command the other node is complaining with no replication origin. Should ideally stop the subscription and then start from origin for these scenarios or is there a cleaner approach

spock 5.0.0

[mason-sharp]

Yes, stop the subscription from the other node you are trying to recover from. If the goal is to have a two node cluster and that these nodes should have identical data and be based on a backup, you could restore one node, then add another node based on it.