View source for 17893317. TRACING DATA IN COMPLEX REPLICATION SYSTEM simplified abstract (International Business Machines Corporation)

=TRACING DATA IN COMPLEX REPLICATION SYSTEM=


==Organization Name==

[[:Category:International Business Machines Corporation|International Business Machines Corporation]]


[[Category:International Business Machines Corporation]]

==Inventor(s)==

[[:Category:He Fang Zhang of Beijing (CN)|He Fang Zhang of Beijing (CN)]][[Category:He Fang Zhang of Beijing (CN)]]

[[:Category:Yan Liu of Beijing (CN)|Yan Liu of Beijing (CN)]][[Category:Yan Liu of Beijing (CN)]]

[[:Category:Meng Zhao of Beijing (CN)|Meng Zhao of Beijing (CN)]][[Category:Meng Zhao of Beijing (CN)]]

[[:Category:Hai Long Shi of Beijing (CN)|Hai Long Shi of Beijing (CN)]][[Category:Hai Long Shi of Beijing (CN)]]

==TRACING DATA IN COMPLEX REPLICATION SYSTEM - A simplified explanation of the abstract==


This abstract first appeared for US patent application 17893317 titled 'TRACING DATA IN COMPLEX REPLICATION SYSTEM

==Simplified Explanation==

* Receiving a message from an agent at a data replication server
* Message includes a status identifier of a checksum validation of a data replication operation
* Identifying a latency value associated with the data replication server
* Determining data loss based on status identifier of checksum validation and latency value
* Transmitting a notification of data loss to a computing system associated with the data replication server

== Potential Applications ==
* Data replication monitoring and error detection
* Data loss prevention in replication processes

== Problems Solved ==
* Identifying data loss in replication operations
* Improving data integrity in replication processes

== Benefits ==
* Early detection of data loss
* Improved data reliability
* Enhanced data replication monitoring and management


==Original Abstract Submitted==

An example operation may include one or more of receiving a message from an agent installed at a data replication server, the message comprising a status identifier of a checksum validation of a data replication operation, identifying a latency value associated with the data replication server, determining whether a data loss has occurred based on the status identifier of the checksum validation and the latency value, and in response to a determination that the data loss has occurred, transmitting a notification of the data loss to a computing system associated with the data replication server.



[[Category:G06F16/27]]
[[Category:G06F16/23]]