What is write order fidelity? Please elaborate.
Requires Free Membership to View
When you register for SearchStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Our goal is to keep you informed on the hottest topics, the latest news and the biggest challenges you face as a storage professional today.
Rich Castagna, Editorial Director
This is a Q&A from SAN School Lesson 6.
Click here for more SAN School lessons. Write order fidelity is a term that describes the ability of d data replication hardware or software to move data between geographic locations while keeping consistency for transaction oriented applications. In other words, it's the ability to keep data "in the same sequence" as it was written at the originating source. This is extremely important for database consistency. If data is written in an incorrect sequence at different sites, the transaction logs will no longer be consistent and databases can become corrupt at the remote site. The operations are kept in proper sequence by assigning either a timestamp or sequence number to each write at the source site. The data is then transmitted to the remote site over multiple links for load balancing or asynchronously for longer distances, then reordered to the proper time sequence before written to the logs at the remote site.
Click here for more SAN School lessons. Write order fidelity is a term that describes the ability of d data replication hardware or software to move data between geographic locations while keeping consistency for transaction oriented applications. In other words, it's the ability to keep data "in the same sequence" as it was written at the originating source. This is extremely important for database consistency. If data is written in an incorrect sequence at different sites, the transaction logs will no longer be consistent and databases can become corrupt at the remote site. The operations are kept in proper sequence by assigning either a timestamp or sequence number to each write at the source site. The data is then transmitted to the remote site over multiple links for load balancing or asynchronously for longer distances, then reordered to the proper time sequence before written to the logs at the remote site.
This was first published in April 2004