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

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

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

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

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

Backup Device setup

I am a novice and have setup a backup device for the
database and one for logs. When I attempt a backup I
recevie a device error. Status = 112. The error log
gives me no definitive reason for the error. CAn anyone
help?Run below from a DOS prompt to get explanation for OS error 112:
NET HELPMSG 112
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
<cneeley@.co.pierce.wi.us> wrote in message
news:09e301c3bf57$e2c38430$3101280a@.phx.gbl...
> I am a novice and have setup a backup device for the
> database and one for logs. When I attempt a backup I
> recevie a device error. Status = 112. The error log
> gives me no definitive reason for the error. CAn anyone
> help?

Backup

I am in the process of setting up my backup schedule. Is it good practice to
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.

> Thank you

Backup

I am in the process of setting up my backup schedule. Is it good practice to
include the transaction logs in the same backup file as my full or
differential backup?
Thank you"Curtis" <Curtis@.discussions.microsoft.com> wrote in message
news:8E90BB0D-F1B9-47C9-9EFD-B8EB41C5061F@.microsoft.com...
> I am in the process of setting up my backup schedule. Is it good practice
to
> include the transaction logs in the same backup file as my full or
> differential backup?
I tend not to. Mostly personal preference.
> Thank you

Backing up transaction logs using two DB Maintainance Plan

If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after backup done by maintainance plan of
Please reply soon
Thank
Saroshthey'll be independent as long as they aren't scheduled for the exact same time. each backup file's name contains the date and time (only to hour and minute) that the backup started so that you could have problems if both backups began running at the same time.
Sarosh wrote:
> If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after backup done by maintainance plan of 1
> Please reply soon.
> Thanks
> Sarosh

Backing up transaction logs using two DB Maintainance Plan

If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after b
ackup done by maintainance plan of 1
Please reply soon.
Thanks
Sarosh
they'll be independent as long as they aren't scheduled for the exact same time. each backup file's name contains the date and time (only to hour and minute) that the backup started so that you could have problems if both backups began running at the sam
e time.
Sarosh wrote:

> If I am doing two different maintainance plan for backing up the transaction logs of the same database of sql server. Will the transactions logs being backed up on plan 2 will be independent of plan 1, or will it be backup of the transactions done after
backup done by maintainance plan of 1
> Please reply soon.
> Thanks
> Sarosh

Backing up transaction logs using two DB Maintainance Plan

If I am doing two different maintainance plan for backing up the transaction
logs of the same database of sql server. Will the transactions logs being b
acked up on plan 2 will be independent of plan 1, or will it be backup of th
e transactions done after b
ackup done by maintainance plan of 1
Please reply soon.
Thanks
Saroshthey'll be independent as long as they aren't scheduled for the exact same t
ime. each backup file's name contains the date and time (only to hour and m
inute) that the backup started so that you could have problems if both backu
ps began running at the sam
e time.
Sarosh wrote:

> If I am doing two different maintainance plan for backing up the transaction logs
of the same database of sql server. Will the transactions logs being backed up on pl
an 2 will be independent of plan 1, or will it be backup of the transactions done af
ter
backup done by maintainance plan of 1
> Please reply soon.
> Thanks
> Sarosh

backing up transaction logs

Hi,
I would like to know if it is really nessary to backup the transaction logs
if their size is above 10 gigabytes. Is it not better to backup only the
database, delete the current log and then re-create the log.
If so, can someone help me with a scheduled script to do this?
Thnx
Hi
Check out
http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
http://msdn.microsoft.com/library/de...r_da2_7vaf.asp
Deleting the log file as you have suggested would mean that the database is
not available during that period of time.
Your log file should be sized appropriately so that it does not continuously
grow, if you re-create a log file that is too small then you may affect
performance.
John
"Jason" <jasonlewis@.hotrmail.com> wrote in message
news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if it is really nessary to backup the transaction
> logs
> if their size is above 10 gigabytes. Is it not better to backup only the
> database, delete the current log and then re-create the log.
> If so, can someone help me with a scheduled script to do this?
>
> Thnx
>
|||Jason
If you don't want to use your transaction log for recovery purposes, set
your database to simple recovery mode. Then your transaction log will be
truncated every time a checkpoint is issued.
Regards
John
"John Bell" wrote:

> Hi
> Check out
> http://msdn.microsoft.com/library/de...r_da2_1uzr.asp
> http://msdn.microsoft.com/library/de...r_da2_7vaf.asp
> Deleting the log file as you have suggested would mean that the database is
> not available during that period of time.
> Your log file should be sized appropriately so that it does not continuously
> grow, if you re-create a log file that is too small then you may affect
> performance.
> John
> "Jason" <jasonlewis@.hotrmail.com> wrote in message
> news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
>
>

