Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Could not backup SQL "instance not found"

Created: 24 Oct 2013 • Updated: 06 Nov 2013 | 7 comments
NewB's picture
This issue has been solved. See solution.

Good day Everyone!

Before I start, i'd like to point out that i am new to NetBackup. And our company wants to backup there microsoft SQL database as a client(w/c i have no background with). the OS of the SQL server is windows 2012, which i have upgraded already from NetBackup 7.5 to 7.5.0.6 version for both Master Server (OS is RHEL 6) and Media Server (OS is RHEL 6) as well as for the client (OS is windows 2012). i already followed this technote http://www.symantec.com/business/support/index?pag... but when i tried to backup the SQL database i get the following error.

 

10/25/2013 11:59:45 - Info nbjm (pid=24811) starting backup job (jobid=417) for client wsus2012, policy wsus2012_SQL, schedule Automatic
10/25/2013 11:59:45 - Info nbjm (pid=24811) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=417, request id:{E25A979E-3D29-11E3-83F8-403D5966ED08})
10/25/2013 11:59:45 - requesting resource NBmedia_storage
10/25/2013 11:59:45 - requesting resource NBU.NBU_CLIENT.MAXJOBS.wsus2012
10/25/2013 11:59:45 - requesting resource NBU.NBU_POLICY.MAXJOBS.wsus2012_SQL
10/25/2013 11:59:45 - granted resource  NBU.NBU_CLIENT.MAXJOBS.wsus2012
10/25/2013 11:59:45 - granted resource  NBU.NBU_POLICY.MAXJOBS.wsus2012_SQL
10/25/2013 11:59:45 - granted resource  NBmedia_storage
10/25/2013 11:59:45 - estimated 0 kbytes needed
10/25/2013 11:59:45 - Info nbjm (pid=24811) started backup (backupid=wsus2012_1382673585) job for client wsus2012, policy wsus2012_SQL, schedule Automatic on storage unit NBmedia_storage
10/25/2013 11:59:46 - started process bpbrm (pid=10295)
10/25/2013 12:00:48 - Info bpbrm (pid=10295) wsus2012 is the host to backup data from
10/25/2013 12:00:48 - Info bpbrm (pid=10295) reading file list from client
10/25/2013 12:00:08 - connecting
10/25/2013 12:01:09 - Info bpbrm (pid=10295) starting bphdb on client
10/25/2013 12:01:09 - Info bphdb (pid=14064) Backup started
10/25/2013 12:00:29 - Info dbclient (pid=18040)     CONTINUATION: - The system cannot find the file specified.
10/25/2013 12:00:29 - Info dbclient (pid=18040)     CONTINUATION: - The system cannot find the file specified.
10/25/2013 12:00:29 - Info dbclient (pid=18040) USER - An instance of SQL Server was not found on this client.
10/25/2013 12:00:29 - Info dbclient (pid=18040) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\allSQL.bch>: 
10/25/2013 12:00:29 - Info dbclient (pid=18040) <0> operations succeeded. <0> operations failed.
10/25/2013 12:00:28 - connected; connect time: 0:00:00
10/25/2013 12:01:30 - Error bpbrm (pid=10295) from client wsus2012: ERR - command failed: none of the requested files were backed up (2)
10/25/2013 12:01:30 - Error bpbrm (pid=10295) from client wsus2012: ERR - bphdb exit status = 2: none of the requested files were backed up
10/25/2013 12:01:30 - Info bphdb (pid=14064) done. status: 2: none of the requested files were backed up
10/25/2013 12:00:50 - end writing
none of the requested files were backed up  (2)
 
 
Is there something i need to do on the database side or did i miss something in netbackup configuration? i'm guessing it has something to do with the database configuration since it is saying "instance of SQL server was not found".
 
Hoping for you kind response.
 
 
Regards,
Bapi
 
Operating Systems:

Comments 7 CommentsJump to latest comment

Marianne's picture

Please show us screenshots of your steps (similar to the TN).

Did you choose to create a script? If so, please show us the contents of the script.

Have you changed NetBackup Client Service logon account as per the TN under 'Related articles' in the link you have found?

Please also show us the policy that you have created on the master server:

bppllist <policy-name> -U
(command is in /usr/openv/netbackup/bin/admincmd)

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

NewB's picture

 Here is the script that was generated:

# This batch file was created for an operation on host <\\.\PIPE\MICROSOFT##WID\TSQL\QUERY> using
# the SQL Server instance <default> .
# Save this file to the Veritas\NetBackup\dbext\MSSQL\ directory
# on host <\\.\PIPE\MICROSOFT##WID\TSQL\QUERY>. Execute it there using the NetBackup
# Database extension graphical user interface or the NetBackup scheduler.
OPERATION BACKUP
DATABASE "SUSDB"
SQLHOST "\\.\PIPE\MICROSOFT##WID\TSQL\QUERY"
NBSERVER "NBU"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
BROWSECLIENT "\\.\PIPE\MICROSOFT##WID\TSQL\QUERY"
NUMBUFS 2
ENDOPER TRUE
 
Here is the policy of the master server:
 
