Backup fail on msllockdb & pwe files

We use Arcserve for our backup software. Everynight, we get errors that
msllockdb.mdf, msllockdb_ldf, pwe.mdf, & pwe_log.ldf cannot be accessed
because they are being used by another process. Does anyone know what is
causing this and how to correct it?
--
Thanks!You are obviously not using the SQL Server plugin for Arcserver. It is
trying to copy the files directly and that is always a no no for SQL Server.
You need to invoke the SQL Server backup command thru Arcserves SQL Server
specific extensions.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"Saucer Man" <saucerman@.nospam.com> wrote in message
news:4742f3fc$0$27025$cc2e38e6@.news.uslec.net...
> We use Arcserve for our backup software. Everynight, we get errors that
> msllockdb.mdf, msllockdb_ldf, pwe.mdf, & pwe_log.ldf cannot be accessed
> because they are being used by another process. Does anyone know what is
> causing this and how to correct it?
> --
> Thanks!
>|||Thanks. I will look into this.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:O0dQXa4KIHA.1184@.TK2MSFTNGP04.phx.gbl...
> You are obviously not using the SQL Server plugin for Arcserver. It is
> trying to copy the files directly and that is always a no no for SQL
> Server. You need to invoke the SQL Server backup command thru Arcserves
> SQL Server specific extensions.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "Saucer Man" <saucerman@.nospam.com> wrote in message
> news:4742f3fc$0$27025$cc2e38e6@.news.uslec.net...
>> We use Arcserve for our backup software. Everynight, we get errors that
>> msllockdb.mdf, msllockdb_ldf, pwe.mdf, & pwe_log.ldf cannot be accessed
>> because they are being used by another process. Does anyone know what is
>> causing this and how to correct it?
>> --
>> Thanks!
>

BACKUP ERRORS MISSING IN THE EVENT LOG

Hi,

One of our backup jobs failed this morning but nothing got written into
win nt application event log. This way our MOM 2005 couldn't generate
an alert on this event since mom inspetcs application event log for
that purpose (event id 17055). I see backup errors about 10 days ago in
the appl log. What could have caused that? Any help will be
appreciated.

Stan(suslikovich@.yahoo.com) writes:
> One of our backup jobs failed this morning but nothing got written into
> win nt application event log. This way our MOM 2005 couldn't generate
> an alert on this event since mom inspetcs application event log for
> that purpose (event id 17055). I see backup errors about 10 days ago in
> the appl log. What could have caused that? Any help will be
> appreciated.

Do you see anything in the SQL Server error log?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.aspsql

Backup Errors in sqlserver

Hello all,

How can I resolve this error message I keep getting when I try to backup my database?

Thanks in Advance.

"Can't open dump device 'D:\MSSQL\BACKUP\dmpApp_tracker.DAT', device error or device off line. Please consult the SQL Server error log for more details. (Message 3201)"Are you appending to the device? I've seen this happen when an active backup operation gets interrupted. After that the device needs to be re-created. If you were appending backups to it see if you can recover the ones that you intend to keep.|||No, I am not appending to it. This is sqlserver 6.5 and it does not give you that option. It does have a expire after date and I set that to 7. Thanks for the help.|||6.5?

Deal me out...

What did the error log say?|||Yes it does! WITH NOINIT is available in 6.5 SP5a, look closely!

Backup Error: 18210, Severity: 16, State: 1

