Solved: Not using sa userid for Sql backups

NBdmecha · ‎11-26-2013

Hi all,

first of all I want to let you know that our sql backups are working properly, but we would like to know if we can make netbackup to use another user different from "sa".

Here you can see the dbclient log of one of our backups launched today:

Microsoft SQL Server 2008 R2 (SP2) - 10.50.4290.0 (X64)

Aug 5 2013 12:40:54

Copyright (c) Microsoft Corporation

Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

Batch = C:\Program files\VERITAS\NetBackup\DbExt\MsSql\TALOS60_PruebaServicio.bch, Op# = 1
13:12:48.991 [24544.24476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:12:48.991 [24544.24476] <2> logconnections: BPRD CONNECT FROM 10.8.141.81.51272 TO 10.8.140.190.1556 fd = 1128
13:12:49.054 [24544.24476] <4> InitPipeInfo: INF - Using backup image SERVIDOR.MSSQL7.TALOS60\SGBDR06.db.HPOO_Orchestration.~.7.001of001.20131126131247..C
13:12:49.054 [24544.24476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:12:49.054 [24544.24476] <2> logconnections: BPRD CONNECT FROM 10.8.141.81.51273 TO 10.8.140.190.1556 fd = 1132
13:12:49.116 [24544.24476] <4> Dbbackrec::CreateSQLcmdSyntax: INF - backup database "HPOO_Orchestration" to VIRTUAL_DEVICE='VNBU0-24544-24476-1385467969' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 1
13:12:49.132 [24544.24476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:12:49.132 [24544.24476] <2> logconnections: BPRD CONNECT FROM 10.8.141.81.51274 TO 10.8.140.190.1556 fd = 1152
13:12:49.132 [24544.24964] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:12:49.132 [24544.24964] <2> logconnections: BPRD CONNECT FROM 10.8.141.81.51275 TO 10.8.140.190.1556 fd = 1180
13:12:49.178 [24544.24476] <4> Dbbackrec::CreateSQLcmdSyntax: INF - Number of stripes: 1, Number of buffers per stripe 1.
13:12:49.210 [24544.24476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:12:49.210 [24544.24476] <2> logconnections: BPRD CONNECT FROM 10.8.141.81.51276 TO 10.8.140.190.1556 fd = 1184
13:12:49.272 [24544.24476] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_24544_13616_1>, SQL userid <sa> handle <0x005fb8c0>.
13:12:49.319 [24544.24476] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <INSTANCE>. Connection timeout is <300> seconds.
1292

as you can see there´s a "SQL userid <sa>" being used. We have changed the NetBackup Client Service Log On account, also the properties in the NetBackup MS SQL Client but we don´t see any change (rebooting client services after changes). Looking into windows registry, there are connection parameters by default for another instance in the same server which have no reference to "sa".

Is there any possible way to change this connection settings and so being able to not use "sa"?

Thanks in advance.

Mark_Solutions · ‎11-27-2013

If using a standard windows account then there are four things to do once you have ensured that account has dbadmin rights to all databases

1. Make that user a local admin on the SQL Server

2. Set the credentials using the NBU agent GUI (while actually logged in as that account)

3. Set the NetBackup Client service account to use that account

4. Set the NetBackup Legacy Network Service to use that account

That should do the trick - see if this helps

View solution in original post

Will_Restore · ‎11-26-2013

in your NetBackup for MS-SQL batch file (located in NetBackup\DbExt\MsSql\ folder) specify

userid (User ID for logging into SQL Server)

example from the Admin Guide:

OPERATION BACKUP
DATABASE "BUSINESS"
SQLHOST "CADOO"
SQLINSTANCE "SECOND"
NBSERVER "CHISEL"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
USERID JSMITH
PASSWORD my.Pwd
ENDOPER TRUE

NBdmecha · ‎11-27-2013

Thanks wr. We are using mixed or integrated security, and the solution you suggest only applies to Standard security.

Mark_Solutions · ‎11-27-2013