Backup failure Error Log Messages

I have not been able to find any details about backup failures for
MSSQL 2000. I am researching the following:
1. when a backup fails at a certain point during the process does the
backup:
A. stop there having recorded some details?
B. quit without backing up any of the data it already processed?
C. skip the data it cannot read and move on?
2. Does the error log record any of the details above? For instance, if
there is a table that the backup could not write to .bak, does the
error log report exactly where the error was?

I need a way to obtain a Backup Exception 'Report' that when a backup
fails it can tell me what did not get into the .bak file. I would
prefer automatic notification. Our Oracle DBs have something setup
that can be run when a piece of the DB does not get backed up letting
the Oracle DBA know where there are issues.

Thank you,
StephanieHi
1. B
2. If it is a write failure, yes it will be in the SQL Log. If it is data
corruption, it is in the SQL Log.

For a backup to fail, due to internal SQL Server problems is very very rare,
and I have not seen it on a clean database before.

Most failures are caused by running out of disk space or anti virus messing
around on the file when SQL is trying to write to it.

Regards
----------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@.epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

"Stephanie" <stuttle@.centene.com> wrote in message
news:1123710578.824686.208370@.g47g2000cwa.googlegr oups.com...
>I have not been able to find any details about backup failures for
> MSSQL 2000. I am researching the following:
> 1. when a backup fails at a certain point during the process does the
> backup:
> A. stop there having recorded some details?
> B. quit without backing up any of the data it already processed?
> C. skip the data it cannot read and move on?
> 2. Does the error log record any of the details above? For instance, if
> there is a table that the backup could not write to .bak, does the
> error log report exactly where the error was?
> I need a way to obtain a Backup Exception 'Report' that when a backup
> fails it can tell me what did not get into the .bak file. I would
> prefer automatic notification. Our Oracle DBs have something setup
> that can be run when a piece of the DB does not get backed up letting
> the Oracle DBA know where there are issues.
> Thank you,
> Stephanie

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
Michael
Michael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName. bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.ba k' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.
).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK =
\\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Serve
r
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3
-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer availabl
e.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak'. Operating system err
or
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\Dat
abaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK =
> \\SERVER_NAME\SQLBackup\Production\Datab
aseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Ser
ver
> Agent account which has full access permission to the backup network drive
.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michael

Backup Failure - Operating system error 64

I am receiving the below error message while doing a Database backup as a
schedule dts package job.
Operating system error 64(The specified network name is no longer available.).
or
Operating system error 64(error not found).
18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device '
\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
64(error not found).
18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
error 64(error not found).
Please note, I am backing up to a networked drive/location using the below
command as an example, which is not a mapped drive,
BACKUP DATABASE [DatabaseName] TO DISK = \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
The same scheduled dts package backup job sometimes run successfully at
the scheduled time and most times failed. The job is ran under the SQL Server
Agent account which has full access permission to the backup network drive.
The backup dts package always run successfully when ran manually using my
login account.
Thank you and kind regards
MichaelMichael,
The OS error 64 usually indicates the network problems.
Intermittent loss of connectivity to the share. To ensure that the
backups for the database are taken properly, I recommend you backup to
the local drive and then create a NT job to move the job to the share
upon completion of the SQL Backup. If the Nt copy job fails, then we
can be sure that the problem is because of network connectivity.
Hope that helps.
Venu
"Michael" <Michael@.discussions.microsoft.com> wrote in message news:<9973687E-E0C3-41C6-BAF3-D0C240895A01@.microsoft.com>...
> I am receiving the below error message while doing a Database backup as a
> schedule dts package job.
> Operating system error 64(The specified network name is no longer available.).
> or
> Operating system error 64(error not found).
> 18210 :
> BackupDiskFile::RequestDurableMedia: failure on backup device '
> \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system error
> 64(error not found).
> 18210 :
> BackupMedium::ReportIoError: write failure on backup device
> '\\\SERVER_NAME\SQLBackup\Production\DatabaseName.bak'. Operating system
> error 64(error not found).
>
> Please note, I am backing up to a networked drive/location using the below
> command as an example, which is not a mapped drive,
> BACKUP DATABASE [DatabaseName] TO DISK => \\SERVER_NAME\SQLBackup\Production\DatabaseName.bak' WITH INIT
> The same scheduled dts package backup job sometimes run successfully at
> the scheduled time and most times failed. The job is ran under the SQL Server
> Agent account which has full access permission to the backup network drive.
> The backup dts package always run successfully when ran manually using my
> login account.
> Thank you and kind regards
> Michaelsql

