Ms-sql backup does not creating correct child job

Question

Hello,
I am facing issue with MS-SQL backup.
I have created batch script as guided here . I have added the script in the policy. There is only two schedule in the policy one full and one application backup.
Here is the policy.
&nbsp;

Policy Name:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CTSDB_TEST
		
		&nbsp; Policy Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; MS-SQL-Server
		&nbsp; Active:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes
		&nbsp; Effective date:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 01/09/2014 05:08:09
		&nbsp; Mult. Data Streams:&nbsp; no
		&nbsp; Client Encrypt:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
		&nbsp; Checkpoint:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; no
		&nbsp; Policy Priority:&nbsp;&nbsp;&nbsp;&nbsp; 0
		&nbsp; Max Jobs/Policy:&nbsp;&nbsp;&nbsp;&nbsp; Unlimited
		&nbsp; Disaster Recovery:&nbsp;&nbsp; 0
		&nbsp; Collect BMR info:&nbsp;&nbsp;&nbsp; no
		&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
		&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NetBackup
		&nbsp; Server Group:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *ANY*
		&nbsp; Keyword:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (none specified)
		&nbsp; Data Classification:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -
		&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp; no
		
		Granular Restore Info:&nbsp; no
		Ignore Client Direct:&nbsp; no
		&nbsp; HW/OS/Client:&nbsp; Windows-x64&nbsp;&nbsp; Windows2008&nbsp;&nbsp; usnvsqldb01
		
		&nbsp; Include:&nbsp; CTSDB_SQL2012_FULLBackup.bch
		
		&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Default-Application-Backup
		&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Application Backup
		&nbsp;&nbsp;&nbsp; Maximum MPX:&nbsp;&nbsp;&nbsp;&nbsp; 1
		&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; Retention Level: 3 (1 month)
		&nbsp;&nbsp;&nbsp; Number Copies:&nbsp;&nbsp; 1
		&nbsp;&nbsp;&nbsp; Fail on Error:&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; Residence:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (specific storage unit not required)
		&nbsp;&nbsp;&nbsp; Volume Pool:&nbsp;&nbsp;&nbsp;&nbsp; (same as policy volume pool)
		&nbsp;&nbsp;&nbsp; Server Group:&nbsp;&nbsp;&nbsp; (same as specified for policy)
		&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; Daily Windows:
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Sunday&nbsp;&nbsp;&nbsp;&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Monday&nbsp;&nbsp;&nbsp;&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Tuesday&nbsp;&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Tuesday&nbsp;&nbsp;&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Wednesday&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Wednesday&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thursday&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Thursday&nbsp;&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Friday&nbsp;&nbsp;&nbsp;&nbsp; 24:00:00
		&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Saturday&nbsp;&nbsp; 00:00:00&nbsp; --&gt;&nbsp; Saturday&nbsp;&nbsp; 24:00:00
		
		&nbsp; Schedule:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Full
		&nbsp;&nbsp;&nbsp; Type:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Automatic Backup
		&nbsp;&nbsp;&nbsp; Frequency:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; every 7 days
		&nbsp;&nbsp;&nbsp; Synthetic:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; PFI Recovery:&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; Retention Level: 0 (1 week)
		&nbsp;&nbsp;&nbsp; Residence is Storage Lifecycle Policy:&nbsp;&nbsp;&nbsp;&nbsp; 0
		&nbsp;&nbsp;&nbsp; Daily Windows:
		&nbsp;

Whenever I am running the backup, the child job which is spawning is for the full schedule instead of Default-Application-Backup. Please advise what can be wrong here.
Let me know which logs you want me give, I uploaded dbclient logs already.
&nbsp;
Here is the Backup script.

