[AdventureWorks] database backup failed with error: 3013

SQL Server 2005
A couple nights ago I got several failures on my 3 AM database backups, my
program generated the message:
[AdventureWorks] database backup failed with error: 3013
on several databases, including: AdventureWorks, AdventureWorksDW, master,
model & msdb.
The error number was captured using @.@.ERROR.
When I saw the error, I did the following:
- Check drive space. Fine.
- Check Windows Event Log - no pertinant messages (particulary drive
space)
- Check SQL Server logs
BACKUP failed to complete the command BACKUP LOG msdb. Check the
backup application log for details
Error 3041, Severity 16, State 1
(repeats for several databases)
- Ran DBCC CHECKALLOC, DBCC CHECKCATALOG, DBCC CHECKDB and all were
fine.
- Re-ran a full backup without any issues.
I know I will see error 3013 if I run out of space on a drive, but that
wasn't the case here.
The only thing "wrong" with this install is that the data and backups are
all on the E: drive and while the drive itself is fragmened, but with only
some minor exceptions, none of the .*df files are in the list.
Oh, and not that I think it matters, but AutoShrink is off on all DB's.
I would appreciate any assistance anyone can give helping me to understand
what may have gone wrong.
Thanks,
Jay
PS. I decided to do some resizing of datafiles and run a defrag.Apparently something changed in the nightly backups so that it is
trying to backup the logs on those databases.
The databases you list all default to SIMPLE recovery mode. The
example you showed for msdb was a failure to backup the log. You can
not backup the log on a database in SIMPLE recovery mode.
Roy Harvey
Beacon Falls, CT
On Wed, 14 Nov 2007 09:40:37 -0800, "Jay" <nospam@.nospam.org> wrote:

>SQL Server 2005
>A couple nights ago I got several failures on my 3 AM database backups, my
>program generated the message:
>[AdventureWorks] database backup failed with error: 3013
>on several databases, including: AdventureWorks, AdventureWorksDW, master,
>model & msdb.
>The error number was captured using @.@.ERROR.
>When I saw the error, I did the following:
> - Check drive space. Fine.
> - Check Windows Event Log - no pertinant messages (particulary drive
>space)
> - Check SQL Server logs
> BACKUP failed to complete the command BACKUP LOG msdb. Check th
e
>backup application log for details
> Error 3041, Severity 16, State 1
> (repeats for several databases)
> - Ran DBCC CHECKALLOC, DBCC CHECKCATALOG, DBCC CHECKDB and all were
>fine.
> - Re-ran a full backup without any issues.
>I know I will see error 3013 if I run out of space on a drive, but that
>wasn't the case here.
>The only thing "wrong" with this install is that the data and backups are
>all on the E: drive and while the drive itself is fragmened, but with only
>some minor exceptions, none of the .*df files are in the list.
>Oh, and not that I think it matters, but AutoShrink is off on all DB's.
>I would appreciate any assistance anyone can give helping me to understand
>what may have gone wrong.
>Thanks,
>Jay
>PS. I decided to do some resizing of datafiles and run a defrag.
>|||You are correct sir.
I have been dealing with the difference between 2000 & 2005 on the issue of
backing up the transaction log for simple mode databases and had just
included extra error traps. I also have a version that won't try the simple
mode log backup on version 9.
I supose I just managed to confuse myself.
Thanks,
Jay
"Roy Harvey (SQL Server MVP)" <roy_harvey@.snet.net> wrote in message
news:h4fmj392cv2vmstka6dkk07qfiovlvgsnu@.
4ax.com...[vbcol=seagreen]
> Apparently something changed in the nightly backups so that it is
> trying to backup the logs on those databases.
> The databases you list all default to SIMPLE recovery mode. The
> example you showed for msdb was a failure to backup the log. You can
> not backup the log on a database in SIMPLE recovery mode.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 14 Nov 2007 09:40:37 -0800, "Jay" <nospam@.nospam.org> wrote:
>|||To add to Roy's comments, I would recommend not backing up the
AdventureWorks sample databases at all. You can always reinstall or download
these later if you need to.
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://technet.microsoft.com/en-us/...r/bb428874.aspx
"Jay" <nospam@.nospam.org> wrote in message
news:%238yk4VuJIHA.6108@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005
> A couple nights ago I got several failures on my 3 AM database backups, my
> program generated the message:
> [AdventureWorks] database backup failed with error: 3013
> on several databases, including: AdventureWorks, AdventureWorksDW, master,
> model & msdb.
> The error number was captured using @.@.ERROR.
> When I saw the error, I did the following:
> - Check drive space. Fine.
> - Check Windows Event Log - no pertinant messages (particulary drive
> space)
> - Check SQL Server logs
> BACKUP failed to complete the command BACKUP LOG msdb. Check
> the backup application log for details
> Error 3041, Severity 16, State 1
> (repeats for several databases)
> - Ran DBCC CHECKALLOC, DBCC CHECKCATALOG, DBCC CHECKDB and all were
> fine.
> - Re-ran a full backup without any issues.
> I know I will see error 3013 if I run out of space on a drive, but that
> wasn't the case here.
> The only thing "wrong" with this install is that the data and backups are
> all on the E: drive and while the drive itself is fragmened, but with only
> some minor exceptions, none of the .*df files are in the list.
> Oh, and not that I think it matters, but AutoShrink is off on all DB's.
> I would appreciate any assistance anyone can give helping me to understand
> what may have gone wrong.
> Thanks,
> Jay
> PS. I decided to do some resizing of datafiles and run a defrag.
>|||Thanks, but no thanks. All databases get backed up.
Besides, I activly monitor these systems, so I'll know if space is an issue
before it becomes an issue.
"Gail Erickson [MS]" <gaile@.online.microsoft.com> wrote in message
news:%23m8HfIvJIHA.3820@.TK2MSFTNGP03.phx.gbl...
> To add to Roy's comments, I would recommend not backing up the
> AdventureWorks sample databases at all. You can always reinstall or
> download these later if you need to.
> --
> Gail Erickson [MS]
> SQL Server Documentation Team
> This posting is provided "AS IS" with no warranties, and confers no rights
> Download the latest version of Books Online from
> http://technet.microsoft.com/en-us/...r/bb428874.aspx
> "Jay" <nospam@.nospam.org> wrote in message
> news:%238yk4VuJIHA.6108@.TK2MSFTNGP03.phx.gbl...
>