VDI error 1010: Failed to get configuration from server

RussFRussF Posts: 25
edited September 4, 2006 9:27AM in SQL Backup Previous Versions
Hi,

I am receiving this error on two of my SQL2000 servers I am backing up. I am backing up multiple DB's on these servers but only get this error on the big DB's (+/-50GB). All other DB's backup perfectly.

Read previous post on V3 about rights and the environmental variable's, mine are all okay.

Thanks
Russ


VDI error 1010: Failed to get configuration from server. Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role. Error code: (-2139684861: The api was waiting and the timeout interval had elapsed.)
2006/08/09 05:22:05 AM: SQL error 3013: BACKUP DATABASE is terminating abnormally.
2006/08/09 05:22:05 AM:
2006/08/09 05:22:06 AM: Memory profile
2006/08/09 05:22:06 AM: Type Maximum Minimum Average Blk count Total
2006/08/09 05:22:06 AM:





2006/08/09 05:22:06 AM: Commit 657653760 4096 1675008 1075 1800634368
2006/08/09 05:22:06 AM: Reserve 1617920 4096 134726 362 48771072
2006/08/09 05:22:06 AM: Free 161865728 4096 1386105 215 298012672
2006/08/09 05:22:06 AM: Private 657653760 4096 1872497 963 1803214848
2006/08/09 05:22:06 AM: Mapped 1060864 4096 81794 98 8015872
2006/08/09 05:22:06 AM: Image 6156288 4096 101528 376 38174720
2006/08/09 05:22:06 AM:
2006/08/09 05:22:06 AM:
2006/08/09 05:22:06 AM: Warning 300: Backup failed. Retry attempt: 1

Comments

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

    The path settings aren't important any more in v4. If all we get is VDI error 1010 and SQL 3013, then SQL Backup doesn't have a clue why it failed. Question is, does the backup succeed after multiple attempts? I get the feeling you haven't included the entire log. SQL Backup should retry four times if you get warning 300.

    More than likely this issue is that the server was too busy to service a request to create a VDI virtual backup device on the server.
  • Hi Brian,

    Looked at the logs again and you are right, it fails on the 1st attempt and on the 2nd attempt it runs successfully.

    I will to see if SQL is potentially busy with something else at that time.

    Thanks
    Russ
  • Hi,

    I´m having de same problem as RussF ... I´m using version v4.6.0.815.
    The error rises one time, then SQL Backup tries again and it goes fine.
    The problem is that the output parameter @exitcode=300 and @sqlerrorcode=0; this isn´t wrong ? If at the second try the execution was fine, then @exitcode shoud be 0 ...

    Well I gues I have two problems: the first is the error itself, the second is the output variable @exitcode that arises value 300 at the second try ..

    The error is described bellow, as soon as you have a answer can you give me a repply?

    Thanks,

    Paulo Ribeiro
    Livraria Saraiva S/A
    Sao Paulo - Brasil

    //

    VDI error 1010: Failed to get configuration from server.
    Check that the SQL Server instance is running, and that you have the SQL Server Systems Administrator server role.
    Error code: (-2139684860: An abort request is preventing anything except termination actions.)
    SQL error 3013: BACKUP LOG is terminating abnormally.

    Memory profile
    Type Maximum Minimum Average Blk count Total





    Commit 35352576 4096 50052 21122 1057214464
    Reserve 4128768 8192 32062 17736 568651776
    Free 3796992 4096 192596 2708 521551872
    Private 35352576 4096 41473 38271 1587224576
    Mapped 1019904 4096 132994 49 6516736
    Image 7569408 4096 59711 538 32124928

    Warning 300: Backup failed. Retry attempt: 1
    Backup data size : 209.250 MB
    Compressed data size: 49.062 MB
    Compression rate : 76.55%

    Processed 26642 pages for database 'dbXYZ', file 'dbXYZ_Log' on file 1.
    BACKUP LOG successfully processed 26642 pages in 14.819 seconds (14.727 MB/sec).

    SQL Backup exit code: 300

    name value
    exitcode 300
    sqlerrorcode 0
    filename01 E:\L\DUMP_dbXYZ_2006-08-30_16-43-00-000_LOG.RGB
  • peteypetey Posts: 2,358 New member
    The first failure is due to an inadequate block of free contiguous memory for SQL Backup to use. From the output, it appears that the largest contiguous block is only ~3.5 MB in size. Your SQL Server memory space is fairly fragmented, by the looks of it.

    Exit code 300 is actually a warning. Any exit codes below 500 are classified as warnings, which basically mean that the backup succeeded, but there are issues that you need to be aware of.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Hi Petey!

    You said the memory is fairly fragmented, and that´s the cause of the failure, but what can I do to banish the error ? It appears to any Red Gate backup backup at this server - MSDB or MASTER, for example, which are very little in size ...

    Paulo
  • peteypetey Posts: 2,358 New member
    When SQL Backup performs a backup using the default settings and one file, it requires a block of free contiguous memory of about 6 MB. This is independent of the database size. In your case, the largest block is only ~3.5 MB in size. When that backup fails, SQL Backup steps down the requirements to 3 MB, which in this case, your server is able to provide.

    You can to some extend, influence the amount of memory required by using the MAXTRANSFERSIZE option e.g.

    BACKUP DATABASE ... WITH MAXTRANSFERSIZE = 524288

    The default value of MAXTRANSFERSIZE is 1048576 (1 MB). Using a large MAXTRANSFERSIZE usually allows for better and faster compression.

    So if you want to 'banish' the error, you could set up your backups to run with smaller MAXTRANSFERSIZE values.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Hello Petey!

    It works fine, thanks a lot !
    Paulo
Sign In or Register to comment.