Skip to content

Netezza internal process – bnrmgr

bnrmgr is on of the Netezza process which starts automatically when Netezza starts (All background processes are started by startupsvr background process). Main purpose of this process is to handle all the incoming requests for nzbackup and nzrestore commands. It launches a instance of backupsvr or restoresvr to handle each client instance.

bnrmgr looks like below when any backup/restore command is issued:
/nz/kit/log/bnrmgr->cat bnrmgr.log
2013-10-08 15:04:35.416165 EDT Info: backup / restore session started: pid = 25583 user = admin
2013-10-08 15:04:36.817095 EDT Info: backup/restore session ended: pid = 25583, status = 0
2013-10-08 15:07:11.163890 EDT Info: backup / restore session started: pid = 2933 user = admin
2013-10-08 15:07:21.322935 EDT Info: backup/restore session ended: pid = 2933, status = 0
2013-10-08 15:10:27.469984 EDT Info: backup / restore session started: pid = 13265 user = admin
2013-10-08 15:10:36.792838 EDT Info: backup/restore session ended: pid = 13265, status = 0
2013-10-08 15:24:13.003794 EDT Info: backup / restore session started: pid = 19276 user = admin
2013-10-08 15:24:22.780980 EDT Info: backup/restore session ended: pid = 19276, status = 0
2013-10-08 15:25:36.306742 EDT Info: backup / restore session started: pid = 23718 user = admin
2013-10-08 15:25:48.655279 EDT Info: backup/restore session ended: pid = 23718, status = 0

You can map this with backup logs placed at /nz/kit/log/backupsvr (Possibly if it a restore it should be under /nz/kit/log/restoresvr)

/nz/kit/log/backupsvr->ls -lrt
total 28
drwxr-xr-x 30 nz nz 4096 Oct 8 15:04 ../
-rw——- 1 nz nz 765 Oct 8 15:04 backupsvr.25583.2013-10-08.log
-rw——- 1 nz nz 3132 Oct 8 15:07 backupsvr.2933.2013-10-08.log
-rw——- 1 nz nz 3222 Oct 8 15:10 backupsvr.13265.2013-10-08.log
-rw——- 1 nz nz 3296 Oct 8 15:24 backupsvr.19276.2013-10-08.log
drwx—— 2 nz nz 4096 Oct 8 15:25 ./
-rw——- 1 nz nz 3560 Oct 8 15:25 backupsvr.23718.2013-10-08.log

Compare the time shown in bnrmgr.log and timestamp of each logfile in /nz/kit/log/backupsvr

Additionally, bnrmgr log also gets updated whenever Netezza stop/start. That is quite obvious since this is one of the internal Netezza process. Log will look like below when Netezza stop and starts:

/nz/kit/log/bnrmgr->cat bnrmgr.2013-10-07.log
2013-07-31 04:34:12.775478 EDT Info: changing bnr mgr state to ‘offliningNow’, stopping current sessions
2013-07-31 04:34:12.775533 EDT Info: bnr mgr completed transition to state ‘offlineNow’, version ’6′
2013-07-31 04:34:15.573641 EDT Info: NZ-00023: — program ‘bnrmgr’ (22734) exiting on host ‘ntzzdrdb01cdp’ … —
2013-07-31 07:00:33.083106 EDT Info: NZ-00022: — program ‘bnrmgr’ (10054) starting on host ‘ntzzdrdb01cdp’ … —
2013-07-31 07:07:05.845653 EDT Info: system is online – enabling backup and restore sessions

How to find NPS versions ever installed on server

Check all the NPS versions ever installed on Netezza server. THis info also includes date time when this activity was performed as well as previous and new version for each upgrade.

/nz/data/config->cat /nz/data/config/callHome.txt | grep transition

# 2011-03-21 21:09:01 -0400 (EDT): Successful transition from 6.0.P4 to 6.0.P7
# 2011-07-22 19:04:02 -0400 (EDT): Successful transition from 6.0.P7 to 6.0.3.P1
# 2011-08-12 08:04:42 -0400 (EDT): Successful transition from 6.0.3.P1 to 6.0.3.P2
# 2011-10-08 21:08:08 -0500 (EST): Successful transition from 6.0.3.P2 to 6.0.5.P2
# 2012-01-07 12:07:39 -0500 (EST): Successful transition from 6.0.5.P2 to 6.0.5.P5
# 2012-04-08 09:03:31 -0400 (EDT): Successful transition from 6.0.5.P5 to 6.0.6
# 2012-07-24 01:05:01 -0400 (EDT): Successful transition from 6.0.6 to 6.0.5.P5
# 2012-08-24 01:41:03 -0400 (EDT): Successful transition from 6.0.5.P5 to 6.0.5.P10
# 2013-03-29 21:35:13 -0500 (EST): Successful transition from 6.0.5.P10 to 7.0.P2
# 2013-04-23 08:58:15 -0400 (EDT): Successful transition from 7.0.P2 to 6.0.8.P6
# 2013-06-08 08:04:51 -0400 (EDT): Successful transition from 6.0.8.P6 to 7.0.P2
# 2013-06-13 12:09:16 -0400 (EDT): Successful transition from 7.0.P2 to 7.0.2.P4
# 2013-09-28 16:09:39 -0400 (EDT): Successful transition from 7.0.2.P4 to 7.0.2.P5

Another way is to check all the kit files stored at /nz. Version against “kit ->” is the current version and “kit.bak ->” is the previous version.

/nz->ls -lrt | grep kit
drwxr-xr-x 11 nz nz 4096 Oct 21 2010 kit.5.0.10.P5/
drwxrwxrwx 4 root root 4096 Nov 22 2010 diagskit/
drwxrwxr-x 11 nz nz 4096 Mar 1 2011 kit.6.0.P4/
drwxr-xr-x 11 nz nz 4096 Mar 10 2011 kit.6.0.P7/
drwxr-xr-x 11 nz nz 4096 Jul 15 2011 kit.6.0.3.P1/
drwxr-xr-x 11 nz nz 4096 Aug 10 2011 kit.6.0.3.P2/
drwxr-xr-x 9 nz nz 4096 Nov 4 2011 kit.6.0.5.P2/
drwxr-xr-x 9 nz nz 4096 Feb 14 2012 kit.6.0.5.P5/
drwxr-xr-x 9 nz nz 4096 Mar 27 2012 kit.6.0.6/
drwxr-xr-x 9 nz nz 4096 Aug 21 2012 kit.6.0.5.P10/
drwxr-xr-x 10 nz nz 4096 Dec 18 2012 kit.7.0.P2.27274/
drwxr-xr-x 10 nz nz 4096 Dec 18 2012 kit.7.0.P2/
drwxr-xr-x 12 nz nz 4096 Mar 26 2013 kit.6.0.8.P6/
drwxr-xr-x 10 nz nz 4096 May 24 15:58 kit.7.0.2.P4/
drwxr-xr-x 10 nz nz 4096 Jun 24 19:19 kit.7.0.2.P5/
lrwxrwxrwx 1 nz nz 12 Jun 28 16:06 kit.bak -> kit.7.0.2.P5/
drwxr-xr-x 10 nz nz 4096 Sep 17 23:29 kit.7.0.2.P8.32960.1/
drwxr-xr-x 10 10507 12009 4096 Sep 17 23:29 kit.7.0.2.P8.32960/
drwxr-xr-x 10 10507 12009 4096 Sep 17 23:29 kit.7.0.2.P8/
lrwxrwxrwx 1 nz nz 20 Oct 23 21:09 kit -> kit.7.0.2.P8.32960.1/