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
In-place restore
The In-place restore covers those use cases, where the VM 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 VM and the original volume are still available and connected. NetBackup for OpenStack is checking this by the saved Object-ID.
The In-place restore will not create any new RHV resources. Please use one of the other restore options if new volumes or VMs are required.
The In-place restore restarts the instance.
There are two possibilities to start an In-place 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.
From the drop-down under Actions column, select .
Configure the In-place restore as desired.
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 Inplace Restore.
Configure the In-place restore as desired.
Click
.
nbosjm snapshot-inplace-restore [--display-name <display-name>] [--display-description <display-description>] [--filename <filename>] <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.
--filename <filename> Provide file path(relative or absolute) including file name , by default it will read file: /usr/lib/python2.7/site-packages/nbosjmclient/input-files/restore.json .You can use this for reference or replace values into this file.