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
- 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 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
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
In-place restore
The in-place restore covers those use cases, where the virtual machine and its volumes are still available, but the data got corrupted or needs to rollback for other reasons.
It allows the user to restore only the data of a selected volume, which is part of a backup.
The in-place restore only works when the original virtual machine and the original volume are still available and connected. NetBackup for OpenStack is checks the status with the saved Object-ID.
The in-place restore will not create any new RHV resources. Use one of the other restore options if new volumes or virtual machines are required.
The in-place restore restarts the instance.
Note:
The in-place restore does not support a restore from the snapshot.
There are two possibilities to start an in-place restore.
Possibility 1: From the recovery point list
On the Horizon console, navigate to NBOS Backups > Protection.
Identify the protection that contains the recovery point to be restored.
Click the protection name to enter the protection overview.
Navigate to the Recovery Points tab.
Identify the recovery point to be restored.
From the drop-down under Actions column, select .
Configure the In-place restore as desired.
Click
.
Possibility 2: From the recovery point overview
On the Horizon console, navigate to NBOS Backups > Policies.
Identify the protection that contains the recovery point to be restored.
Click the protection name to enter the protection overview.
Navigate to the Recovery Points tab.
Identify the recovery point to be restored.
Click the recovery point name.
Navigate to the Restores tab.
Click Inplace Restore.
Configure the In-place restore as desired.
Click
.
nbosjm inplace-restore [--display-name <display-name>] [--display-description <display-description>] [--filename <filename>] <recovery_point_id>
<recovery_point_id> ID of the recovery point to restore from the backup copy.
--display-name Optional name for the restore.
--display-description Optional description for restore.
--filename Provide file path (relative or absolute) including file name. By default it reads the file
/home/stack/myansible/lib/python3.8/site-packages/nbosjmclient/input-files/restore_from_backup_copy.json
. You can use this file for reference or replace values into this file.