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

Backup file HUGE compared to DB size Expand / Collapse
Author
Message
Posted Thursday, November 15, 2012 8:12 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:23 AM
Points: 41, Visits: 356
Hi Guys,

Have a strange one...
Found a job running on one of my servers. Job did a full backup of a database, using the following:

BACKUP DATABASE [tinyDB]
TO DISK = N'<backup drive location here>'
WITH NOFORMAT
, INIT
, SKIP
, NOREWIND
, COPY_ONLY
, NOUNLOAD
, STATS = 10

All fine and dandy that the guy decided to set up a backup for this DB, but what scares me is the size of the backup compared to
the size of the DB and LOG. Backup ends up at 250+GB, but when I do a normal backup of the database I end up with a 3GB backup file.

How the heck ... How is that possible?? Can you guys please help me out with any experiences that you guys have had
in a similar situation??

Grateful for all replies..
Anthony
Post #1385185
Posted Thursday, November 15, 2012 8:28 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, October 27, 2014 3:30 PM
Points: 356, Visits: 919
My first thought was that the process was appending backups. However, INIT and SKIP options imply that it should be overwriting any old backups.

What happens if you try to restore the very large file? Do you see multiple backups in there?
Post #1385198
Posted Thursday, November 15, 2012 8:37 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 8:40 AM
Points: 5,221, Visits: 5,116
whats the output of RESTORE HEADERONLY 'backup path.bak'?



Want an answer fast? Try here
How to post data/code for the best help - Jeff Moden
Need a string splitter, try this - Jeff Moden
How to post performance problems - Gail Shaw
CrossTabs-Part1 & Part2 - Jeff Moden
SQL Server Backup, Integrity Check, and Index and Statistics Maintenance - Ola Hallengren
Managing Transaction Logs - Gail Shaw
Troubleshooting SQL Server: A Guide for the Accidental DBA - Jonathan Kehayias and Ted Krueger

Post #1385203
Posted Thursday, November 15, 2012 11:00 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, October 27, 2014 3:30 PM
Points: 356, Visits: 919
anthony.green (11/15/2012)
whats the output of RESTORE HEADERONLY 'backup path.bak'?


Good one Tony. I forgot about RESTORE HEADERONLY.
Post #1385278
Posted Friday, November 16, 2012 1:03 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:23 AM
Points: 41, Visits: 356
Hi Guys,

Thanks for the replies, unfortunately a team member went and deleted the file due to disk space constraints...
Though I would love to know if I used the RESTORE HEADERONLY/RESTORE and found that there were multiple files,
why would it do that if INIT and SKIP were specified??

Like I say this was so strange, and I have no idea would could be happening...
Any ideas to what you think could have happened??

Thanks,
Anthony
Post #1385521
Posted Friday, November 16, 2012 7:29 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, October 27, 2014 3:30 PM
Points: 356, Visits: 919
Just out of curiosity, was the Agent job running the TSQL commands you specified directly? Or was it executing a backup task via a Maintenance Plan? I've recently seen perfectly fine Maintenance Plan tasks start exhibiting odd, unintended behavior. Deleting and re-creating the Maintenance Plan task fixed the issue. I've learned through that experience that it's better to executing the backup action through the job directly or, even better, create some DBA stored procedures and then execute the sproc through a job.
Post #1385702
Posted Monday, November 19, 2012 1:20 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 3:57 AM
Points: 2,840, Visits: 3,971
Scott D. Jacobson (11/16/2012)
I've learned through that experience that it's better to executing the backup action through the job directly or, even better, create some DBA stored procedures and then execute the sproc through a job.
+1


-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done
Post #1386197
Posted Monday, November 19, 2012 2:18 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Yesterday @ 2:23 AM
Points: 41, Visits: 356
Hi Scott,

Thanks for the reply... The script was executed directly "as is" by the SQL Agent as a job.
That's what is bugging me...
Post #1386235
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse