March 15, 2010 at 12:36 am
Hello,
What can be done to prevent the deterioration in performance when the full backup runs?
Since the backup process itself will generate lot of IO to slow down the regular transactions?
Also, does anyone has statistics of how much time does a 1TB full backup take?
We are backing up on a network share over 1GB network. both servers have 15K RPM DAS disks.
Regards,
Abhishek
March 15, 2010 at 1:57 am
Change the backup so it goes to a local drive, will be much faster. Once the backup has completed then copy it remotely. That should decrease the time that the backup impacts the performance.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 15, 2010 at 3:32 am
SQL-Student (3/15/2010)
What can be done to prevent the deterioration in performance when the full backup runs? Since the backup process itself will generate lot of IO to slow down the regular transactions?
It depends on what is causing the deterioration in performance. This is a complex subject, so even if you are able to provide local disk recommended by Gail, I would recommend reading the following Microsoft White Paper:
Technical Case Study: Backup VLDB Over The Network (note this link downloads a 4.25MB Word document)
In the example studied there, a 2TB database was backed up to a site 10 miles away in 38 minutes. It is a very thorough document; I recommend it to you.
Paul
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply