Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Backup Time for 2 TB DB Expand / Collapse
Author
Message
Posted Thursday, January 31, 2013 2:27 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Yesterday @ 10:49 AM
Points: 423, Visits: 316
I am using SQL 2008 R2 before I start backup want to know how long it will take to do full backup for 2 TB database (Aprrox time to backup)

72 GB of Ram dual CPU 2 processor

Post #1414354
Posted Thursday, January 31, 2013 4:54 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Today @ 5:03 PM
Points: 55, Visits: 571
Is this with native backup? Where you backing up,means backup server or same server?

Thanks
Post #1414398
Posted Thursday, January 31, 2013 9:22 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 10:43 AM
Points: 2,945, Visits: 10,517
Why can't you just run a backup and see how long it takes?

Post #1414435
Posted Thursday, January 31, 2013 11:20 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562, Visits: 3,451
a lots of facitor,

1) are you taking backup on local drive or on network ?
2) how fast is the disk and is this is dedicated or not ?
3) are other background processes runnig or not ?
3) how big is the RAM and other resources like CPU , buses etlc etc


-------Bhuvnesh----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post
Post #1414448
Posted Friday, February 01, 2013 3:38 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 6:00 PM
Points: 343, Visits: 1,077
Michael Valentine Jones (1/31/2013)
Why can't you just run a backup and see how long it takes?

That is probably the best advice.
While you are waiting for a backup to finish, you can estimate the time. For example, if your network/storage throughput is 50MB/s sequential write with one thread, one queue. You turned on backup compression and compression ratio is e.g. 2x.
So, 2 000 000 MB / 2 compression ratio / 50 MB/s = 20 000 seconds = about 6 hours.

You can:
- parallelize backup e.g. over 10 separate NIC-s and achieve e.g. 30 minute.
- reorganize some static archive tables/partitions into READ-ONLY marked filegroups. Backup those filegroups once and never more, just regularly check is the backup still readable. Rest of the db that is read-write you need to backup, but it will be much smaller than 2TB.
- use differential backup daily. Full backup not so often. Dif backup is much smaller and much faster than full backup, but to restore you also need last full backup file.


_____________________________________________________
XDetails Addin - for SQL Developers and DBA
blog.sqlxdetails.com - Transaction log myths - debunked!
Post #1414542
Posted Friday, February 01, 2013 4:26 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 1:09 PM
Points: 13,383, Visits: 25,187
And backup is an operation that lets you see what percentage complete it is if you look at the running process in sys.dm_exec_requests.

----------------------------------------------------
"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 #1414566
Posted Friday, February 01, 2013 6:01 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 2:19 PM
Points: 2,037, Visits: 3,761
Use this code (as Grant mentioned, from dm_exec_requests) - it's pretty accurate and will give you a rough idea of when it will complete once you let it run for a while...
USE MASTER
SELECT
SESSION_ID [spid] ,
'[' + CAST( DATABASE_ID AS VARCHAR(10 )) + '] ' + DB_NAME (DATABASE_ID) AS [DB],
PERCENT_COMPLETE [%] ,
START_TIME [Started] , STATUS [Sts], COMMAND [Cmd] ,
DATEADD(MS , ESTIMATED_COMPLETION_TIME, GETDATE()) AS [Est.Comp.Time] ,
CPU_TIME [CPUTime]
FROM SYS .DM_EXEC_REQUESTS
WHERE
COMMAND LIKE '%BACKUP%'
OR COMMAND LIKE '%RESTORE%'
OR COMMAND LIKE '%DBCC%'



______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1414616
Posted Friday, February 01, 2013 6:08 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 2:19 PM
Points: 2,037, Visits: 3,761
Also Bhuvnesh and Vedran have made excellent points. To give you a rough idea, I have nearly the same size DB, I use Idera's SQL Safe software (backup compression) and it takes just over an hour to back up the database. Using Red Gate's Hyperbac software (and not altering the config file) it used to take 5+ hours. Without any compression at all...it would take over 8+

Due to the length of time it took in the past, I opted for a full backup every 2 days, with differentials running every 6 hours, with TLOG backups running every 15 minutes. In my situation, this works for us...




______________________________________________________________________________
"Never argue with an idiot; They'll drag you down to their level and beat you with experience"
Post #1414623
Posted Monday, February 04, 2013 9:58 PM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Today @ 2:45 AM
Points: 525, Visits: 1,005
As all mentioned in my view my backup of a database size is 109 Gb approximately takes one hour then around 1 TB will take nearly 22 hours
and then 2 Tb might take nearly 45 to 46 hours if there is no disturbances like network failure, backup job failure, disk space issue

and my suggestion if it u have device backups then it is good to split the backup and run in this cases a single backup file might fail.then all the work time effort might be waste.

If it is a device backup even if u run the device backup through split backup maintenance plan jobs it is easy to identify the backup job number easy


Thanks & Regards
NAGA.ROHITKUMAR
Post #1415565
Posted Tuesday, February 05, 2013 7:32 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Friday, April 26, 2013 2:58 PM
Points: 221, Visits: 452
I used Litespeed on a 2005/2008 R2 SQL Cluster. Like many mentioned a lot of factors, disk IO being a major part. Native backup would have never worked out for me, too slow... I backed up 1.5TB database with about 80% compression using litespeed in just over 1 hr. It's faster with lighter compression. Litespeed also has a backup analysis tool that will simulate backup of 50% of your DB size with various compression and give you time and compression rate info.
The storage was an Equalogic Fibre San, RAID10, 4 data LUN, 1 TLog Lun, I think about 30 disks.
Disk IO has always been the bottleneck for me so beefy server is great but beefy storage is better, and by beefy storage I mean lots and lots of spindles...



---------------------------------------------------------------
Mike Hahn - Future MCM 2025
Right way to ask for help!!
http://www.sqlservercentral.com/articles/Best+Practices/61537/
I post so I can see my avatar
I want a personal webpage
I want to win the lotto
I want a gf like Tiffa
Post #1415836
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse