Expiring Today—Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

restore fails after -g option added for SQL server

Posted on 2004-10-18
4
Medium Priority
?
717 Views
Last Modified: 2012-06-21
This restore failure happened one day after we started using -g option for SQL server's start up parameter, and also upgrade to SQL litespeed 3.1 from 3.0. Anyone has seen similar errors or knows the cause?  

We are win 2k3, enterprise edition sql 2000, sp3a with additional security patch, NAS device for disk, awe enabled, 8 proc, 8GB (6GB max mem for sql server)

Thanks!


2004-10-18 21:50:28.06 backup    BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(Insufficient system resources exist to complete the requested service.).
2004-10-18 21:50:28.11 spid127   Internal I/O request 0x45B51420: Op: WriteDatabaseScattered, pBuffer: 0x24950000, Size: 1048576, PageNumber: 0:0, UMS: Internal: 0x46707CE8, InternalHigh: 0x46707EA0, Offset: 0x46707E48, OffsetHigh: 0x45B983A8, m_buf: 0x24950000, m_len: 68, m_actualBytes: 0, m_errcode: 1450, File: n/a
2004-10-18 21:50:28.17 backup    BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(Insufficient system resources exist to complete the requested service.).
2004-10-18 21:50:28.19 spid127   Internal I/O request 0x45B51420: Op: WriteDatabaseScattered, pBuffer: 0x24950000, Size: 1048576, PageNumber: 0:0, UMS: Internal: 0x46707CE8, InternalHigh: 0x46707EA0, Offset: 0x46707E48, OffsetHigh: 0x45B983A8, m_buf: 0x24950000, m_len: 68, m_actualBytes: 0, m_errcode: 1450, File: n/a
2004-10-18 21:50:28.22 backup    BackupIoRequest::WaitForIoCompletion: write failure on backup device ''. Operating system error 1450(Insufficient system resources exist to complete the requested service.).
2004-10-18 21:50:28.25 spid127   Internal I/O request 0x45B51590: Op: WriteDatabaseScattered, pBuffer: 0x24A50000, Size: 1048576, PageNumber: 0:0, UMS: Internal: 0x45B63118, InternalHigh: 0x45B63118, Offset: 0x45B63118, OffsetHigh: 0x45B63118, m_buf: 0x24A50000, m_len: 1169568024, m_actualBytes: 0, m_errcode: 1450, File: n/a

....

2004-10-18 22:04:55.50 spid131   Error: 947, Severity: 16, State: 1
2004-10-18 22:04:55.50 spid131   Error while closing database '[database name removed]' cleanly..

0
Comment
Question by:loveviolet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
4 Comments
 
LVL 34

Expert Comment

by:arbert
ID: 12344000
Did Microsoft or Imceda recommend you change the -g option?  This is usually an option you don't mess with unless you've been receiving errors in the event log that warrant it.

We've been running Litespeed and SQL in the same environment as you (SAN instead of NAS) and we haven't experienced any problems.

Judging by this question and your previous questions, I still think you have some NAS issues....
0
 
LVL 1

Author Comment

by:loveviolet
ID: 12344113
Microsoft recommended us to add the -g option, to get away with the memory allocation problems.  Now when we remove the -g, it seems like it's working now.  However, we still want to know why this is happening.  Maybe you are right, it is NAS...
0
 
LVL 1

Author Comment

by:loveviolet
ID: 12364547
So we are trying to rebuild the machine.  Another thing that the management decided to test is to increase the memory from 8GB to 16GB.  Is there anything we should be aware of, such as some registry settings or memtoleave settings?  

Thanks!
0
 
LVL 34

Accepted Solution

by:
arbert earned 1500 total points
ID: 12364850
Pretty much the same thing as with the 8gb---leave enough memory for Windows and any other apps/drivers that run on the box.  Don't over allocate to SQL Server.  You should also get a baseline test to see if the extra memory helps or hurts SQL Server since AWE can have a lot of overhead...
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
Recently we ran in to an issue while running some SQL jobs where we were trying to process the cubes.  We got an error saying failure stating 'NT SERVICE\SQLSERVERAGENT does not have access to Analysis Services. So this is a way to automate that wit…
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

718 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question