Error: Get configuration error x80770004 when backing up or restoring using LiteSpeed
LiteSpeed verbose log may also contain messages similar to:
Warning: The maxtransfer size has been correct from: 1048576 to 65536 in order to satisfy the contiguous memory available in the SQLServer process.
OR
LiteSpeed 2005 has automatically corrected the thread count to 2. This will allow a backup operation to continue.
OR
In the SQL Server error log:
BackupVirtualDeviceSet::Initialize: EndConfiguration failure on backup device 'VDI_78E40140-FFEF-4FFC-A16D-45241414077F_0'. Operating system error 0x80070008(Not enough storage is available to process this command.).
The minimum contiguous memory required by LiteSpeed is 64 KB (required by the VDI). Please follow troubleshooting techniques below for memory fragmentation on the SQL Server (see attached document).
2. This error may be caused by sending large chunks of data over to your backup destination. Add the parameter @maxtransfersize to the LiteSpeed backup scripts or set the option within the LiteSpeed Backup options available from the Enterprise Console. If nothing is selected for this option the default value is 1Mb (1048576 bytes).
Add the @maxtransfersize parameter to the backup and reducing the size to 500Kb (512000), then perform the backup again.
3. The other parameter that has been used in conjunction with the MaxTransferSize parameter has been the Threads parameter. The installation default for LiteSpeed is 3. The script parameter is @threads and may be reduced to 1. The recommended setting is n-1 (n being the number of CPUs) in a multi-processor environment. This parameter is available within the LiteSpeed Backup options from the Enterprise Console.
4. SQL Server's MemToLeave area becoming fragmented so that there is insufficient contiguous space to allocate the buffers required for the backups. Microsoft's suggestion to resolving the issue is to use the start-up parameter '-g' with SQL Server. The '-g' parameter can be set in Enterprise Manager by right-clicking on the server, selecting 'Properties' and clicking on the Start-Up parameters button at the bottom of the properties window. The default -g setting is 128Mb. It is recommended that -g256 is used, if this does not resolve the issue increase the value to -g512. Changing these settings does require SQL Server to be restarted for the changes to take affect.
5. As recommended by Microsoft, NT Fibers works best when the server has multiple CPUs and a relatively low user to CPU ratio. For example, on an Enterprise installation with 32 CPUs and 250 users, you may see a noticeable performance boost with fibers. But when you have eight CPUs and 5000 users, you may see performance decrease with fibers. LightWeight Pooling is an advanced option. Sp_configure system stored procedure allows verification as well as a change to system settings in SQL Server 2000 and 2005. Note, for a change to this setting to take effect requires a restart SQL Server services
To verify the contiguous transfer size of SQL Server, run the command XP_MEMORY_SIZE from within Query Analyzer. The value is set in SQL
Server properties, Startup Parameters. Note, for a change to this setting to take effect requires a restart SQL Server services.
NOTE: SQL Server 7.0 Service Pack 2 users: The -g parameter is documented in the Readme.txt of the SQL Server 7.0 service pack, and in SQL Server 2000 Books Online.
See attached for a complete list of VDI error messages.
See related solutions 14674, 21043 and 21954 on SupportLink