Getting errors on my backups, SQL 2005 SP2. Backups do complete successfully
however I'm getting errors in my App logs on my SQL Server.
During the snapshot part of the backups, these for lines appear in my SQL
Logs:
03/17/2008 11:36:49,spid75,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
03/17/2008 11:36:49,spid75,Unknown,BackupVirtualDeviceFile::P repareToFreeze:
failure on backup device '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'.
Operating system error 995(The I/O operation has been aborted because of
either a thread exit or an application request.).
03/17/2008 11:36:49,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
03/17/2008 11:36:49,Backup,Unknown,BACKUP failed to complete the command
BACKUP DATABASE SMS_DA1. Check the backup application log for detailed
messages.
These corresponding events appeared in the App log on the server:
Type:Error
Source:SQLVDI
Event ID:1
Event Time:3/17/2008 11:36:49 AM
User:n/a
Computer:SERVERNAME
Description:
SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0).
Process=2288. Thread=4324. Server. Instance=MSSQLSERVER.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Type:Error
Source:SQLVDI
Event ID:1
Event Time:3/17/2008 11:36:49 AM
User:n/a
Computer:SERVERNAME
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2288.
Thread=4324. Server. Instance=MSSQLSERVER.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Type:Error
Source:MSSQLSERVER
Event ID:18210
Event Time:3/17/2008 11:36:49 AM
User:NT AUTHORITY\SYSTEM
Computer:SERVERNAME
Description:
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device
'{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'. Operating system error 995(The I/O
operation has been aborted because of either a thread exit or an application
request.).
Type:Error
Source:MSSQLSERVER
Event ID:3041
Event Time:3/17/2008 11:36:49 AM
User:NT AUTHORITY\SYSTEM
Computer:SERVERNAME
Description:
BACKUP failed to complete the command BACKUP DATABASE SMS_DA1. Check the
backup application log for detailed messages.
Type:Error
Source:SQLWRITER
Event ID:24583
Event Time:3/17/2008 11:36:49 AM
User:n/a
Computer:SERVERNAME
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr =
0x80040e14.
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file
"{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1:" 995(The I/O operation has been
aborted because of either a thread exit or an application request.).
Type:Error
Source:SQLVDI
Event ID:1
Event Time:3/17/2008 11:36:49 AM
User:n/a
Computer:SERVERNAME
Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
Process=2876. Thread=29988. Client. Instance=.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Should I be concerned with these errors?
Sandy Wood
Orange County District Attorney
Is there any info in the event log that would give you any more info?
Did you have this issue prior to SP2?
Have you recently made any changes to the databases?
Are you using any 3rd party backup tools?
~lb
"Sandy Wood" wrote:

> Getting errors on my backups, SQL 2005 SP2. Backups do complete successfully
> however I'm getting errors in my App logs on my SQL Server.
> During the snapshot part of the backups, these for lines appear in my SQL
> Logs:
> 03/17/2008 11:36:49,spid75,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
> 03/17/2008 11:36:49,spid75,Unknown,BackupVirtualDeviceFile::P repareToFreeze:
> failure on backup device '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'.
> Operating system error 995(The I/O operation has been aborted because of
> either a thread exit or an application request.).
> 03/17/2008 11:36:49,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
> 03/17/2008 11:36:49,Backup,Unknown,BACKUP failed to complete the command
> BACKUP DATABASE SMS_DA1. Check the backup application log for detailed
> messages.
> These corresponding events appeared in the App log on the server:
> Type:Error
> Source:SQLVDI
> Event ID:1
> Event Time:3/17/2008 11:36:49 AM
> User:n/a
> Computer:SERVERNAME
> Description:
> SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0).
> Process=2288. Thread=4324. Server. Instance=MSSQLSERVER.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Type:Error
> Source:SQLVDI
> Event ID:1
> Event Time:3/17/2008 11:36:49 AM
> User:n/a
> Computer:SERVERNAME
> Description:
> SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2288.
> Thread=4324. Server. Instance=MSSQLSERVER.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Type:Error
> Source:MSSQLSERVER
> Event ID:18210
> Event Time:3/17/2008 11:36:49 AM
> User:NT AUTHORITY\SYSTEM
> Computer:SERVERNAME
> Description:
> BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device
> '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'. Operating system error 995(The I/O
> operation has been aborted because of either a thread exit or an application
> request.).
> Type:Error
> Source:MSSQLSERVER
> Event ID:3041
> Event Time:3/17/2008 11:36:49 AM
> User:NT AUTHORITY\SYSTEM
> Computer:SERVERNAME
> Description:
> BACKUP failed to complete the command BACKUP DATABASE SMS_DA1. Check the
> backup application log for detailed messages.
> Type:Error
> Source:SQLWRITER
> Event ID:24583
> Event Time:3/17/2008 11:36:49 AM
> User:n/a
> Computer:SERVERNAME
> Description:
> Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr =
> 0x80040e14.
> SQLSTATE: 42000, Native Error: 3013
> Error state: 1, Severity: 16
> Source: Microsoft SQL Native Client
> Error message: BACKUP DATABASE is terminating abnormally.
> SQLSTATE: 42000, Native Error: 3271
> Error state: 1, Severity: 16
> Source: Microsoft SQL Native Client
> Error message: A nonrecoverable I/O error occurred on file
> "{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1:" 995(The I/O operation has been
> aborted because of either a thread exit or an application request.).
> Type:Error
> Source:SQLVDI
> Event ID:1
> Event Time:3/17/2008 11:36:49 AM
> User:n/a
> Computer:SERVERNAME
> Description:
> SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
> Process=2876. Thread=29988. Client. Instance=.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Should I be concerned with these errors?
> --
> Sandy Wood
> Orange County District Attorney
|||The event log information is in my previous post. The backup is being
controlled by my Microsoft System Center Configuration Manager 2007
installation. It has a built-in Task that runs the backup. I've not had this
problem until I upgraded my SMS 2003 installation to System Center
Configuration Manager 2007 which uses VSS for backups now. Something in how
VSS behaves that's causing the problems. Funny thing, the backups are
sucessfull and my data is there. It's just disconcerting to see all the
warnings and errors everyday.
Sandy Wood
Orange County District Attorney
"lonnye" wrote:
[vbcol=seagreen]
> Is there any info in the event log that would give you any more info?
> Did you have this issue prior to SP2?
> Have you recently made any changes to the databases?
> Are you using any 3rd party backup tools?
> --
> ~lb
>
> "Sandy Wood" wrote:
sql

