Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I had a maintenance plan fail last night (runs daily) for the first time in ages. The following is the specific error I received, minus the actual database name:

Extend Disk Backup: failure on backup device 'b:\Mydatabase.bak'. Operating system >error 112(There is not enough space on the disk.).

I use WhatsUp Gold for monitoring and upon looking at the historical report, there was more than enough space left during the point the SQL logs say it failed.

The database is nearly 7GB and there was well over 300 GB of free space at the time of failure.

Is this a fluke or am I missing some inside information?

share|improve this question
Is the backup destination a SAN location? Is it thin provisioned? – Mike Fal Jun 3 '14 at 13:56
Yes to SAN and no to thin provisioned. – Sean Perkins Jun 3 '14 at 13:58
You might want to doublecheck that or at least have a chat with your SAN admin. I've seen the scenario you're describing when my disk is thin provisioned. – Mike Fal Jun 3 '14 at 13:59
Okay, will do, I'm in a forward time zone from my SAN admin, so it'll have to wait, but I'll post my findings after, thanks guys. If the off chance this isn't it, any other suggestions? – Sean Perkins Jun 3 '14 at 14:02
I've verified from my SAN admin that we're not using thin provisioning on any of drives for our SQL Servers. – Sean Perkins Jun 3 '14 at 17:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.