Updating backup exec remote agent


In this, each node acts as a publisher as well as a subscriber that means it receives and sends transactions to other nodes, data is synchronised across the nodes.Below is the architecture for two node peer to peer replication As per the above architecture, we can see the application server is sending requests to both the database servers.Suppose we have been working an online supermarket website spread across multiple locations.Customers from different countries open the website and then redirected to the website for their respective country.This way we can achieve both high availability and fault tolerance.If we look at the three nodes architecture below, we can see each one is replicating transactions to the other node and all are having the same copy of the data.Transaction replication in SQL server is used to replicate a full database or a subset of the database configured for the scalability of the database.Below are the terms used in the replication: Publisher: It is the source database, which contains data to replicate.



So topology will remain in an inconsistent state until it is resolved and data is consistent across all the nodes.The application should be getting a consistent result whether it is connecting to either node.So since, it is bi-directional replication, each database is publisher and subscriber so these are called as nodes and replication is called peer to peer replication.In another scenario, there may be a separate application server for each databases node so each database server is getting its own inserts, updates but at the end, it is also being replicated to other nodes as well.

The primary concept of peer to peer replication is that each node is updated with the data but responsible for updating its own data thus it is the essential requirement to have identical schema and data.

Database restoration is required on participating nodes to fulfil the requirement.