SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Backup file HUGE compared to DB size


Backup file HUGE compared to DB size

Author
Message
AnthonyFourieMS
AnthonyFourieMS
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 433
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 Crazy... 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
Scott D. Jacobson
Scott D. Jacobson
SSChasing Mays
SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)

Group: General Forum Members
Points: 618 Visits: 1017
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?
anthony.green
anthony.green
SSChampion
SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)SSChampion (10K reputation)

Group: General Forum Members
Points: 10052 Visits: 6321
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
When a question, really isn't a question - Jeff Smith
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


Scott D. Jacobson
Scott D. Jacobson
SSChasing Mays
SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)

Group: General Forum Members
Points: 618 Visits: 1017
anthony.green (11/15/2012)
whats the output of RESTORE HEADERONLY 'backup path.bak'?


Good one Tony. I forgot about RESTORE HEADERONLY.
AnthonyFourieMS
AnthonyFourieMS
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 433
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
Scott D. Jacobson
Scott D. Jacobson
SSChasing Mays
SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)SSChasing Mays (618 reputation)

Group: General Forum Members
Points: 618 Visits: 1017
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.
Bhuvnesh
Bhuvnesh
SSCertifiable
SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)SSCertifiable (5.2K reputation)

Group: General Forum Members
Points: 5186 Visits: 4076
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;-)
AnthonyFourieMS
AnthonyFourieMS
Valued Member
Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)Valued Member (53 reputation)

Group: General Forum Members
Points: 53 Visits: 433
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...
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search