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

VDI Error 100. MAXTRANSFERSIZE is set but not used?

msalasmsalas Posts: 19
edited May 19, 2010 3:52PM in SQL Backup Previous Versions
We are getting this error sometimes during the day, but mainly during the duration when a full database back-up is in progress.
The script that we use for the log back-up already has the MAXTRANSFERSIZE = 524288 option in it.
During the duration of the full back-up, we continue to get the VDI Error 1010. The thing is that, when we get the error, the email has the result of that sqbmemory and it shows that the maximum free memory is bigger than that MAXTRANSFERSIZE, so it seems that that setting is not being used?

Here is the error as received from the email (after 1 or 2 attempts, the lgo back-up succeeds) :

5/17/2010 9:04:38 PM: 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.) 5/17/2010 9:04:38 PM: SQL error 3013: BACKUP LOG is terminating abnormally.
5/17/2010 9:04:38 PM: SQL error 18210: BackupVirtualDeviceSet::Initialize: Request large buffers failure on backup device 'SQLBACKUP_8E86F849-92CA-4B74-9DB6-C2AC546FC40C'. Operating system error 0x8007000e(Not enough storage is available to complete this operation.).

Memory profile
Type Maximum Minimum Average Blk count Total





Commit 297598976 4096 99679 8816 878776320
Reserve 7729152 4096 178848 6930 1239416832
Free 1835008 4096 80068 365 29224960
Private 297598976 4096 131232 14927 1958912000
Mapped 4718592 4096 230278 177 40759296
Image 24948736 4096 184613 642 118521856

Maximum Free memory is 1835008 which is larger than the MAXTRANSFERSIZE setting. What prevents the job from using that setting?

Thanks!

Comments

  • Options
    This issue is now resolved.

    I have updated the version of my Backup to the current version 6.4 and I can see that the MAXTRANSFERSIZE setting is now being used. The messages are clearer on what size does the SQL Backup requires based on this and the BUFFERCOUNT.

    Thanks a lot!
Sign In or Register to comment.