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
Loading the images from tar and pushing them to the local repository
Ensure that the proper tar files of nbosdmapi, nbosdm and nbos-horizon-plugin are available on the deployment node.
NBOS_Version | NetBackup for OpenStack version number. |
kolla-base-distro | CentOS or Ubuntu |
kolla-install-type | Binary or source |
FQDN | Hostname of kolla deployment server. |
To load the images from tar and push them to the local repository
- Load NetBackup for OpenStack images from the tar file.
Run the following commands:
nbosdmapi
docker load --input nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri.tar
For example,
docker load --input nbosdmapi-ubuntu-9.1.2.20211021104525-ussuri.tar
nbosdm
docker load i-input nbosdm-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri.tar
For example,
docker load --input nbosdm-ubuntu-9.1.2.20211021104525-ussuri.tar
nbos-horizon-plugin
docker load --input nbos-horizon-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri.tar
For example,
docker load --input nbos-horizon-plugin-source-ubuntu-9.1.2.20211021104525-ussuri.tar
- Tag the NetBackup for OpenStack images with appropriate name.
Run the following commands:
nbosdmapi
docker tag nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri nbos/nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
docker tag nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri FQDN:5001/nbos/nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
Examples,
docker tag nbosdmapi-ubuntu:9.1.2.20211021104525-ussuri nbos/nbosdmapi-ubuntu:9.1.2.20211021104525-ussuri
docker tag nbosdmapi-ubuntu:9.1.2.20211021104525-ussuri deployment-vm.vxindia.veritas.com:5001/nbos/nbosdmapi-ubuntu:9.1.2.20211021104525-ussuri
nbosdm
docker tag nbosdm-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri nbos/nbosdm-<kolla-base-distro>:<NBOS_version>-ussuri
docker tag nbosdm-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri FQDN:5001/nbos/nbosdm-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
Examples,
docker tag nbosdm-ubuntu:9.1.2.20211021104525-ussuri nbos/nbosdm-ubuntu:9.1.2.20211021104525-ussuri
docker tag nbosdm-ubuntu:9.1.2.20211021104525-ussuri deployment-vm.vxindia.veritas.com:5001/nbos/nbosdm-ubuntu:9.1.2.20211021104525-ussuri
nbos-horizon-plugin
docker tag nbos-horizon-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri nbos/nbos-horion-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
docker tag nbos-horizon-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri FQDN:5001/nbos/nbos-horizon-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
Examples,
docker tag nbos-horizon-plugin-source-ubuntu:9.1.2.20211021104525-ussuri nbos/nbos-horizon-plugin-source-ubuntu:9.1.2.20211021104525-ussuri
docker tag nbos-horizon-plugin-source-ubuntu:9.1.2.20211021104525-ussuri deployment-vm.vxindia.veritas.com:5001/nbos/nbos-horizon-plugin-source-ubuntu:9.1.2.20211021104525-ussuri
- Push the tagged image to local registry.
Run the following commands:
nbosdmapi
docker push FQDN:5001/nbos/nbosdmapi-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
For example,
docker push deployment-vm.vxindia.veritas.com:5001/nbos/nbosdmapi-ubuntu:9.1.2.20211021104525-ussuri
nbosdm
docker push FQDN:5001/nbos/nbosdm-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
For example,
docker push deployment-vm.vxindia.veritas.com:5001/nbos/nbosdm-ubuntu:9.1.2.20211021104525-ussuri
nbos-horizon-plugin
docker push FQDN:5001/nbos/nbos-horizon-plugin-{{ kolla-install-type }}-{{ kolla-base-distro }}:{{ NBOS_version }}-ussuri
For example,
docker push deployment-vm.vxindia.veritas.com:5001/nbos/nbos-horizon-plugin-source-ubuntu:9.1.2.20211021104525-ussuri
- Add the insecure-registries entry in
/etc/docker/daemon.json
on all controller and compute nodes.Open the daemon.json file and make the changes as follows:
cat /etc/docker/daemon.json { "log-opts": { "max-file": "5", "max-size": "50m" }, "registry-mirrors": [ "http://<deployment node ip>:4000" ], "insecure-registries": [ "FQDN:5001" ] }
- Add the insecure-registries entry in
/etc/docker/daemon.json
on deployment nodes.If
/etc/docker/
directory does not exist, create it and createdaemon.json
file.Open the daemon.json file and make the changes as follows:
cat /etc/docker/daemon.json { "insecure-registries":["FQDN:5001"] }
- Restart the docker.
systemctl restart docker
- Verify that the specified images are pushed in the registry.
Controller and compute nodes: curl -X GET http://FQDN:5001/v2/_catalog
Deployment node: docker info
For example,
curl -X GET http://deployment-vm.vxindia.veritas.com:5001/v2/_catalog
Sample output:
curl -X GET http://deployment-vm.vxindia.veritas.com: 5001/v2/_catalog //Output should look like below: {"repositories":["nbos/nbos-horizon-plugin-source-centos", "nbos/nbosdm-centos","nbos/nbosdmapi-centos"]}