May 28, 2014 at 10:43 am
More of an observation that I can't come up with a good explanation for through google. Hoping some of the seasoned pro's can weigh in.
When setting up P2P replication I follow this sequence:
1. Create publication on node 01.
2. Backup database on node 01.
3. Restore database on node 02.
4. Add subscription from node 01 to node 02.
5. Create publication on node 02 (Ensure P2P originator ID is set properly).
6. Add subscription from node 02 to node 01.
7. Make change on node 01.
8. Verify change on node 02.
9. Make change on node 02.
10. Verify change on node 01.
This is all fine and good and has always worked very well for me, but; when I open replication monitor I can see a plethora of undistributed commands from node 01 to node 02. Even though changes are moving between the 2 nodes in near real-time.
What is the cause for this?
Is it anything to be concerned about?
When making the backup from node 01 to restore on node 02, will using copy-only make any difference? (note: I have tried both copy-only and standard full backups for this)
If I were to restore another recent backup on top of the db at node 02, will it completely wreck the entire thing? or will it bring everything into sync.
Thanks!
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply