All TeraByte Unlimited imaging products support a variety of validation methods. This functionality is designed to provide you with as much flexibility as possible, while assuring the best data integrity available.<\/p>\r\n
When considering the differences between the different types of validation, it helps to consider the following depiction of the "flow" of data during a backup:<\/p>\r\n
[source drive] >>> [system memory] >>> [target drive]<\/strong><\/p>\r\n Validate<\/font><\/strong><\/p>\r\n The Validate<\/strong> option (sometimes referred to as a "standard validation") serves primarily to catch errors that occur between the system memory and the target drive. This includes the CPU, mainboard caches, data cables, the IDE\/SATA\/USB\/IEEE 1394 controller, and the target drive itself. This checking is performed on the entire image.<\/p>\r\n When an error is detected during a standard validation, one of the following error messages will be displayed:<\/p>\r\n Version 3.00 or later:<\/p>\r\n ABORT: Data corruption was encountered<\/font> (error occurred during data processing) <\/p>\r\n FAIL: Data did not pass validation<\/font> (data processed, failed validation check)<\/p>\r\n <\/blockquote>\r\n Version 2.99-00 or earlier:<\/p>\r\n The image stream is corrupt<\/font> or Validation failure<\/font><\/p>\r\n <\/blockquote>\r\n These error messages indicates that a problem occurred somewhere between the system memory and the target drive.<\/p>\r\n <\/blockquote>\r\n Validate Byte-for-Byte<\/font><\/strong><\/p>\r\n The primary capability of a byte-for-byte validation is to detect errors that occur from the source drive to the system memory. As with a standard validation, a byte-for-byte validation applies to the entire image.<\/p>\r\n Note that when you use the Validate Byte-for-Byte<\/strong> option, you are actually performing a byte-for-byte validation in addition to<\/em> a standard validation. Therefore, when using this option, it is possible to receive the aforementioned error messages (those which refer to the standard validation process) or<\/em> Byte-for-Byte comparison failed<\/font> error messages. This latter message denotes that an error was detected between the source drive and system memory.<\/p>\r\n Validate Disc<\/font><\/strong><\/p>\r\n The Validate Disc<\/strong> option is only available when saving images to optical discs. This type of validation is designed to verify that the data sent to the disc is exactly what is actually written to the disc. This type of validation cannot detect errors that may occur between the source drive and system memory.<\/p>\r\n The Validate Disc<\/strong> option can be used either alone or in conjunction with the Validate<\/strong>\/Validate Byte-for-Byte<\/strong> options.<\/p>\r\n If the Validate Disc<\/strong> function detects an error, it offers to let you recreate the affected disc. This is beneficial because errors detected by the other types of validation require you to restart the entire imaging process. Please note, however, that if you use the Validate Disc<\/strong> option along with the Validate<\/strong>\/Validate Byte-for-Byte<\/strong> options, it is possible for the latter validation method(s) to detect an error that Validate Disc<\/strong> was not able to. In such a case, you would have to start the imaging process over.<\/p>","protected":false},"excerpt":{"rendered":" All TeraByte Unlimited imaging products support a variety of validation methods. This functionality is designed to provide you with as much flexibility as possible, while assuring the best data integrity available. When considering the differences between the different types of validation, it helps to consider the following depiction of the "flow" of data during a […]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"lsvr_kba_cat":[1805],"lsvr_kba_tag":[],"class_list":["post-350","lsvr_kba","type-lsvr_kba","status-publish","hentry","lsvr_kba_cat-shared-issues"],"_links":{"self":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/350","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/comments?post=350"}],"version-history":[{"count":0,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba\/350\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/media?parent=350"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_cat?post=350"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/www.terabyteunlimited.com\/kb\/wp-json\/wp\/v2\/lsvr_kba_tag?post=350"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\r\n
\r\n
\r\n