Backup Failure - Delete old files

I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.
What is the error message you get at 3rd step?
"helpplease" wrote:

> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' and
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fine
> before.
> Any kind of help is greatly appreciated.
|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
[vbcol=seagreen]
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
|||Specify a report file for the maint plan and check the report file for the error messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...[vbcol=seagreen]
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:

Backup Failure - Delete old files

I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:
> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' and
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fine
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
> > I have setup my backup job to delete file older than 12 hours. I want to
> > keep atleast 2 backup files saved. The backup runs every night.
> > My backup job fails on alternate days.
> >
> > The day it fails, it completes just 2 steps 'backup database' and 'verify
> > database'.
> >
> > The day is completes sucessfully, it completes 4 steps 'backup database' and
> > 'verify database' and 'delete old backup files' and 'check data and index
> > linkage'.
> >
> > It started failing for last few months. The same setting used to work fine
> > before.
> >
> > Any kind of help is greatly appreciated.|||Specify a report file for the maint plan and check the report file for the error messages.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>> What is the error message you get at 3rd step?
>>
>> "helpplease" wrote:
>> > I have setup my backup job to delete file older than 12 hours. I want to
>> > keep atleast 2 backup files saved. The backup runs every night.
>> > My backup job fails on alternate days.
>> >
>> > The day it fails, it completes just 2 steps 'backup database' and 'verify
>> > database'.
>> >
>> > The day is completes sucessfully, it completes 4 steps 'backup database' and
>> > 'verify database' and 'delete old backup files' and 'check data and index
>> > linkage'.
>> >
>> > It started failing for last few months. The same setting used to work fine
>> > before.
>> >
>> > Any kind of help is greatly appreciated.

Backup Failure - Delete old files

I have setup my backup job to delete file older than 12 hours. I want to
keep atleast 2 backup files saved. The backup runs every night.
My backup job fails on alternate days.
The day it fails, it completes just 2 steps 'backup database' and 'verify
database'.
The day is completes sucessfully, it completes 4 steps 'backup database' and
'verify database' and 'delete old backup files' and 'check data and index
linkage'.
It started failing for last few months. The same setting used to work fine
before.
Any kind of help is greatly appreciated.What is the error message you get at 3rd step?
"helpplease" wrote:

> I have setup my backup job to delete file older than 12 hours. I want to
> keep atleast 2 backup files saved. The backup runs every night.
> My backup job fails on alternate days.
> The day it fails, it completes just 2 steps 'backup database' and 'verify
> database'.
> The day is completes sucessfully, it completes 4 steps 'backup database' a
nd
> 'verify database' and 'delete old backup files' and 'check data and index
> linkage'.
> It started failing for last few months. The same setting used to work fin
e
> before.
> Any kind of help is greatly appreciated.|||Does not show the description of error inside the job or the maintenance
plan. The following error message is shown on the Application event log.
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on:
2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
"bluefish" wrote:
[vbcol=seagreen]
> What is the error message you get at 3rd step?
>
> "helpplease" wrote:
>|||Specify a report file for the maint plan and check the report file for the e
rror messages.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"helpplease" <helpplease@.discussions.microsoft.com> wrote in message
news:E2EA51C2-6ED1-4EF6-BA39-FEF7D275245E@.microsoft.com...[vbcol=seagreen]
> Does not show the description of error inside the job or the maintenance
> plan. The following error message is shown on the Application event log.
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'Insite
> Maint'' (0xE5E76C0F4E0B7546BB973E5A02710F7F) - Status: Failed - Invoked on
:
> 2006-02-20 21:00:00 - Message: The job failed. The Job was invoked by
> Schedule 17 (Schedule 1). The last step to run was step 1 (Step 1).
>
> "bluefish" wrote:
>

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL using backup under the Management folder in Enterprise manager. Logged in as administrator. Can backup the pubs, Northwind and master databases with no problem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using option to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Dave
can you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Dave

