Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SQL bch script error

Status
Not open for further replies.

joenok

MIS
Feb 27, 2002
49
US
I tried to manually run a sql script I created using the GUI on the sql server itself. I used the "Netbackup MS SQL Client" on the sql server and used the GUI to create a script. I used the Actions - Database Files and FileGroups" I drilled down to find the sql db and expanded it and selected "PRIMARY" tab'd over selected the file for backup. specified my corresponding policy in Backup attributes on bottom left corner - did save for later execution, then went back to my server and added the script to the policy and got this error "none of the requested files were backed up(2)" when I tried to do a manual backup.

thanks for any help.
 
Did you specify the correct user to access the database and did you check the users ability to access the databases?? Try this from the SQL server admin screen. Also did you use the Veritas client GUI to specify the correct user to Netbackup to use. We use a user of netbackup with full SA privileges.

To test the netbackup user’s ability to access the databases, select Tools from the menu and then select SQL Query Analyzer. Disconnect any existing user which is done by selecting File, Disconnect from the menu. To test the new netbackup user connection Select File, Connect and enter the server name in the SQL Server field. Select SQL Server Authentication and enter the netbackup user name and password in the appropriate fields. Click on OK and the query window will display if a valid connection is obtained. Close the query window and close the SQL Enterprise Manager Window.
 
we checked the sa password in odbc and tested successfully, also verified sa & password in the netbackup gui on the client under "set dbms login parameters"

???

 
You also created a policy with the MS-SQL policy type which creates the default-application-backup schedule, ensured that its policy type was application, and opened the start window on the default application schedule to 24x7?
 
I just ran into a similar issue and managed to solve it by running the Veritas NetBackup client as an account that has domain admin priv. It may be worth a shot.
 
My solution to this ... Set up an administrator account on the server. Have the NetBackup services run under this account. Have the same account set up as a full administrator in the SQL databases. Log on as that user and set up an ODBC user connection for SQL.

This works like a charm.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top