Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  3. NetBackup™ for OpenStack Administrator's Guide
  5. Troubleshooting
  7. Health check of NetBackup for OpenStack
  9. On the NetBackup for OpenStack Cluster
NetBackup™ for OpenStack Administrator's Guide

On the NetBackup for OpenStack Cluster

nbosjm-policies

This service runs and is active on every NetBackup for OpenStack node. 

[root@Upstream ~]# systemctl status nbosjm-policies
● nbosjm-policies.service - nbosjm policies service
   Loaded: loaded (/etc/systemd/system/nbosjm-policies.service; enabled; 
   vendor preset: disabled)
   Active: active (running) since Wed 2020-06-10 13:42:42 UTC; 1 weeks 
   4 days ago
 Main PID: 12779 (nbosjm-wor)
    Tasks: 17
   CGroup: /system.slice/nbosjm-policies.service
           ├─12779 /home/stack/myansible/bin/python 
/home/stack/myansible/bin/nbosjm-policies 
--config-file=/etc/nbosjm/nbosjm.conf
           ├─12982 /home/stack/myansible/bin/python 
/home/stack/myansible/bin/nbosjm-policies 
--config-file=/etc/nbosjm/nbosjm.conf
           ├─12983 /home/stack/myansible/bin/python 
/home/stack/myansible/bin/nbosjm-policies 
--config-file=/etc/nbosjm/nbosjm.conf
           ├─12984 /home/stack/myansible/bin/python 
/home/stack/myansible/bin/nbosjm-policies 
--config-file=/etc/nbosjm/nbosjm.conf
           [...]
nbosjm-api

This service runs and is active on every NetBackup for OpenStack node. 

[root@Upstream ~]# systemctl status nbosjm-api
● nbosjm-api.service - nbosjm api service
   Loaded: loaded (/etc/systemd/system/nbosjm-api.service; disabled; 
   vendor preset: disabled)
  Drop-In: /run/systemd/system/nbosjm-api.service.d
           └─50-pacemaker.conf
   Active: active (running) since Thu 2020-04-16 22:30:11 UTC; 
   2 months 5 days ago
 Main PID: 11815 (nbosjm-api)
    Tasks: 1
   CGroup: /system.slice/nbosjm-api.service
           └─11815 /home/stack/myansible/bin/python /home/stack/
           myansible/bin/nbosjm-api --config-file=/etc/
           nbosjm/nbosjm.conf
nbosjm-scheduler

This service runs and is active on every NetBackup for OpenStack node. 

[root@Upstream ~]# systemctl status nbosjm-scheduler
● nbosjm-scheduler.service - nbosjm scheduler service
   Loaded: loaded (/etc/systemd/system/nbosjm-scheduler.service; disabled; 
   vendor preset: disabled)
  Drop-In: /run/systemd/system/nbosjm-scheduler.service.d
           └─50-pacemaker.conf
   Active: active (running) since Thu 2020-04-02 13:49:22 UTC; 2 months 
   20 days ago
 Main PID: 29439 (nbosjm-sch)
    Tasks: 1
   CGroup: /system.slice/nbosjm-scheduler.service
           └─29439 /home/stack/myansible/bin/python /home/stack/myansible
           /bin/nbosjm-scheduler --config-file=/etc/nbosjm/
           nbosjm.conf
nbosjm-cron

This service is controlled by pacemaker and runs only on the master node 

[root@Upstream ~]# systemctl status nbosjm-cron
● nbosjm-cron.service - Cluster Controlled nbosjm-cron
   Loaded: loaded (/etc/systemd/system/nbosjm-cron.service; disabled; 
   vendor preset: disabled)
  Drop-In: /run/systemd/system/nbosjm-cron.service.d
           └─50-pacemaker.conf
   Active: active (running) since Wed 2021-01-27 19:59:26 UTC; 6 days ago
 Main PID: 23071 (nbosjm-cro)
   CGroup: /system.slice/nbosjm-cron.service
           ├─23071 /home/stack/myansible/bin/python3 /home/stack/
myansible/bin/nbosjm-cron --config-file=/etc/nbosjm
/nbosjm.conf
           └─23248 /home/stack/myansible/bin/python3 /home/stack/
