When trying to backup a sql2000 database I receive the following error:
"Microsoft SQL-DOM (odbc sqlstate: 42000)
The Volume on device xxx e:\backupfilename.bak belongs to a different media set.
Backup or restore operation terminating abnormally."
Thanks for any help,
JimIf you have no use for the existing backup file, you could
either delete the file from the file system before doing
the backup or add the FORMAT option to the BACKUP
statement.
Linchi
>--Original Message--
>When trying to backup a sql2000 database I receive the
following error:
>"Microsoft SQL-DOM (odbc sqlstate: 42000)
>The Volume on device xxx e:\backupfilename.bak belongs to
a different media set.
>Backup or restore operation terminating abnormally."
>Thanks for any help,
>Jim
>
>.
>
Showing posts with label state. Show all posts
Showing posts with label state. Show all posts
Sunday, March 25, 2012
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
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
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
Each time I run a backup the following error appears in
SQL Server's error log: Error: 4035, Severity: 10, State: 1
Can anyone help in explaining why I keep getting the above
error? Your help will be greatly appreciated.
Hi,
Can you run the backup command from query analyzer an check the status of
backup
Backup database <dbname> to disk='c:\backup\dbname.bak' with init
Which version of SQL Server you are running?
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
> Each time I run a backup the following error appears in
> SQL Server's error log: Error: 4035, Severity: 10, State: 1
> Can anyone help in explaining why I keep getting the above
> error? Your help will be greatly appreciated.
|||Hi,
I have run the backup command from query analyser and
still getting the same error.
I am running SQL Server 2000 Enterprise SP3.
Thanks
>--Original Message--
>Hi,
>Can you run the backup command from query analyzer an
check the status of
>backup
>Backup database <dbname> to disk='c:\backup\dbname.bak'
with init
>Which version of SQL Server you are running?
>
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
State: 1[vbcol=seagreen]
above
>
>.
>
|||Hi,
I feel this is just a informational message.
Can you validate the backup file by restoring it to a diffrent database.
After that run a DBCC CHECKDB on that
new database and confirm things are fine.
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:251cb01c46024$c778ac00$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I have run the backup command from query analyser and
> still getting the same error.
> I am running SQL Server 2000 Enterprise SP3.
> Thanks
> check the status of
> with init
> <anonymous@.discussions.microsoft.com> wrote in message
> State: 1
> above
|||Thanks Hari,
I have restored the backup file to another database and
ran the DBCC Checkdb against the restored database, it
returned no errors. Everything appears to be fine. I
guess I will have to ignore the error message for now.
Thank you very much for your help.
>--Original Message--
>Hi,
>I feel this is just a informational message.
>Can you validate the backup file by restoring it to a
diffrent database.
>After that run a DBCC CHECKDB on that
>new database and confirm things are fine.
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:251cb01c46024$c778ac00$a401280a@.phx.gbl...
in
>
>.
>
SQL Server's error log: Error: 4035, Severity: 10, State: 1
Can anyone help in explaining why I keep getting the above
error? Your help will be greatly appreciated.
Hi,
Can you run the backup command from query analyzer an check the status of
backup
Backup database <dbname> to disk='c:\backup\dbname.bak' with init
Which version of SQL Server you are running?
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
> Each time I run a backup the following error appears in
> SQL Server's error log: Error: 4035, Severity: 10, State: 1
> Can anyone help in explaining why I keep getting the above
> error? Your help will be greatly appreciated.
|||Hi,
I have run the backup command from query analyser and
still getting the same error.
I am running SQL Server 2000 Enterprise SP3.
Thanks
>--Original Message--
>Hi,
>Can you run the backup command from query analyzer an
check the status of
>backup
>Backup database <dbname> to disk='c:\backup\dbname.bak'
with init
>Which version of SQL Server you are running?
>
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:24d5401c4601f$c79722c0$a301280a@.phx.gbl...
State: 1[vbcol=seagreen]
above
>
>.
>
|||Hi,
I feel this is just a informational message.
Can you validate the backup file by restoring it to a diffrent database.
After that run a DBCC CHECKDB on that
new database and confirm things are fine.
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:251cb01c46024$c778ac00$a401280a@.phx.gbl...[vbcol=seagreen]
> Hi,
> I have run the backup command from query analyser and
> still getting the same error.
> I am running SQL Server 2000 Enterprise SP3.
> Thanks
> check the status of
> with init
> <anonymous@.discussions.microsoft.com> wrote in message
> State: 1
> above
|||Thanks Hari,
I have restored the backup file to another database and
ran the DBCC Checkdb against the restored database, it
returned no errors. Everything appears to be fine. I
guess I will have to ignore the error message for now.
Thank you very much for your help.
>--Original Message--
>Hi,
>I feel this is just a informational message.
>Can you validate the backup file by restoring it to a
diffrent database.
>After that run a DBCC CHECKDB on that
>new database and confirm things are fine.
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message[vbcol=seagreen]
>news:251cb01c46024$c778ac00$a401280a@.phx.gbl...
in
>
>.
>
Thursday, March 22, 2012
Backup Error
Each time I run a backup the following error appears in
SQL Server's error log: Error: 4035, Severity: 10, State: 1
Can anyone help in explaining why I keep getting the above
error? Your help will be greatly appreciated.Hi,
Can you run the backup command from query analyzer an check the status of
backup
Backup database <dbname> to disk='c:\backup\dbname.bak' with init
Which version of SQL Server you are running?
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:24d5401c4601f$c79722c0$a301280a@.phx
.gbl...
> Each time I run a backup the following error appears in
> SQL Server's error log: Error: 4035, Severity: 10, State: 1
> Can anyone help in explaining why I keep getting the above
> error? Your help will be greatly appreciated.|||Hi,
I have run the backup command from query analyser and
still getting the same error.
I am running SQL Server 2000 Enterprise SP3.
Thanks
>--Original Message--
>Hi,
>Can you run the backup command from query analyzer an
check the status of
>backup
>Backup database <dbname> to disk='c:\backup\dbname.bak'
with init
>Which version of SQL Server you are running?
>
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message
> news:24d5401c4601f$c79722c0$a301280a@.phx
.gbl...
State: 1[vbcol=seagreen]
above[vbcol=seagreen]
>
>.
>|||Hi,
I feel this is just a informational message.
Can you validate the backup file by restoring it to a diffrent database.
After that run a DBCC CHECKDB on that
new database and confirm things are fine.
--
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:251cb01c46024$c778ac00$a401280a@.phx
.gbl...[vbcol=seagreen]
> Hi,
> I have run the backup command from query analyser and
> still getting the same error.
> I am running SQL Server 2000 Enterprise SP3.
> Thanks
> check the status of
> with init
> <anonymous@.discussions.microsoft.com> wrote in message
> State: 1
> above|||Thanks Hari,
I have restored the backup file to another database and
ran the DBCC Checkdb against the restored database, it
returned no errors. Everything appears to be fine. I
guess I will have to ignore the error message for now.
Thank you very much for your help.
>--Original Message--
>Hi,
>I feel this is just a informational message.
>Can you validate the backup file by restoring it to a
diffrent database.
>After that run a DBCC CHECKDB on that
>new database and confirm things are fine.
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message
> news:251cb01c46024$c778ac00$a401280a@.phx
.gbl...
in[vbcol=seagreen]
>
>.
>
SQL Server's error log: Error: 4035, Severity: 10, State: 1
Can anyone help in explaining why I keep getting the above
error? Your help will be greatly appreciated.Hi,
Can you run the backup command from query analyzer an check the status of
backup
Backup database <dbname> to disk='c:\backup\dbname.bak' with init
Which version of SQL Server you are running?
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:24d5401c4601f$c79722c0$a301280a@.phx
.gbl...
> Each time I run a backup the following error appears in
> SQL Server's error log: Error: 4035, Severity: 10, State: 1
> Can anyone help in explaining why I keep getting the above
> error? Your help will be greatly appreciated.|||Hi,
I have run the backup command from query analyser and
still getting the same error.
I am running SQL Server 2000 Enterprise SP3.
Thanks
>--Original Message--
>Hi,
>Can you run the backup command from query analyzer an
check the status of
>backup
>Backup database <dbname> to disk='c:\backup\dbname.bak'
with init
>Which version of SQL Server you are running?
>
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message
> news:24d5401c4601f$c79722c0$a301280a@.phx
.gbl...
State: 1[vbcol=seagreen]
above[vbcol=seagreen]
>
>.
>|||Hi,
I feel this is just a informational message.
Can you validate the backup file by restoring it to a diffrent database.
After that run a DBCC CHECKDB on that
new database and confirm things are fine.
--
Thanks
Hari
MCDBA
"y_shoge@.yahoo.co.uk" <anonymous@.discussions.microsoft.com> wrote in message
news:251cb01c46024$c778ac00$a401280a@.phx
.gbl...[vbcol=seagreen]
> Hi,
> I have run the backup command from query analyser and
> still getting the same error.
> I am running SQL Server 2000 Enterprise SP3.
> Thanks
> check the status of
> with init
> <anonymous@.discussions.microsoft.com> wrote in message
> State: 1
> above|||Thanks Hari,
I have restored the backup file to another database and
ran the DBCC Checkdb against the restored database, it
returned no errors. Everything appears to be fine. I
guess I will have to ignore the error message for now.
Thank you very much for your help.
>--Original Message--
>Hi,
>I feel this is just a informational message.
>Can you validate the backup file by restoring it to a
diffrent database.
>After that run a DBCC CHECKDB on that
>new database and confirm things are fine.
>--
>Thanks
>Hari
>MCDBA
>"y_shoge@.yahoo.co.uk"
<anonymous@.discussions.microsoft.com> wrote in message
> news:251cb01c46024$c778ac00$a401280a@.phx
.gbl...
in[vbcol=seagreen]
>
>.
>
Monday, March 19, 2012
Backup Database Failure
I have two databases that both give the following error when attempting to
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas?
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
Check msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Good point but per the OP I had already done this (via restorehistory table
even).
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>
|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>
|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas?
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
Check msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Good point but per the OP I had already done this (via restorehistory table
even).
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>
|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>
|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TR N'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TR N', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas?
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>
|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>
Backup Database Failure
I have two databases that both give the following error when attempting to
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas'
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt netCheck msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Good point but per the OP I had already done this (via restorehistory table
even).
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas'
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt netCheck msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Good point but per the OP I had already done this (via restorehistory table
even).
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_20071
2271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_20071
2271121.TRN', description =
> 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>
Sunday, March 11, 2012
Backup Database Failure
I have two databases that both give the following error when attempting to
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas'
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt netCheck msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Good point but per the OP I had already done this (via restorehistory table
even).
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting to
>>do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for both,
>> including one last night around 7pm. I did those manually. I also did 5
>> transaction log backups in a row for each with no problem, 4 manually the
>> final using a scheduled job. If I use SSMS and go to Tasks - Restore
>> Database, the Full backup and all 5 Log Backups do populate in the grid
>> of available backups to restore from, so the system is definitely seeing
>> them.
>> In msdb.dbo.backupset the only difference I note is that the username for
>> the Full and first 4 tlog backups is SA and the last tlog backup is a
>> domain admin account used by SQL Agent. I did try the above backup both
>> using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting to
>>do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for both,
>> including one last night around 7pm. I did those manually. I also did 5
>> transaction log backups in a row for each with no problem, 4 manually the
>> final using a scheduled job. If I use SSMS and go to Tasks - Restore
>> Database, the Full backup and all 5 Log Backups do populate in the grid
>> of available backups to restore from, so the system is definitely seeing
>> them.
>> In msdb.dbo.backupset the only difference I note is that the username for
>> the Full and first 4 tlog backups is SA and the last tlog backup is a
>> domain admin account used by SQL Agent. I did try the above backup both
>> using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>> Check msdb..restorehistory to see if something is doing a restore
>> operation that you are not aware of...I've seen this, but don;t recall
>> the conditions or product
>> --
>> Kevin Hill
>> IC3 North Texas
>> www.ChristianCycling.com
>> Please support me in the 2008 MS150:
>> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting
>>to do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for
>> both, including one last night around 7pm. I did those manually. I
>> also did 5 transaction log backups in a row for each with no problem, 4
>> manually the final using a scheduled job. If I use SSMS and go to
>> Tasks - Restore Database, the Full backup and all 5 Log Backups do
>> populate in the grid of available backups to restore from, so the system
>> is definitely seeing them.
>> In msdb.dbo.backupset the only difference I note is that the username
>> for the Full and first 4 tlog backups is SA and the last tlog backup is
>> a domain admin account used by SQL Agent. I did try the above backup
>> both using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>>
>
do a BACKUP LOG:
Msg 4214, Level 16, State 1, Line 1
BACKUP LOG cannot be performed because there is no current database backup.
Msg 3013, Level 16, State 1, Line 1
BACKUP LOG is terminating abnormally.
The backup statement is this:
backup log [00000005]
to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
with name = 'e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN',
description = 'Nightly Maintenance', password='thepassword'
I have verified the following: There are multiple full backups for both,
including one last night around 7pm. I did those manually. I also did 5
transaction log backups in a row for each with no problem, 4 manually the
final using a scheduled job. If I use SSMS and go to Tasks - Restore
Database, the Full backup and all 5 Log Backups do populate in the grid of
available backups to restore from, so the system is definitely seeing them.
In msdb.dbo.backupset the only difference I note is that the username for
the Full and first 4 tlog backups is SA and the last tlog backup is a domain
admin account used by SQL Agent. I did try the above backup both using SA
and the SQL Agent job. Both give same error. I have also verified that
these two databases have not been restored since the last log backup.
I checked profiler but it blanks-out all BACKUP operations for security
reasons.
Any ideas'
Server is 2005, build 1366. Looks like I need to upgrade to latest service
pack at some point, although I did review the fix lists for SP1 and 2 and
didn't see anything that would cause this.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt netCheck msdb..restorehistory to see if something is doing a restore operation
that you are not aware of...I've seen this, but don;t recall the conditions
or product
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Ouch this one doesn't sound like a fun one. Just an idea but are the full
backups possibly being run 'with copy_only'. If you have copy_only set I
wouldn't think it would show up in the grid for restores but its always
something to check. There's a bit column in msdb.dbo.backupset called
is_copy_only that you can check.
Good Luck!
-Mike
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Good point but per the OP I had already done this (via restorehistory table
even).
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
> Check msdb..restorehistory to see if something is doing a restore
> operation that you are not aware of...I've seen this, but don;t recall the
> conditions or product
> --
> Kevin Hill
> IC3 North Texas
> www.ChristianCycling.com
> Please support me in the 2008 MS150:
> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting to
>>do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for both,
>> including one last night around 7pm. I did those manually. I also did 5
>> transaction log backups in a row for each with no problem, 4 manually the
>> final using a scheduled job. If I use SSMS and go to Tasks - Restore
>> Database, the Full backup and all 5 Log Backups do populate in the grid
>> of available backups to restore from, so the system is definitely seeing
>> them.
>> In msdb.dbo.backupset the only difference I note is that the username for
>> the Full and first 4 tlog backups is SA and the last tlog backup is a
>> domain admin account used by SQL Agent. I did try the above backup both
>> using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>|||Another good check, but no luck. All rows in backupset showed that no
backups were copy only. Besides, I wouldn't have been able to do the 5 tlog
backups successfully prior to the one that failed if the full backup was
copy only.
I wish I could 'know' what happened between 8:22pm last night and 1am this
morning when the agent job kicked off and failed!! Being able to see
statement-level activity from within sql server for the backup log command
would be immensely helpful too darn it!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
kgboles a earthlink dt net
"Michael Abair" <mabair@.autotask.com> wrote in message
news:emsnlwKSIHA.3532@.TK2MSFTNGP04.phx.gbl...
> Ouch this one doesn't sound like a fun one. Just an idea but are the full
> backups possibly being run 'with copy_only'. If you have copy_only set I
> wouldn't think it would show up in the grid for restores but its always
> something to check. There's a bit column in msdb.dbo.backupset called
> is_copy_only that you can check.
> Good Luck!
> -Mike
> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting to
>>do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for both,
>> including one last night around 7pm. I did those manually. I also did 5
>> transaction log backups in a row for each with no problem, 4 manually the
>> final using a scheduled job. If I use SSMS and go to Tasks - Restore
>> Database, the Full backup and all 5 Log Backups do populate in the grid
>> of available backups to restore from, so the system is definitely seeing
>> them.
>> In msdb.dbo.backupset the only difference I note is that the username for
>> the Full and first 4 tlog backups is SA and the last tlog backup is a
>> domain admin account used by SQL Agent. I did try the above backup both
>> using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>|||Another guess from personal experience: Something switched the database to
SIMPLE mode then back to FULL mode.
If this is the case, a differential backup should be enough to reestablish
the LOG backups. (Then go hunting for what changed the database option. A
good target for a server level DDL trigger to catch the ALTER DATABASE
statement.)
FWIW,
RLF
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n7m6plje6dv17@.corp.supernews.com...
>I have two databases that both give the following error when attempting to
>do a BACKUP LOG:
> Msg 4214, Level 16, State 1, Line 1
> BACKUP LOG cannot be performed because there is no current database
> backup.
> Msg 3013, Level 16, State 1, Line 1
> BACKUP LOG is terminating abnormally.
>
> The backup statement is this:
> backup log [00000005]
> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
> with name = 'e:\MSSQL
> Backup\20071227\00000005_logbackup_200712271121.TRN', description => 'Nightly Maintenance', password='thepassword'
>
> I have verified the following: There are multiple full backups for both,
> including one last night around 7pm. I did those manually. I also did 5
> transaction log backups in a row for each with no problem, 4 manually the
> final using a scheduled job. If I use SSMS and go to Tasks - Restore
> Database, the Full backup and all 5 Log Backups do populate in the grid of
> available backups to restore from, so the system is definitely seeing
> them.
> In msdb.dbo.backupset the only difference I note is that the username for
> the Full and first 4 tlog backups is SA and the last tlog backup is a
> domain admin account used by SQL Agent. I did try the above backup both
> using SA and the SQL Agent job. Both give same error. I have also
> verified that these two databases have not been restored since the last
> log backup.
> I checked profiler but it blanks-out all BACKUP operations for security
> reasons.
> Any ideas'
> Server is 2005, build 1366. Looks like I need to upgrade to latest
> service pack at some point, although I did review the fix lists for SP1
> and 2 and didn't see anything that would cause this.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
>|||Crud...that line got a bit buried in the text.
Any Truncation of the T-log happening that would cause a variation in the
recovery path? Anything else in the ERRORLOG between working and broken?
--
Kevin Hill
IC3 North Texas
www.ChristianCycling.com
Please support me in the 2008 MS150:
http://www.ms150.org/dallas/donate/donate.cfm?id=208000
"TheSQLGuru" <kgboles@.earthlink.net> wrote in message
news:13n817an3aton89@.corp.supernews.com...
> Good point but per the OP I had already done this (via restorehistory
> table even).
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
> kgboles a earthlink dt net
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:eW3Q4vKSIHA.6036@.TK2MSFTNGP03.phx.gbl...
>> Check msdb..restorehistory to see if something is doing a restore
>> operation that you are not aware of...I've seen this, but don;t recall
>> the conditions or product
>> --
>> Kevin Hill
>> IC3 North Texas
>> www.ChristianCycling.com
>> Please support me in the 2008 MS150:
>> http://www.ms150.org/dallas/donate/donate.cfm?id=208000
>> "TheSQLGuru" <kgboles@.earthlink.net> wrote in message
>> news:13n7m6plje6dv17@.corp.supernews.com...
>>I have two databases that both give the following error when attempting
>>to do a BACKUP LOG:
>> Msg 4214, Level 16, State 1, Line 1
>> BACKUP LOG cannot be performed because there is no current database
>> backup.
>> Msg 3013, Level 16, State 1, Line 1
>> BACKUP LOG is terminating abnormally.
>>
>> The backup statement is this:
>> backup log [00000005]
>> to disk='e:\MSSQL Backup\20071227\00000005_logbackup_200712271121.TRN'
>> with name = 'e:\MSSQL
>> Backup\20071227\00000005_logbackup_200712271121.TRN', description =>> 'Nightly Maintenance', password='thepassword'
>>
>> I have verified the following: There are multiple full backups for
>> both, including one last night around 7pm. I did those manually. I
>> also did 5 transaction log backups in a row for each with no problem, 4
>> manually the final using a scheduled job. If I use SSMS and go to
>> Tasks - Restore Database, the Full backup and all 5 Log Backups do
>> populate in the grid of available backups to restore from, so the system
>> is definitely seeing them.
>> In msdb.dbo.backupset the only difference I note is that the username
>> for the Full and first 4 tlog backups is SA and the last tlog backup is
>> a domain admin account used by SQL Agent. I did try the above backup
>> both using SA and the SQL Agent job. Both give same error. I have also
>> verified that these two databases have not been restored since the last
>> log backup.
>> I checked profiler but it blanks-out all BACKUP operations for security
>> reasons.
>> Any ideas'
>> Server is 2005, build 1366. Looks like I need to upgrade to latest
>> service pack at some point, although I did review the fix lists for SP1
>> and 2 and didn't see anything that would cause this.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>> kgboles a earthlink dt net
>>
>>
>
Subscribe to:
Posts (Atom)