Very large backup

[icemel]

Question about very large backup.

If I am backing up to a local directory with 279 GB available, and the database size that I am backing up is 164 GB, is there any reason that space would be an issue??

Ok sounds silly, but this particular backup has been failing for reasons I can't explain. There is no job history recorded, or any events in the application logs.

Has worked in the past.

Thank you

 

[mrdenny]

That should fit fine. Check security permiossions on the folder.

If your using a maint plan check the plans report. If it's just a backup database command turn on the output from the job step to write to a file. Or run the command manually.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[SQLBill]

Make sure that is the real size of the database and not just of the data. Remember, the database also has 'unused' space. That also gets backed up.

For example, I have a database where the data is 99 GB, but the database size is 155 GB. We have to do an upgrade and the vendor says it will take over 12 hours to upgrade a large database, so we backed up the database for archive and are removing old data - down to only 30 days. As we are removing data, it's leaving a large amount of unused space. Unfortunately, that unused space gets backed up also.

-SQLBill

Posting advice: FAQ481-4875

 

[SQLDenis]

You can always take a look at SQL litespeed

http://www.quest.com/litespeed_for_sql_server/

This will compress the backup and speed things up dramatically (in addition to using a lot less space)

Play around with the trial version



Denis The SQL Menace
SQL blog:

http://sqlservercode.blogspot.com/

Personal Blog:

http://otherthingsnow.blogspot.com/

 

[icemel]

Thanks all for your responses. I will check out Quest litespeed.