When SQL Backup copies backup files for full, differential, filegroup and file backups, the copying is performed as part of the backup task. Hence, the e-mail you receive notifying you that the backup has completed should also have a line indicating that the backup file has been successfully copied to its destination.
For transaction log backups, the copying is performed by a separate process, that runs independently of the backup. Hence, when the backup completes, an e-mail is sent. Details of the file that needs to be copied are placed in a queue, and when the file is eventually copied to its destination by the 'copying' process, another e-mail is sent.
The reason its done this way is that in log shipping scenarios, it is critical that the transaction log backup files gets copied to its destination one way or another. By having a separate process perform the copy, SQL Backup can make multiple attempts to copy the file, without blocking the backup process.
If you want SQL Backup to copy the transaction log backup files as part of the backup process, use the USESIMPLECOPY option e.g.
- Code: Select all
EXEC master..sqlbackup '-sql "BACKUP LOG ... TO ... WITH USESIMPLECOPY"'