Policy Name:       wsus2012_sql
Policy Type:         MS-SQL-Server
Active:              yes
Effective date:      10/23/2013 11:38:28
Mult. Data Streams:  no
Client Encrypt:      no
Checkpoint:          no
Policy Priority:     0
Max Jobs/Policy:     Unlimited
Disaster Recovery:   0
Collect BMR info:    no
Residence:           NBmedia_storage
Volume Pool:         NetBackup
Server Group:        *ANY*
Keyword:             (none specified)
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Application Discovery:      no
Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)
 
Granular Restore Info:  no
Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  no
HW/OS/Client:  Windows-x64   Windows2008   wsus2012
 
Include:  C:\Program Files\Veritas\NetBackup\DbExt\MsSql\allSQL.bch
 
Schedule:              Automatic_Backup
Type:                Automatic Backup
Frequency:           every 7 days
Synthetic:           0
Checksum Change Detection: 0
PFI Recovery:        0
Retention Level:     3 (1 month)
Residence is Storage Lifecycle Policy:         0
Schedule indexing:     0
Daily Windows:
 Sunday     00:00:00  -->  Sunday     24:00:00
 Monday     00:00:00  -->  Monday     24:00:00
 Tuesday    00:00:00  -->  Tuesday    24:00:00
 Wednesday  00:00:00  -->  Wednesday  24:00:00
 Thursday   00:00:00  -->  Thursday   24:00:00
 Friday     00:00:00  -->  Friday     24:00:00
 Saturday   00:00:00  -->  Saturday   24:00:00
 
And if i may add i found this error logs on the mssql_backup_failures:
 
TIMESTAMP 20131024171126
MASTERSERVER NBU
CLIENT wsus2012
INSTANCE \\.\PIPE\MICROSOFT##WID\TSQL\QUERY
DATABASE master
OPERATION BACKUP
OBJECTTYPE DATABASE
STATUS -1
INFO Error in CreateEx: 0x80770007.
INFO Failed to recognize the SQL Server instance name.
ENDOPER TRUE
TIMESTAMP 20131024171222
MASTERSERVER NBU
CLIENT wsus2012
INSTANCE \\.\PIPE\MICROSOFT##WID\TSQL\QUERY
DATABASE model
OPERATION BACKUP
OBJECTTYPE DATABASE
STATUS -1
INFO Error in CreateEx: 0x80770007.
INFO Failed to recognize the SQL Server instance name.
ENDOPER TRUE
TIMESTAMP 20131024171318
MASTERSERVER NBU
CLIENT wsus2012
INSTANCE \\.\PIPE\MICROSOFT##WID\TSQL\QUERY
DATABASE msdb
OPERATION BACKUP
OBJECTTYPE DATABASE
STATUS -1
INFO Error in CreateEx: 0x80770007.
INFO Failed to recognize the SQL Server instance name.
ENDOPER TRUE
TIMESTAMP 20131024171415
MASTERSERVER NBU
CLIENT wsus2012
INSTANCE \\.\PIPE\MICROSOFT##WID\TSQL\QUERY
DATABASE SUSDB
OPERATION BACKUP
OBJECTTYPE DATABASE
STATUS -1
INFO Error in CreateEx: 0x80770007.
INFO Failed to recognize the SQL Server instance name.
ENDOPER TRUE
 
Thanks for the response Marianne i really appreciate it a lot. 
 
Regards,
Bapi
 
 
D@ry1's picture

Hi NewB,

I read the logs and found out that the problem is because your computer chair is too low.

Thanks,

Marianne's picture

This is wrong:

SQLHOST "\\.\PIPE\MICROSOFT##WID\TSQL\QUERY" 
BROWSECLIENT  "\\.\PIPE\MICROSOFT##WID\TSQL\QUERY"

 I am curious to know why this machine is reporting its own hostname as  \\.\PIPE\MICROSOFT##WID\TSQL\QUERY ???? 

Show this to SQL dba - maybe he/she will be able to tell you why?

Entry should match hostname. 
If I look at your policy. it should be wsus2012.

So, replace with these lines:

SQLHOST WSUS2012

BROWSECLIENT WSUS2012 

Also add a line in the script with the correct instance name.

INSTANCE <NAME>

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Will Restore's picture

That's an odd sqlhost name so I did a search and found this:

http://en.wikipedia.org/wiki/Windows_Internal_Data...

SQL Server Management Studio Express can be used to connect to an instance of Windows Internal Database using \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query (2003-2008) or \\.\pipe\MICROSOFT##WID\tsql\query (2012) as instance name. But this will only work locally, as Remote Connections cannot be enabled for this edition of SQL Server.

 

As Marianne says you need to replace that string with the actual hostname that is recognized over the network.

( SQLINSTANCE keyword can be omitted in which case it points to the default instance. )

 

Will Restore -- where there is a Will there is a way

NewB's picture

Hi Guys,

I aplogize for not getting back to you guys soon enough, but i follow the lead you've given me and asked the DBA regarding this matter. And I found out that Windows Server Update Services (WSUS) has an embedded Windows Internal Database which can be access through the SQL Management Studio. that's the reason why the hostname looks like this "\\.\PIPE\MICROSOFT##WID\TSQL\QUERY" and not "WSUS2012" i guess this is more of an embedded configuration issue rather than NetBackup. Anyways, I am very grateful for the both of you for giving me some leads regarding this matter. Thanks you so much.

 

Regards,

Bapi

Marianne's picture

If your issue is solved, please mark the post that helped you most as Solution?

If more than one post helped you, select 'Request split solution' and select al helpful posts.

This will help other users with similar issues.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links