Restore space needed WAY more than bak file size

Question

Restore space needed WAY more than bak file size

peterjbassi

SSC-Addicted

Points: 457
More actions
February 11, 2013 at 10:40 am

#289256

I have a 14GB uncompressed .bak file that I'm trying to restore to a new 20GB (20,000MB) database that I just created . When I run the restore it fails with the following error:
There is insufficient free space on disk volume 'F:\' to create the database. The database requires 236339200000 additional free bytes, while only 198730047488 bytes are available.
Unless my math is off, 14GB is less than ~220-230GB. (The stated available bytes left on the disk is correct though). Anybody know what could be causing this? Thanks.
--------------------------------------------------------------
"Daterbase, taterbase, gatorbase."

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply

Bill (DBAOnTheGo) Hall of Fame Points: 3841 More actions · Answer 1

My understanding is that even uncompressed backups do not backup "Free space". so where ever this bak came from... check the actual mdf/ndf file sizes. the space used data space can be 14GB and still have 250GB of "free space" that will be restored on .. .well restore.

Please someone correct me if this statement is wrong.

.

Bill (DBAOnTheGo) Hall of Fame Points: 3841 More actions · Answer 2

http://www.sqlservercentral.com/Forums/Topic777462-169-1.aspx

This is a previous link that has this exact same issue.

.

peterjbassi SSC-Addicted Points: 457 More actions · Answer 3

Thanks Bill. That's exactly what I was looking for. Sorry for the repost.

--------------------------------------------------------------

"Daterbase, taterbase, gatorbase."

Bill (DBAOnTheGo) Hall of Fame Points: 3841 More actions · Answer 4

No worries. They can get lost in time. Glad to help ^.^

.

Jeff Moden SSC Guru Points: 1003857 More actions · Answer 5

As a sidebar, I'm thinking there's something seriously wrong with the database. You're talking about a very small database using almost a quarter of a Terabyte! When you finally get this bugger loaded, look at the recovery model. I'd bet credits to Navy beans that it's in the FULL or Bulk Logged recovery model and that no one has taken a transactional log backup for MONTHS.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

Gazareth One Orange Chip Points: 27737 More actions · Answer 6

Jeff Moden (2/11/2013)
As a sidebar, I'm thinking there's something seriously wrong with the database. You're talking about a very small database using almost a quarter of a Terabyte! When you finally get this bugger loaded, look at the recovery model. I'd bet credits to Navy beans that it's in the FULL or Bulk Logged recovery model and that no one has taken a transactional log backup for MONTHS.

I had a similar problem recently - the culprit was an autogrow setting that been set to 1,000... percent. :w00t: