Results 1 to 2 of 2

Thread: How does R-1 ensure that no data corruption takes place when files are replicated?

  1. #1
    Andrew.Lupton is offline Banned
    Join Date
    Apr 2013
    Posts
    18
    Rep Power
    0

    How does R-1 ensure that no data corruption takes place when files are replicated?

    How does R-1 ensure that no data corruption takes place when files are being replicated? Also, how does a replication job recover from an unexpected error?

  2. #2
    Andrew.Lupton is offline Banned
    Join Date
    Apr 2013
    Posts
    18
    Rep Power
    0
    To be a part of mission-critical environments, integrity and recovery are mandatory requirements. The integrity of files being replicated and the ability to recover from unexpected errors or problems were key factors addressed in the development of R-1.

    R-1 is an entirely stateless application and holds nothing in RAM. Whether it be a system time-out, reboot or a loosened network cable, as soon as the systems are up and running, R-1 will recover all of the interrupted replications from the block level in any file transfer.

    • R-1 does not trust the write-caching of the operating systems it is installed on, so even the partial file that exists on the target is checked on the fly to guarantee its integrity - if corruption occurs, R-1 "scrolls back" through the file until a common point is reached before resuming transfer.
    • R-1’s Transactional Updates overcomes content inconsistency over lengthy replication processes. It enables performing publishing on all servers at a future set date and time after content has been completely deployed. The deployment process provides complete business integrity, starting from data integrity on the file level, up to distribution to multiple centers, enabling a scheduled deployment and rollback capabilities. In the event of failure in the publishing process, all servers can be rolled-back to their original content.
    • Files are transferred to a unique temporary location before being renamed to the target filespec. This guarantees that incomplete / corrupted files never exist on the target's live directory.
    • If the WAN or LFA transport engines are used, the transfer also verifies as follows:
      • Synchronization - Guarantees the synchronized writing of the output file to the disk.
      • CRC - Performs a double CRC check on each transmitted packet. This ensures that the data which was received at the target node has not been changed - either by the network or by compression and decompression algorithms.
      • Compare - Performs a comparison on the full source and destination files following the file transfer, to ensure that they are identical.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •