Further update to my reply of the 9th May 2014.
The situation described in this forum post is very rare. From my experiences supporting SQL Backup, this problem occurs when manually copying files from one location to another, normally between different physical machines.
If the user does encounter this problem, you can use the SQL Backup Testing Utilities to check the file integrity of the copied file and to generate a MD5 hash of the copied file, generate MD5 hash of the original backup file and compare the hash codes. If there is a mismatch in the MD5 hash code, the copied file is most likely corrupted.
Retry the manual copy process, or use an alternative copying tool.
If you still continue to encounter problems, please send an email to the Red Gate Support team [support@red-gate.com] and create a support ticket.
Many Thanks
Eddie
The situation described in this forum post is very rare. From my experiences supporting SQL Backup, this problem occurs when manually copying files from one location to another, normally between different physical machines.
If the user does encounter this problem, you can use the SQL Backup Testing Utilities to check the file integrity of the copied file and to generate a MD5 hash of the copied file, generate MD5 hash of the original backup file and compare the hash codes. If there is a mismatch in the MD5 hash code, the copied file is most likely corrupted.
Retry the manual copy process, or use an alternative copying tool.
If you still continue to encounter problems, please send an email to the Red Gate Support team [support@red-gate.com] and create a support ticket.
Many Thanks
Eddie