Please enter search query.
Search <book_title>...
NetBackup™ for OpenStack Administrator's Guide
Last Published:
2024-09-29
Product(s):
NetBackup & Alta Data Protection (10.5)
- Introduction
- Deploying NetBackup for OpenStack
- Requirements
- NetBackup for OpenStack network considerations
- Existing endpoints in OpenStack
- OpenStack endpoints required by NetBackup for OpenStack
- Recommendation: Provide access to all OpenStack Endpoint types
- Backup target access required by NetBackup for OpenStack
- Example of a typical NetBackup for OpenStack network integration
- Other examples of NetBackup for OpenStack network integrations
- Preparing the installation
- Spinning up the NetBackup for OpenStack virtual machine
- About NetBackup for OpenStack backup target types
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- Prepare for deployment
- Uploading the NetBackup for OpenStack puppet module
- Updating the overcloud roles data file to include NetBackup for OpenStack services
- Preparing the NetBackup for OpenStack container images
- Providing the environment details in nbos_env.yaml
- Deploying the overcloud with NetBackup OpenStack environment
- Verifying the deployment
- Additional Steps on NetBackup for OpenStack Appliance
- Troubleshooting for overcloud deployment failures
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla
- Changing the nova user ID on the NetBackup for OpenStack Nodes
- Copying the NetBackup for OpenStack deployment scripts
- Copying the NetBackup for OpenStack deployment scripts to Kolla-ansible deploy scripts
- Pushing NetBackup for OpenStack images to the local registry
- Editing globals.yml to set NetBackup for OpenStack parameters
- Enabling the NetBackup for OpenStack backup mount feature
- Pulling the NetBackup for OpenStack container images
- Deploying the NetBackup for OpenStack components
- Verifying the NetBackup for OpenStack deployment
- Installing on RHOSP
- Configuring NetBackup for OpenStack
- Resource throttling in NetBackup for OpenStack
- Post Installation Health-Check
- Uninstalling NetBackup for OpenStack
- Uninstalling from RHOSP
- Clean NetBackup for OpenStack datamover API service
- Clean NetBackup for OpenStack datamover service
- Clean NetBackup for OpenStack haproxy resources
- Clean NetBackup for OpenStack Keystone resources
- Clean NetBackup for OpenStack database resources
- Revert overcloud deploy command
- Revert back to original RHOSP Horizon container
- Destroy the NetBackup for OpenStack virtual machine cluster
- Uninstalling from Ansible OpenStack
- Uninstall NetBackup for OpenStack Services
- Destroy NetBackup for OpenStack datamover API container
- Clean openstack_user_config.yml
- Remove NetBackup for OpenStack haproxy settings in user_variables.yml
- Remove NetBackup for OpenStack datamover API inventory file
- Remove NetBackup for OpenStack datamover API service endpoints
- Delete NetBackup for OpenStack datamover API database and user
- Remove nbosdmapi rabbitmq user from rabbitmq container
- Clean haproxy
- Remove certificates from Compute nodes
- Destroy the NetBackup for OpenStack virtual machine cluster
- Uninstalling from Kolla Openstack
- Cleaning NetBackupOpenStack_datamover_api container
- Cleaning NetBackupOpenStack_datamover container
- Cleaning haproxy of NetBackupOpenStack datamover API
- Cleaning Kolla Ansible deployment procedure
- Reverting to original Horizon container
- Cleaning Keystone resources
- Cleaning NetBackup for OpenStack database resources
- Destroy the NetBackup for OpenStack virtual machine cluster
- Uninstalling from RHOSP
- Install nbosjm CLI client
- About log rotation in NetBackup for OpenStack
- Upgrading NetBackup for OpenStack
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup primary server
- NetBackup for OpenStack protections
- Performing snapshots, backups, and restores of OpenStack
- About recovery points
- List of recovery points
- Creating a snapshot
- Snapshot and backup overview
- Expire recovery points
- Cleaning up the volume snapshots
- About restores
- List of Restores
- Restores overview
- Delete a restore
- Cancel a restore
- One-click restore
- Selective restore
- In-place restore
- Required restore.json file for CLI
- About backup mount
- Creating a file recovery manager instance
- Mounting a backup copy
- Accessing the file recovery manager
- Identifying mounted backups
- Unmounting a backup
- About schedules
- About activating the email notifications
- Performing Backup Administration tasks
- Disaster recovery
- Troubleshooting
- General Troubleshooting Tips
- Using the nbosjm CLI tool on the NetBackup for OpenStack Appliance
- Health check of NetBackup for OpenStack
- Important log files
- Troubleshooting NBOSDM container in offline state due to unavailable mount point
- After restore of the Windows instance, the disk is in an offline state
- Selective restore from snapshot copy fails
- A backup fails due to an old nova ID in the universal share path
- Using the NetBackup support utility in NetBackup for OpenStack
- Cannot create volumes if the metadata size for physical volume and volume group is small
- NBOSVM configuration fails if DNS server cannot resolve IP address or IP address is wrong
- Error when storage unit is created with multiple storage servers
- Snapshot job fails if the OpenStack image is not accessible to the OpenStack user
- One-click restore fails if the subnet attached to the instance is not accessible to the OpenStack user
- The NBOSVM configurator UI does not detect the primary server
- A recovery point name is updated to a default name
- NBOS Backups and NBOS Backup Admin tabs disappear from Horizon UI after stack is updated
- The protection creation fails on the Horizon UI
- The NetBackup for OpenStack services do not start after NBOSVM is restarted
- The NBOSVM is not able to communicate with the nbosdmapi on the controller node
- Troubleshooting the OpenStack Keystone authentication failure
- Index
Verify that the nbosdm services are up and running
The nbosdm service is the datamover that got installed on all compute nodes. Check its status after the installation.
[root@upstreamcompute1 ~]# systemctl status tripleo-nbosdm.service
● tripleo_nbosdm.service - nbosdm container
Loaded: loaded (/etc/systemd/system/tripleo_nbosdm.service; enabled;
vendor preset: disabled)
Active: active (running) since Wed 2020-06-10 10:07:28 EDT; 1 day 19h ago
Main PID: 10384 (python)
Tasks: 21
CGroup: /system.slice/tripleo_nbosdm.service
└─10384 /usr/bin/python /usr/bin/nbosdm --config-file=/etc...
Jun 12 03:15:33 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 03:15:33 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 03:16:11 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 03:16:31 upstreamcompute1 sudo[13977]: nova : TTY=unknown ;
PWD=/...n
Jun 12 03:16:33 upstreamcompute1 sudo[14004]: nova : TTY=unknown ;
PWD=/ ...
Jun 12 05:15:33 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 05:15:33 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 05:16:11 upstreamcompute1 python[10384]: libvirt: QEMU Driver
error :...d
Jun 12 05:16:29 upstreamcompute1 sudo[23356]: nova : TTY=unknown ;
PWD=/...n
Jun 12 05:16:32 upstreamcompute1 sudo[23422]: nova : TTY=unknown ;
PWD=/ ...
Hint: Some lines were ellipsized, use -l to show in full.