cancel
Showing results for 
Search instead for 
Did you mean: 

Catalog backup is getting failed with error code 2

Sharad_Singh7
Level 4

Hello All,

 

Catalog backup of one of our master server is getting failed with 2.

 

Master Server ---Linux

Master Server netbackup version----NetBackup-RedHat2.6 7.1.0.4

 

 

I am getting the below error when I ran the command ./nbdb_admin -validate NBAZDB

 

SQL error (-832) -- Connection error: Insufficient system resources - failed to allocate a SYSV semaphore
SQL error (-832) -- Connection error: Insufficient system resources - failed to allocate a SYSV semaphore
SQL Anywhere Validation Utility Version 11.0.1.2745

 

 

 

./nbdb_admin -validate BMRDB

 

Can't identify database BMRDB.

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   
 failed to allocate a SYSV semaphore

OK - This should be easy to fix. Take a look at this tech note and apply the kernel tunables.

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

You need to re-start Netbackup (better to reboot) for changes to apply.

I usally apply these kernel tunabes to /etc/sysctl.conf and apply with with "sysctl -p"

# Netbackup tuning variables.
net.ipv4.tcp_keepalive_time=1800
kernel.msgmni = 256
net.ipv4.tcp_keepalive_time=1800
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.ipv4.tcp_rmem = 8192 524288 16777216
net.ipv4.tcp_wmem = 8192 524288 16777216
net.core.netdev_max_backlog = 30000
kernel.sem=300  307200  32  1024

View solution in original post

5 REPLIES 5

Marianne
Level 6
Partner    VIP    Accredited Certified

How many jobs are getting activated for Catalog backup?

Is parent or child job(s) failing?

Please show us all text in Details tab for all Catalog parent and/or child backup jobs.

Nicolai
Moderator
Moderator
Partner    VIP   
 failed to allocate a SYSV semaphore

OK - This should be easy to fix. Take a look at this tech note and apply the kernel tunables.

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

You need to re-start Netbackup (better to reboot) for changes to apply.

I usally apply these kernel tunabes to /etc/sysctl.conf and apply with with "sysctl -p"

# Netbackup tuning variables.
net.ipv4.tcp_keepalive_time=1800
kernel.msgmni = 256
net.ipv4.tcp_keepalive_time=1800
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.rmem_default = 262144
net.core.wmem_default = 262144
net.ipv4.tcp_rmem = 8192 524288 16777216
net.ipv4.tcp_wmem = 8192 524288 16777216
net.core.netdev_max_backlog = 30000
kernel.sem=300  307200  32  1024

Sharad_Singh7
Level 4

Hello Marianne,

 

Child jobs are not generating.

 

Please find detailed status of parent job.

 

 

11/08/2014 00:59:07 - Info bpdbm (pid=19521) staging relational database files for catalog backup
11/08/2014 00:59:07 - Info bpdbm (pid=19521) staging NBAZDB backup to /usr/openv/db/staging
11/08/2014 00:59:07 - Error bpdbm (pid=19521) error staging NBAZDB backup to /usr/openv/db/staging
11/08/2014 00:59:07 - Info bpdbm (pid=19521) staging NBDB backup to /usr/openv/db/staging
11/08/2014 00:59:07 - Error bpdbm (pid=19521) error staging NBDB backup to /usr/openv/db/staging
none of the requested files were backed up  (2)

Nicolai
Moderator
Moderator
Partner    VIP   

Did you resolve the SYSV semaphore you wrote about before ?

This look like a new error. 

Marianne
Level 6
Partner    VIP    Accredited Certified

Problem has been around for a couple of weeks now. 
No a big priority??

I am wondering about the health of NBU relational databases on this master server...