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
OpenStack Quotas
To protect the Cinder volumes, NetBackup for OpenStack creates Cinder snapshots and additional temporary Cinder volumes. The tenant administrator must configure the OpenStack quotas accordingly to provision adequate snapshots and the volumes that full and incremental backups need. The temporary volumes are used to generate disk map information per disk, and to calculate incrementally changed data.
Volume quota requirement is based on the total number of disks getting backed up simultaneously though one or more protections. As the number of simultaneous backups increases, more volume quota is required. Tenant administrator can determine the volume quota by calculating the sum of the total number of instances and the total number of disks that are attached to those instances. For example, you want to protect 10 instances and each instance has two disks attached. To protect these instances simultaneously through one or more protections, the required volume quota is 30.