Backup file size 150 GB - Restore requires 3 times that size on disk

  • Folks,

    I am trying to restore my production db backup to a test server that has 198 GB free. My initial production backup db size is 148 GB. When I try and do a restore to my TEST server I get an error telling me there is insufficient disk space and that I need roughly 438 GB free space to do the restore...

    I am not understanding why this is the case. Any suggestions on how I can get a back up small enough to fit the 198 GB space would definitely be very helpful!!

  • the file sizes the backup is trying to restore add up to 438GB.

    the files of the source database would need to be shrunk before taking the backup.

    This is something you only want do with care..

    check file sizes of the prod database, what are they?

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

  • you can create a database that researves a ton of freespace for future growth; when you restore that backup, it requires all that reserved free space as well...so getting a backcup from a client that did that space reservation makes it hard.

    Red Gates Virtual Restore lets you open and edit an actual full backup without that space headache; I know Idera has a similar product.

    you can at least use the demo version for now, but it's a handy tool to have for exactly that type of situation.

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • I would recommend that you check the recovery model of the source database. Is it full recovery? If yes, are you backing up the transaction log on a regular basis?

    Most of the time I see this, the source system is not backing up the transaction log - which causes the transaction log to continually grow until it fills the drive. When you try to restore to another system, that file needs to be created and you don't have enough space.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • I know of an issue where restoring the backup the file growth value gets set to some random value and usually its a percent.

    I think there was a hot fix (might be included in the latest service pack).

    Jayanth Kurup[/url]

  • any chance there is a script or job doing something like this?

    since you said it happens "regularly, maybe there's an obscure snippet in a job or something

    IF EXISTS (SELECT * FROM sys.database_principals WHERE name = N'YOURROLE' AND type = 'R')

    DROP ROLE YOURROLE

    GO

    CREATE ROLE YOURROLE

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • wrong thread lowell!

    :w00t:

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

  • too many windows open!

    i editit it off in another window, and then when i thought it was ready, hit the "reply" on the wrong tab...

    I'm properly admonished now, thanks!

    :w00t:

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • george sibbald (6/30/2011)


    the file sizes the backup is trying to restore add up to 438GB.

    the files of the source database would need to be shrunk before taking the backup.

    This is something you only want do with care..

    check file sizes of the prod database, what are they?

    I actually figured out what my issue was... My initial Log size was set to 399GB which now makes sense as to why the restore did have enough space to complete. I am changing the size of the log file before tonights backup and then we'll try this again. I did check and I haven't had a transaction log backup that was over 98GB in size. I am going to set my initial log file size to 175GB and this should lower the size of the full backup to around 325GB. And hopefully will provide enough room to do a restore on our test server.

    I appreciate all the replies... sometimes you just have to hear someone give their perspective to start the thinking process... 🙂

  • "did NOT have enough space to complete" rather...

  • glad to help.

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

  • timr-1113026 (7/1/2011)


    sometimes you just have to hear someone give their perspective to start the thinking process... 🙂

    The following in future may be helpful to trouble shoot these problems

    RESTORE FILELISTONLY

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

    "Ya can't make an omelette without breaking just a few eggs" 😉

Viewing 12 posts - 1 through 11 (of 11 total)

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