# available only in SQL Backup 6 Professional and
newer
With the availability of the COPYTO option in SQL Backup, users could easily
copy their backup files to one or more network shares, in
accordance with the best practice of not having all your backup
files on one box. However, the copy process could fail due to
a temporary network outage. The impact of this outage is most
disruptive on log shipping setups, which causes a break in the
chain of log backups that the secondary server can restore.
To overcome this, SQL Backup will make multiple attempts to copy
the file to the network share(s) when it encounters a network
glitch. Furthermore, it doesn't copy the entire file from the
beginning. Instead, it will resume the copying from the point
of the last successful write.
This feature is easily configurable using the DISKRETRYINTERVAL
and DISKRETRYCOUNT options. For example, if you want SQL
Backup to reattempt the copy 5 times in between intervals of 60
seconds, you would run the following:
EXEC master..sqlbackup '-sql "BACKUP DATABASE AdventureWorks TO DISK =
[g:\backups\<AUTO>] WITH COPYTO =
[\\backupstore\AdventureWorks\], DISKRETRYINTERVAL = 60,
DISKRETRYCOUNT = 5" '
By default, SQL Backup uses a DISKRETRYINTERVAL value of 30
seconds, and a DISKRETRYVALUE of 10.
This network resilience feature is also available for primary
backups i.e. if you back up directly to a network share and there
is a network glitch, SQL Backup will make multiple attempts to
complete the disk write. While backing up directly to a
network share is not something we recommend doing, we undersand
that sometimes circumstances dictate the need to do this, and
that's what we have the network resilience feature for.
Document history
11/4/2010 | Initial release. |