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 virtual machine
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- Prepare for deployment
- Updating the overcloud roles data file to include NetBackup for OpenStack services
- Additional Steps on NetBackup for OpenStack Appliance
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla
- 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
- Upgrading NetBackup for OpenStack
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup primary server
- NetBackup for OpenStack protections
- Performing snapshots, backups, and restores of OpenStack
- About restores
- Required restore.json file for CLI
- About schedules
- Performing Backup Administration tasks
- Disaster recovery
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
Other examples of NetBackup for OpenStack network integrations
Each OpenStack installation is different and so is the network configuration. There are endless possibilities of how to configure the OpenStack network and how to implement the NetBackup for OpenStack appliance into this network. The following three examples have been seen in production:
The first example is from a manufacturing company, which wanted to split the networks by function and decided to put the NetBackup for OpenStack backup target on the internal network as the backup and recovery function was identified as an OpenStack internal solution. This example looks complex but integrates NetBackup for OpenStack as recommended.
The second example is from a financial institute that wanted to be sure that the OpenStack Users have no direct uncontrolled network access to the OpenStack infrastructure. Following this example requires additional work as the internal HA-Proxy needs to be configured to correctly translate the API calls towards the NetBackup for OpenStack
The third example is from a service company that was forced to treat NetBackup for OpenStack as an external 3rd party solution, as we require a virtual machine running outside of OpenStack. This kind of network configuration requires good planning on the NetBackup for OpenStack endpoints and firewall rules.