Problems with backup on SQL server

  • Thomasberg

    Old Hand

    Points: 345

    Hi all SQL brainers.

    Im starting to receive these errors on my SQL server, when I run my daily FULL backup. I cant seem to find the source of the problem, and I dont know if its the SQL server, or my backup agent which is causing the problem. I tried troubleshoot them both, but the backup is still causing theses problems.

    Can someone please help me on my way?

    Thanks alot!

    I receive these 4 kinds of errors

    Event Type: Error

    Event Source: MSSQLSERVER

    Event Category: (6)

    Event ID: 17055

    Date: 21-08-2008

    Time: 22:12:01

    User: NT AUTHORITY\SYSTEM

    Computer: SQL1

    Description:

    3041 :

    BACKUP failed to complete the command BACKUP DATABASE [master] TO VIRTUAL_DEVICE='BE_SQLAgent-master__6df2c99b_f398_44d2_aa55_2b1d4d938e95_' WITH name='Backup Exec SQL Server Agent', SNAPSHOT

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: e1 0b 00 00 10 00 00 00 á.......

    0008: 05 00 00 00 53 00 51 00 ....S.Q.

    0010: 4c 00 31 00 00 00 07 00 L.1.....

    0018: 00 00 6d 00 61 00 73 00 ..m.a.s.

    0020: 74 00 65 00 72 00 00 00 t.e.r...

    Event Type: Error

    Event Source: Backup Exec

    Event Category: None

    Event ID: 57859

    Date: 21-08-2008

    Time: 22:12:01

    User: N/A

    Computer: SQL1

    Description:

    An error occurred while executing the following query: "BACKUP DATABASE [master] TO VIRTUAL_DEVICE='BE_SQLAgent-master__6df2c99b_f398_44d2_aa55_2b1d4d938e95_' WITH name='Backup Exec SQL Server Agent', SNAPSHOT".

    On server: "SQL1".

    SQL error number: "0C98".

    SQL error message: "Cannot create worker thread.

    ".

    For more information, click the following link:

    http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

    Data:

    0000: 98 0c 00 00 00 00 00 00 ˜.......

    0008: 00 00 00 00 00 00 00 00 ........

    Event Type: Error

    Event Source: MSSQLSERVER

    Event Category: (2)

    Event ID: 17055

    Date: 21-08-2008

    Time: 22:12:14

    User: N/A

    Computer: SQL1

    Description:

    17120 :

    SQL Server could not spawn process_loginread thread.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Data:

    0000: e0 42 00 00 10 00 00 00 àB......

    0008: 05 00 00 00 53 00 51 00 ....S.Q.

    0010: 4c 00 31 00 00 00 00 00 L.1.....

    0018: 00 00 ..

    Event Type: Error

    Event Source: Backup Exec

    Event Category: None

    Event ID: 57859

    Date: 21-08-2008

    Time: 22:12:23

    User: N/A

    Computer: SQL1

    Description:

    An error occurred while executing the following query: "DBCC CHECKDB([CSI2005]) WITH PHYSICAL_ONLY".

    On server: "SQL1".

    SQL error number: "21C2".

    SQL error message: "The query processor could not start the necessary thread resources for parallel query execution.

    ".

    For more information, click the following link:

    http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml

    Data:

    0000: c2 21 00 00 00 00 00 00 Â!......

    0008: 00 00 00 00 00 00 00 00 ........

  • CDBA

    Hall of Fame

    Points: 3266

    Looks like some disc related issue to me (May be I am wrong),,

    Can you take a full backup manually using TSQL and see what it is doing?

    Also do a checkdb and fix errors ASAP and do a scandisc on HDD also.

  • rajiniforu

    Ten Centuries

    Points: 1147

    From the error messages provided, seems like the server load was too high to create a worker thread. Please check the following and proceed accordingly.

    >> Try to run the FULL backup in non peak hours and check if this works.

    >> While the backup is running, check to see if they are any parallel high resource intensity jobs\process is running, which is causing this error.

    >> This can also be because of the huge concurrently active user connections on the server.

    >> Also it could be because of the virtual memory issues. SQL Server may generate these kind of error messages after the whole virtual address space is used up.

    Check if the server is facing any of the above situation.

    -Rajini

  • Thomasberg

    Old Hand

    Points: 345

    Thanks for both of your suggestions. I did run some diagnostics on my server, and backup last night.

    My backup is always in nonpeak hours at night, so user load shouldnt be an issue.

    The next thing is I did a backup job without the Symantec Open File Option, and It came out allright. SQL server didnt generate any errors.

    This is quite strange, because Its been working fine the last couple of months, when it suddenly started with these errors.

    Bottom line is I now localized the error, the Symantec Backup Exec 11d Open File Option. An I will therefore continue troubleshooting my problem with symantec.

    Thanks for your responses 🙂

Viewing 4 posts - 1 through 4 (of 4 total)

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