Veritas 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
- 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
Prerequisites for the disaster recovery process
This runbook assumes that the following is true:
OpenStack Cloud A and OpenStack Cloud B both have an active NetBackup for OpenStack installation with a valid license
OpenStack Cloud A and OpenStack Cloud B have free resources to host additional VMs
OpenStack Cloud A and OpenStack Cloud B have Tenants/Projects available that are the designated restore points for Tenant/Projects of the other side
Access to a user with the admin role permissions on domain level
One of the OpenStack clouds is down/lost
We assume that OpenStack Cloud A is down and the polices are getting restored into OpenStack Cloud B.
In the case of the usage of shared Tenant networks, beyond the floating IP, the following additional requirement is needed: All Tenant Networks, Routers, Ports, Floating IPs, and DNS Zones are created.