myansible/bin/nbosjm-cron --config-file=/etc/nbosjm/
nbosjm.conf

Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ● nbosjm-cron.service - Cluster Controlled nbosjm-cron
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Loaded: loaded (/etc/systemd/system/nbosjm-cron.service; disabled; 
vendor preset: disabled)
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Drop-In: /run/systemd/system/nbosjm-cron.service.d
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: └─50-pacemaker.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Active: active (running) since Wed 2021-01-27 19:59:26 UTC; 
6 days ago
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: Main PID: 23071 (nbosjm-cro)
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: CGroup: /system.slice/nbosjm-cron.service
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ├─23071 /home/stack/myansible/bin/python3 /home/stack/myansible/
bin/nbosjm-cron --config-file=/etc/nbosjm/nbosjm.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: ├─23248 /home/stack/myansible/bin/python3 /home/stack/myansible/
bin/nbosjm-cron --config-file=/etc/nbosjm/nbosjm.conf
Feb 03 19:28:43 nbosvm1-ansible-ussuri-ubuntu18-vagrant nbosjm-cron
[23071]: └─27145 /usr/bin/systemctl status nbosjm-cron
Pacemaker Cluster Status

The pacemaker cluster controls and watches the VIP on the NetBackup for OpenStack Cluster. It also controls on which node the nbosjm-api and nbosjm-scheduler service runs. 

[root@Upstream ~]# pcs status
Cluster name: NetBackup for OpenStack

WARNINGS:
Corosync and pacemaker node names do not match (IPs used in setup?)

Stack: corosync
Current DC: nbosvm1-ansible-ussuri-ubuntu18-vagrant (version 
1.1.23-1.el7_9.1-9acf116022) - chapterition with quorum
Last updated: Wed Feb  3 19:20:02 2021
Last change: Wed Jan 27 20:00:12 2021 by root via crm_resource on 
nbosvm1-ansible-ussuri-ubuntu18-vagrant

1 node configured
6 resource instances configured

Online: [ nbosvm1-ansible-ussuri-ubuntu18-vagrant ]

Full list of resources:

 virtual_ip     (ocf::heartbeat:IPaddr2):       Started nbosvm1-ansible-
ussuri-ubuntu18-vagrant
 virtual_ip_public      (ocf::heartbeat:IPaddr2):       Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
 virtual_ip_admin       (ocf::heartbeat:IPaddr2):       Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
 virtual_ip_internal    (ocf::heartbeat:IPaddr2):       Started nbosvm1-
ansible-ussuri-ubuntu18-vagrant
 nbosjm-cron       (systemd:nbosjm-cron):     Started nbosvm1-ansible-
ussuri-ubuntu18-vagrant
 Clone Set: lb_nginx-clone [lb_nginx]
     Started: [ nbosvm1-ansible-ussuri-ubuntu18-vagrant ]

Daemon Status:
  corosync: active/enabled
  pacemaker: active/enabled
  pcsd: active/enabled
Mount availability

The NetBackup for OpenStack Cluster needs access to the Backup Target and should have the correct mount at all times. 

[root@Upstream ~]# df -h
Filesystem             Size  Used Avail Use% Mounted on
devtmpfs               3.8G     0  3.8G   0% /dev
tmpfs                  3.8G   38M  3.8G   1% /dev/shm
tmpfs                  3.8G  427M  3.4G  12% /run
tmpfs                  3.8G     0  3.8G   0% /sys/fs/cgroup
/dev/vda1               40G  8.8G   32G  22% /
tmpfs                  773M     0  773M   0% /run/user/996
tmpfs                  773M     0  773M   0% /run/user/0
10.10.2.20:/upstream  1008G  704G  254G  74% /var/NetBackupOpenStack-mounts/
                                             MTAuMTAuMi4yMDovdXBzdHJlYW0=
10.10.2.20:/upstream2  483G   22G  462G   5% /var/NetBackupOpenStack-mounts/
                                             MTAuMTAuMi4yMDovdXBzdHJlYW0y

Feedback

Was this page helpful?
Previous

Health check of NetBackup for OpenStack

Next

The nbosdmapi service

Feedback

Was this page helpful?