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
NetBackup for OpenStack Datamover service logs on Ansible OpenStack
Following are the NetBackup for OpenStack Datamover service logs on Ansible OpenStack:
nbosdmapi log
The log for the NetBackup for OpenStack Datamover API service is located on the nodes, typically controller, where the NetBackup for OpenStack Datamover API container is running. Log in to the nbosdmapi container using lxc-attach command.
lxc-attach -n controller_nbosdmapi_container-a11984bf
The log file is then located under:
/var/log/nbosdmapi/nbosdmapi.log
nbosdm log
The log for the NetBackup for OpenStack Datamover service is typically located on the compute nodes and the logs can be found here:
/var/log/nbosdm/nbosdm.log
In case of S3 being used in the log for the S3 Fuse plug-in that is located on the same nodes under:
/var/log/nbos-object-store/nbos-object-store.log
For VxMS-supported Linux file systems, VxMS logs for the incremental backups are stored at the following location: /usr/openv/netbackup/logs/vxms/
VxMS log level is defined in /usr/openv/netbackup/bp.conf file and it is configured to 3 by default.
VXMS_VERBOSE = 3
You can configure the log level from 0 to 5. Higher number results in more verbose logs.
Note:
VxMS log may take significant disk space when the log verbosity is set to high. Ensure that you clean up the VxMS log files periodically to avoid any disk space-related issues.
Table: VxMS log levels
Log level | Description |
---|---|
0 | No logging |
1 | Error logging |
2 | Level 1 + warning messages |
3 | Level 2 + informative messages |
4 | Same as level 3. |
5 | Highly verbose (includes level 1) + auxiliary evidence files (.MMF, .DUMP, .XML, .RVPMEM) |