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
Backup target access required by NetBackup for OpenStack
The NetBackup for OpenStack solution uses backup target storage to securely place the backup data. NetBackup for OpenStack divides its backup data into two parts:
Metadata
Volume Disk Data
The first type of data is generated by the NetBackup for OpenStack appliance through communicating with the OpenStack Endpoints. All metadata that is stored together with a backup is written by the NetBackup for OpenStack Appliance to the backup target in the JSON format.
The second type of data is generated by the NetBackup for OpenStack datamover service running on the compute nodes. The nbosdm service reads the Volume Data from the Cinder or Nova storage and transferring this data as QCOW2 image to the backup target. Each datamover service is hereby responsible for the virtual machines running on its compute node.
The network requirements are therefore:
The NetBackup for OpenStack appliance needs access to the backup target.
Every compute node needs access to the backup target.