Either way, if you want to ensure that the transmitted file is exactly the same as the source file, you can use a checksum.The checksum is calculated using a hash function and is normally posted along with the download.
Since I never encountered any restore issue, I have these two questions: -- How critical is it to actually perform a backup validation, in the first place? By adding the validation option to the backup settings, doing it right after the backup operation completes or right before restoring an image?
To ease me in gently, can you recommend a quick primer on My SQL using My SQL/Connector/NET? I tried it, but ended up going back to an earlier version of My SQL GUI Tools which you can download here: My SQL GUI Tools People also use Toad.
I'm gonna see if I can convert this to use MS SQL and use a customized version of this code as a File Itegrity Monitoring tool to meet security compliance requirements. I'm sure that you've just saved me many weeks of work on a project I have been putting off for ages.
Sure, just enable checking the checksum in the protocol preferences of IPv4.
To do that, either click on the decode header line for IPv4 and use the pop up menu option to enable the check, or go to Edit - IPv4 options UDP checksum error on IPv4 frame with loose source route.