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 VM
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- Prepare for deployment
- Updating the overcloud roles data file to include NetBackup for OpenStack services
- Verifying the deployment
- Additional Steps on NetBackup for OpenStack Appliance
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla Ussuri
- 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
- Install nbosjm CLI client
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup Master Server
- NetBackup for OpenStack policies
- Performing backups and restores of OpenStack
- About restores
- Required restore.json for CLI
- Configuring and starting a file search in Horizon
- Performing Backup Administration tasks
- NBOS Backup Admin Area
- Policy Attributes
- Policy Quotas
- Managing Trusts
- Policy import and migration
- Disaster Recovery
- Example runbook for disaster recovery using NFS
- Disaster recovery of a single policy
- Copy the policy directories to the configured NFS Volume
- Make the Mount-Paths available
- Reassign the policy
- Restore the policy
- Clean up
- Disaster recovery of a complete cloud
- Reconfigure the Target NetBackup for OpenStack installation
- Make the Mount-Paths available
- Reassign the policy
- Restore the policy
- Reconfigure the Target NetBackup for OpenStack installation back to the original one
- Clean up
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
Editing globals.yml to set NetBackup for OpenStack parameters
Edit /etc/kolla/globals.yml file to configure NetBackup for OpenStack backup target and build details. You can find the NetBackup for OpenStack related parameters at the end of globals.yml file. You must configure the information such as NetBackupOpenStack tag, backup target type, and backup target details.
Following is the list of parameters that you can edit.
Table: globals.yml parameters
Parameter | Description |
---|---|
NetBackupOpenStack_tag | Container tags. |
horizon_image_full | By default, the NetBackup for OpenStack Horizon container does not get deployed. Uncomment this parameter to deploy NetBackup for OpenStack Horizon container instead of Openstack Horizon container. |
NetBackupOpenStack_docker_username | Default docker user of NetBackup for OpenStack. (read permission only) |
NetBackupOpenStack_docker_password | Password for default docker user of NetBackup for OpenStack. |
NetBackupOpenStack_docker_registry | Local registry name, which contains NetBackup for OpenStack component images. |
NetBackupOpenStack_backup_target |
|
NetBackupOpenStack_nfs_shares | NFS share path. For example: 192.168.145.110:/nfs/nbos |
NetBackupOpenStack_nfs_options | Configure NFS mount options. |
NetBackupOpenStack_s3_access_key | Valid for amazon_s3 and ceph_s3. |
NetBackupOpenStack_s3_secret_key | Valid for amazon_s3 and ceph_s3. |
NetBackupOpenStack_s3_region_name | Valid for amazon_s3 and ceph_s3. If s3 storage does not have region parameter, keep the default value. |
NetBackupOpenStack_s3_bucket_name | A name of the s3 bucket. Valid for amazon_s3 and ceph_s3 |
NetBackupOpenStack_s3_endpoint_url | s3 endpoint URL. Valid for ceph_s3 only. |
NetBackupOpenStack_s3_ssl_enabled | Valid for ceph_s3 only. Set to true for SSL enabled S3 endpoint URL. |
NetBackupOpenStack_s3_ssl_cert_file_name | Valid for ceph_s3 only with SSL enabled and self-signed certificates
OR issued by a private authority.
In this case, copy the ceph s3 CA chain file to |
NetBackupOpenStack_copy_ceph_s3_ssl_cert | Valid for ceph_s3 only Set to True when: SSL enabled with self-signed certificates or issued by a private authority. |