Large database backup files integrity check after or before copy I was trying to copy large database backup files(appx. 2TB each) to different region using robocopy. But I have noticed the speeds are drastically slow when using the switch /Z. So I have removed this switch and my copy is now faster. But now the challenge is,


how to verify the consistency of copied files.
what is the best possible way to skip the files if the files are already present in target location. 
I have tried using powershell get-filehash command to verify file consistency but it’s too slow on large files especially on files located in different region.


My current command syntax,

robocopy source_directory destination_directory file_name /R:3 /W:10 /LOG+:log_file_location

Any best possible ways to address this?
SQL Server has a very handy command which checks the headers, checksums (if present) and that the backup set is complete. A data integrity check will be performed if a checksum is present but is optional. From the documentation here

RESTORE VERIFYONLY FROM DISK = 'D:\AdventureWorks.bak' WITH CHECKSUM;
GO