OPERATION BACKUP
		BROWSECLIENT "USNVSQLDB01"
		DATABASE "master"
		SQLHOST "USNVSQLDB01"
		SQLINSTANCE "CTSDB"
		NBSERVER "EBACKUP01"
		MAXTRANSFERSIZE 0
		BLOCKSIZE 7
		POLICY CTSDB_TEST
		VERIFYOPTION STOPONERROR
		ENDOPER TRUE

tollboy · Accepted Answer

We took alternative route. We are triggering the backup from client side only. They are going fine now.

&nbsp;

Thanks every one for support.

rizwan84tx · Answer

I believe you need to update the complete path of bch script file.
&nbsp;

HW/OS/Client:&nbsp; Windows-x64&nbsp;&nbsp; Windows2008&nbsp;&nbsp; usnvsqldb01
	&nbsp; Include:&nbsp; CTSDB_SQL2012_FULLBackup.bch

marianne · Answer

rizwan is 100% right.
You need to specify the FULL path to the script.&nbsp;
Have another look at the article that you used as refence - Zahid specified the full path in the policy:&nbsp;
	C:\Program Files\Veritas\Netbackup\..............
Always good to consult NBU documentation as well:
NBU for Microsoft SQL Server Admin Guide &nbsp;http://www.symantec.com/docs/DOC3670

tollboy · Answer

Hello,
There are numerous SQL policies in our environment. All policies are having this relative path only in their include list.
It resolves to &lt;install directory&gt;\veritas
etbackup\dbext\Mssql\
&nbsp;
If policy is not able to find the path it should fail with 71. But it is not. My problem is, the chile job it is spawning is for the automatic full backup, not for the application backup.
&nbsp;
Regards

tollboy · Answer

Hello,
&nbsp;
Just for the giggles I have chnaged the relative paths to absoulte. Still its same behaviour. I am going thorugh the guide again to check, what I have missed this time.
&nbsp;
Regards.

marianne · Answer

I have seen SQL policy failing with status 2 with incorrect path in Backup Selection.&nbsp;
	Please edit path and type full pathname.
I've looked at your dbclient log. This is the first error:
00:00:42.688 [10248.11152] &lt;16&gt; OpenParmFile: ERR - Failed trying to get read access to C:\Program Files\Veritas\NetBackup\dbext\mssql\/USNVWDBPSQL01.MSSQL7.USNVSQLDB01\CTSDB.trx.ARSystem.~.7.001of001.20140109000026..C
Please check the logon account used for NetBackup Client Service.
Best to start this service as the same account used for SQL services.
	Ensure that this account has Local Admin rights on the SQL server.
Next error:
00:01:04.887 [2256.12704] &lt;16&gt; serverResponse: ERR - server exited with status 2: none of the requested files were backed up
00:01:04.887 [2256.12704] &lt;16&gt; CreateNewImage: ERR - serverResponse() failed
This means that the client tried to connect to bprd on the master server:
logconnections: BPRD CONNECT FROM 172.23.91.32.64078 TO 172.23.244.100.1556 fd = 1244
This connection attempt either never reached the master server or the something was wrong with with backup request and master server did not respond to request.
2 things to double-check:

Port 1556 open in both directions between master an client.
	Forward and reverse hostname lookup between master and client.
		Master must be able to resolve Client IP address to same hostname that appears in SQL policy. (Easiest will be to add '172.23.91.32 &nbsp;usnvsqldb01' to /etc/hosts on master, following by refreshing NBU host cache.)

To troubleshoot connection to master server, we need to see bprd log on the master.
	If log folder does not exist, create it and restart NBU on the master.&nbsp;
	Post bprd log after next failure.

Forum Discussion

Ms-sql backup does not creating correct child job

12 Replies

Related Content

Re: MS SQL backups for a single Database happening partially

Backup Issues with MS SQL

MS SQL backup

MS-SQL database restore failed

MS SQL Restore Error

Recent Discussions

command: bperror

MS-SharePoint policy restore error (2804) .

How to restore a backup

How to configure RBAC

10 years old netbackup appliance database service down, ssl certification out date