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

VDI error 1010: How do I set maxbuffersize

randyvrandyv Posts: 166
edited August 4, 2011 10:10AM in SQL Backup Previous Versions
I need to reduce the maxbuffersize (apparently) down to 512KB.

I keep getting this error on log file backups...

VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 0 bytes of free SQL Server memory, which was not available. VDI error: An abort request is preventing anything except termination actions.

Thanks much

randyv
What we do in life echoes in eternity <><
Randy Volters

Comments

  • Options
    peteypetey Posts: 2,358 New member
    Use the MAXTRANSFERSIZE option e.g.
    EXEC master..sqlbackup '-sql "BACKUP LOG ... WITH MAXTRANSFERSIZE = 524288..." '
    

    It's strange that SQL Backup reports that it required 0 bytes of free memory. What version of SQL Backup are you using?

    Thanks.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    6.4.0.56
    What we do in life echoes in eternity <><
    Randy Volters
  • Options
    Not sure what went wrong.
    Ran the suggested code:
    EXEC master..sqlbackup '-sql "BACKUP LOG ... WITH MAXTRANSFERSIZE = 524288..." '
    Got two answer sets back:
    #1
    SQL Backup v6.4.0.56
    Syntax error: 'WITH' after '...'

    #2
    name value
    exitcode 850
    sqlerrorcode 0
    What we do in life echoes in eternity <><
    Randy Volters
  • Options
    peteypetey Posts: 2,358 New member
    I apologise for the brevity in my previous example. You need to use whatever parameters you were using previously, and add the MAXTRANSFERSIZE option e.g.
    EXEC master..sqlbackup '-sql "BACKUP LOG AdventureWorks TO DISK = &#91;&lt;AUTO&gt;&#93; WITH MAXTRANSFERSIZE = 524288"'
    
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    Seems to work. I've changed the parm in the job. Will see if that eliminates the 'error' messages.
    What we do in life echoes in eternity <><
    Randy Volters
  • Options
    Here is the complete message as I'm receiving it in email from SQL Backup -
    Seems the local backup is completing fine, but the network backup is not.
    Any idea why?

    ERRORS AND WARNINGS


    4/1/2011 8:15:05 AM:
    4/1/2011 8:15:05 AM: Verifying files:
    4/1/2011 8:15:05 AM: E:\Davisware\LDF Backup\Service\LOG_(local)_Service_20110401_081501.sqb
    4/1/2011 8:15:05 AM:
    4/1/2011 8:15:05 AM: VDI error 1010: Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required 0 bytes of free SQL Server memory, which was not available. VDI error: An abort request is preventing anything except termination actions.
    4/1/2011 8:15:05 AM: SQL error 3013: VERIFY DATABASE is terminating abnormally.
    4/1/2011 8:15:05 AM: SQL error 18210: BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_F9F1FB46-C191-4698-9504-C760D475A239'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).
    4/1/2011 8:15:05 AM:
    4/1/2011 8:15:05 AM: Memory profile
    4/1/2011 8:15:05 AM: Type Maximum Minimum Average Blk count Total
    4/1/2011 8:15:05 AM:





    4/1/2011 8:15:05 AM: Commit 243068928 4096 56452 22147 1250242560
    4/1/2011 8:15:05 AM: Reserve 284266496 4096 41963 20477 859279360
    4/1/2011 8:15:05 AM: Free 7262208 4096 132504 286 37896192
    4/1/2011 8:15:05 AM: Private 284266496 4096 47296 41896 1981550592
    4/1/2011 8:15:05 AM: Mapped 1060864 4096 128107 76 9736192
    4/1/2011 8:15:05 AM: Image 24948736 4096 181342 652 118235136
    4/1/2011 8:15:05 AM:
    4/1/2011 8:15:05 AM: Validation of all backup files failed.



    PROCESSES COMPLETED SUCCESSFULLY

    4/1/2011 8:15:00 AM: Backing up Service (transaction log) to:
    4/1/2011 8:15:00 AM: E:\Davisware\LDF Backup\Service\LOG_(local)_Service_20110401_081500.sqb

    4/1/2011 8:15:01 AM: Deleting old backup file: E:\Davisware\LDF Backup\Service\LOG_(local)_Service_20110401_064500.sqb
    4/1/2011 8:15:01 AM: Deleting old backup file: \\whaley09\WFR-DailyBackups\Whaley03\LOG_(local)_Service_20110401_070000.sqb
    4/1/2011 8:15:01 AM: BACKUP LOG [Service] TO VIRTUAL_DEVICE = 'SQLBACKUP_CFF69D11-89C3-4F68-AEE0-D5D2F39F204E', VIRTUAL_DEVICE = 'SQLBACKUP_CFF69D11-89C3-4F68-AEE0-D5D2F39F204E01' WITH BUFFERCOUNT = 12, BLOCKSIZE = 65536, MAXTRANSFERSIZE = 524288, NAME = N'Database (Service), 4/1/2011 8:15:01 AM', DESCRIPTION = N'Backup on 4/1/2011 8:15:01 AM Server: WHALEY03 Database: Service', FORMAT

    4/1/2011 8:15:04 AM: Backup data size : 6.438 MB
    4/1/2011 8:15:04 AM: Compressed data size: 678.000 KB
    4/1/2011 8:15:04 AM: Compression rate : 89.71%

    4/1/2011 8:15:04 AM: Processed 533 pages for database 'Service', file 'ServiceDev_log' on file 1.
    4/1/2011 8:15:04 AM: BACKUP LOG successfully processed 533 pages in 0.583 seconds (7.478 MB/sec).
    What we do in life echoes in eternity <><
    Randy Volters
  • Options
    peteypetey Posts: 2,358 New member
    As of the current version, the MAXTRANSFERSIZE option isn't used by the verification process, which results in an error in your case as there is a lack of free virtual address space to service the RESTORE VERIFYONLY process. Neither does the RESTORE VERIFYONLY process retry multiple times automatically with smaller MAXTRANSFERSIZE values, unlike the BACKUP command.
    Peter Yeoh
    SQL Backup Consultant Developer
    Associate, Yohz Software
    Beyond compression - SQL Backup goodies under the hood, updated for version 8
  • Options
    OK, but do you have some suggestions on what to change to eliminate the error?
    What we do in life echoes in eternity <><
    Randy Volters
  • Options
    Is there any resolution to this? I am not all that interested in going in and modifying each of my scripts manually. I have 28 databases that are configured for log shipping. Unlike many SQL administrators I can't sit and monitor or waste a lot of time with SQL.

    I have found through increasing notification that this is the exact scenario that has caused me to lose many of my log shipped databases.

    Ignore this.. creating a new thread.
  • Options
    What version of SQL are you using? Have you set the -g startup option to give you enough VAS memory?

    Chris
    English DBA living in CANADA
Sign In or Register to comment.