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
Set up an external database
NetBackup for OpenStack allows the use of an external MySQL or MariaDB database.
This database needs to be prepared by creating the empty nbosjm database, creating the nbosjm user and setting the right permissions. An example command to create this database would be:
create database nbosjm_auto; CREATE USER 'nbos'@'localhost' IDENTIFIED BY 'password'; GRANT ALL PRIVILEGES ON nbosjm_auto.* TO 'nbos'@'10.10.10.67' IDENTIFIED BY 'password';
Provide the connection string to the NetBackup for OpenStack configurator.
mysql://nbos:password@10.10.10.67/nbosjm_auto?charset=utf8
This value can only be set upon an initial configuration of the NetBackup for OpenStack solution.
When the Cluster has been configured to use the internal database, then the connection string will not be shown in the next configuration attempt.
In the case of an external database, the connection string is shown but is not editable.