05-31-2015 11:31 PM
We are receiveing any failure alerts and by suspecting the service NBNOS isnot running in master server. It would be great thankful if i got a solution.
Solved! Go to Solution.
06-01-2015 01:18 AM
nbnos – Name of the binary for NetBackup
/usr/openv/netbackup/bin/nbnos [-console] [-terminate]
[-Factory name] [-IORoutput file] [-ChannelName name]
[-Channel]
DESCRIPTION
The nbnos command can be used to register an event channel, to set a channel name, to
start NetBackup in console mode, and to set a factory name.
OPTIONS
-channel
Enables you to register an event channel. The default setting is to not
register an event channel.
-ChannelName
Enables you to set the channel name. The default channel name is,
VRTS_NotifyEventChannel.
-console
This option enables you to start NetBackup in console mode.
-Factory name
This option enables you to set the factory name. The default value for this
setting is, VRTS_NotifyEventChannelFactory.
-terminate
This option enables you to stop nbnos.
so to start it, just try:
/usr/openv/netbackup/bin/nbnos
06-01-2015 12:02 AM
NBOS is Netbackup NetBackup Notification Service.
There is not NetBackup Notification Service in Netbackup 6.5 - 7.6 so I presume this installation run NBU 6.0 - Time to upgrade to a supported version
Any reason for shutting this service down ?
I NBOS is one of the required services you can't stop it without breaking Netbackup functionality.
06-01-2015 12:21 AM
Thanks Nicolai, Backups are running fine but we used to get the alerts the service - NBNOSis in down state. How can we start the service please?
06-01-2015 12:33 AM
You will need to find NBU 6.0 documentation...
Honestly - this version is so old that nobody remembers anything about it.
All we can tell you is to either start the service manually or restart NBU.
06-01-2015 12:38 AM
Thanks Marianne, what is the command to start the service in the master server?
we are not getting any failure alerts from the master server so is this the reason ?
06-01-2015 12:57 AM
I honestly don't know - I do not have any 6.0 documentation on my laptop.
Even trying to Google for anything related to nbnos finds one or 2 posts on Connect (including yours)
You can try to specify the full path to the command and see what happens.
The alternative is to restart NBU.
06-01-2015 01:18 AM
nbnos – Name of the binary for NetBackup
/usr/openv/netbackup/bin/nbnos [-console] [-terminate]
[-Factory name] [-IORoutput file] [-ChannelName name]
[-Channel]
DESCRIPTION
The nbnos command can be used to register an event channel, to set a channel name, to
start NetBackup in console mode, and to set a factory name.
OPTIONS
-channel
Enables you to register an event channel. The default setting is to not
register an event channel.
-ChannelName
Enables you to set the channel name. The default channel name is,
VRTS_NotifyEventChannel.
-console
This option enables you to start NetBackup in console mode.
-Factory name
This option enables you to set the factory name. The default value for this
setting is, VRTS_NotifyEventChannelFactory.
-terminate
This option enables you to stop nbnos.
so to start it, just try:
/usr/openv/netbackup/bin/nbnos
06-01-2015 01:59 AM
You are better off stop & starting all Netbbackup services.
/etc/init.d/netbackup stop (assuming Linux)
/etc/init.d/netbackup start
06-01-2015 02:14 AM
I would try the running the binary first then your approach if that does not work, leaving jobs to carry on in the first event.
06-01-2015 02:25 AM
thanks everyone for the response, i will try and update here very shortly
06-30-2015 09:38 PM
service isn't required since the master server is at 7.1, thanks for helping me in getting idea about nbnos.