Backup failure

All,
I am receiving the following error when I try to backup to tape from SQL usi
ng backup under the Management folder in Enterprise manager. Logged in as ad
ministrator. Can backup the pubs, Northwind and master databases with no pro
blem.
The database is approx. 8.5GB and the tape can hold 40GB formatted. Using op
tion to overwrite and initialize.
Microsoft SQL-DMO (ODBC SQLState: 42000)
Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log for
more details, backup database is terminating abnormally.
In the error log;
Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size: 65536,
position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000, offse
t: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536, m_actualbytes
: 65536, m_errcode: 1117, b
ackupfile: \\.\Tape0
Any thought would be appreciated.
Regards,
Davecan you back it up to disk instead of to tape?
can you backup a large file from disk to tape?
I will do it this way because backup done faster and eliminating the hassle
of dealing with the tape drive.
my 0.02
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:C1CCFEFC-AD93-4715-919F-C468273BD974@.microsoft.com...
> All,
> I am receiving the following error when I try to backup to tape from SQL
using backup under the Management folder in Enterprise manager. Logged in as
administrator. Can backup the pubs, Northwind and master databases with no
problem.
> The database is approx. 8.5GB and the tape can hold 40GB formatted. Using
option to overwrite and initialize.
> Microsoft SQL-DMO (ODBC SQLState: 42000)
> Write on '\\.\Tape0' failed, status = 1117. See the SQL Server error log
for more details, backup database is terminating abnormally.
> In the error log;
> Internal I/O request 0x075CB728: op: write, pBuffer: 0x07d3000, size:
65536, position: 11141120, UMS: internal: 0xC0000185, internalhigh: 0x10000,
offset: 0xAA0000, offsethigh: 0x0, m_buf: 0x07d30000, m_len: 65536,
m_actualbytes: 65536, m_errcode: 1117, backupfile: \\.\Tape0
> Any thought would be appreciated.
> Regards,
> Davesql

Backup Failure

I've encountered an error while performing a database backup. I can't seem t
o
find this error anywhere:
BACKUP failed to complete the command master.dbo.sp_sqlexec;1
Does anyone have any insight into this error?
Thank You!How do you execute the backup? For troubleshooting purposes, try executing a
BACKUP command from
Query analyzer.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:6DCC9B4B-4EE8-428A-842B-7E191FFE5AB6@.microsoft.com...
> I've encountered an error while performing a database backup. I can't seem
to
> find this error anywhere:
> BACKUP failed to complete the command master.dbo.sp_sqlexec;1
> Does anyone have any insight into this error?
> Thank You!|||The backup is executed as a scheduled job. This job has been running for
months without any issues - then suddenly...
When run manually, works just fine...
"Tibor Karaszi" wrote:

> How do you execute the backup? For troubleshooting purposes, try executing
a BACKUP command from
> Query analyzer.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:6DCC9B4B-4EE8-428A-842B-7E191FFE5AB6@.microsoft.com...
>|||Is it a TSQL job? How many jobsteps does the job contain? Where did you get
the error message from?
The job output of a job step in the job?
If you are uncertain, define a different output file for each jobstep and se
e exactly which jobstep
this message is from. Then post the TSQL commands you have in that jobstep.
I'm asking because the
error you posted doesn't look like an error that the BACKUP command would pr
oduce.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:D2BB3DBC-BFC5-4581-877B-6BE65F7E0E23@.microsoft.com...
> The backup is executed as a scheduled job. This job has been running for
> months without any issues - then suddenly...
> When run manually, works just fine...
> "Tibor Karaszi" wrote:
>

