Veritas NetBackup™ for OpenStack Administrator's Guide
- Introduction
- Deploying NetBackup for OpenStack
- Requirements
- NetBackup for OpenStack network considerations
- Existing endpoints in OpenStack
- OpenStack endpoints required by NetBackup for OpenStack
- Recommendation: Provide access to all OpenStack Endpoint types
- Backup target access required by NetBackup for OpenStack
- Example of a typical NetBackup for OpenStack network integration
- Other examples of NetBackup for OpenStack network integrations
- Preparing the installation
- Spinning up the NetBackup for OpenStack VM
- Installing NetBackup for OpenStack Components
- Installing on RHOSP
- 1. Prepare for deployment
- 2] Upload NetBackup for OpenStack puppet module
- 3] Update overcloud roles data file to include NetBackup for OpenStack services
- 4] Prepare NetBackup for OpenStack container images
- 5] Provide environment details in nbos_env.yaml
- 6] Deploy overcloud with NetBackup OpenStack environment
- 7] Verify deployment
- 8] Additional Steps on NetBackup for OpenStack Appliance
- 9] Troubleshooting for overcloud deployment failures
- Installing on RHOSP
- Configuring NetBackup for OpenStack
- Post Installation Health-Check
- Uninstalling from RHOSP
- Clean NetBackup for OpenStack Datamover API service
- Clean NetBackup for OpenStack Datamover Service
- Clean NetBackup for OpenStack haproxy resources
- Clean NetBackup for OpenStack Keystone resources
- Clean NetBackup for OpenStack database resources
- Revert overcloud deploy command
- Revert back to original RHOSP Horizon container
- Destroy the NetBackup for OpenStack VM Cluster
- Install workloadmgr CLI client
- Configuring NetBackup OpenStack Appliance
- Configuring NetBackup Master Server
- NetBackup for OpenStack policies
- Performing backups and restores of OpenStack
- About snapshots
- List of snapshots
- Creating a snapshot
- Snapshot overview
- Delete snapshots
- Snapshot Cancel
- About restores
- List of Restores
- Restores overview
- Delete a Restore
- Cancel a Restore
- One-Click Restore
- Selective Restore
- Inplace Restore
- Required restore.json for CLI
- About file search
- Navigating to the file search tab in Horizon
- Configuring and starting a file search in Horizon
- Start the File Search and retrieve the results in Horizon
- Doing a CLI File Search
- About snapshot mount
- Create a File Recovery Manager Instance
- Mounting a snapshot
- Accessing the File Recovery Manager
- Identifying mounted snapshots
- Unmounting a snapshot
- About schedulers
- Disable a schedule
- Enable a schedule
- Modify a schedule
- About email notifications
- Requirements to activate email Notifications
- Activate/Deactivate the email Notifications
- 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
- Scenario
- Prerequisites for the disaster recovery process
- Disaster recovery of a single policy
- Copy the policy directories to the configured NFS Volume
- Make the Mount-Paths available
- Reassign the policy
- Add admin-user to required domains and projects
- Discover orphaned policies from NFS-Storage of Target Cloud
- List available projects on Target Cloud in the Target Domain
- List available users on the Target Cloud in the Target Project that have the right backup trustee role
- Reassign the policy to the target project
- Verify that the policy is available at the desired target_project
- 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
- Add admin-user to required domains and projects
- Discover orphaned policies from NFS-Storage of Target Cloud
- List available projects on Target Cloud in the Target Domain
- List available users on the Target Cloud in the Target Project that have the right backup trustee role
- Reassign the policy to the target project
- Verify that the policy is available at the desired target_project
- Restore the policy
- Reconfigure the Target NetBackup for OpenStack installation back to the original one
- Clean up
- Troubleshooting
- Index
Information required in instances
This part contains all information about all instances that are part of the snapshot to restore and how they are to be restored.
Even when VMs are not to be restored, they are required to be inside the restore.json to allow a clean execution of the restore.
Each instance requires the following information
id Original ID of the instance
include <True/False> Set True when the instance shall be restored
All further information is only required, when the instance is part of the restore.
name New name of the instance
availability_zone Nova Availability Zone the instance shall be restored into. Leave empty for "Any Availability Zone"
Nics List of the OpenStack Neutron ports that shall be attached to the instance. Each Neutron Port consists of:
id ID of the Neutron port to use
mac_address Mac Address of the Neutron port
ip_address IP address of the Neutron port
network Network the port is assigned to. Contains the following information:
id ID of the network the Neutron port is part of
subnetSubnet the port is assigned to. Contains the following information:
id ID of the network the Neutron port is part of
To use the next free IP available, set Nics to an empty list [ ]
Using an empty list for Nics combined with the Network Topology Restore, the restore job sets the original IP address of the instance.
vdisks List of all volumes that are part of the instance. Each volume requires the following information:
id Original ID of the volume.
new_volume_type The volume type to use for the restored volume. Leave empty for Volume Type None.
availability_zone The Cinder Availability Zone to use for the volume. The default Availability Zone of Cinder is Nova.
flavor Defines the Flavor to use for the restored instance. Contains the following information:
ram How much RAM the restored instance will have (in MB).
ephemeralHow big the ephemeral disk of the instance will be (in GB).
vcpus How many vcpus the restored instance will have available.
swap How big the Swap of the restored instance will be (in MB). Leave empty for none.
disk Size of the root disk the instance will boot with.
id ID of the flavor that matches the provided information.
Warning:
The root disk needs to be at least as big as the root disk of the backed up instance.
The following example describes a single instance with all values.
'instances':[
{
'name':'cdcentOS-1-selective',
'availability_zone':'US-East',
'nics':[
{
'mac_address':'fa:16:3e:00:bd:60',
'ip_address':'192.168.0.100',
'id':'8b871820-f92e-41f6-80b4-00555a649b4c',
'network':{
'subnet':{
'id':'2b1506f4-2a7a-4602-a8b9-b7e8a49f95b8'
},
'id':'d5047e84-077e-4b38-bc43-e3360b0ad174'
}
}
],
'vdisks':[
{
'id':'4cc2b474-1f1b-4054-a922-497ef5564624',
'new_volume_type':'ceph',
'availability_zone':'nova'
}
],
'flavor':{
'ram':2048,
'ephemeral':0,
'vcpus':1,
'swap':'',
'disk':20,
'id':'2'
},
'include':True,
'id':'890888bc-a001-4b62-a25b-484b34ac6e7e'
}
]