Is the Network Copy functionality actually breaking the backup file into segments to transfer to the remote location in order to achieve higher bandwidth?
No, SQL Backup does not split the backup file into multiple segments to copy the file.
Could you please try using the USESIMPLECOPY option in your backup command e.g.
- Code: Select all
EXEC master..sqlbackup '-sql "BACKUP ... WITH USESIMPLECOPY ..."'
This causes SQL Backup to use the Windows API to copy the file, instead of its internal copy process. The difference is that if the copying fails midway, USESIMPLECOPY will restart from the beginning, while the internal copy process tries to restart from where it last failed. For the purpose of this test, we just want to know if your issue lies with the internal copy process.