backup failure

Hi
My DB backup and transaction backup of a database keep on failing with
the following error:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC
SQL Server Driver][SQL Server]Write on
'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
terminating abnormally.
Any idea what it really means ?
Thanks
DavidYou can get the description of Win32 error codes with NET HELPMSG from a
command prompt:

NET HELPMSG 112

Yields:

There is not enough space on the disk.

--
Hope this helps.

Dan Guzman
SQL Server MVP

"David Greenberg" <davidgr@.iba.org.il> wrote in message
news:444B9239.2010804@.iba.org.il...
> Hi
> My DB backup and transaction backup of a database keep on failing with the
> following error:
> Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL
> Server Driver][SQL Server]Write on
> 'E:\SqlServer\testdb_db_200604221313.BAK' failed, status = 112. See the
> SQL Server error log for more details.
> [Microsoft][ODBC SQL Server Driver][SQL Server]BACKUP DATABASE is
> terminating abnormally.
> Any idea what it really means ?
> Thanks
> David

Backup fails with Operating system error 33

Backing up a large '78 GB' database to a compressed folder
gives this error: BackupMedium::ReportIoError: write
failure on backup device '*replaced file name here*.BAK'.
Operating system error 33(The process cannot access the
file because another process has locked a portion of the
file.). The BAK file size should be about 66 GB. This
backup works if the target is an uncompressed folder on
the same drive, and it did work the first time it was used
to the compressed drive. The system reports over 100 GB
free space on this drive.Have a look at the KB article:
INF: SQL Server Databases Not Supported on Compressed Volumes
# 231347
http://support.microsoft.com/?id=231347
--
Mike Epprecht, Microsoft SQL Server MVP
Epprecht Consulting (PTY) LTD
Johannesburg, South Africa
Mobile: +27-82-552-0268
IM: mike@.NOSPAMepprecht.net
Specialist SQL Server Solutions and Consulting
"Warren" <bauerwa@.wsdot.wa.gov> wrote in message
news:00ef01c3d947$a43136e0$a601280a@.phx.gbl...
> Backing up a large '78 GB' database to a compressed folder
> gives this error: BackupMedium::ReportIoError: write
> failure on backup device '*replaced file name here*.BAK'.
> Operating system error 33(The process cannot access the
> file because another process has locked a portion of the
> file.). The BAK file size should be about 66 GB. This
> backup works if the target is an uncompressed folder on
> the same drive, and it did work the first time it was used
> to the compressed drive. The system reports over 100 GB
> free space on this drive.sql

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
Dave
In order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

Backup fails with event 17055, 18210 BackupTapeFile::UnloadTape: PrepareTape

