keeps getting error code 1

[manatee]

NBU 7.6.0.3

twice this week i received the following errors:

10/9/2016 2:10:15 PM - Info dbclient(pid=27312) INF - BACKUP STARTED USING        
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)    
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) Apr  2 2010 15:48:46        
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) Copyright (c) Microsoft Corporation         
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) 
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) Batch = C:\Program Files\VERITAS\NetBackup\dbext\Mssql\dbDiffBackup.bch, Op# = 2      
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) INF - Using backup image DB1.MSSQL7.DB1.inc.DB1.~.7.001of001.20161009141014..C       
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) INF - backup database "DB1" to VIRTUAL_DEVICE='VNBU0-27312-18340-1476011415' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, differential
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) INF - Number of stripes: 1, Number of buffers per stripe 2. 
10/9/2016 2:10:15 PM - Info dbclient(pid=27312) INF - Created VDI object for SQL Server instance <DB1>. Connection timeout is <1800> seconds.
10/9/2016 2:40:16 PM - Info dbclient(pid=27312) ERR - Error in GetConfiguration: 0x80770003.       
10/9/2016 2:40:16 PM - Info dbclient(pid=27312)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
10/9/2016 2:40:19 PM - Info dbclient(pid=27312) 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/9/2016 2:40:21 PM - Info dbclient(pid=27312) INF - Results of executing <C:\Program Files\VERITAS\NetBackup\dbext\Mssql\dbDiffBackup.bch>:      
10/9/2016 2:40:21 PM - Info dbclient(pid=27312) <1> operations succeeded. <1> operations failed.       
10/9/2016 2:40:22 PM - Info dbclient(pid=27312) INF - The following object(s) were not backed up successfully.   
10/9/2016 2:40:22 PM - Info dbclient(pid=27312) INF - DB1          
10/9/2016 2:40:42 PM - Error bpbrm(pid=4662) from client db1: ERR - command failed: the requested operation was partially successful (1)
10/9/2016 2:40:42 PM - Error bpbrm(pid=4662) from client db1: ERR - bphdb exit status = 1: the requested operation was partially successful
10/9/2016 2:40:42 PM - Info bpbrm(pid=4662) validating image for client db1        
10/9/2016 2:40:42 PM - Info bphdb(pid=27696) done. status: 1: the requested operation was partially successful    
10/9/2016 2:40:42 PM - end writing
the requested operation was partially successful(1)

so to verify, we restored today's backup and the DBA confirmed the restore was successful. nothing corrupt or wrong with the restored database.

question is, why NBU keeps throwing this messages when the fact is nothing was wrong with the backup?

[PatS729]

Hello,

Whats the MSSQL version used here? Also would like to know what the Recovery Model used for databse "DB1" (simple or Full) ?

You may like understand how recovery model works with NBU

https://www.veritas.com/support/en_US/article.000019176

If this doesnt work, please gather dbclient log from Client with VERBOSE settings.

[Marianne]

This is a differential backup that failed.
Is Full backup successful?

This is the only error reported here and not very helpful:

The api was waiting and the timeout interval had elapsed.

Lots of possible reasons when you Google the error, but you need logs to troubleshoot. 
Level 3 dbclient log should give us sufficient info. 
Please copy the log to dbclient.txt and upload here.

[Systems_Team · Accepted solution]

Hi Rino19ny,

As Marianne has suggested, check if your last full backup was good, and see if you can generate another log file.

There are plenty of possible causes, but one I have seen a few examples of which are similar to yours is a hung dbbackex.exe process or processes.  Have a look in task manager when no backups are running, and kill off any dbdbbackex.exe processes.

May not be your issue, but easy to check - and as your backups seems to be mostly working it's worth a look.

Steve

[manatee]

i saw that hunged process. the restore was fine alright (last full backup).

will monitor this.