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
One-Click Restore
The One-Click Restore brings back all VMs from the snapshot in the same state as they were backed up. They will:
be located in the same cluster in the same data center
use the same storage domain
connect to the same network
have the same flavor
The user can't change any Metadata.
The One-Click Restore requires that the original VMs that have been backed up are deleted or otherwise lost. Even if one VM is still running, the One-Click Restore fails.
The One-Click Restore automatically updates the policy to protect the restored VMs.
There are two possibilities to start a One-click Restore.
Possibility 1: From the snapshot list
On the Horizon console, navigate to NBOS Backups > Policies.
Identify the policy that contains the snapshot to be restored.
Click the policy name to enter the policy overview.
Navigate to the Snapshots tab.
Identify the snapshot to be restored.
Click
in the same line as the identified snapshot.(Optional) Provide the name and description.
Click
.
Possibility 2: From the snapshot overview
On the Horizon console, navigate to NBOS Backups > Policies.
Identify the policy that contains the snapshot to be restored.
Click the policy name to enter the policy overview.
Navigate to the Snapshots tab.
Identify the snapshot to be restored.
Click the snapshot name.
Navigate to the Restores tab.
Click
.(Optional) Provide a name/description
Click
.
nbosjm snapshot-oneclick-restore [--display-name <display-name>] [--display-description <display-description>] <snapshot_id>
<snapshot_id> ID of the snapshot to restore.
--display-name <display-name> Optional name for the restore.
--display-description <display-description> Optional description for restore.