08-30-2017 07:29 AM
I have clients with identical specs backing up successfully. These are the details for the last failed job
08/30/2017 10:08:08 - Info nbjm (pid=9633) starting backup job (jobid=245727589) for client server123, policy US_NYK_SQL_D_PREL_DB_EOM, schedule EOM_25Y
08/30/2017 10:08:08 - Info nbjm (pid=9633) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=245727589, request id:{A62BF40E-8D8C-11E7-8AC6-FF512A32749A})
08/30/2017 10:08:08 - requesting resource US_NYK_NWFDD01_LSU01_MS1
08/30/2017 10:08:08 - requesting resource master123.NBU_CLIENT.MAXJOBS.server123
08/30/2017 10:08:08 - requesting resource master123.NBU_POLICY.MAXJOBS.US_NYK_SQL_D_PREL_DB_EOM
08/30/2017 10:08:08 - granted resource master123.NBU_CLIENT.MAXJOBS.server123
08/30/2017 10:08:08 - granted resource master123.NBU_POLICY.MAXJOBS.US_NYK_SQL_D_PREL_DB_EOM
08/30/2017 10:08:08 - granted resource US_NYK_NWFDD01_LSU01_MS1
08/30/2017 10:08:08 - estimated 0 kbytes needed
08/30/2017 10:08:08 - Info nbjm (pid=9633) started backup (backupid=server123_1504102088) job for client server123, policy US_NYK_SQL_D_PREL_DB_EOM, schedule EOM_25Y on storage unit US_NYK_NWFDD01_LSU01_MS1
08/30/2017 10:08:11 - started process bpbrm (pid=40353)
08/30/2017 10:08:12 - Info bpbrm (pid=40353) server123 is the host to backup data from
08/30/2017 10:08:13 - Info bpbrm (pid=40353) reading file list for client
08/30/2017 10:08:13 - connecting
08/30/2017 10:08:15 - Info bpbrm (pid=40353) starting bphdb on client
08/30/2017 10:08:15 - connected; connect time: 0:00:00
08/30/2017 10:08:15 - Info bphdb (pid=12444) Backup started
08/30/2017 10:08:51 - Info dbclient (pid=5016) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][SQL Server Native Client 11.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. >.
08/30/2017 10:08:52 - Info dbclient (pid=5016) DBMS MSG - SQL Message <2><[Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
08/30/2017 10:08:52 - Info dbclient (pid=5016) DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 11.0]Login timeout expired>
08/30/2017 10:09:28 - Info dbclient (pid=5016) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][ODBC Driver 11 for SQL Server]Named Pipes Provider: Could not open a connection to SQL Server [2]. >.
08/30/2017 10:09:28 - Info dbclient (pid=5016) DBMS MSG - SQL Message <2><[Microsoft][ODBC Driver 11 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.>
08/30/2017 10:09:28 - Info dbclient (pid=5016) DBMS MSG - SQL Message <0><[Microsoft][ODBC Driver 11 for SQL Server]Login timeout expired>
08/30/2017 10:10:02 - Info dbclient (pid=5016) DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <17><[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.>.
08/30/2017 10:10:02 - Info dbclient (pid=5016) DBMS MSG - SQL Message <2><[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).>
08/30/2017 10:10:03 - Info dbclient (pid=5016) INF - Results of executing <D:\Apps\VERITAS\NetBackup\DbExt\MsSql\mssqldb.bch>:
08/30/2017 10:10:03 - Info dbclient (pid=5016) <0> operations succeeded. <0> operations failed.
08/30/2017 10:10:23 - Error bpbrm (pid=40353) from client server123: ERR - command failed: none of the requested files were backed up (2)
08/30/2017 10:10:23 - Error bpbrm (pid=40353) from client server123: ERR - bphdb exit status = 2: none of the requested files were backed up
08/30/2017 10:10:25 - Info bphdb (pid=12444) done. status: 2: none of the requested files were backed up
08/30/2017 10:10:25 - end writing
none of the requested files were backed up (2)
Solved! Go to Solution.
08-30-2017 11:31 AM
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
08-30-2017 07:53 AM
You need to find out from SQL server owner and dba what is wrong.
Show them this:
Could not open a connection to SQL Server
DBMS MSG - SQL Message <2><[Microsoft][ODBC Driver 11 for SQL Server]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections.
08-30-2017 08:06 AM
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
08-30-2017 10:51 AM
I've been working with them, and they're able to successfully run a backup from the Netbackup SQL client. Netbackup Windows backup is successful also
08-30-2017 10:54 AM
Yes, I am able to connect on NetBackup MS SQL Client and see the SQL instances.
The Netbackup services use a "local system account"
08-30-2017 11:03 AM
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:
For more informations about NetBackup services see https://www.veritas.com/support/en_US/article.000029885
Regards,
Thiago
08-30-2017 11:04 AM
08-30-2017 11:31 AM
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
08-30-2017 11:48 AM
Hi,
Is it possible that someone has changed this .bch script? Did you check the last changed?
08-30-2017 12:40 PM
This was a newly deployed server