March 21, 2016 at 2:24 pm
There is plenty of space left on the disk where the backup is stored. Why am I getting this error?
Using a maintenance plan to do full backups every week. Approx 110 dB's (out of 500 total) didn't get backed up because of this error. I found them and did a full backup of each. There is still plenty of space on the disk. Is this not really disk space it's talking about? Maybe temp space or something?
Any help is appreciated.
March 21, 2016 at 2:53 pm
Are you backing up to a network share? Did the network 'drop' during the backup file creation?
March 21, 2016 at 2:57 pm
Backing up to a local drive on the server
March 21, 2016 at 4:00 pm
I can't find an article to reference, but IIRC SQL does something that results in a much higher number than actual when estimating how much space it's going to need to do a backup. It might actually be that built in maintenance task that has the bad estimate.
March 22, 2016 at 12:20 am
This was removed by the editor as SPAM
March 22, 2016 at 8:37 am
Can you be more specific? What temp space are you referring to? tempdb? The OS temp directory?
This post specified that SQL doesn't use temp space for backup:
March 22, 2016 at 9:02 am
Could it be that new backups are taken and then old ones are removed, so when the backups are being taken there is indeed insufficient space, but once the old ones are deleted there is once again plenty of space?
March 22, 2016 at 9:09 am
I've done the backup routine steps one at a time. There is plenty of space left even before the old backups are removed.
March 22, 2016 at 9:16 am
Are you using compression? If so, the initial size creation calculation for the file may be the size of the uncompressed backup. You might need more wiggle room on the drive if this is the case.
March 22, 2016 at 9:40 am
The task in the maintenance plan has the backup compression set to server default. The server properties show the compress backup setting as unchecked.
March 22, 2016 at 10:33 am
You may want to validate that the shadow copy service isn't causing an issue (I've had that happen before)
vssadmin list shadowstorage (from cmd prompt)
March 22, 2016 at 1:39 pm
Results from that command....
"No items found that satisfy the query."
March 23, 2016 at 8:07 am
That's a pretty good stumper. Personally I would turn on compression, aside from saving space it will frequently also save time as it compresses the data after the read but before the write to backup, so the write time is saved. And you're backing up A LOT of databases. But I don't think that's your problem. Also, I'd consider Ola Hallengren's backup script, perhaps there's some tuning that you could do through it rather than relying on a maintenance plan. Myself and many others here are not fans of maintenance plans for a variety of reasons, one being the inability to fine-tune what it's doing.
One thing to check is the version of SQL Server: are you fully patched? It looks like we're basically grasping at straws since the common/obvious things do not seem to be the problem. Since you're backing up to a local drive, have you checked OS system logs to make sure it's not reporting I/O errors? Could the drive be having problems?
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply