Failed to close vdi

JeffatWorkJeffatWork Posts: 7
edited May 11, 2006 1:50PM in SQL Backup Previous Versions
Thread 0 error:
Below is the error I receive when trying to backup a database with RedGate. I had a generic error and then upgraded to 4.2. Does anyone have any idea how I can move past this or what the problem may be?

Thanks...
Process terminated unexpectedly. Error code: -2139684860

Server: Msg 3013
BACKUP DATABASE is terminating abnormally.
Failed to close vdi.

SQL Backup exit code: 1050
SQL error code: 3013

(12 row(s) affected)

name,value
exitcode,1050
sqlerrorcode,3013
filename01,L:\msdb_Full_rg.bak
· Share on Twitter

Comments

  • JeffatWorkJeffatWork Posts: 7
    This error shows up in the VDI log....

    2006/05/08 16:05:29 pid(2324) tid(3264)
    Error on Global\SQLBACKUP_8AB7AB53-D604-4815-92DA-757B536C8517
    Error at ServerBufferAreaManager::Allocate: Map buffers Status Code: 8, x8
    Explanation: Not enough storage is available to process this command.


    2006/05/08 16:05:29 pid(2324) tid(3264)
    Error on Global\SQLBACKUP_8AB7AB53-D604-4815-92DA-757B536C8517
    Error at TriggerAbort: invoked
    · Share on Twitter
  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hi Jeff,

    We are working on tracking this one down at the moment. I suspect that this has crept into the 4.2 extended stored procedure code.
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    If you are still experiencing the problem during the backup, could you pls run

    exec master..sqbmemory

    and post the results? Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • henkmeulekamphenkmeulekamp Posts: 14
    The error is raised during logshipping and after the file is copied from backup location to the destination server.

    I discoverd that the databas was still (2.8 GB ) loading on the secondairy machine where the error was raised when sqb transaction logs where restored.. This raised this same error. I will retry the restores again after the first initial restore is loaded and fully (readonly) operational.. I guess the error will dissapear then.

    [edit]
    I do have a different error description just mailed to me:
    09/05/2006 17:50:01: Thread 0 error:
    Process terminated unexpectedly. Error code: -2139684860

    09/05/2006 17:50:01: Server: Msg 3013
    BACKUP LOG is terminating abnormally.
    09/05/2006 17:50:01: Server: Msg 3241
    The media family on device 'SQLBACKUP_BBE3F288-793E-42C5-B181-B7157546D398' is incorrectly formed. SQL Server cannot process this media family.
    09/05/2006 17:50:01: Failed to close vdi.

    [/edit]

    so I might just have another issue then...
    · Share on Twitter
  • JeffatWorkJeffatWork Posts: 7
    Alright Petey...I ran exec master..sqbmemory and here are my results.

    Type Minimum Maximum Average Blk count Total
    Commit 4096 66547712 0 20873 -1506115584
    Reserve 4096 4128768 22242 17571 390819840
    Free 4096 2011136 132128 314 41488384
    Private 4096 66547712 0 37858 -1155485696
    Mapped 4096 1019904 123881 45 5574656
    Image 4096 5808128 63983 541 34615296


    Whatcha think?
    · Share on Twitter
  • HJoyceHJoyce Posts: 186
    See http://www.red-gate.com/messageboard/vi ... php?t=2387 to download the server components which includes the MAXTRANSFERSIZE keyword.
    Helen Joyce
    SQL Backup Project Manager
    Red Gate Software
    · Share on Twitter
  • peteypetey Posts: 2,358 New member
    Some of the numbers look strange. Are you running a 64-bit operating system?

    Your largest contiguous block of free memory is 2011136 bytes. That's under 2 MB. SQL Backup by default requires SQL Server to be able to use approximately 6.5 MB of contiguous free memory. That would explain the error message in vdi.log.

    The amount of memory required is determined in part by the MAXTRANSFERSIZE value. By default, this is 1 MB. In build 510, you can use any value from 65536 to 1048576, in increments of 65536 bytes (see the link provided by Helen).

    In your case, I think you could use a MAXTRANSFERSIZE value of up to 256 KB, given that SQL Server usually allocates 6 buffers of the given MAXTRANSFERSIZE value (+ some overhead).

    A higher MAXTRANSFERSIZE value allows for better compression, while a lower MAXTRANSFERSIZE value would ensure that backups get made even in low memory conditions.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
    · Share on Twitter
  • JeffatWorkJeffatWork Posts: 7
    It is up and working now :D

    Thanks for the input. I knew there was a reason we are getting off of Litespeed :twisted:

    Petey..I assumed the memory numbers were going to be strange and knew there were contiguous memory issues.

    Thanks!!
    · Share on Twitter
  • JeffatWorkJeffatWork Posts: 7
    Bad News..having the same errors on the restore. Have tried using the MAXTRANSFERSIZE variable in the restore command and it will not accept it.
    · Share on Twitter
  • HJoyceHJoyce Posts: 186
    Updated server components so that Restore command supports MAXTRANSFERSIZE, please download ftp://ftp.red-gate.com/SQB4.2.0.511.zip
    Helen Joyce
    SQL Backup Project Manager
    Red Gate Software
    · Share on Twitter
Sign In or Register to comment.