Netbackup SQL Agent - Server 2008 R2

[Taztopher]

We have a new 2008 R2 server with SQL 2008 and Netbackup 6.5.6 client installed. The master server is Redhat Linux 5.5.

When I login as Administrator I can run the command:

C:\Program Files\Veritas\NetBackup\bin

dbbackex -f "C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rskt_ironsand_bkup.bch" -p SQL-DB-RSKD-IS-FULL –np

It runs fine.

When it’s run from the server policy it errors (error 29) on the policy and the log shows:

Error <5> encountered trying to open <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rskd_ironsand_bkup.bch>

This also happens when a user in the local Administrator group runs the command locally. Is this something to do with the UAC on 2008 R2? Even though its at the lowest setting? How can you completely turn it of (no right click run as admin) ?

Any ideas? The Netbackup services run as System, and  SQL as sa

A local admin account for the service doesn’t work either, even if that account is the owner and had full control of C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rskd_ironsand_bkup.bch

[Marianne]

Check NetBackup Client Service logon account.

Verify that the Service is running with sufficient priveleges.

[Taztopher]

Hi Marianne

The service account is running as system. Any accoutn I try still gets the error.

penParmFile: ERR - Failed trying to get read access to C:\Program Files\Veritas\NetBackup\DbExt\MsSql\rskt_ironsand_bkup.bch

Must be UAC or some odd secuirty.

Regards,

Mark Tarry

[jim_dalton]

im fairly sure 2008r2 + sql 2008 is supported 701 onwards...possibly even 71...which would make you down rev.

Im on 71 and indeed it works just fine.

Check the compat list first.

Jim

[Taztopher]

Hi Jim

Thanks for your post.

It works / is compatible with 6.5.6, in fact this did work to begin with.

[Oddy]

You get status 29 normally if the path is wrong or the batch script is not readable.

Change the netbackup client service to run in the same account you were logged in as when you succesfully started the script using dbbackex.exe.

Create a new batch script using the Netbackup MSSQL databse gui on the client and create a new sql policy and use the browse option  in the policy to specify the path to sql batch script.

Create following log directories on the sql server to troubleshooting,

<install dir>\netbackup\logs\bpcd
<install dir>\netbackup\logs\bphdb
<install dir>\netbackup\logs\dbclient

Increase the logging level on the sql server, open the Backup Archive and Restore window and go to File, Netbackup Client Properties, Troubleshooting, change General to 2, Verbose to 5 and Databaset to 9.

Also try to copy the script to another folder without any spaces and run the backup and check the logs created in above folders for failures.

/Oddy