cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Ms-sql backup does not creating correct child job

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.

 

Policy Name:       CTSDB_TEST

  Policy Type:         MS-SQL-Server
  Active:              yes
  Effective date:      01/09/2014 05:08:09
  Mult. Data Streams:  no
  Client Encrypt:      no
  Checkpoint:          no
  Policy Priority:     0
  Max Jobs/Policy:     Unlimited
  Disaster Recovery:   0
  Collect BMR info:    no
  Residence:           (specific storage unit not required)
  Volume Pool:         NetBackup
  Server Group:        *ANY*
  Keyword:             (none specified)
  Data Classification:       -
  Residence is Storage Lifecycle Policy:    no

Granular Restore Info:  no
Ignore Client Direct:  no
  HW/OS/Client:  Windows-x64   Windows2008   usnvsqldb01

  Include:  CTSDB_SQL2012_FULLBackup.bch

  Schedule:          Default-Application-Backup
    Type:            Application Backup
    Maximum MPX:     1
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 3 (1 month)
    Number Copies:   1
    Fail on Error:   0
    Residence:       (specific storage unit not required)
    Volume Pool:     (same as policy volume pool)
    Server Group:    (same as specified for policy)
    Residence is Storage Lifecycle Policy:     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

  Schedule:          Full
    Type:            Automatic Backup
    Frequency:       every 7 days
    Synthetic:       0
    PFI Recovery:    0
    Retention Level: 0 (1 week)
    Residence is Storage Lifecycle Policy:     0
    Daily Windows:
 

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.

 

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

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

We took alternative route. We

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

 

Thanks every one for support.

View solution in original post

12 Replies
Highlighted

I believe you need to update

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

 

HW/OS/Client:  Windows-x64   Windows2008   usnvsqldb01

  Include:  CTSDB_SQL2012_FULLBackup.bch

Highlighted

rizwan is 100% right. You

rizwan is 100% right.

You need to specify the FULL path to the script. 

Have another look at the article that you used as refence - Zahid specified the full path in the policy: 
C:\Program Files\Veritas\Netbackup\..............

Always good to consult NBU documentation as well:

NBU for Microsoft SQL Server Admin Guide  http://www.symantec.com/docs/DOC3670

Highlighted

Hello, There are numerous SQL

Hello,

There are numerous SQL policies in our environment. All policies are having this relative path only in their include list.

It resolves to <install directory>\veritas\netbackup\dbext\Mssql\

 

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.

 

Regards

Highlighted

Hello,   Just for the giggles

Hello,

 

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.

 

Regards.

Highlighted

I have seen SQL policy

I have seen SQL policy failing with status 2 with incorrect path in Backup Selection. 
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] <16> 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] <16> serverResponse: ERR - server exited with status 2: none of the requested files were backed up
00:01:04.887 [2256.12704] <16> 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:

  1. Port 1556 open in both directions between master an client.
  2. 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  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. 
Post bprd log after next failure.

Highlighted

Please see my post below.....

Please see my post below.....

Highlighted

Full path is not required if

Full path is not required if the .bch file is in the default directory.  We do this all the time. 

 

What caught my eye is your client name indicated above is USNVSQLDB01 so what is USNVWDBPSQL01 ??

 

MASTERSERVER EBACKUP01
CLIENT USNVWDBPSQL01
INSTANCE USNVSQLDB01\CTSDB
DATABASE ARSystem
OPERATION BACKUP
OBJECTTYPE TRXLOG
STATUS 2
INFO Server Status:  none of the requested files were backed up
INFO Error in VxBSACreateObject: 3.
INFO System detected error, operation aborted.
ENDOPER TRUE
Highlighted

Wr, USNVSQLDB01  is cluster

Wr,

USNVSQLDB01  is cluster running on  USNVWDBPSQL01  and USNVWDBPSQL02. At the time of backup VIP was with USNVWDBPSQL01.

 

Highlighted

Hello,   All the netbackup

Hello,

 

All the netbackup services are running with LOCAL SYSTEM.

I have made local account member of all the necessary roles of the permission as per technote.

http://www.symantec.com/business/support/index?page=content&id=TECH43512

 

I have tested the coummincation using bptestbpcd, it is working from the master(same media) server.

Somehow bprd logs are not getting generated. I have verbosity set to 5 for the logs, robust logging is also turned on.

 

 

 

Highlighted

OK that makes sense.    In

OK that makes sense. 

 

In the log file, client name is preceded with /

Don't know where it is picking that up (typo in hosts file?) but that seems to be the source of the trouble.

 

00:00:28.382 [2256.12704] <4> CreateNewImage: INF - backing up File:</USNVWDBPSQL01.MSSQL7.USNVSQLDB01\CTSDB.trx.ARSystem.~.7.001of001.20140109000026..C>

00:00:42.688 [10248.11152] <16> 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

 

Highlighted

Somehow bprd logs are not

Somehow bprd logs are not getting generated. 

As per my post above - you need to restart NBU on the master server after creating the log folder.
Logs for background daemons on the master such as bpdbm and bprd will only be enabled on initial startup of the daemons.

(For this level of troubleshooting there is no need for level 5 logs. Default level 0 is sufficient.
Level 5 makes log files uneccesary big and slows down performance. It is only needed when Symantec Support needs deep level diagnostics.)
 

We need to see in bprd log which IP address is arriving at Master for backup request and how master is resolving IP to hostname.

Highlighted
Accepted Solution!

We took alternative route. We

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

 

Thanks every one for support.

View solution in original post