backing up transaction logs

Hi,
I would like to know if it is really nessary to backup the transaction logs
if their size is above 10 gigabytes. Is it not better to backup only the
database, delete the current log and then re-create the log.
If so, can someone help me with a scheduled script to do this?
ThnxHi
Check out
http://msdn.microsoft.com/library/d...r />
_1uzr.asp
http://msdn.microsoft.com/library/d...r />
_7vaf.asp
Deleting the log file as you have suggested would mean that the database is
not available during that period of time.
Your log file should be sized appropriately so that it does not continuously
grow, if you re-create a log file that is too small then you may affect
performance.
John
"Jason" <jasonlewis@.hotrmail.com> wrote in message
news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if it is really nessary to backup the transaction
> logs
> if their size is above 10 gigabytes. Is it not better to backup only the
> database, delete the current log and then re-create the log.
> If so, can someone help me with a scheduled script to do this?
>
> Thnx
>|||Jason
If you don't want to use your transaction log for recovery purposes, set
your database to simple recovery mode. Then your transaction log will be
truncated every time a checkpoint is issued.
Regards
John
"John Bell" wrote:

> Hi
> Check out
> http://msdn.microsoft.com/library/d.../>
a2_1uzr.asp
> http://msdn.microsoft.com/library/d.../>
a2_7vaf.asp
> Deleting the log file as you have suggested would mean that the database i
s
> not available during that period of time.
> Your log file should be sized appropriately so that it does not continuous
ly
> grow, if you re-create a log file that is too small then you may affect
> performance.
> John
> "Jason" <jasonlewis@.hotrmail.com> wrote in message
> news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
>
>

Backing Up Transaction Logs

Dear sirs/ma'am

When setting up a maintenance plan in 2000, I can remove files older than 1 day.

When creating a maintenance task in 2005, I do not have that option (the database is in full mode). The only thing I can do (it seems) is to;

1. create a job with a step that uses a script from going through the motions of creating a log backup directly off the database. This is where I can say that the backup set will expire after 1 day, but in the destination field, the backup filename is hard-coded.

2. Then I schedule this script to run every hour. Sure enough, the log backup is overwritten due to the hard coded name.

The script reads;

BACKUP LOG [CSEPPWebCADB] TO DISK = N'D:\MSSQL\BACKUP\CSEPPWebCADB_backup.trn' WITH RETAINDAYS = 1, NOFORMAT, NOINIT, NAME = N'WebCADB_backup', SKIP, REWIND, NOUNLOAD, STATS = 10

How can I maintain a days worth of log backups or better yet, set up a maintenance plan to give me log backups every hour & delete them after they are a day old?

Sorry, I'm just not seeing how to do this.

Thanks for your help.

what is the srevice pack on this instance ? there are many enhancement in Maintenaceplan component in SP2 and the patch released after sp2 release. post back the result of

select @.@.Version

Madhu

|||

I don't believe that the person setting this up put SP 2 or the patch. I'll look into this and reply.

Thanks for your suggestion.

|||You need the correct SP2 loaded on your machine to start with. When you build a maintenance plan, you need to put in 2 tasks. One task is the backup database task. The second task is a clean up task. The clean up task is what removes the files older than X.|||

Thank you sir!

JDA

backing up transaction logs

Hi,
I would like to know if it is really nessary to backup the transaction logs
if their size is above 10 gigabytes. Is it not better to backup only the
database, delete the current log and then re-create the log.
If so, can someone help me with a scheduled script to do this?
ThnxHi
Check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_7vaf.asp
Deleting the log file as you have suggested would mean that the database is
not available during that period of time.
Your log file should be sized appropriately so that it does not continuously
grow, if you re-create a log file that is too small then you may affect
performance.
John
"Jason" <jasonlewis@.hotrmail.com> wrote in message
news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I would like to know if it is really nessary to backup the transaction
> logs
> if their size is above 10 gigabytes. Is it not better to backup only the
> database, delete the current log and then re-create the log.
> If so, can someone help me with a scheduled script to do this?
>
> Thnx
>|||Jason
If you don't want to use your transaction log for recovery purposes, set
your database to simple recovery mode. Then your transaction log will be
truncated every time a checkpoint is issued.
Regards
John
"John Bell" wrote:
> Hi
> Check out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_1uzr.asp
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_da2_7vaf.asp
> Deleting the log file as you have suggested would mean that the database is
> not available during that period of time.
> Your log file should be sized appropriately so that it does not continuously
> grow, if you re-create a log file that is too small then you may affect
> performance.
> John
> "Jason" <jasonlewis@.hotrmail.com> wrote in message
> news:O$kKVGDEFHA.3032@.TK2MSFTNGP12.phx.gbl...
> > Hi,
> >
> > I would like to know if it is really nessary to backup the transaction
> > logs
> > if their size is above 10 gigabytes. Is it not better to backup only the
> > database, delete the current log and then re-create the log.
> >
> > If so, can someone help me with a scheduled script to do this?
> >
> >
> > Thnx
> >
> >
>
>

