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
Policy import and migration
Each NetBackup for OpenStack policy has a dedicated owner. The ownership of a policy is defined by:
OpenStack User: The OpenStack User-ID assigned to a policy.
OpenStack Project: The OpenStack Project-ID is assigned to a policy.
OpenStack Cloud: The NetBackup for OpenStack Serviceuser-ID assigned to a policy.
OpenStack users can update the user ownership of a policy by modifying the policy. This ownership ensures that only the owners of a policy are able to work with it.
OpenStack Administrators can reassign policies or reimport policies from older NetBackup for OpenStack installations.
Note:
The policy-reassign command is not supported in NetBackup for OpenStack 10.4.