SummaryThis article summarizes the issue with SMB file transfer corrupting files and the fix for that issue
OverviewIn situations where users are accelerating SMB traffic between 2 sites, the transferred file may get corrupted. The receiving end will receive a corrupted file which would not open, or open up with garbage information in it. or is not the same file as expected (the information has changed).
CauseWhen the data write size on the client is higher than the server, this issue happens.
If the client writes at 32Kb chunks to the client Exinda and the server side Exinda writes to the server at 16Kb chunks, there is a clear mis-match there. Which causes this issue
WorkaroundThe workaround is to disable SMBAD service on the Exinda under System -> Optimization -> Services
This will accelerate traffic with TCP acceleration engine of the Exinda and not add the extra bit we do with SMB acceleration.
ResolutionThe resolution is to upgrade to version 7.4
There is a fix for this issue in the version stated above.