cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup client triggered scripts wont initiate

James_D80
Level 3

Hi Everyone,

 

I wonder if anyone has come across this before, I've recently setup a new client (virtual machine, server 2008 R2, SQL server 2008 R2) and installed netbackup 6.5.6 (and tested 7.1.0.2) the issue I'm having is that when creating a script and triggering it on the client (sql agent) it doesn't run, theres nothing in any logs to indicate as to why.

If I trigger the same script from the master server in a policy it runs without issue.

I've tried running netbackup client services as locally system and backup (domain admin)

I've tried netbackup 6.5.6, 7.1, 7.1.0.1 and 7.1.0.2 and several re-installs.

All to no avail and I'm at a total loss as to where to look now.

Any advice anyone can offer would be much appreciated.

Thanks

James

9 REPLIES 9

Mark_Solutions
Level 6
Partner Accredited Certified

Were you logged in as the backup account when you tried to run the script?

Any logs should go to \netbackup\logs\user_ops\mssql\logs\ or to \netbackup\log\mssql_backup_failures\

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you tried to right-click, Run as Administrator?

UAC on W2008 causes all sorts of weird and wonderful headaches....

James_D80
Level 3

Cheers Chaps,

Yes I login as the backup user, I've also logged in as myself (enterprise admin) to no avail,

UAC is disabled as is the firewall, we've even re-enabled then disabled the firewall to make sure as I know sometimes when you change a nic it can creep back in.

Nothing gets logged in \netbackup\logs\user_ops\mssql\logs\ which is the odd thing, its like the click in the GUI is totally unacknowledged.

 

To add a bit more detail, what happens, sql agent gui open, click, file, manage script files, double click on script, box pops up "start batch file" click yes, ack pops up "a netbackup for microsoft sql server operation has been launched" but nothing happens, check view status theres no operation, and nothing appears to be logged,

in logs\nbconsole, a blank file is created with the date thats it.

Doing the same starting the sql agent with run as admin makes no difference either.

I'm so confused with this and dont know where to start.

 

Thanks again

James

Mark_Solutions
Level 6
Partner Accredited Certified

Just to be sure could you post the text in the script that you are using on here please

Thanks

Mark_Solutions
Level 6
Partner Accredited Certified

#edited#

two other points - are the bch files in the default directory? (\veritas\netbackup\dbext\mssql)

is there only one SQL instance on the client?

confirm that and paste the script and i will see if i can spot anything

James_D80
Level 3

Hi Mark,

 

Thanks for the response, apologies for the delay a good long holiday over Christmas.

the batchfile is located in the default folder C:\Program Files\Veritas\NetBackup\DbExt\MsSql and is constructed as below.

I've tried it without the browseclient too.

OPERATION BACKUP
DATABASE "EMISState"
SQLHOST "NBU-RESTORE-3"
SQLINSTANCE "NBURESTORE3"
NBSERVER "NBU-MASTER-3-BK"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
BROWSECLIENT "nbu-restore-3-bk"
NUMBUFS 2
ENDOPER TRUE

I'm going to do a SQL compare today of one of the other restore servers and see if something has been setup wrong, it just strikes me to be a permissions thing or odbc between netbackup and SQL

Thanks again

James

James_D80
Level 3

I've been profiling SQL and poking arround a bit more, I've set trace and logging to max debug levels and saw this in the dbclient log.

 

