Forum Discussion

symsonu's avatar
symsonu
Level 6
11 years ago
Solved

backup jobs failing status 2505 and 252

backup jobs are failing as below

 

6/26/2014 00:26:29 - estimated 8946870 kbytes needed
06/26/2014 00:26:29 - Info nbjm (pid=3930) started backup (backupid=xxxxbp_1403735189) job for client xxxxxbp, policy xxx_i386_DATA_xxx01xxxbp_xxx01sybbp, schedule Daily_Incr on storage unit xxxxx01-hcart-robot-tld-0
06/26/2014 00:26:30 - Info bpbrm (pid=632) xxxxxxxbp is the host to backup data from
06/26/2014 00:26:30 - Info bpbrm (pid=632) reading file list from client
06/26/2014 00:26:30 - started process bpbrm (pid=632)
06/26/2014 00:26:30 - connecting
06/26/2014 00:26:31 - Info bpbrm (pid=632) starting bpbkar on client
06/26/2014 00:26:31 - Info bpbkar (pid=0) Starting bpstart_notify script
06/26/2014 00:26:31 - connected; connect time: 0:00:00
06/26/2014 00:26:40 - Info bpbkar (pid=0) Finished bpstart_notify script
06/26/2014 00:26:40 - Info bpbkar (pid=1620) Backup started
06/26/2014 00:26:40 - Info bpbrm (pid=632) bptm pid: 667
06/26/2014 00:26:41 - Info bptm (pid=667) start
06/26/2014 00:26:41 - Info bptm (pid=667) using 65536 data buffer size
06/26/2014 00:26:41 - Info bptm (pid=667) setting receive network buffer to 262144 bytes
06/26/2014 00:26:41 - Info bptm (pid=667) using 30 data buffers
06/26/2014 00:26:41 - Info bptm (pid=667) start backup
06/26/2014 00:26:41 - Info bptm (pid=667) backup child process is pid 669
06/26/2014 00:26:41 - Info bptm (pid=667) media id 5941L4 mounted on drive index 0, drivepath /dev/rmt/1cbn, drivename HP.ULTRIUM4-SCSI.000, copy 1
06/26/2014 00:26:41 - mounted 5941L4
06/26/2014 00:26:41 - positioning 5941L4 to file 737
06/26/2014 00:26:43 - positioned 5941L4; position time: 0:00:02
06/26/2014 00:26:43 - begin writing
06/26/2014 00:31:11 - Error bpbrm (pid=632) db_FLISTsend failed: Unable to connect to the database (2505)
06/26/2014 00:31:13 - Error bptm (pid=667) media manager terminated by parent process
06/26/2014 00:35:18 - Info bpbkar (pid=1620) done. status: 2505: Unable to connect to the database
06/26/2014 00:35:18 - end writing; write time: 0:08:35
Failed to get status code information (2505)

 

what is the solution for error code 2505 ?

 

I can see few jobs failed with status 2505 and few with 252 ?

please help.

 

Regards

S.

7.5
Backing Up
Backup and Recovery
NetBackup
Solaris
Troubleshooting
  • revarooo's avatar
    revarooo
    11 years ago

    Come across this issue multiple times. It is fixed in NetBackup 7.5.0.7

    Sybase does not respond for a brief moment causing bpdbm updates to fail resulting in a 2505.

    Tuning the higher cache limit -ch in the server.conf can help, but doesn't always.

     

    Upgrade to 7.5.0.7 will fix this as bpdbm has been recoded to attempt to talk to sybase more than once before failing.

     

13 Replies

  • RamNagalla's avatar
    RamNagalla
    Moderator
    11 years ago

    tell us more about your infrastcture..

    what is the OS and netbackup verisons in Master server..

    it looks like you need to tune the server kernal parameters..

    have a look into below T/N.

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

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

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Have a look at the following:

    https://www-secure.symantec.com/connect/forums/after-upgrade-7503-71-status-2505-and-252 

    http://www.symantec.com/docs/TECH203316

    http://www.symantec.com/docs/TECH210207 

    The 2nd TN is probably applicable here as both error codes are listed.

    Issue is caused by insufficient semaphore tuning.

    See the TN mentioned under 'Related Articles':

    As well as NBU 7.5 Performance Tuning doc: 
    Updated NetBackup Backup Planning and Performance Tuning Guide for Release 7.5 and Release 7.6

  • sri_vani's avatar
    sri_vani
    Level 6
    11 years ago

    It would be helpful if you could provide us more details to troubleshoot on the issue

    What is ur Master/media/client- OS and NBU versions?

    How many backups are impacted and what kind of backups? bptm and bpdbm logs will log us more details

    When verified I found below notes on this error: Please go through it(Status code 2505 along with 252)

     

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

    The error is typically when the RHEL system is the NetBackup (NBU) master server. This error can be caused by a lack of semaphore tuning within the kernel.  This error cannot be resolved by NetBackup.

     

    Solution

    In this case, the semmni value was insufficient at 128. By increasing this value to 1024, the ODBC connection was successful and NetBackup was then able to run successfully.

     

  • symsonu's avatar
    symsonu
    Level 6
    11 years ago

    where is the bpdbm logs located ?

     

    Do I need to create directory for it? and does we need to restart netbackup services after creation of firectory ?

     

     

    Regards

    S.

  • sri_vani's avatar
    sri_vani
    Level 6
    11 years ago

    Unix: usr/openv/netbackup/logs/bpdbm/

    Windows:Installationpath/netbackup/logs/bpdbm/

    It is best to stop and restart the NetBackup services after making any changes .

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Come across this issue multiple times. It is fixed in NetBackup 7.5.0.7

    Sybase does not respond for a brief moment causing bpdbm updates to fail resulting in a 2505.

    Tuning the higher cache limit -ch in the server.conf can help, but doesn't always.

     

    Upgrade to 7.5.0.7 will fix this as bpdbm has been recoded to attempt to talk to sybase more than once before failing.

     

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Just for the record - bpdbm log folder needs to be created on the master server under /usr/openv/netbackup/logs. 

    NBU needs to be restarted for log to take effect.

  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    Don't bother with the logs, go straight to 7.5.0.7- you won't have this problem after.

  • symsonu's avatar
    symsonu
    Level 6
    11 years ago

    our netbackup version is 7.5.0.4

    and I can see from system file in solaris the below values are set

    set semsys:seminfo_semmni=1024

    set msgsys:msginfo_msgmni=256

    set shmsys:shminfo_shmmni=256

    set shmsys:shminfo_shmmax=16759808

     

    we are not using projects and above values are set in system file in solaris.

     

    # cat  /usr/openv/var/global/server.conf

     -n NB_cpombs01

       -x tcpip(LocalOnly=YES;ServerPort=13785)  -gp 4096 -gd DBA -gk DBA -gl DBA -ti 0 -c 100M -ch 1024M -cl 100M -zl -os 1M -m -o /usr/openv/db//log/server.log

     -ud

     

     

    Regards

    S.