Please enter search query.
Search <book_title>...
Veritas NetBackup™ for OpenStack Administrator's Guide
Last Published:
2021-06-07
Product(s):
NetBackup (9.1)
- 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
- 1. Prepare for deployment
- 3] Update overcloud roles data file to include NetBackup for OpenStack services
- 7] Verify deployment
- 8] Additional Steps on NetBackup for OpenStack Appliance
- Installing on RHOSP
- Configuring NetBackup for OpenStack
- Post Installation Health-Check
- Uninstalling from RHOSP
- Install workloadmgr CLI client
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup Master Server
- NetBackup for OpenStack policies
- Performing backups and restores of OpenStack
- Required restore.json for CLI
- Configuring and starting a file search in Horizon
- Create a File Recovery Manager Instance
- 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
Providing the Metadata
Cloud-init uses two files for its metadata.
The first file is called meta-data and contains the information about the network configuration. Following is an example of this file.
[root@kvm]# cat meta-data instance-id: NetBackup for OpenStack network-interfaces: | auto ens3 iface ens3 inet static address 158.69.170.20 netmask 255.255.255.0 gateway 158.69.170.30 dns-nameservers 11.11.0.51 local-hostname: nbos-controller.domain.org
Warning:
The instance-id has to match the VM name in virsh.
The second file is called user-data and contains little scripts and information to set up for example the user passwords. Following is an example of this file.
[root@kvm]# cat user-data #cloud-config chpasswd: list: | root:password1 stack:password2 expire: False