When performing a full Integity Check , some files are reported as having invalid hashes e.g.:
When a Streaming Backup connection was dropped due to communications issues and the backup client retried the backup, the file that was being backed up during the connection drop would have been stored on the SP with an incorrect hash. Even though the file had an incorrect hash reference the data was still correct and restorable at that point. However, manually running a Full IC at that point would have detected this invalid hash and reported it as data corruption, deleting the file and any dependencies in the process. If no IC was run the affected file will however be restored without error, and rolling up to any patches that were dependent on the file would also result in valid data.
The bug in the backup client has been fixed in V7.0.3 so that connection issues will no longer result in invalid hashes on the SP.
Also added in the V7.0.3 StorageServer are two new settings:
This issue is resolved in V7.0.3 Storage Platform.