Backup is taking much time

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » SQL Server 2005 » Backups » Backup is taking much time

Backup is taking much time

Rate Topic

Display Mode

Topic Options

Author

Message

ksr39

Posted Thursday, September 06, 2012 10:28 PM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, November 29, 2012 1:48 AM
Points: 34, Visits: 142

Hi Experts,

Today one of my database took more than expected time for backup i have no idea why it took much time, can any one help me in this if any one gone through this condition/situation. your suggections could help me out in future.

The size of the backup is 30GB and the server is SQL Server 2005 enterprise edition on windows 2003 enterprise edition.

Thank you in advance

Post #1355720

Steve Jones - SSC Editor

Posted Thursday, September 06, 2012 10:41 PM

SSC-Dedicated

Group: Administrators
Last Login: Today @ 4:46 PM
Points: 31,433, Visits: 13,745

How much longer did it take? Is the backup larger? Can you determine if there was other activity at the time of the backup?

Usually if a backup takes more time, it's more data or I/O issues.

Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help

Post #1355724

ksr39

Posted Thursday, September 06, 2012 11:10 PM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, November 29, 2012 1:48 AM
Points: 34, Visits: 142

Hi Steve,
Thank you for your reply, usually it use to take 18 minutes but now it took more than 45 minutes and there is one job running at that time that was Backup of that database, I have not checked the I/O of the data at that time, and can we see that information now after completing the backup if so where can we find that.

Please let me know about this so that I can trace the things and can be aware of that for future.

Thank you in advance.

Post #1355737

GilaMonster

Posted Friday, September 07, 2012 3:27 AM

SSC-Dedicated

Group: General Forum Members
Last Login: Today @ 3:28 PM
Points: 37,730, Visits: 29,996

Backup is an IO bound operation. Either your DB has become significantly bigger (unlikely) or the source or destination drives for the backup are reading or writing slower. Check disk stats on both drives.

Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1355856

ksr39

Posted Tuesday, September 11, 2012 11:27 PM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, November 29, 2012 1:48 AM
Points: 34, Visits: 142

Hi,
Actually I am taking my backup from cmd window with a script it’s a general script to take a backup, but I am taking the backup file to a local drive/disk, as I do in general to a SAN drive/disk through maintenance plan. Will this cause any time variation in taking a backup to a local than to a SAN drive?

Post #1357791

Grant Fritchey

Posted Friday, September 14, 2012 8:51 AM

SSChampion

Group: General Forum Members
Last Login: Today @ 6:44 PM
Points: 13,381, Visits: 25,173

ksr39 (9/11/2012)

Yes. Backing up across the network will absolutely be slower than backing up to a local drive.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software

Post #1359356

Arjen Krap

Posted Saturday, September 15, 2012 9:28 AM

Valued Member

Group: General Forum Members
Last Login: Sunday, April 07, 2013 1:20 PM
Points: 51, Visits: 161

Hi Ksr,

First thing to do is explain your disk setup, so we can understand more about your system. You have already explained that the normally backups are written to a SAN drive, but now your backup is written to a local drive.

The information we need includes the following:

- Is it a physical server or a virtual server?
- On a physical server, how many local disks does your server have? How are they setup? (.e.g. raid levels, partitions, etc.)
- On a virtual server, how many other virtual servers share the same storage facility? (In most cases local disks of virtual servers are actually on a SAN drive.)
- How many other servers have a SAN drive on the same storage facility? (In most cases all these SAN drives share the same physical disks so they compete for performance which each other.)
- On a virtual server, is the SAN drive located on the same storage facility as the local disks?
- Which drives are magnetic rotating disks (e.g. normal hard drives) and which are Solid State Drives (SSD)? (SSD's have significantly better performance, but are a lot more expensive.)

For instance you may have a simple setup where you have a physical server with one local drive which contains the Windows operating system, SQL Server, and all your databases files. Backups are normally written to the SAN drive. In this case during a normal backup the database is read from the local disk and written to the SAN disk. However when you are performing a backup to the local disk the databases is read and written from the same drive which typically reduces performance significantly. For as I can see this compares best to your explanation but we can't be too sure.

If you can't answer those questions, you should probably speak with your storage administrator to get learn how the storage facilities are setup.

Post #1359814

« Prev Topic | Next Topic »

Permissions