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

Restore Failing on 5.4

mrclodmrclod Posts: 60
edited June 18, 2009 12:44PM in SQL Backup Previous Versions
I am doing restore testing and keep getting the error message below. I am restoring 12 databases in sequential order and have plenty of available disk space.

If I restart the SQL BACKUP Agent, then it will work for that go around. This is getting frustrating as it could happen between any of the restores and I am potentially looking to break the job up to restore a few databases in parallel due to some time constraints.

So is this a known issue fixed in the next version? And when is the next version supposed to be released anyway?

SQL Backup v5.4.0.55
Restoring BUILD_T1_12650 (database) from:

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.)
Also check that the database is not currently in use.
SQL error 3013: RESTORE DATABASE is terminating abnormally.
SQL error 18210: BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_E851E6F1-C67E-4A86-84A0-9B0B3EE144A1'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).

Memory profile
Type Maximum Minimum Average Blk count Total

Commit 795410432 4096 1239661 1588 1968582656
Reserve 15855616 4096 456125 301 137293824
Free 5853184 4096 136650 304 41541632
Private 795410432 4096 1717005 1117 1917894656
Mapped 1060864 4096 318278 166 52834304
Image 24948736 4096 223015 606 135147520

SQL Backup exit code: 1010
SQL error code: 18210
name value

exitcode 1010
sqlerrorcode 18210
filename001 \\p5stagefile1\backup\databasebackup\p5trialdb1\FULL_mydb_20090611_000000.sqb


  • Options
    Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    Hi Jon,

    If the problem is simply that there is not enough SQL Server procedure memory, then the problem may never, ever be fixed by an upgrade. The SQL Server memory space gets used up and fragmented by things such as extended stored procedure code, sp_oacreate COM objects that are not freed, and the like, not leaving enough (contiguous) memory space for SQL Backup buffers. You can minimize the memory by reducing the number of threads the backup uses or by employing the MAXTRANSFERSIZE parameter in the backup script.

    You may also want to ensure that the SQL Server memory configuration is optimal for SQL Backup. We have an in-depth KB article to discuss that here:
    http://www.red-gate.com/supportcenter/C ... 000142.htm
Sign In or Register to comment.