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
6] Deploy overcloud with NetBackup OpenStack environment
Use the following heat environment file and roles data file in overcloud deploy command:
nbos_env.yaml
roles_data.yaml
Use correct NetBackup OpenStack endpoint map file as per available Keystone endpoint configuration
Instead of tls-endpoints-public-dns.yaml file, use environments/nbos_env_tls_endpoints_public_dns.yaml
Instead of tls-endpoints-public-ip.yaml file, useenvironments/nbos_env_tls_endpoints_public_ip.yaml
Instead of tls-everywhere-endpoints-dns.yaml file, useenvironments/nbos_env_tls_everywhere_dns.yaml
To include new environment files use -e option and for roles data file use -r option.
An example of overcloud deploy command:
openstack overcloud deploy --templates \ -e /home/stack/templates/node-info.yaml \ -e /home/stack/templates/overcloud_images.yaml \ -e /home/stack/nbos-cfg-scripts/redhat-director-scripts/ <RHOSP_RELEASE_DIRECTORY>/environments/nbos_env.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/ enable-tls.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/ssl/ inject-trust-anchor.yaml \ -e /home/stack/nbos-cfg-scripts/redhat-director-scripts/<RHOSP_RELEASE_ DIRECTORY>/environments/nbos_env_tls_endpoints_public_dns.yaml \ --ntp-server 192.168.1.34 \ --libvirt-type qemu \ --log-file overcloud_deploy.log \ -r /home/stack/templates/roles_data.yaml