What are the challenges you face when working across database platforms? Take the survey
Options

SqlbackupC.exe crashes on 'Not enough Storage' error

ihfrickihfrick Posts: 6
edited July 27, 2005 7:31PM in SQL Backup Previous Versions
I have a scheduled task that runs SQLBackupC.exe against two databases every hour. It has been running fine for weeks and this morning suddenly quit working. The one database is 8GB and the log is 400 MB. The second DB is under 2 GB and the log is only 25 MB. I have 66GB of free space on the data drive, and 4GB free on the OS drive. RAM is 2 GB. Every time it runs now I get the following entries in the event log:

BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'SQLBACKUP_24445053'. Operating system error 0x80070008(Not enough storage is available to process this command.).

BACKUP failed to complete the command BACKUP LOG [stats] TO VIRTUAL_DEVICE = 'SQLBACKUP_24445053' WITH BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = '', DESCRIPTION = '', FORMAT

BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'SQLBACKUP_24445053'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

And in the VDI.log I get:

2005/07/26 11:00:00 pid(804) tid(2032)
Error on Global\SQLBACKUP_24445053
Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8
Explanation: Not enough storage is available to process this command.



2005/07/26 11:00:01 pid(804) tid(2032)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked

2005/07/26 11:00:01 pid(1664) tid(2252)
Error on Global\SQLBACKUP_24445053
Error at CVD::GetCommand: AbortDetected

2005/07/26 11:00:01 pid(804) tid(1060)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked

2005/07/26 11:00:01 pid(804) tid(1060)
Error on Global\SQLBACKUP_24445053
Error at SVDS::CloseDevice: Abort detected

2005/07/26 11:00:01 pid(1664) tid(2252)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked

2005/07/26 11:00:01 pid(804) tid(1060)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked

2005/07/26 11:00:01 pid(1664) tid(2264)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked

2005/07/26 11:00:01 pid(804) tid(2032)
Error on Global\SQLBACKUP_24445053
Error at TriggerAbort: invoked


Thanks,
Rick

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Are there any errors in the SQL Server errorlog file?
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Only the same errors I get in the Event Log (as indicated below).

    BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'SQLBACKUP_24445053'. Operating system error 0x80070008(Not enough storage is available to process this command.).

    BACKUP failed to complete the command BACKUP LOG [stats] TO VIRTUAL_DEVICE = 'SQLBACKUP_24445053' WITH BLOCKSIZE = 65536, MAXTRANSFERSIZE = 1048576, NAME = '', DESCRIPTION = '', FORMAT

    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'SQLBACKUP_24445053'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
  • Options
    peteypetey Posts: 2,358 New member
    The error is most likely due to a fragmented MemtoLeave (non-buffer pool). You can use VMStat to confirm this (a tool included with Microsoft's PSS labs http://www.microsoft.com/downloads/details.aspx?FamilyId=AEC18337-887F-4EC6-A858-81F84DE8082F&displaylang=en.

    There doesn't seem to be a way to resolve this other than restarting the service. You might want to try identifying the cause of the fragmentation instead.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
Sign In or Register to comment.