NetBackup™ for OpenStack Administrator's Guide
- Introduction
- Deploying NetBackup for OpenStack
- Requirements
- NetBackup for OpenStack network considerations
- Preparing the installation
- Spinning up the NetBackup for OpenStack virtual machine
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- Prepare for deployment
- Updating the overcloud roles data file to include NetBackup for OpenStack services
- Additional Steps on NetBackup for OpenStack Appliance
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla
- Pushing NetBackup for OpenStack images to the local registry
- Installing on RHOSP
- Configuring NetBackup for OpenStack
- Post Installation Health-Check
- Uninstalling NetBackup for OpenStack
- Uninstalling from RHOSP
- Uninstalling from Ansible OpenStack
- Uninstalling from Kolla Openstack
- Uninstalling from RHOSP
- Upgrading NetBackup for OpenStack
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup primary server
- NetBackup for OpenStack protections
- Performing snapshots, backups, and restores of OpenStack
- About restores
- Required restore.json file for CLI
- About schedules
- Performing Backup Administration tasks
- Disaster recovery
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
Verifying the deployment
If the nbosdmapi container is not deployed on the controller node and the nbosdm container is not deployed on the compute node, perform the following steps:
Run the following command to render the templates with the modified
roles_data.yaml
file and perform the overcloud deployment./usr/share/openstack-tripleo-heat-templates/tools/process-templates.py -p /usr/share/openstack-tripleo-heat-templates -r /home/stack/templates/roles_data.yaml -n /home/stack/templates/default-network-isolation.yaml -o /home/stack/templates/generated-openstack-tripleo-heat-templates --safe
Specify the generated template path with the overcloud deploy command.
For example,
openstack overcloud deploy --stack overcloud --templates /home/stack/templates/generated-openstack-tripleo-heat-templates
If the containers are in restarting state or not listed by the following commands, your deployment is not done correctly.
On the controller node:
Ensure that the NetBackup for OpenStack datamover API and horizon containers are in a running state and no other NetBackup for OpenStack container is deployed on controller nodes. When the role for these containers is not controller, check on the respective nodes according to configured
roles_data.yaml
.[root@overcloud-controller-0 ~]# podman ps | grep nbos 26fcb9194566 rhospqa.ctlplane.localdomain:8787/nbosdmapi:10.4.1.1035-rhosp17.1 kolla_start 5 days ago Up 5 days ago nbosdmapi 094971d0f5a9 rhospqa.ctlplane.localdomain: 8787/nbos-horizon-plugin:10.4.1.1035-rhosp17.1 kolla_start 5 days ago Up 5 days ago horizon
On the compute node:
Ensure that the NetBackup for OpenStack datamover API and horizon containers are in a running state and no other NetBackup for OpenStack container is deployed on controller nodes. When the role for these containers is not controller, check on the respective nodes according to configured
roles_data.yaml
.[root@overcloud-controller-0 ~]# podman ps | grep nbos 26fcb9194566 rhospqa.ctlplane.localdomain:8787/nbosdmapi:10.4.1.1035-rhosp17.1 kolla_start 5 days ago Up 5 days ago nbosdmapi 094971d0f5a9 rhospqa.ctlplane.localdomain: 8787/nbos-horizon-plugin:10.4.1.1035-rhosp17.1 kolla_start 5 days ago Up 5 days ago horizon
On the node with Horizon service:
Ensure that the horizon container is in the running state.
Note:
The Horizon container is replaced with NetBackup for OpenStack Horizon container. This container has the latest OpenStack horizon + NetBackup for OpenStack horizon plug-in.
[root@overcloud-controller-0 ~]# podman ps | grep horizon 094971d0f5a9 rhospqa.ctlplane.localdomain: 8787/nbos-horizon-plugin:10.4.1.1035-rhosp17.1 kolla_start 5 days ago Up 5 days ago horizon