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 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
About disaster recovery in NetBackup for OpenStack
In case of a disaster, perform the following steps for recovery:
To perform the disaster recovery for the different OpenStack cloud
- Perform the disaster recovery on NetBackup.
See the Disaster recovery chapter of the NetBackup Troubleshooting Guide.
- Reconfigure the NetBackup for OpenStack cluster.
- Import the protections from NetBackup for OpenStack VM.
nbosjm protection-import-to-new-cloud
The protections are listed as orphaned protections. The project and user of the OpenStack cloud A do not exist on the OpenStack cloud B.
- List the orphaned protections.
Orphaned protections are the protections that are no longer linked to an active tenant or user within the cloud. To identify and list all orphaned protections that do not have tenant_id or user_id associated with the current cloud environment, run the following command:
nbosjm protection-get-orphaned-protections-list [--migrate_cloud {True,False}]
--migrate_cloud Set to True if you want to list policies from other clouds as well. The default value is False.
- Assign protections to a new tenant or user.
nbosjm protection-reassign-protections [--old_tenant_ids <old_tenant_id>] [--new_tenant_id <new_tenant_id>] --protection_plan_id <protection_plan_id> [--user_id <user_id>] [--migrate_cloud {True,False}] [--map_file <map_file>]
--old_tenant_ids The IDs of the old tenants from which you want to assign the protections.
--new_tenant_id The ID of the new tenant to which you want to assign the protections.
--protection_plan_id The ID of the protection plan to which you want to assign the protections.
--user_id The user ID to which you want to assign the protections.
--migrate_cloud Set to True if you want to assign the protections from other clouds also. The default value is False
--map_file The file path with the file name of map file. The file format is YAML.
To perform the disaster recovery for the same OpenStack cloud
- Perform the disaster recovery on NetBackup.
See the Disaster recovery chapter of the NetBackup Troubleshooting Guide.
- Reconfigure the NetBackup for OpenStack cluster.
- Import protections from the NetBackup for OpenStack VM.
nbosjm protection-import
- Run the following command to see the status of the import job.
nbosjm get-protection-import-status
- After the protection import operation is complete, enable the global job scheduler.
nbosjm enable-global-job-scheduler