"Jim Bailey" wrote:

> First off, I'm fairly certain this is an OS issue.  However, it manifested
> itself in Sql Server operations, so I hoping someone here may be of
> assistance, or has seen it. Sorry for the length of the post, but I'm trying
> to be complete.
>
> Over the past year, we have been restoring a DB, on another machine, from
> the nightly backup of our production DB.  The restore is performed by a SQL
> script that compares the backup filegroups to the existing filegroups, then
> restores with MOVE over our internal network via a UNC name.
>
> This has served us well for quite some time (like I said, about a year).  Of
> course over time the backp grew in size (currently approx 70 GB bacup file,
> about 100GB restored) and along with that of course the time to complete it.
> Last time was just over 2 hrs, up from about 1 hr 40 min a year ago. We have
> approx 200+GB free space.
>
> Suddenly, we can't complete the restore.  It fails with the log errors shown
> here.
>
> Internal I/O request 0x442D9A70: Op: Read, pBuffer: 0x066A0000, Size: 65536,
> Position: 35332761088, UMS: Internal: 0x0, InternalHigh: 0x0, Offset:
> 0x39FF2600, OffsetHigh: 0x8, m_buf: 0x066A0000, m_len: 65536, m_actualBytes:
> 0, m_errcode: 1130, BackupFile:
> \\<server>\y$\dbbackup\<dbname>\<dbname>_DB_20070315020128.BAK
>
> BackupMedium::ReportIoError: read failure on backup device '\\<server
> name>\y$\dbbackup\<dbname>\<dbname>_DB_20070315020128.BAK'. Operating system
> error 1130(Not enough server storage is available to process this command.).
>
> This translates into the OS error in event viewer (on restore machine).
>
> 18210 :
> BackupMedium::ReportIoError: read failure on backup device
> '\\<servername>\y$\dbbackup\<dbname>\<dbname>_db_20070314020125.bak'.
> Operating system error 1130(Not enough server storage is available to
> process this command.).
>
>  This failure occurs 2+ hours into the restore - all the files seem to be
> there and sized. The DB remains in 'loading' state.
>
>  Now - this error CAN be duplicated by simply trying to copy the backup file
> across the network.  That's why I said I don't believe it's a Sql Server
> issue - but, I'm hoping maybe someone here has seen it as well, happen in
> this fashion.
>
>  Myself and another DBA have researched this to death.  Articles, forums,
> and MS KB articles all say the same thing - the IPRStackSize, and the
> PagedPool registry params.  We have read all these references and followed
> them exactly, and then some.  No change.  We finally rebuilt the machine
> from the ground up - Windows 2000 all the Service Packs, SS 2000 all the
> SP's and hot fixes. We also happen to find an older backup file of about the
> same size on the same machine, and had no problem restoring it locally.
>
>  At this point we were even going to try something we'd never done - call MS
> and pay Per Incident, but we're told they won't do that.
>
>  Can anyone shed any light on this ?
>
>  Thanks.
>
>  jim in fl
>
>
>
>

"Hate_orphaned_users" <Hateorphanedus***@discussions.microsoft.com> wrote in
message news:5BCC0BC4-B831-4385-BE1E-C8A55CD29FF4@microsoft.com...
> Well i would agree that this looks like a hardware problem.
> But youre IT team must exclude all options , so if the backup( bak file)
> of
> SQL is ok , then check if there are network performance issues.
> Then check the os and hardware for errors.
>
> Good luck.
>
>
> --
> I drank alot of beer and ended up in the police department database.
> Drank more beer and learned SQL in the dark hours.
> DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
> I love SQL :)
>
>
>
>
> "Jim Bailey" wrote:
>
>> First off, I'm fairly certain this is an OS issue.  However, it
>> manifested
>> itself in Sql Server operations, so I hoping someone here may be of
>> assistance, or has seen it. Sorry for the length of the post, but I'm
>> trying
>> to be complete.
>>
>> Over the past year, we have been restoring a DB, on another machine, from
>> the nightly backup of our production DB.  The restore is performed by a
>> SQL
>> script that compares the backup filegroups to the existing filegroups,
>> then
>> restores with MOVE over our internal network via a UNC name.
>>
>> This has served us well for quite some time (like I said, about a year).
>> Of
>> course over time the backp grew in size (currently approx 70 GB bacup
>> file,
>> about 100GB restored) and along with that of course the time to complete
>> it.
>> Last time was just over 2 hrs, up from about 1 hr 40 min a year ago. We
>> have
>> approx 200+GB free space.
>>
>> Suddenly, we can't complete the restore.  It fails with the log errors
>> shown
>> here.
>>
>> Internal I/O request 0x442D9A70: Op: Read, pBuffer: 0x066A0000, Size:
>> 65536,
>> Position: 35332761088, UMS: Internal: 0x0, InternalHigh: 0x0, Offset:
>> 0x39FF2600, OffsetHigh: 0x8, m_buf: 0x066A0000, m_len: 65536,
>> m_actualBytes:
>> 0, m_errcode: 1130, BackupFile:
>> \\<server>\y$\dbbackup\<dbname>\<dbname>_DB_20070315020128.BAK
>>
>> BackupMedium::ReportIoError: read failure on backup device '\\<server
>> name>\y$\dbbackup\<dbname>\<dbname>_DB_20070315020128.BAK'. Operating
>> system
>> error 1130(Not enough server storage is available to process this
>> command.).
>>
>> This translates into the OS error in event viewer (on restore machine).
>>
>> 18210 :
>> BackupMedium::ReportIoError: read failure on backup device
>> '\\<servername>\y$\dbbackup\<dbname>\<dbname>_db_20070314020125.bak'.
>> Operating system error 1130(Not enough server storage is available to
>> process this command.).
>>
>>  This failure occurs 2+ hours into the restore - all the files seem to be
>> there and sized. The DB remains in 'loading' state.
>>
>>  Now - this error CAN be duplicated by simply trying to copy the backup
>> file
>> across the network.  That's why I said I don't believe it's a Sql Server
>> issue - but, I'm hoping maybe someone here has seen it as well, happen in
>> this fashion.
>>
>>  Myself and another DBA have researched this to death.  Articles, forums,
>> and MS KB articles all say the same thing - the IPRStackSize, and the
>> PagedPool registry params.  We have read all these references and
>> followed
>> them exactly, and then some.  No change.  We finally rebuilt the machine
>> from the ground up - Windows 2000 all the Service Packs, SS 2000 all the
>> SP's and hot fixes. We also happen to find an older backup file of about
>> the
>> same size on the same machine, and had no problem restoring it locally.
>>
>>  At this point we were even going to try something we'd never done - call
>> MS
>> and pay Per Incident, but we're told they won't do that.
>>
>>  Can anyone shed any light on this ?
>>
>>  Thanks.
>>
>>  jim in fl
>>
>>
>>
>>