We currently have a SQL (2008) job that creates a backup of a 200Gb database and uses another networked server as a target. Both servers are on a Gig backbone. From there the file is backed up daily to tape.
The time taken to create the SQL backup on the target server is becoming excessive, ranging from 9 hours upward.
Backing up the file from the target server to tape (Netbackup) is magnitudes faster and I'm left wondering if we are going about things the wrong way. I don't believe this is a network issue and have monitored both servers/network for bottlenecks.
1) This backup process is a hold-over from an old, non-SQL based system which was recently replaced. What is best practice/the fastest way to back up large SQL databases? Would we be better off installing a Netbackup SQL agent on the source server (and if so why)?
2) What sort of transfer rates are others seeing when creating a SQL backup across the network in such a fashion?
We're pulling our hair out trying to prove/disprove theories at this point so guidelines from anyone with experience in this field would be welcomed.