backup thread in a wiat state for the last 2 days.

  • SQL Server 2005 Standard Edition.

    We use Netbackup to backup our Databases directly to Tape.

    I have 2 Databases that have not been backed up in 2 Days. One is the MASTER Database and one is a user database.

    When I look in the activity monitor on the sql server,

    I have Backup threads for these 2 Databases that are in a SUSPENDED status with a wait type of BACKUPTHREAD

    Is it safe to cancel these threads???

  • Any other threads on the instance with a different backup wait type, e.g.

    BACKUP - Occurs when a task is blocked as part of backup processing.

    BACKUP_CLIENTLOCK - Internal only.

    BACKUP_OPERATOR - Occurs when a task is waiting for a tape mount. To view the tape status, query sys.dm_io_backup_tapes. If a mount operation is not pending, this wait type may indicate a hardware problem with the tape drive.

    BACKUPBUFFER - Occurs when a backup task is waiting for data, or is waiting for a buffer in which to store data. This type is not typical, except when a task is waiting for a tape mount.

    BACKUPIO - Occurs when a backup task is waiting for data, or is waiting for a buffer in which to store data. This type is not typical, except when a task is waiting for a tape mount.

    What are the other threads in the instance waiting on?

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Both Databases have threads with wait types of Backupthread, backupio and lck_m_u

  • BACKUPIO - Occurs when a backup task is waiting for data, or is waiting for a buffer in which to store data. This type is not typical, except when a task is waiting for a tape mount.

    How/What is your tape lib doing?

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Netbackup running a Full Backup everynight and TLOG backups every 2 hours during busines hours. Sometimes we do have jobs waiting for media.. but not often. I'm not sure what happened with the library 2 days ago but since the 26th, the nightly Full backup of the master and the nightly full and daily tlog backups of the other DB have been failng because of these hung threads. Not sure if I can kill these threads. I would hate to screw up my master DB especially.. this is a production box

  • Ultimately it is your call but I do not anticipate any issues with killing those threads in terms of you ending up with a corrupt database, but it is master and I understand your concern.

    Please have a read through this, and the comments, especially the one from 10/16/2009

    http://connect.microsoft.com/SQLServer/feedback/details/433703/killed-rollback

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • Thanks for all your help. I think I will Kill the threads on the user database first and see how I make out. I can at least get get a good FULL backup of that one before i attempt the 'kill' : ) as it is the tlog backup transaction thread that is hung.

  • How are you getting along?

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • You have been so very helpfull and I apologize for not posting back with results!!

    I ended up killing the hung backup threads and it turns out that there were Netbackup jobs that we still in queue waiting - those jobs completed and everything has been normal since. I will have to backtrack with my infrastructure guys to find out what might have happened to cause these threads to be hung - i suspect we had a problem with the libary on that day.

    thanks again for all your support!!!

  • You're welcome. I am happy it was all sorted without a major incident!

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • : ) Major incidents we can do without! ciao!

Viewing 11 posts - 1 through 10 (of 10 total)

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