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
Troubleshooting for overcloud deployment failures
NetBackup for OpenStack components are deployed using the puppet scripts.
If the overcloud deployment fails, run the following command to get the list of errors.
(undercloud)$ openstack stack failures list <overcloud>--long
<overcloud> The name of the overcloud.
(undercloud)$ openstack stack list --nested --property status=FAILED
For more information, see the OpenStack documentation.
If the nbosdmapi container does not start or is in the restarting state, run the following commands to get the logs to troubleshoot.
podman logs nbosdmapi
tail -f /var/log/containers/nbosdmapi/nbosdmapi.log
If the nbosdm container does not start or is in the restarting state, run the following commands to get the logs to troubleshoot.
podman logs nbosdm
tail -f /var/log/containers/nbosdm/nbosdm.log