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
- Additional Steps on NetBackup for OpenStack Appliance
- Installing on Ansible OpenStack Ussuri
- Installing on Kolla
- 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
- Upgrading NetBackup for OpenStack
- 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
- Disaster recovery
- Troubleshooting
- General Troubleshooting Tips
- Health check of NetBackup for OpenStack
- Important log files
Importing the policies
You can import policies from the backup target to the NetBackup for OpenStack database.
The policy import feature is designed to import the policies that are owned by the cloud. It does not import or list any policies that are owned by a different cloud.
To import the policies
- Get a list of policies that can be imported.
nbosjm policy-get-importpolicies-list [--project_id <project_id>] [--storage_type <storage_type>] [--backup_path <backup_path>]
--project_id List the policies that belong to the specified project only.
--storage_type The storage type (S3 or NFS), where the policies are stored.
--backup_path The backup storage path where backups are stored.
For S3, storage_type and backup_path are optional parameters.
- Import the policies into the NetBackup for OpenStack database.
nbosjm policy-importpolicy [--policies <policyid>] [--storage_type <storage_type>] [--backup_path <backup_path>]
--policyids Specify policy IDs to import. Repeat option for multiple policies.
--storage_type The storage type (S3 or NFS), where the policies are stored.
--backup_path The backup storage path where backups are stored.
For S3, storage_type and backup_path are optional parameters.
- Verify that the policies are imported properly.
./nbosjm ./nbosjm policy-verify-importedpolicies
--policyids Specify policy IDs to verify that the policies are imported properly.
--storage_type The storage type (S3 or NFS), where the policies are stored.
--backup_path The backup storage path where backups are stored.
Before you run import policy commands for S3 storage type, perform the following.
Add the following details in the
/etc/nbos/nbosjm.conf
file.vault_s3_auth_version = DEFAULT vault_s3_access_key_id = << s3_access_key >> vault_s3_secret_access_key = <<s3_secret_access_key>> vault_s3_region_name = << s3_region_name >> vault_s3_bucket = << vault_s3_bucket >> vault_s3_endpoint_url = << vault_s3_endpoint_url >> vault_s3_signature_version = default vault_s3_ssl = False vault_s3_ssl_cert = vault_enable_threadpool = True vault_s3_support_empty_dir = False [s3fuse_sys_admin] helper_command = sudo /home/stack/myansible/bin/nbosjm-rootwrap /etc/nbosjm/rootwrap.conf privsep-helper
Start thenbos-object-store service.
systemctl start nbos-object-store
Check the status of the nbos-object-store service. It must be in the running state.
systemctl status nbos-object-store