There are a couple of things you can check/try:

- The disk where you are storing the database backup has enough space.

- Try using compression with backup.

Try doing backup to a different location.

There is no blocking and no triggers.

Agents set to run every five min. has been working fine from a long time as we don't have that many transactions. Distributor and publisher are the same server.

yes,I did detach...

The problem was disk corruption causing the database to get corrupted frequently. Thanks a lot for all your help.

running dbcc checkdb with repair_rebuild took care of the consistency and allocation errors. But I still get "non-recoverable I/O error"

where I try to do a full backup. Get error MS_DOS...

Login failed message..

yes, I know it should but we started seeing errors from application.

Lately I had an issue when I moved one of my windows user to active directory group and gave the same permissions to the group as the user, the user...

Freeing up proc cache really helped. Thanks..

Chirag: I can't change indexes..:-( I have to go to developers for that, which is a really-really long process.

I have a job setup which runs the script below on the database:

EXEC sp_MSforeachtable @command1="print '?' DBCC DBREINDEX ('?', ' ', 80)"

GO

EXEC sp_updatestats

GO

Thanks Mike..I'll do some more diggin' and see what's going on.

Thanks a lot..

One more question..why is it then that when I manually rebuild one of the table index, performance gets better and then again after a week with reindexing..it goes down again.