Got a weird one...
I have 20 databases on one SQL 2000 sp4, .2187 instance.
I also have a backup database and backup log script that I run, which
enumerates the datbase list and runs a backup for each one.
One specific database errors, while the ones before and after it succeed.
It used to work just fine, no changes (especially since I can pinpoint the
failure time to 5:50am, and I know nobody was fooling with the server at
that time).
The error is 3013 - "Backup terminating abnormally" (not the verbatim
error). Error happens for full backup and t-log.
I cannot backup manually through QA or Enterprise manger either. Nor can I
backup to a different location one the same or different drives...
Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
\LOG folder. Plenty of space on the backup drive, running out on the T-Log
drive...
Help?
Thanks,
Kevin Hill
3NF Consulting
http://kevinbhill.powweb.com/NewsGroups.htm
My random SQL Server encounters:
http://kevin3nf.blogspot.com/Forgot to mention that DBCC CheckAlloc and DBCC CheckDB come up clean
"Kevin3NF" <Kevin@.DontSpamMe3NF-inc.com> wrote in message
news:%23Qybs8kFHHA.1080@.TK2MSFTNGP05.phx.gbl...
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can
> I backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
> the \LOG folder. Plenty of space on the backup drive, running out on the
> T-Log drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>|||Kevin3NF wrote:
> Got a weird one...
> I have 20 databases on one SQL 2000 sp4, .2187 instance.
> I also have a backup database and backup log script that I run, which
> enumerates the datbase list and runs a backup for each one.
> One specific database errors, while the ones before and after it succeed.
> It used to work just fine, no changes (especially since I can pinpoint the
> failure time to 5:50am, and I know nobody was fooling with the server at
> that time).
> The error is 3013 - "Backup terminating abnormally" (not the verbatim
> error). Error happens for full backup and t-log.
> I cannot backup manually through QA or Enterprise manger either. Nor can I
> backup to a different location one the same or different drives...
> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in the
> \LOG folder. Plenty of space on the backup drive, running out on the T-Log
> drive...
> Help?
> Thanks,
> Kevin Hill
> 3NF Consulting
> http://kevinbhill.powweb.com/NewsGroups.htm
> My random SQL Server encounters:
> http://kevin3nf.blogspot.com/
>
>
>
Anything in the error log?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Just backup failed
Customer has since changed the db to Simple, and now we cannot change it
back to FULL (3013 and 5069)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45742818.40402@.realsqlguy.com...
> Kevin3NF wrote:
>> Got a weird one...
>> I have 20 databases on one SQL 2000 sp4, .2187 instance.
>> I also have a backup database and backup log script that I run, which
>> enumerates the datbase list and runs a backup for each one.
>> One specific database errors, while the ones before and after it succeed.
>> It used to work just fine, no changes (especially since I can pinpoint
>> the failure time to 5:50am, and I know nobody was fooling with the server
>> at that time).
>> The error is 3013 - "Backup terminating abnormally" (not the verbatim
>> error). Error happens for full backup and t-log.
>> I cannot backup manually through QA or Enterprise manger either. Nor can
>> I backup to a different location one the same or different drives...
>> Tried to generate a mini-dump using DBCC DUMPTRIGGER, but got nothing in
>> the \LOG folder. Plenty of space on the backup drive, running out on the
>> T-Log drive...
>> Help?
>> Thanks,
>> Kevin Hill
>> 3NF Consulting
>> http://kevinbhill.powweb.com/NewsGroups.htm
>> My random SQL Server encounters:
>> http://kevin3nf.blogspot.com/
>>
>>
> Anything in the error log?
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Kevin3NF wrote:
> Just backup failed
> Customer has since changed the db to Simple, and now we cannot change it
> back to FULL (3013 and 5069)
>
- Are you able to run queries against this database?
- Are you able to modify data within this database?
- Is something (tape backup, anti-virus software) preventing SQL from
writing to the MDF or LDF file?
- Does the SQL Server service account have proper rights to the MDF and
LDF files?
This sounds to me like something is restricting writes to the
transaction log file...
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||See below...everything appears to be working normally except the backups
This database is a replication publisher and that process is working just
fine..
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
Yes
> - Are you able to modify data within this database?
Yes
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
Not that I am aware of...failures have been happening since 11/30
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
Yes
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com|||Everything else has failed, so we aer using DTS to send everything to a new
database...
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45743322.7040206@.realsqlguy.com...
> Kevin3NF wrote:
>> Just backup failed
>> Customer has since changed the db to Simple, and now we cannot change it
>> back to FULL (3013 and 5069)
> - Are you able to run queries against this database?
> - Are you able to modify data within this database?
> - Is something (tape backup, anti-virus software) preventing SQL from
> writing to the MDF or LDF file?
> - Does the SQL Server service account have proper rights to the MDF and
> LDF files?
> This sounds to me like something is restricting writes to the transaction
> log file...
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
Actually, I found that yesterday; changed two path settings in the registry, and that fixed it. Apparently, when I duplicated the hard drive, it somehow used the DOS ~ naming conventions. Once I changed back to the named path, all seemed to work fine. Thanks to all who replied to my question.|||