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 VM
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- Prepare for deployment
- Updating the overcloud roles data file to include NetBackup for OpenStack services
- Verifying the deployment
- Additional Steps on NetBackup for OpenStack Appliance
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla Ussuri
- 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
- Install nbosjm CLI client
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup Master Server
- NetBackup for OpenStack policies
- Performing backups and restores of OpenStack
- About restores
- Required restore.json for CLI
- Configuring and starting a file search in Horizon
- Performing Backup Administration tasks
- NBOS Backup Admin Area
- Policy Attributes
- Policy Quotas
- Managing Trusts
- Policy import and migration
- Disaster Recovery
- Example runbook for disaster recovery using NFS
- Disaster recovery of a single policy
- Copy the policy directories to the configured NFS Volume
- Make the Mount-Paths available
- Reassign the policy
- Restore the policy
- Clean up
- Disaster recovery of a complete cloud
- Reconfigure the Target NetBackup for OpenStack installation
- Make the Mount-Paths available
- Reassign the policy
- Restore the policy
- Reconfigure the Target NetBackup for OpenStack installation back to the original one
- Clean up
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
Changing the nova user ID on the NetBackup for OpenStack Nodes
NetBackup for OpenStack VM uses the nova user ID and group ID 162:162 by default. Kolla Ussuri OpenStack is not always nova user ID 162 on nova-compute containers. The nova user ID on the NetBackup for OpenStack VM nodes must be same as the nova-compute containers. If nova ID is not 162:162, perform the following steps on all NetBackup for OpenStack VM nodes.
Before you perform the following steps, verify that the user ID and group ID is not used by any other services on NetBackup for OpenStack VM. For example, If nova ID on compute node is 997, verify that user ID is not used by any other services on NetBackup for OpenStack VM. If 997 user ID is assigned to rabbitmq
and 997 group ID is assigned to SSH
service on NetBackup for OpenStack VM, you must free this ID.
#cat /etc/passwd | grep 997 #pid 997 #ps -ef | grep 997 #usermod -u 900 rabbitmq #cat /etc/group | grep 997 #groupmod -g 901 ssh_keys #reboot
Go to the directory
/home/stack
.Assign the executable permissions to
nova_userid.sh
file.#chmod +x nova_userid.sh
Edit script to use the correct nova ID.
Execute the script.
#./nova_userid.sh
Verify that nova user and group ID has changed to the desired value.
#id nova