Forum Discussion

N_J's avatar
N_J
Level 3
6 years ago

online/archive backup of DB2 backing up through netbackup failing after upgrade from 7.6.0.2 to 8.1

Hi All, I have a DB2 redhat linux 2.6 client running SAP on it whose online and archive backups were running fine on version 7.6.0.2 before upgrading to 8.1. There are 4 DB2 databases on this client and after upgrade, 2 are running fine and other 2 are failing with EC 130. Below is the error from job details: ----------------------------------------------- 27 juil. 2018 09:39:39 - Error bprd (pid=6411) Unable to write progress log  on client ******. Policy=DB2_*****_ONLINE Sched=Default-Application-Backup 27 juil. 2018 09:39:39 - Error bprd (pid=6411) CLIENT ****** POLICY DB2_*****_ONLINE  SCHED Default-Application-Backup  EXIT STATUS 130 (system error occurred) ------------------------------------------------- Since 2 DBs on this client are writing fine, there is no issues with communication on master server (Also a Redhat Linux Machine 2.6 NB Version 8.1). The problem happened earlier as well when we tried upgrading the client to 7.7.3 but we then rolled back to 7.6.0.2. I have tried adding the progress log path to BPCD_WHITELIST_PATH under bp.conf of the client but still no luck. I would be happy to provide further logs.
8
Linux
NetBackup 8.1
Netbackup for DB2

7 Replies

Sort By
  • Tape_Archived's avatar
    Tape_Archived
    Moderator
    6 years ago

    Please compare the permissions on the /usr/openv/netbackup/logs/user_ops/ with the client that is working fine.

    With 8.1 you will also have to check if client has been issued a certificate for secure communication.

     

    • N_J's avatar
      N_J
      Level 3
      6 years ago

      Tape_Archived 

      Actually, as I said, the 2 DBs on the same client is working fine, and 2 aren't. Also, the permissions are 777 to the user_ops, and its sub directories.

      The DBs that are getting successful are writing the progress log well in the folder but the other 2 DBs doesn't.

      Since, 2 DBs are writing fine, this doesn't look like a secure connection issue.

      Since it started happening after upgrading from 7.6.0.2 to 8.1, I checked what has changed but couldn't find anything except the WHITELIST that I mentioned. 

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        Have you tried to check bprd log on the master server?
        The log file name and path that is having the issue is normally documented in bprd log. 

        About the scripts - I was wondering if there was something different about the 2 non-working DBs. 
        Maybe some other path is specified for progress logs. That is why I asked if the scripts could be compared. 

  • Marianne's avatar
    Marianne
    Level 6
    6 years ago

    N_J

    The issue seems to be with the 'progress log' :

     Error bprd (pid=6411) Unable to write progress log  on client

    Is there something different about the progress logs for these 2 DBs ?
    Have you tried to compare scripts with those of the working DBs? 
    Have you checked bprd log on the master to see if there is more info w.r.t. to the log path? 

    • N_J's avatar
      N_J
      Level 3
      6 years ago

      Marianne Thanks for your time for looking into it.

      I don't find anything wrong with the script. Morever, the backups were fine before the upgrade.. I am attaching the scripts for your reference and bpdb2 logs for working db and non working db for your reference.

      PS: bprd logs were not building up on master and I guess I have to restart the services on master which I cannot do it now (unless you suggest if there is any other option so that it starts generating).

      • Marianne's avatar
        Marianne
        Level 6
        6 years ago

        Yes - bprd needs to be restarted to enable logging. 

        About the scripts - I can see that there are no output files specified in the backup scripts. 

        The only difference seems to be the Database name and User.
        And the fact that the non-working one loads a profile before the backup command is started:

        . /db2/BID/sqllib/db2profile;db2 BACKUP DATABASE $MY_DB2 $MY_SCHED online LOAD $MY_LIB BUFFER 1024

        Any idea why? (I realize that this was working on 7.6, but we need to look at this as if it is a new issue.)
        What is listed in this db2profile that the other user for working DB does not need? 

        My suggestion: 

        Find a time to restart NBU so that we can have bprd logs.

        Log on to the client as user db2bid. 
        Manually run the commands in CMD_LINE and watch the output.

         

        I will have a look at the logs a bit later in the day (if time permits...)