13:38:31.010 [3392.3276] <2> vnet_pbxConnect: pbxConnectEx Succeeded
13:38:31.010 [3392.3276] <2> logconnections: BPRD CONNECT FROM 100.x.x.x.55230 TO 100.x.x.x.1556 fd = 568
13:38:31.322 [3392.3276] <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed.
13:38:31.322 [3392.3276] <1> CGlobalInformation::VCSVirtualNameList:     CONTINUATION: - The system cannot find the path specified.
13:38:31.322 [3392.3276] <4> getServerName: Read server name from nb_master_config: nbu-master-3-bk
13:38:31.322 [3392.3276] <4> CDBIniParms::CDBIniParms: INF - NT User is james don
13:38:31.369 [3392.3276] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3392_3276_1>, SQLuserid <backup user> handle <0x010c9270>.
13:38:31.431 [3392.3276] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <NBU-RESTORE-3\NBURESTORE3> has been made using standard security with DSN <NBMSSQL_temp_3392_3276_1>
13:38:31.431 [3392.3276] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x010c9270>
13:38:31.431 [3392.3276] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3392_3276_1>, SQL userid <backup user> handle <0x010c9270>.
13:38:31.463 [3392.3276] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x010c9270>
13:38:41.276 [3392.3276] <4> StartupProcess: INF - Starting: <"C:\Program files\Veritas\NetBackup\bin\progress" MSSQL>
13:38:44.557 [3392.3276] <8> CDBbackupView::ClassDropDownList: WARN - Error: bppllist not found in C:\Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe.
13:38:44.557 [3392.3276] <1> CDBbackupView::ClassDropDownList:     CONTINUATION: - The system cannot find the path specified.
13:38:44.557 [3392.3276] <8> CBatchDlg::OnInitDialog: WARN - Policy Dropdown not created: Server = NBU-MASTER-3-BK Client = nbu-restore-3-bk
13:38:44.557 [3392.3276] <1> CBatchDlg::OnInitDialog:     CONTINUATION: - The system cannot find the path specified.
13:38:48.651 [3392.3276] <4> StartupProcess: INF - C:\Program Files\Veritas\NetBackup\bin\dbbackex" -u backup user -pw ***** -np -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\test2.bch" 
13:38:48.651 [3392.3276] <4> StartupProcess: INF - Starting: <C:\Program Files\Veritas\NetBackup\bin\dbbackex" -u backup user -pw ***** -np -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\test2.bch"  >

13:38:49.385 [3392.3276] <8> CDBbackupView::ClassDropDownList: WARN - Error: bppllist not found in C:\Program Files\Veritas\NetBackup\bin\admincmd\bppllist.exe.
13:38:49.385 [3392.3276] <1> CDBbackupView::ClassDropDownList:     CONTINUATION: - The system cannot find the path specified.
13:38:49.385 [3392.3276] <8> CBatchDlg::OnInitDialog: WARN - Policy Dropdown not created: Server = NBU-MASTER-3-BK Client = nbu-restore-3-bk
13:38:49.385 [3392.3276] <1> CBatchDlg::OnInitDialog:     CONTINUATION: - The system cannot find the path specified.

 

So the request to run the script is being triggered, SQL login on netbackup startup is also successful this is shown in the above log and SQL profiler, but the dbbackex -u backup user -pw ***** -np -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\test2.bch" isn't triggering the resulting processes for some reason, I've triggered this command from a cmd propmt as administrator but no process is triggered.

Again worth noting that this script works fine when triggered via the master server in a policy.

Regards

James

James_D80
Level 3

I've got some good news and an update,

I've finally managed to get the client working but it's more of a workround than a solution, it would appear netbackup will only work if I set the sql server connection properties userid as SA, the backup user we use is added in sql and has all the nessecary rights etc but it just doesn't work unless I've got SA as the userid.

I can replicate this and would be interested if anyone else can? this may be a bug or it may be caused by something else in my config but for now I have a workround, just not happy with it as in our environment SA is usually disabled for security.

 

Regards

James

Mark_Solutions
Level 6
Partner Accredited Certified

Thanks for the update and sorry not to get back to you earlier (long Christmas break followed by mayhem everywhere upon my return!)

My only though here is that it is a rights issue of somesort.

One test, based on you running this as as a user backup, is to set the NetBackup Client and the two legacy client service accounts to use the user account you have it initially setup as, ensure that account is a local admin on the SQL Server, re-set the connection back to the account and try again.

Most of what this does is done via User ODBC connections so it may be a rights issue that goes deeper than it looks.