backup job failing because of insufficient quota

gsegungsegun Posts: 2
Some of my backups have failed recently. Below is the log entry for one of the failures:
######################################################
17/02/2007 08:01:40: Backing up MyDatabase (full database) to:
C:\sql\dumps\MSSQL\FULLs\MyDatabase_db_20070217_080140.sqb

17/02/2007 08:01:40: BACKUP DATABASE [MyDatabase] TO DISK = 'C:\sql\dumps\MSSQL\FULLs\MyDatabase_db_20070217_080140.sqb' WITH NAME = '<AUTO>', DESCRIPTION = '<AUTO>', ERASEFILES_ATSTART = 1, COMPRESSION = 1, THREADS = 1

17/02/2007 08:05:42: Thread 0 error:
Error 620: Error writing to backup file(s).
Process terminated unexpectedly. Error code: -2139684860
Thread 0 warning:
Warning 210: Error writing to backup file: C:\sql\dumps\MSSQL\FULLs\MyDatabase_db_20070217_080140.sqb
Warning: System error code: (Insufficient quota to complete the requested service)

17/02/2007 08:05:42: Server: Msg 3013
BACKUP DATABASE is terminating abnormally.
17/02/2007 08:05:42: Server: Msg 3202
Write on 'SQLBACKUP_EAF84200-FFD4-4557-8D22-B0BF1636D51F' failed, status = 112. See the SQL Server error log for more details.
#######################################################

There is a similar case on the forum (http://www.red-gate.com/MessageBoard/viewtopic.php?p=13240&sid=a8eb1cb488c8c9fd2bf8d41f43f134d6) where the resolution was set the MAXDATABLOCK value to reduce size of each block that's written to the network share. However, in this instance the storage is not a network share but locally (SAN) attached. The help pages also explicitly state that MAXDATABLOCK should not be set on local disks.

At the time of the backup there was another backup job running with 4 threads (on an 8 cpu server). Would this have had an impact and has anyone seen this problem before?

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 New member
    Hi,

    I do't think MAXDATABLOCK has any effect on a SAN at any rate, because SQL Backup should consider your SAN drive as a local disk. If the disk is determined to be local, the buffering setup is hard-coded.

    The closest issue I could find on the Microsoft forum mentioned that SQL Server might do this if the server was doing heavy processing at the time of the backup, but that article applied to SQL Server 7, and has since been claimed to be fixed in SP3.
  • In case you have not, there is, according to msdn error code listing, the possibility that an expired password has caused this to pop up.
    What we do in life echoes in eternity <><
    Randy Volters
Sign In or Register to comment.