agradmin
asked on
Slow SQL backup across network
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.
Questions;
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.
Thanks!
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.
Questions;
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.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
In addition to backing up to a local drive, if you have an edition that supports it consider using compression. If you don't consider purchasing a third party tool such as Red-Gate's SQL Backup
ASKER
Thanks for the help. We are still trying to speed things up but the information will help us make decisions.
If you are that takes a significant amount of time because it is basically unpacking the backup.
I agree with Padawan -- see if you can do a local backup and copy the resulting file over.
If you have to do it to the UNC then skip the verify. You can always setup a SQL instance on the other server just to do a verify. Not used for any other purpose it shouldn't need a license.
I still have not found a SQL backup agent that I trust.