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
Clean NetBackup for OpenStack Datamover Service
The following steps need to be run on all nodes, which have the NetBackup for OpenStack Datamover service running. Those nodes can be identified by checking the roles_data.yaml for the role that contains the entry OS::TripleO::Services::nbosdm.
Once the role that runs the NetBackup for OpenStack Datamover API service has been identified, the following commands will clean the nodes from the service.
Warning:
Run all commands as root or user with sudo permissions.
Stop nbosdm container.
# For RHOSP16 onwards systemctl disable tripleo_nbosdm.service systemctl stop tripleo_nbosdm.service podman stop nbosdm
Remove nbosdm container.
# For RHOSP16 onwards podman rm nbosdm
Unmount NetBackup for OpenStack Backup Target on compute host.
## Following steps applicable for all supported RHOSP releases. # Check NetBackup for OpenStack backup target mount point mount | grep NetBackup # Unmount it -- If it's NFS (COPY UUID_DIR from your compute host using above command) umount /var/lib/nova/NetBackupOpenStack-mounts/<UUID_DIR> -- If it's S3 umount /var/lib/nova/NetBackupOpenStack-mounts # Verify that it's unmounted mount | grep NetBackup df -h | grep NetBackup # Remove mount point directory after verifying that backup target unmounted successfully. # Otherwise actual data from backup target may get cleaned. rm -rf /var/lib/nova/NetBackupOpenStack-mounts
Clean NetBackup for OpenStack Datamover service conf directory.
rm -rf /var/lib/config-data/puppet-generated/nbosdm/ rm /var/lib/config-data/puppet-generated/nbosdm.md5sum
Clean log directory of NetBackup for OpenStack Datamover service.
rm -rf /var/log/containers/nbosdm/