<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Backups
»
Backup file HUGE compared to DB size
Backup file HUGE compared to DB size
Rate Topic
Display Mode
Topic Options
Author
Message
SQLAnthibian
SQLAnthibian
Posted Thursday, November 15, 2012 8:12 AM
Grasshopper
Group: General Forum Members
Last Login: 2 days ago @ 3:33 AM
Points: 19,
Visits: 300
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
Scott D. Jacobson
Scott D. Jacobson
Posted Thursday, November 15, 2012 8:28 AM
Old Hand
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:17 PM
Points: 335,
Visits: 841
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
anthony.green
anthony.green
Posted Thursday, November 15, 2012 8:37 AM
SSCertifiable
Group: General Forum Members
Last Login: Friday, April 12, 2013 3:51 AM
Points: 5,075,
Visits: 4,831
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
Scott D. Jacobson
Scott D. Jacobson
Posted Thursday, November 15, 2012 11:00 AM
Old Hand
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:17 PM
Points: 335,
Visits: 841
anthony.green (11/15/2012)
whats the output of RESTORE HEADERONLY 'backup path.bak'?
Good one Tony. I forgot about RESTORE HEADERONLY.
Post #1385278
SQLAnthibian
SQLAnthibian
Posted Friday, November 16, 2012 1:03 AM
Grasshopper
Group: General Forum Members
Last Login: 2 days ago @ 3:33 AM
Points: 19,
Visits: 300
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
Scott D. Jacobson
Scott D. Jacobson
Posted Friday, November 16, 2012 7:29 AM
Old Hand
Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:17 PM
Points: 335,
Visits: 841
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
Bhuvnesh
Bhuvnesh
Posted Monday, November 19, 2012 1:20 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, March 26, 2013 8:41 AM
Points: 2,562,
Visits: 3,451
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----------
While 1 = 1 (Learning SQL....)
Click to get fast response of your post
Post #1386197
SQLAnthibian
SQLAnthibian
Posted Monday, November 19, 2012 2:18 AM
Grasshopper
Group: General Forum Members
Last Login: 2 days ago @ 3:33 AM
Points: 19,
Visits: 300
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 »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
