Veritas 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
- 1. Prepare for deployment
- 3] Update overcloud roles data file to include NetBackup for OpenStack services
- 7] Verify deployment
- 8] Additional Steps on NetBackup for OpenStack Appliance
- Installing on RHOSP
- Configuring NetBackup for OpenStack
- Post Installation Health-Check
- Uninstalling from RHOSP
- Install workloadmgr CLI client
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup Master Server
- NetBackup for OpenStack policies
- Performing backups and restores of OpenStack
- Required restore.json for CLI
- Configuring and starting a file search in Horizon
- Create a File Recovery Manager Instance
- 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
4] Prepare NetBackup for OpenStack container images
Warning:
All commands need to be run as user "stack".
NetBackup for OpenStack uses the local registry on the undercloud to house packages.
NetBackup for OpenStack provides a shell script, which pushes the containers to the undercloud and updates the nbos_env.yaml.
cd /home/stack/nbos-cfg-scripts/redhat-director-scripts/<RHOSP_RELEASE_DIRECTORY>//scripts
sudo ./prepare_nbos_images.sh <UNDERCLOUD_REGISTRY_HOSTNAME> <IMAGE_SOURCE_FOLDER>
## Run following command to find 'UNDERCLOUD_REGISTRY_HOSTNAME'.
In the following example 'nbos-undercloud' is <UNDERCLOUD_REGISTRY_HOSTNAME>
$ openstack tripleo container image list | grep keystone | docker://nbos-undercloud:8787/rhosp-rhel8/openstack-keystone:16.0-82 | | docker://nbos-undercloud:8787/rhosp-rhel8/openstack-barbican-keystone-listener:16.0-84
'CONTAINER_TAG' format for RHOSP16: <NBOS_VERSION>-rhosp16
'CONTAINER_TAG' format for RHOSP16.1: <NBOS_VERSION>-rhosp16.1
Example,
sudo ./prepare_nbos_images.sh nbos-undercloud 9.0.1017-rhosp16.1 /home/stack/nbos/nbos-rhosp16.1-9.0.1017
The changes can be verified using the following commands.
(undercloud) [stack@nbos-undercloud scripts]$ sudo podman images | grep 9.0.1017-rhosp16.1 localhost/nbos-horizon-plugin 9.0.1017-rhosp16.1 8705f72da6d4 5 days ago 1.16 GB localhost/nbosdmapi 9.0.1017-rhosp16.1 2da0be5dcacb 5 days ago 1.46 GB localhost/nbosdm 9.0.1017-rhosp16.1 d6e1168faae2 5 days ago 2.97 GB ----------------------------------------------------------------------------------------------------- (undercloud) [stack@host scripts]$ grep 'Image' ../environments/nbos_env.yaml DockerNbosdmImage: nbos-undercloud:8787/nbosdm:9.0.1017-rhosp16.1 DockerNbosdmapiImage: nbos-undercloud:8787/nbosdmapi:9.0.1017-rhosp16.1 ContainerHorizonImage: nbos-undercloud:8787/nbos-horizon-plugin: 9.0.1017-rhosp16.1