Forum Discussion

manatee's avatar
manatee
Level 6
8 years ago

how do i troubleshoot this sql backup error

NBU 7.6.0.3

i have a dbclient log now. to summarise, i keep getting this error level 1 message:

0/11/2016 2:10:21 PM - Info dbclient(pid=26984) INF - Created VDI object for SQL Server instance <DB1>. Connection timeout is <1800> seconds.
10/11/2016 2:40:22 PM - Info dbclient(pid=26984) ERR - Error in GetConfiguration: 0x80770003.       
10/11/2016 2:40:22 PM - Info dbclient(pid=26984)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
10/11/2016 2:40:25 PM - Info dbclient(pid=26984) INF - OPERATION #2 of batch C:\Program Files\VERITAS\NetBackup\dbext\Mssql\dbDiffBackup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 1805(1805) seconds.
10/11/2016 2:40:27 PM - Info dbclient(pid=26984) INF - Results of executing <C:\Program Files\VERITAS\NetBackup\dbext\Mssql\dbDiffBackup.bch>:      
10/11/2016 2:40:27 PM - Info dbclient(pid=26984) <1> operations succeeded. <1> operations failed.       
10/11/2016 2:40:28 PM - Info dbclient(pid=26984) INF - The following object(s) were not backed up successfully.   
10/11/2016 2:40:28 PM - Info dbclient(pid=26984) INF - BMB          
10/11/2016 2:40:48 PM - Error bpbrm(pid=29859) from client db1: ERR - command failed: the requested operation was partially successful (1)
10/11/2016 2:40:48 PM - Error bpbrm(pid=29859) from client db1: ERR - bphdb exit status = 1: the requested operation was partially successful
10/11/2016 2:40:48 PM - Info bpbrm(pid=29859) validating image for client db1        
10/11/2016 2:40:48 PM - Info bphdb(pid=28892) done. status: 1: the requested operation was partially successful    
10/11/2016 2:40:48 PM - end writing
the requested operation was partially successful(1)

i skimmed the log and couldn't find (understand) what i'm supposed to be looking for.

i have dbclient log and will send them via PM (if that's possible).

7.6
Windows Server (2003
  • Marianne's avatar
    Marianne
    Level 6
    8 years ago

    Look for lines with <8> (Warning), <16> (Error) or <32> (Severe Error). 

    Especially <16> and/or <32>. 
    Then scroll up a few lines for the <2> (Debug) lines that led to the Error.

    By the looks of it, this is a Timeout error as we see exactly 30 minutes between these 2 timestamps:

    10/11/2016 2:10:21 PM - Info dbclient(pid=26984) INF - Created VDI object for SQL Server instance <DB1>. Connection timeout is <1800> seconds.
10/11/2016 2:40:22 PM - Info dbclient(pid=26984) ERR - Error in GetConfiguration: 0x80770003.

    For some reason, SQL did not respond within the 30 minute timeout.

    I do not recommend increasing the timeout - rather look at SQL logs to see what happened after 2PM that could cause the timeout. 
    Look in Event Viewer Application logs, SQL Errorlog and SQL VDI logs.

    Extract from http://www.veritas.com/docs/000029177: 

    - The SQL error log (named ERRORLOG, and usually located in the <install_path>\mssql\log directory)
    - The VDI log (named vdi.log and usually located in the <install_path>\mssql\log directory)
    - The Microsoft Application Event Viewer log

    Since the backup ran during the day, maybe a good idea to log into the SQL server to see what 'else' is running at this time and monitor system resources. 

     

    • manatee's avatar
      manatee
      Level 6
      8 years ago

      i don't have that <install path>\mssql\log folder but i found a "mssql_backup_failures" log that contains the following:

      TIMESTAMP 20161011144024
MASTERSERVER OVMMANAGER
CLIENT DB1
INSTANCE ABC
DATABASE BMB
OPERATION BACKUP
OBJECTTYPE DATABASE
OPTION INCREMENTAL
STATUS -1
INFO Error in GetConfiguration: 0x80770003.
INFO The api was waiting and the timeout interval had elapsed.
ENDOPER TRUE

      i have a VDITIMEOUT set for 1800 which is at the bottom of the command block. so i move it up. i don't know if that would help.

      GROUPSIZE 2
OPERATION BACKUP
DATABASE "BMB"
SQLHOST "DB1"
NBSERVER "OVMMANAGER"
VDITIMEOUTSECONDS 1800  <===
MAXTRANSFERSIZE 6
BLOCKSIZE 7
DUMPOPTION INCREMENTAL
NUMBUFS 2
ENDOPER TRUE
      • Marianne's avatar
        Marianne
        Level 6
        8 years ago

        The problem is not with the VDI Timeout or with it's location in the script.
        The entry is working - the default is 5 minutes. 
        Without the 

        VDITIMEOUTSECONDS 1800


        in the script, the backup would've failed sooner.

        You need to find out what is happening within SQL and/or the OS in this 30 minutes as suggested in my previous post.