Backing up transaction logs

Hi,
I have a single Windows Server 2003 and SQL Server 2000.
I have created a maintanance plan to back up my SQL data
base as well as the transaction log. I am getting this
error in my event viewer and haven't been able to figure
out why. I have recreated the job, making sure I was
signed in as administrator and it didn't change
anything. I have also gone into Logins under enterprise
manager and the user xxxdomainxxx\administrator does not
exist and I an not able to add it (it says it can't find
it). Any help is appreciated. Thanks
SQL Server Scheduled Job 'Transaction Log Backup Job for
DB Maintenance Plan 'DB Maintenance Plan2''
(0xB829073EE903F94A8783BC84D54506C6) - Status: Failed -
Invoked on: 2004-03-30 13:00:00 - Message: The job
failed. Unable to determine if the owner
(xxxdomainxxx\Administrator) of job Transaction Log
Backup Job for DB Maintenance Plan 'DB Maintenance Plan2'
has server access (reason: Could not obtain information
about Windows NT group/user 'xxxdomainxxx\Administrator'.
[SQLSTATE 42000] (Error 8198)).Have a look at these. I tend to set job owner to sa to avoid this
http://support.microsoft.com/defaul...3&Product=sql2k
http://support.microsoft.com/defaul...4&Product=sql2k
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Travis" <anonymous@.discussions.microsoft.com> wrote in message
news:15b4301c41684$27b8e7a0$a301280a@.phx
.gbl...
> Hi,
> I have a single Windows Server 2003 and SQL Server 2000.
> I have created a maintanance plan to back up my SQL data
> base as well as the transaction log. I am getting this
> error in my event viewer and haven't been able to figure
> out why. I have recreated the job, making sure I was
> signed in as administrator and it didn't change
> anything. I have also gone into Logins under enterprise
> manager and the user xxxdomainxxx\administrator does not
> exist and I an not able to add it (it says it can't find
> it). Any help is appreciated. Thanks
>
> SQL Server Scheduled Job 'Transaction Log Backup Job for
> DB Maintenance Plan 'DB Maintenance Plan2''
> (0xB829073EE903F94A8783BC84D54506C6) - Status: Failed -
> Invoked on: 2004-03-30 13:00:00 - Message: The job
> failed. Unable to determine if the owner
> (xxxdomainxxx\Administrator) of job Transaction Log
> Backup Job for DB Maintenance Plan 'DB Maintenance Plan2'
> has server access (reason: Could not obtain information
> about Windows NT group/user 'xxxdomainxxx\Administrator'.
> [SQLSTATE 42000] (Error 8198)).|||Thanks for your reply. I set the job owner to sa like
you suggested. However, now I am getting this error in
my event viewer. I think it says it was invoked by
administrator because I went to jobs and right clicked
and selected run? Any other ideas? Thanks
SQL Server Scheduled Job 'Transaction Log Backup Job for
DB Maintenance Plan 'DB Maintenance Plan1''
(0xD35D479ECC6E8840A93C091C8876BF07) - Status: Failed -
Invoked on: 2004-03-30 15:29:31 - Message: The job
failed. The Job was invoked by User
xxxdomainxxx\Administrator. The last step to run was
step 1 (Step 1).
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

