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
Mounting a snapshot
Mounting a snapshot to a File Recovery Manager provides read access to all the data that is located in the mounted snapshot.
Unmount any mounted snapshot once there is no further need to keep it mounted. Mounted snapshots will not be purged by the Retention policy.
It is possible to run the mounting process against any OpenStack instance. During this process the instance is restarted.
Always mount snapshots to File Recovery Manager instances only.
There are 2 possibilities to mount a snapshot in Horizon.
Through the snapshot list
To mount a snapshot through the snapshot list follow these steps:
On the Horizon console, navigate to NBOS Backups > Policies.
Identify the policy that contains the snapshot to mount.
Click the policy name to enter the policy overview.
Navigate to the Snapshots tab.
Identify the searched snapshot in the snapshot list.
From the drop-down under Actions column, select .
Click
.Choose the File Recovery Manager instance to mount to.
Click
to confirm.
Should all instances of the project be listed and there is a File Recovery Manager instance existing verify together with the administrator that the File Recovery Manager image has the following property set:
nbos_recovery_manager=yes
Through the File Search results
To mount a snapshot through the File Search results follow these steps:
On the Horizon console, navigate to NBOS Backups > Policies.
Identify the policy that contains the snapshot to mount.
Click the policy name to enter the policy overview.
Navigate to the File Search tab.
Do a File Search.
Identify the snapshot to be mounted.
Click
for the chosen snapshot.Choose the File Recovery Manager instance to mount to.
Click
.
Should all instances of the project be listed and there is a File Recovery Manager instance existing verify together with the administrator that the File Recovery Manager image has the following property set:
nbos_recovery_manager=yes
nbosjm snapshot-mount <snapshot_id> <mount_vm_id>
<snapshot_id> ID of the snapshot to be mounted
<mount_vm_id> ID of the File Recovery Manager instance to mount the snapshot to.