Please enter search query.
Search <book_title>...
NetBackup™ for OpenStack Administrator's Guide
Last Published:
2024-09-29
Product(s):
NetBackup & Alta Data Protection (10.5)
- 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
Creating a file recovery manager instance
Create an OpenStack image using a Linux-based cloud image like Ubuntu or RHEL 8.2 or later. Add the following metadata parameters and upload the cloud image to the Glance.
--file <File Manager Image Path> \ --container-format bare \ --disk-format qcow2 \ --public \ --property hw_qemu_guest_agent=yes \ --property nbos_recovery_manager=yes \ --property hw_disk_bus=virtio \ nbos-file-manager
Spin up an instance from that image. It is recommended to have at least 8GB RAM for the mount operation. A large backup copy may require more RAM.
Steps to apply on RHEL 8.2 or later cloud images
- Install and activate qemu-guest-agent.
- Edit /etc/sysconfig/qemu-ga and remove the following from the BLACKLIST_RPC section.
guest-file-read guest-file-write guest-file-open guest-file-close
- Disable SELINUX in /etc/sysconfig/selinux.
SELINUX=disabled
- Install python3.
yum install python3
- Install lvm2.
yum install lvm2
- Restart the instance.
Steps to apply on Ubuntu cloud images
- Install and activate qemu-guest-agent.
- Edit
/etc/init.d/qemu-guest-agent
and add Freeze-Hook file path in daemon args.DAEMON_ARGS="-F /etc/qemu/fsfreeze-hook"
- Generate
qemu-ga.conf
file.qemu-ga -D > /etc/qemu/qemu-ga.conf
- Append following line to the file.
fsfreeze-hook=/etc/qemu/fsfreeze-hook
- Restart the qemu-guest-agent service.
- Install Python 3.
apt-get install python3
- Restart the instance.