cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Cluster 2012 backup Falied

ALMARID
Level 2

Hello,

I teried to configure new online backup for SQL cluster 2012.  Netbackup version is 7.6.1running on window server 2008 R2.

we have SQL cluster vertiual name MSQL , NODE01 named MSQL01 , NODE02 named MSQL02

I configure following script 

OPERATION BACKUP
DATABASE $ALL
SQLHOST "MSQL"
INSTANCE "MSQL"
BROWSECLIENT "MSQL"
NBSERVER "MASTER.domain.local"
#STRIPES 3
MAXTRANSFERSIZE 6
BLOCKSIZE 7
OBJECTTYPE TRXLOG
NUMBUFS 2
ENDOPER TRUE

 

 when I run the backup I got following 

08/12/2016 1:27:46 PM - Info nbjm(pid=8056) starting backup job (jobid=120725) for client MSQL, policy MSQL_Full, schedule Full
08/12/2016 1:27:46 PM - Info nbjm(pid=8056) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=120725, request id:{07BF0CDF-F2B3-4509-9037-1385E74C39BC})
08/12/2016 1:27:46 PM - requesting resource NBU_DP01_STU01
08/12/2016 1:27:46 PM - requesting resource MASTER.NBU_CLIENT.MAXJOBS.MSQL
08/12/2016 1:27:46 PM - requesting resource MASTER.NBU_POLICY.MAXJOBS.MSQL_Full
08/12/2016 1:27:46 PM - granted resource MASTER.NBU_CLIENT.MAXJOBS.MSQL
08/12/2016 1:27:46 PM - granted resource MASTER.NBU_POLICY.MAXJOBS.MSQL_Full
08/12/2016 1:27:46 PM - granted resource NBU_DP01_STU01
08/12/2016 1:27:47 PM - estimated 0 Kbytes needed
08/12/2016 1:27:47 PM - Info nbjm(pid=8056) started backup (backupid=MSQL_1481189266) job for client MSQL, policy MSQL_Full, schedule Full on storage unit NBU_DP01_STU01
08/12/2016 1:27:47 PM - started process bpbrm (13552)
08/12/2016 1:27:49 PM - Info bpbrm(pid=13552) MSQL is the host to backup data from
08/12/2016 1:27:49 PM - Info bpbrm(pid=13552) reading file list for client
08/12/2016 1:27:49 PM - connecting
08/12/2016 1:27:51 PM - Info bpbrm(pid=13552) starting bphdb on client
08/12/2016 1:27:51 PM - connected; connect time: 0:00:02
08/12/2016 1:27:52 PM - Info bphdb(pid=7228) Backup started
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) INF - BACKUP STARTED USING
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) Microsoft SQL Server 2012 (SP3-GDR) (KB3194721) - 11.0.6248.0 (X64)
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) Sep 23 2016 15:49:43
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) Copyright (c) Microsoft Corporation
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Full_SQL_DB.bch, Op# = 1
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) INF - Using backup image MSQL02.MSSQL7.MSQL.trx.ADManager.~.7.001of001.20161208132753..C
08/12/2016 1:27:54 PM - Info dbclient(pid=7172) INF - backup log "ADManager" to VIRTUAL_DEVICE='VNBU0-7172-3636-1481189275' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
08/12/2016 1:27:55 PM - Info dbclient(pid=7172) INF - Number of stripes: 1, Number of buffers per stripe 2.
08/12/2016 1:27:57 PM - Info dbclient(pid=7172) ERR - Error in CreateEx: 0x80770007.
08/12/2016 1:27:57 PM - Info dbclient(pid=7172) CONTINUATION: - Failed to recognize the SQL Server instance name.

with following error 

 

08/12/2016 1:27:57 PM - Info dbclient(pid=7172) ERR - Error in CreateEx: 0x80770007.
08/12/2016 1:27:57 PM - Info dbclient(pid=7172) CONTINUATION: - Failed to recognize the SQL Server instance name.

 

thank you and waiting your support

Ibra

Regards

3 REPLIES 3

Mystre316
Level 4

Have you setup an app_cluster on your master server for the sql cluster?

Michal_Mikulik1
Moderator
Moderator
Partner    VIP    Accredited Certified

Hello,

try to omit SQLINSTANCE row in your script. Because in default installation first SQL Instance on a physical/virtual server does not have its own name and can be referred just with SQLHOST parameter.

If it wont work, check with yout dba what is the proper name for the instance. Check Windows Services on the nodes for the name MSSQLSERVER("INSTANCE NAME").

Regards

Michal

manatee
Level 6

did you configure first the NBU sql agent?