Differential backups failing regularly

Hi,
Don't know what the problem is here. We are running a clustered
instance of SQL Server 2005 on Windows 2003 - the backups are being
written to a location on a SAN.
Here is the error message:
[SQLSTATE 40001] (Error 1205) Could not insert a backup or restore
history/detail record in the msdb database. This may indicate a problem
with the msdb database. The backup/restore operation was still
successful. [SQLSTATE 42000] (Error 3009) BACKUP DATABASE WITH
DIFFERENTIAL successfully processed 6529 pages in 2.079 seconds (25.726
MB/sec). [SQLSTATE 01000] (Error 3014). The step failed.
Says there's something wrong with msdb' Haven't made any changes.
ThanksActually, I have made some small changes - I removed the Backups user
from the databases. The Backups login still exists.
I notice that SQL Server now creates this login/user by default. I
don't think it comes with any built-in permissions, so I couldn't
figure out what it's for.
I removed the Backups user from another server - that one has had no
problems, so I doubt that is what is the causing the above error.|||Who starts the backup? Do you get the same problem if you login with a sysadmin account and execute
the backup command?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tootsuite@.gmail.com> wrote in message news:1157576820.954491.165730@.m79g2000cwm.googlegroups.com...
> Actually, I have made some small changes - I removed the Backups user
> from the databases. The Backups login still exists.
> I notice that SQL Server now creates this login/user by default. I
> don't think it comes with any built-in permissions, so I couldn't
> figure out what it's for.
> I removed the Backups user from another server - that one has had no
> problems, so I doubt that is what is the causing the above error.
>|||Hi Tibor,
The "owner" of the job that start the backup is a SQL server login with
sysadmin privileges. Is that what you are asking?
Also, I am now also seeing this problem when I run the translog backup
job. I searched the application logs in event viewer, as well as the
sql server error logs - it indicates nothing whatsover out of the
ordinary. No error msgs, nothing.
So it's hard to say what it is.
Tibor Karaszi wrote:
> Who starts the backup? Do you get the same problem if you login with a sysadmin account and execute
> the backup command?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> <tootsuite@.gmail.com> wrote in message news:1157576820.954491.165730@.m79g2000cwm.googlegroups.com...
> > Actually, I have made some small changes - I removed the Backups user
> > from the databases. The Backups login still exists.
> >
> > I notice that SQL Server now creates this login/user by default. I
> > don't think it comes with any built-in permissions, so I couldn't
> > figure out what it's for.
> >
> > I removed the Backups user from another server - that one has had no
> > problems, so I doubt that is what is the causing the above error.
> >|||Did you try executing the backup command from a query window?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<tootsuite@.gmail.com> wrote in message news:1157656240.841901.298570@.h48g2000cwc.googlegroups.com...
> Hi Tibor,
> The "owner" of the job that start the backup is a SQL server login with
> sysadmin privileges. Is that what you are asking?
> Also, I am now also seeing this problem when I run the translog backup
> job. I searched the application logs in event viewer, as well as the
> sql server error logs - it indicates nothing whatsover out of the
> ordinary. No error msgs, nothing.
> So it's hard to say what it is.
>
> Tibor Karaszi wrote:
>> Who starts the backup? Do you get the same problem if you login with a sysadmin account and
>> execute
>> the backup command?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> <tootsuite@.gmail.com> wrote in message
>> news:1157576820.954491.165730@.m79g2000cwm.googlegroups.com...
>> > Actually, I have made some small changes - I removed the Backups user
>> > from the databases. The Backups login still exists.
>> >
>> > I notice that SQL Server now creates this login/user by default. I
>> > don't think it comes with any built-in permissions, so I couldn't
>> > figure out what it's for.
>> >
>> > I removed the Backups user from another server - that one has had no
>> > problems, so I doubt that is what is the causing the above error.
>> >
>|||It looks like it's the writing of the backup history that is
causing the problem. The error you posted is:
Could not insert a backup or restore history/detail record
in the msdb database. This may indicate a problem with the
msdb database. The backup/restore operation was still
successful.
Have you run a DBCC CHECKDB on msdb? Can you view job
histories without any problems and are they current and
accurate? Did you check for any other errors related to job
history or msdb in general? Have you run a trace and run a
backup during this time to track down where exactly the
error happens, what statement and what if any other errors
are raised?
-Sue
On 7 Sep 2006 12:10:40 -0700, tootsuite@.gmail.com wrote:
>Hi Tibor,
>The "owner" of the job that start the backup is a SQL server login with
>sysadmin privileges. Is that what you are asking?
>Also, I am now also seeing this problem when I run the translog backup
>job. I searched the application logs in event viewer, as well as the
>sql server error logs - it indicates nothing whatsover out of the
>ordinary. No error msgs, nothing.
>So it's hard to say what it is.
>
>Tibor Karaszi wrote:
>> Who starts the backup? Do you get the same problem if you login with a sysadmin account and execute
>> the backup command?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> <tootsuite@.gmail.com> wrote in message news:1157576820.954491.165730@.m79g2000cwm.googlegroups.com...
>> > Actually, I have made some small changes - I removed the Backups user
>> > from the databases. The Backups login still exists.
>> >
>> > I notice that SQL Server now creates this login/user by default. I
>> > don't think it comes with any built-in permissions, so I couldn't
>> > figure out what it's for.
>> >
>> > I removed the Backups user from another server - that one has had no
>> > problems, so I doubt that is what is the causing the above error.
>> >