Backup Error: 18210, Severity: 16, State: 1

Getting errors on my backups, SQL 2005 SP2. Backups do complete successfully
however I'm getting errors in my App logs on my SQL Server.
During the snapshot part of the backups, these for lines appear in my SQL
Logs:
03/17/2008 11:36:49,spid75,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
03/17/2008 11:36:49,spid75,Unknown,BackupVirtualDeviceFile::PrepareToFreeze:
failure on backup device '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'.
Operating system error 995(The I/O operation has been aborted because of
either a thread exit or an application request.).
03/17/2008 11:36:49,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
03/17/2008 11:36:49,Backup,Unknown,BACKUP failed to complete the command
BACKUP DATABASE SMS_DA1. Check the backup application log for detailed
messages.
These corresponding events appeared in the App log on the server:
Type: Error
Source: SQLVDI
Event ID: 1
Event Time: 3/17/2008 11:36:49 AM
User: n/a
Computer: SERVERNAME
Description:
SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0).
Process=2288. Thread=4324. Server. Instance=MSSQLSERVER.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Type: Error
Source: SQLVDI
Event ID: 1
Event Time: 3/17/2008 11:36:49 AM
User: n/a
Computer: SERVERNAME
Description:
SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2288.
Thread=4324. Server. Instance=MSSQLSERVER.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Type: Error
Source: MSSQLSERVER
Event ID: 18210
Event Time: 3/17/2008 11:36:49 AM
User: NT AUTHORITY\SYSTEM
Computer: SERVERNAME
Description:
BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device
'{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'. Operating system error 995(The I/O
operation has been aborted because of either a thread exit or an application
request.).
Type: Error
Source: MSSQLSERVER
Event ID: 3041
Event Time: 3/17/2008 11:36:49 AM
User: NT AUTHORITY\SYSTEM
Computer: SERVERNAME
Description:
BACKUP failed to complete the command BACKUP DATABASE SMS_DA1. Check the
backup application log for detailed messages.
Type: Error
Source: SQLWRITER
Event ID: 24583
Event Time: 3/17/2008 11:36:49 AM
User: n/a
Computer: SERVERNAME
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14.
SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Native Client
Error message: A nonrecoverable I/O error occurred on file
"{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1:" 995(The I/O operation has been
aborted because of either a thread exit or an application request.).
Type: Error
Source: SQLVDI
Event ID: 1
Event Time: 3/17/2008 11:36:49 AM
User: n/a
Computer: SERVERNAME
Description:
SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
Process=2876. Thread=29988. Client. Instance=.
VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
Should I be concerned with these errors?
--
Sandy Wood
Orange County District AttorneyIs there any info in the event log that would give you any more info?
Did you have this issue prior to SP2?
Have you recently made any changes to the databases?
Are you using any 3rd party backup tools?
--
~lb
"Sandy Wood" wrote:
> Getting errors on my backups, SQL 2005 SP2. Backups do complete successfully
> however I'm getting errors in my App logs on my SQL Server.
> During the snapshot part of the backups, these for lines appear in my SQL
> Logs:
> 03/17/2008 11:36:49,spid75,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
> 03/17/2008 11:36:49,spid75,Unknown,BackupVirtualDeviceFile::PrepareToFreeze:
> failure on backup device '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'.
> Operating system error 995(The I/O operation has been aborted because of
> either a thread exit or an application request.).
> 03/17/2008 11:36:49,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
> 03/17/2008 11:36:49,Backup,Unknown,BACKUP failed to complete the command
> BACKUP DATABASE SMS_DA1. Check the backup application log for detailed
> messages.
> These corresponding events appeared in the App log on the server:
> Type: Error
> Source: SQLVDI
> Event ID: 1
> Event Time: 3/17/2008 11:36:49 AM
> User: n/a
> Computer: SERVERNAME
> Description:
> SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0).
> Process=2288. Thread=4324. Server. Instance=MSSQLSERVER.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Type: Error
> Source: SQLVDI
> Event ID: 1
> Event Time: 3/17/2008 11:36:49 AM
> User: n/a
> Computer: SERVERNAME
> Description:
> SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2288.
> Thread=4324. Server. Instance=MSSQLSERVER.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Type: Error
> Source: MSSQLSERVER
> Event ID: 18210
> Event Time: 3/17/2008 11:36:49 AM
> User: NT AUTHORITY\SYSTEM
> Computer: SERVERNAME
> Description:
> BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device
> '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'. Operating system error 995(The I/O
> operation has been aborted because of either a thread exit or an application
> request.).
> Type: Error
> Source: MSSQLSERVER
> Event ID: 3041
> Event Time: 3/17/2008 11:36:49 AM
> User: NT AUTHORITY\SYSTEM
> Computer: SERVERNAME
> Description:
> BACKUP failed to complete the command BACKUP DATABASE SMS_DA1. Check the
> backup application log for detailed messages.
> Type: Error
> Source: SQLWRITER
> Event ID: 24583
> Event Time: 3/17/2008 11:36:49 AM
> User: n/a
> Computer: SERVERNAME
> Description:
> Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr => 0x80040e14.
> SQLSTATE: 42000, Native Error: 3013
> Error state: 1, Severity: 16
> Source: Microsoft SQL Native Client
> Error message: BACKUP DATABASE is terminating abnormally.
> SQLSTATE: 42000, Native Error: 3271
> Error state: 1, Severity: 16
> Source: Microsoft SQL Native Client
> Error message: A nonrecoverable I/O error occurred on file
> "{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1:" 995(The I/O operation has been
> aborted because of either a thread exit or an application request.).
> Type: Error
> Source: SQLVDI
> Event ID: 1
> Event Time: 3/17/2008 11:36:49 AM
> User: n/a
> Computer: SERVERNAME
> Description:
> SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
> Process=2876. Thread=29988. Client. Instance=.
> VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> Should I be concerned with these errors?
> --
> Sandy Wood
> Orange County District Attorney|||The event log information is in my previous post. The backup is being
controlled by my Microsoft System Center Configuration Manager 2007
installation. It has a built-in Task that runs the backup. I've not had this
problem until I upgraded my SMS 2003 installation to System Center
Configuration Manager 2007 which uses VSS for backups now. Something in how
VSS behaves that's causing the problems. Funny thing, the backups are
sucessfull and my data is there. It's just disconcerting to see all the
warnings and errors everyday.
--
Sandy Wood
Orange County District Attorney
"lonnye" wrote:
> Is there any info in the event log that would give you any more info?
> Did you have this issue prior to SP2?
> Have you recently made any changes to the databases?
> Are you using any 3rd party backup tools?
> --
> ~lb
>
> "Sandy Wood" wrote:
> > Getting errors on my backups, SQL 2005 SP2. Backups do complete successfully
> > however I'm getting errors in my App logs on my SQL Server.
> >
> > During the snapshot part of the backups, these for lines appear in my SQL
> > Logs:
> >
> > 03/17/2008 11:36:49,spid75,Unknown,Error: 18210<c/> Severity: 16<c/> State: 1.
> > 03/17/2008 11:36:49,spid75,Unknown,BackupVirtualDeviceFile::PrepareToFreeze:
> > failure on backup device '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'.
> > Operating system error 995(The I/O operation has been aborted because of
> > either a thread exit or an application request.).
> > 03/17/2008 11:36:49,Backup,Unknown,Error: 3041<c/> Severity: 16<c/> State: 1.
> > 03/17/2008 11:36:49,Backup,Unknown,BACKUP failed to complete the command
> > BACKUP DATABASE SMS_DA1. Check the backup application log for detailed
> > messages.
> >
> > These corresponding events appeared in the App log on the server:
> >
> > Type: Error
> > Source: SQLVDI
> > Event ID: 1
> > Event Time: 3/17/2008 11:36:49 AM
> > User: n/a
> > Computer: SERVERNAME
> > Description:
> > SQLVDI: Loc=WaitForResource. Desc=Partner process aborted. ErrorCode=(0).
> > Process=2288. Thread=4324. Server. Instance=MSSQLSERVER.
> > VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> >
> > Type: Error
> > Source: SQLVDI
> > Event ID: 1
> > Event Time: 3/17/2008 11:36:49 AM
> > User: n/a
> > Computer: SERVERNAME
> > Description:
> > SQLVDI: Loc=TriggerAbort. Desc=invoked. ErrorCode=(0). Process=2288.
> > Thread=4324. Server. Instance=MSSQLSERVER.
> > VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> >
> > Type: Error
> > Source: MSSQLSERVER
> > Event ID: 18210
> > Event Time: 3/17/2008 11:36:49 AM
> > User: NT AUTHORITY\SYSTEM
> > Computer: SERVERNAME
> > Description:
> > BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device
> > '{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1'. Operating system error 995(The I/O
> > operation has been aborted because of either a thread exit or an application
> > request.).
> >
> > Type: Error
> > Source: MSSQLSERVER
> > Event ID: 3041
> > Event Time: 3/17/2008 11:36:49 AM
> > User: NT AUTHORITY\SYSTEM
> > Computer: SERVERNAME
> > Description:
> > BACKUP failed to complete the command BACKUP DATABASE SMS_DA1. Check the
> > backup application log for detailed messages.
> >
> > Type: Error
> > Source: SQLWRITER
> > Event ID: 24583
> > Event Time: 3/17/2008 11:36:49 AM
> > User: n/a
> > Computer: SERVERNAME
> > Description:
> > Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr => > 0x80040e14.
> > SQLSTATE: 42000, Native Error: 3013
> > Error state: 1, Severity: 16
> > Source: Microsoft SQL Native Client
> > Error message: BACKUP DATABASE is terminating abnormally.
> > SQLSTATE: 42000, Native Error: 3271
> > Error state: 1, Severity: 16
> > Source: Microsoft SQL Native Client
> > Error message: A nonrecoverable I/O error occurred on file
> > "{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1:" 995(The I/O operation has been
> > aborted because of either a thread exit or an application request.).
> >
> > Type: Error
> > Source: SQLVDI
> > Event ID: 1
> > Event Time: 3/17/2008 11:36:49 AM
> > User: n/a
> > Computer: SERVERNAME
> > Description:
> > SQLVDI: Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0).
> > Process=2876. Thread=29988. Client. Instance=.
> > VD=Global\{7EDC34FF-1A81-4635-8D71-99A7FCFA8CA8}1_SQLVDIMemoryName_0.
> >
> > Should I be concerned with these errors?
> >
> > --
> > Sandy Wood
> > Orange County District Attorney

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