>--Original Message--
>Have a look at these. I tend to set job owner to sa to
avoid this
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;241643&Product=sql2k
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;834124&Product=sql2k
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Travis" <anonymous@.discussions.microsoft.com> wrote in
message
> news:15b4301c41684$27b8e7a0$a301280a@.phx
.gbl...
2000.
data
figure
enterprise
not
find
for
Plan2'
group/user 'xxxdomainxxx\Administrator'.
>
>.
>|||You'll need to get the details of the failure to resolve
the issue.
o find the details of the failures with maintenance plans,
you need to go to the maintenance plans, right click on the
plan that is failing and select Database Maintenance Plan
History.
-Sue
On Tue, 30 Mar 2004 12:41:21 -0800, "Travis"
<anonymous@.discussions.microsoft.com> wrote:
>Thanks for your reply. I set the job owner to sa like
>you suggested. However, now I am getting this error in
>my event viewer. I think it says it was invoked by
>administrator because I went to jobs and right clicked
>and selected run? Any other ideas? Thanks
>SQL Server Scheduled Job 'Transaction Log Backup Job for
>DB Maintenance Plan 'DB Maintenance Plan1''
>(0xD35D479ECC6E8840A93C091C8876BF07) - Status: Failed -
>Invoked on: 2004-03-30 15:29:31 - Message: The job
>failed. The Job was invoked by User
>xxxdomainxxx\Administrator. The last step to run was
>step 1 (Step 1).
>For more information, see Help and Support Center at
>http://go.microsoft.com/fwlink/events.asp.
>
>avoid this
>us;241643&Product=sql2k
>us;834124&Product=sql2k
>message
>2000.
>data
>figure
>enterprise
>not
>find
>for
>Plan2'
>group/user 'xxxdomainxxx\Administrator'.|||Thanks for your reply!
I did what you said and it looks like it is backing up
the "master" and "msdb" databases and it shouldn't be.
So should I recreate the mantenance plan and not include
these in the backup, or will I need them?
Thanks!

>--Original Message--
> You'll need to get the details of the failure to resolve
>the issue.
>o find the details of the failures with maintenance
plans,
>you need to go to the maintenance plans, right click on
the
>plan that is failing and select Database Maintenance Plan
>History.
>-Sue
>On Tue, 30 Mar 2004 12:41:21 -0800, "Travis"
><anonymous@.discussions.microsoft.com> wrote:
>
for
in
this
Failed -
information
>.
>|||If you specified a report you should see more error details in there. From
the sound of it you may have specified a single plan for all databases and
included log backups. You can't do log backups of master and SQLAgent will
set msdb to simple when it starts if it's not already so you can't really do
if for msdb either. I'd usggest 1 plan for system databases (full backups
only) , 1 for user databases in simple mode and one for databases in full
recovery mode with log backups.
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Travis" <anonymous@.discussions.microsoft.com> wrote in message
news:131a101c4169e$5a5e9b90$a601280a@.phx
.gbl...
> Thanks for your reply!
> I did what you said and it looks like it is backing up
> the "master" and "msdb" databases and it shouldn't be.
> So should I recreate the mantenance plan and not include
> these in the backup, or will I need them?
> Thanks!
>
> plans,
> the
> for
> in
> this
> Failed -
> information|||I got it working with no errors! I did like you said and
created 3 seperate plans. Thanks so much for your help.

>--Original Message--
>If you specified a report you should see more error
details in there. From
>the sound of it you may have specified a single plan for
all databases and
>included log backups. You can't do log backups of master
and SQLAgent will
>set msdb to simple when it starts if it's not already so
you can't really do
>if for msdb either. I'd usggest 1 plan for system
databases (full backups
>only) , 1 for user databases in simple mode and one for
databases in full
>recovery mode with log backups.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Travis" <anonymous@.discussions.microsoft.com> wrote in
message
> news:131a101c4169e$5a5e9b90$a601280a@.phx
.gbl...
include
resolve
on
Plan
like
in
clicked
Failed -
to
scid=kb;en-
scid=kb;en-
SQL
was
does
can't
Job
Log
>
>.
>|||The error that I am having(which is along the same vane) is occurring
when trying to delete old Tlog backup files.
Any ideas how to fix this one?
Travis wrote:[vbcol=seagreen]
> I got it working with no errors! I did like you said and
> created 3 seperate plans. Thanks so much for your help.
>
> details in there. From
> all databases and
> and SQLAgent will
> you can't really do
> databases (full backups
> databases in full
> message
> include
> resolve
> on
> Plan
> like
> in
> clicked
> Failed -
> to
> scid=kb;en-
> scid=kb;en-
> SQL
> was
> does
> can't
> Job
> Log|||There are a couple of completely different error messages
posted in this thread. Could you please post exactly what
problems you are having and the exact error message?
For example, is this an error you get with a maintenance
plan, please post that and some details about the task in
the maintenance plan. If you are receiving errors when a
maintenance plan runs, get the details of the error from the
maintenance plan history and post those.
It's hard to tell from piggy backing off this thread what
your specific issue is. If you could post more details,
someone should be able to help you out.
Thanks -
-Sue
On 20 Jan 2005 07:10:19 -0800, "Tim"
<Timothy.Juarez@.Ipaper.com> wrote:
[vbcol=seagreen]
>The error that I am having(which is along the same vane) is occurring
>when trying to delete old Tlog backup files.
>
>Any ideas how to fix this one?
>
>Travis wrote: