Sunday, March 25, 2012

Backup Error

After applying Win2K SP3 earlier this month, our Veritas
tape backups started failing with the following errors:
BackupMedium::ReportIoError: write failure on backup
device 'VNBU0-2000-2912'. Operating system error 995(The
I/O operation has been aborted because of either a thread
exit or an application request.).
Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
0x28A70200, Size: 512, Position: 0, UMS: Internal:
0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
m_errcode: 995, BackupFile: VNBU0-2000-2912
I also started getting the following error reported around
the same time of day:
The SQL Server cannot obtain a LOCK resource at this time.
Rerun your statement when there are fewer active users or
ask the system administrator to check the SQL Server lock
and memory configuration..
I am able to do a regular dump to disk with no errors.
Any ideas on resolution here?
Thanks for your time.
MilesI think veritas.com will have more helpful info.
Are you using BackupExec to backup SQL databases?
"Miles" <miles.schor@.echostar.com> wrote in message
news:016b01c36742$ecf70520$a401280a@.phx.gbl...
> After applying Win2K SP3 earlier this month, our Veritas
> tape backups started failing with the following errors:
> BackupMedium::ReportIoError: write failure on backup
> device 'VNBU0-2000-2912'. Operating system error 995(The
> I/O operation has been aborted because of either a thread
> exit or an application request.).
> Internal I/O request 0x4431FAE8: Op: Write, pBuffer:
> 0x28A70200, Size: 512, Position: 0, UMS: Internal:
> 0x65E5A030, InternalHigh: 0x0, Offset: 0x1, OffsetHigh:
> 0x4862F628, m_buf: 0x00000012, m_len: 1, m_actualBytes: 0,
> m_errcode: 995, BackupFile: VNBU0-2000-2912
> I also started getting the following error reported around
> the same time of day:
> The SQL Server cannot obtain a LOCK resource at this time.
> Rerun your statement when there are fewer active users or
> ask the system administrator to check the SQL Server lock
> and memory configuration..
> I am able to do a regular dump to disk with no errors.
> Any ideas on resolution here?
> Thanks for your time.
> Miles

No comments:

Post a Comment