I started to get failed backups with the following error in event
viewer
Event 17055
18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
device '\\.\Tape0'. Operating system error 1(Incorrect function.).
The backup runs for a few hours then fails
I changed 4 tapes (all new), used a different SDLT drive... Same
result
Can't find a clue anywhere...
Any help is greatly appreciated
DaveIn order to better clarify the problem
1) SQL2000 on Win2003 Adv Srv
2) Here's the last lines of the job history
[...] (Message 4035) Processed 17151872 pages for database 'P01',
file 'P01DATA2' on file 4. [SQLSTATE 01000] (Message 4035) 100
percent backed up. [SQLSTATE 01000] (Message 3211) Processed 33070
pages for database 'P01', file 'P01LOG1' on file 4. [SQLSTATE 01000]
(Message 4035) Operation on device '\\.\Tape1' exceeded retry count.
[SQLSTATE 42000] (Error 3230) BACKUP DATABASE is terminating
abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
It seems the db backup has been 100% completed but in some way there
is an error
3) Here's the part of the script that fails
BACKUP DATABASE [P01] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT , NOUNLOAD , NAME = N'P01 backup', SKIP , STATS = 10
DECLARE @.i INT
select @.i = position from msdb..backupset where database_name='P01'and
type!='F' and backup_set_id=(select max(backup_set_id) from
msdb..backupset where database_name='P01')
RESTORE VERIFYONLY FROM TAPE = N'\\.\Tape1' WITH FILE = @.i, UNLOAD
It is preceeded by three other steps, backing up master, model and
msdb. No problem for them
Step1 (Completes with no problems)
BACKUP DATABASE [master] TO TAPE = N'\\.\Tape1' WITH FORMAT,
NOUNLOAD , NOREWIND, RETAINDAYS = 7, NAME = N'master backup',
SKIP , STATS = 10
Step2 (Completes with no problems)
BACKUP DATABASE [model] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'model backup', SKIP , STATS =
10
Step3 (Completes with no problems)
BACKUP DATABASE [msdb] TO TAPE = N'\\.\Tape1' WITH NOFORMAT,
NOINIT, NOUNLOAD, NOREWIND, NAME = N'msdb backup', SKIP , STATS =
10
On Feb 5, 4:35 pm, "dbowman" <dbwmn2...@.yahoo.com> wrote:
> I started to get failed backups with the following error in event
> viewer
> Event 17055
> 18210 : BackupTapeFile::UnloadTape: PrepareTape failure on backup
> device '\\.\Tape0'. Operating system error 1(Incorrect function.).
> The backup runs for a few hours then fails
> I changed 4 tapes (all new), used a different SDLT drive... Same
> result
> Can't find a clue anywhere...
> Any help is greatly appreciated
> Dave

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArch ive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchi ve\MercuryArchive.bak
The connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:

>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
>'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArc hive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
>\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArch ive\MercuryArchive.bak
>

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\M
ercuryArchive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\Me
rcuryArchive\MercuryArchive.bakThe connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:

>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
> '\\Na00vdmdba01\ProductionBackup\PSSQL\M
ercuryArchive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write
,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
> \\Na00vdmdba01\ProductionBackup\PSSQL\Me
rcuryArchive\MercuryArchive.bak
>

backup faild to VDM

I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
am getting the following failure any idea.
2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
on backup device
'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak'.
Operating system error 64(The specified network name is no longer
available.).
2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bakThe connection to the backup server is dropping. It could be
a lot of things - the size of the backup file makes a
difference - large backup files can be problematic, the
hardware involved may not be able to handle the load of the
backup, if the destination is having resource issues you can
hit this error, or if you just have something unstable in
network mix, you can get dropped connections in general.
If you have the space and it's SQL Server having the problem
writing the backup across the network, you could try backing
up locally and then do a copy of the backup over to the
network location.
-Sue
On Mon, 2 Apr 2007 09:02:41 -0700, <msnews.microsoft.com>
wrote:
>I am doing a full backup if one of my DAtabases to Virtual backup (SAN) , I
>am getting the following failure any idea.
>
>2007-03-30 21:16:33.17 spid86 BackupMedium::ReportIoError: write failure
>on backup device
>'\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak'.
>Operating system error 64(The specified network name is no longer
>available.).
>2007-03-30 21:16:33.20 spid86 Internal I/O request 0x67103D80: Op: Write,
>pBuffer: 0x0C760000, Size: 983040, Position: 116869634560, UMS: Internal:
>0x0, InternalHigh: 0xF0000, Offset: 0x35F91A00, OffsetHigh: 0x1B, m_buf:
>0x0C760000, m_len: 983040, m_actualBytes: 0, m_errcode: 64, BackupFile:
>\\Na00vdmdba01\ProductionBackup\PSSQL\MercuryArchive\MercuryArchive.bak
>sql

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...
>

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...
>