Backup problems

  • I am running two jobs on one database, one runs every half hour log backups, and the other runs once a day at night performing Full backup.

    The log backup job continuous running successfully, however, the full backup job is now giving me the following error...

    Backup and file manipulation operations (such as ALTER DATABASE ADD FILE) on a database must be serialized. Reissue the statement after the current backup or file manipulation operation is completed.

    I am not running any other jobs, or scripts other than this two. I went to job monitor and disable the jobs that I have, I then went to the database right click, select backup, tried to run a full backup to a new Media file and the same error occurs..

    One weird thing that occurs is when I try to run the Full backup job it does not complete, it stays running....not sure why.

  • Is there a shrink of the database occurring manually or is the database set to auto-shrink, and coincidentally it's doing it at the time of backup? What do you get when you run sp_who or sp_who2? Lastly, did you even try google?

    http://tinyurl.com/34mvvsl

    -- You can't be late until you show up.

  • Sorry, double-post. My screen never cleared. My fault!!

    -- You can't be late until you show up.

  • I think tosscrosby is spot on !

    You should be able to pull that info (alter database) from the instances default trace data.

    Have a look at :http://www.sqlservercentral.com/articles/SQL+Server+2005/64547/

    Johan

    Learn to play, play to learn !

    Dont drive faster than your guardian angel can fly ...
    but keeping both feet on the ground wont get you anywhere :w00t:

    - How to post Performance Problems
    - How to post data/code to get the best help[/url]

    - How to prevent a sore throat after hours of presenting ppt

    press F1 for solution, press shift+F1 for urgent solution 😀

    Need a bit of Powershell? How about this

    Who am I ? Sometimes this is me but most of the time this is me

  • Thank you all for your help, there was another backup running at the same time from Symentic. I guess I never received an error alert because they were both on idle.

  • By running sp_who & Sp_who2 ,u ll get more clarity on this issue

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply