SQL Backups Error in VxBSACreateObject: 3

Hi All,

I'm attempting to backup several instances of an SQL server running on one host.

I created a domain user, and have given that user sysadmin permissions on each instance of SQL.

I've also changed the NB Client on that host to run as that domain user. Each instance should be running in SQL Server and Authentication mode.
 

From the SQL client on the host, I've been able to run a backup.

If I try running a scheduled job from the Master server though I get several child jobs created (each DB I think), but they all fail. The master job contains this in its log:

5/08/2011 11:23:46 - Info dbclient(pid=9944) Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)    
25/08/2011 11:23:46 - Info dbclient(pid=9944) Apr  2 2010 15:48:46        
25/08/2011 11:23:46 - Info dbclient(pid=9944) Copyright (c) Microsoft Corporation         
25/08/2011 11:23:46 - Info dbclient(pid=9944) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: )  
25/08/2011 11:23:46 - Info dbclient(pid=9944) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\mycompany-serv15_MRP_Full_Simple.bch, Op# = 1      
25/08/2011 11:23:46 - Info dbclient(pid=9944) INF - Using backup image mycompany-SERV15.MSSQL7.mycompany-SERV15\MRP_INSTANCE.db.123MRP.~.7.001of001.20110825112345..C       
25/08/2011 11:23:46 - Info dbclient(pid=9944) INF - backup database "123MRP" to VIRTUAL_DEVICE='VNBU0-9944-5236-1314267826' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
25/08/2011 11:23:46 - Info dbclient(pid=9944) INF - Number of stripes: 1, Number of buffers per stripe 2.
25/08/2011 11:23:47 - Info dbclient(pid=9944) INF - Created VDI object for SQL Server instance <MRP_INSTANCE>. Connection timeout is <300> seconds.
25/08/2011 11:23:59 - Info dbclient(pid=9944) ERR - Error in VxBSACreateObject: 3.       
25/08/2011 11:23:59 - Info dbclient(pid=9944)     CONTINUATION: - System detected error, operation aborted.  
25/08/2011 11:23:59 - Info dbclient(pid=9944) ERR - Error in GetCommand: 0x80770004.       
25/08/2011 11:23:59 - Info dbclient(pid=9944)     CONTINUATION: - An abort request is preventing anything except termination actions.
25/08/2011 11:24:04 - Info dbclient(pid=9944) ERR - Error in VDS->Close: 0x80770004.  

In the dbclient log I see references that suggest its trying to use the sa password:

11:04:14.173 [7588.3868] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_7588_3868_4>, SQL userid <sa> handle <0x00faab40>.
11:04:14.188 [7588.3868] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <mycompany-SERV15\MRP_INSTANCE> has been made using standard security with DSN <NBMSSQL_temp_7588_3868_4>
11:04:14.188 [7588.3868] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x00faab40>
11:04:14.188 [7588.3868] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_7588_3868_4>, SQL userid <sa> handle <0x00faab40>.
11:04:14.251 [7588.3868] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x00faab40>
11:04:17.511 [7588.3868] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7588_3868_5>, SQL userid <sa> handle <0x00faab40>.
11:04:17.511 [7588.3868] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <mycompany-SERV15\MRP_INSTANCE> has been made using standard security with DSN <NBMSSQL_7588_3868_5>
11:04:17.511 [7588.3868] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x00faab40>
11:04:17.511 [7588.3868] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7588_3868_5>, SQL userid <sa> handle <0x00faab40>.
11:04:18.712 [7588.3868] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x00faab40>

I've tried specifying a domain username and password in the bch file. I then see that user being used (connecting successfully), and get the same result.

Either method, I eventually get an error:

11:13:42.668 [7992.7940] <2> logconnections: BPRD CONNECT FROM 192.168.50.4.61650 TO 192.168.50.250.1556 fd = 1220
11:13:47.738 [7992.7940] <16> serverResponse: ERR - server exited with status 199: operation not allowed during this time period
11:13:47.738 [7992.7940] <16> CreateNewImage: ERR - serverResponse() failed

I'm going to simplify the script down to just trying the master database, but which is the right auth mechanism to use???

I had thought that putting the Service to running as the domain user meant it would authenticate as that user, but, from the first log suggests its still using SA (but I've not specified an SA password anywhere, so I'm not sure how!).

Which is the right way to do it ?

4 Replies

Mmmm... ok I simplified the

Mmmm... ok I simplified the backup job, and its now also failing when run from the client too. I've attached the dbclient log.

 

I don't really understand why there are "file not found" messages - what path ??

I think I understand that it is authenticating ok, as my Domain user (thats the DSN reference right ?).

So - my best guess is that its authing ok, looking for some file, failing, and then timining out ?

I'll try re-creating the Policy again

I should add this is

I should add this is Netbackup 7.1

Sigh... never mind... I think

Sigh... never mind... I think I found my problem.. I think it was something to do with the Start Window timeframe in the policy.

sql backup

Error : server exited with status 199: operation not allowed during this time period

You need to open the Default Application Backup Schedule in the sql policy on the master during the time you run the backup. By default this is 24/7.

If the backup works from the client and fails when you try to kick it off from the master, try to change the netbackup client service to run in a local administrator with sysadmin rights in sql. You can use the same account that you logged in as when you successfully did a backup from the client.

/Oddy