Forum Discussion
Hi,
On the client, are you able to connect on NetBackup MS SQL Client and see the SQL instance?
Try to log on the client with account that you should config on Netbackup services, and open the SQL Server Management Studio, it can be a test.
Check this article, this is a problem similar to your.
Regards,
Thiago
Yes, I am able to connect on NetBackup MS SQL Client and see the SQL instances.
The Netbackup services use a "local system account"
- Thiago_Ribeiro7 years agoModerator
Hi,
Are you using SQL Intelligent Policy or Legacy configuration? Can you check this information about Local System acconunt?
NetBackup uses the NetBackup Client Service and the NetBackup Legacy Network Service to access the SQL Server when it performs backups and restores. With the proper configuration, these services can log on with the Local System account or another account that has the necessary privileges.
The logon account for the services requires the following:
- Both services must use the same logon account.
- The SQL Server “sysadmin” role.
- If you want to use Local System for the logon account, the requirements depend on the SQL Server version:
- For SQL Server 2008, the sysadmin role is automatically applied to the NT AUTHORITY\SYSTEM and BUILTIN\Administrators groups.
- For SQL Server 2012 and later, you must first apply the sysadmin role manually to the NT AUTHORITY\SYSTEM or the BUILTIN\Administrators group.
- For a SQL Server cluster or SQL Server availability group (AG), configure the NetBackup services on each node in the cluster or AG.
- For VMware backups, different configuration is required for logon account for the services.
For more informations about NetBackup services see https://www.veritas.com/support/en_US/article.000029885
Regards,
Thiago
- Marianne7 years agoLevel 6When the SQL dba runs the backup from the SQL client, they login with sufficient SQL rights. Right?
Ask the dba to change NBU Client service account to a SQL account with sufficient rights. Preferrably same service account as SQL services.- perez_cmz7 years agoLevel 6
Found the issue
For some reason, this particular bch file was missing "SQLINSTANCE $ALL"
Once I added this line into the bch file, the backup ran and completed successfully
- Thiago_Ribeiro7 years agoModerator
Hi,
Is it possible that someone has changed this .bch script? Did you check the last changed?