NetBackup™ for OpenStack Administrator's Guide

Clean NetBackup for OpenStack datamover service

The following steps need to be run on all nodes, which have the NetBackup for OpenStack datamover service running. Those nodes can be identified by checking the roles_data.yaml for the role that contains the entry OS::TripleO::Services::nbosdm.

Once the role that runs the NetBackup for OpenStack datamover API service has been identified, the following commands will clean the nodes from the service.

Stop nbosdm container.

# For RHOSP17.1 onwards
systemctl disable tripleo_nbosdm.service
systemctl stop tripleo_nbosdm.service
podman stop nbosdm

Remove nbosdm container.

# For RHOSP17.1 onwards
podman rm nbosdm

Unmount NetBackup for OpenStack Backup Target on compute host.

## Following steps applicable for all supported RHOSP releases.

# Check NetBackup for OpenStack backup target mount point
mount | grep NetBackup

# Unmount it
-- If it's NFS  (COPY UUID_DIR from your compute host using above command)
umount /var/lib/nova/NetBackupOpenStack-mounts/<UUID_DIR>

-- If it's S3
umount /var/lib/nova/NetBackupOpenStack-mounts

# Verify that it's unmounted        
mount | grep NetBackup
    
df -h  | grep NetBackup

# Remove mount point directory after verifying that backup target unmounted 
successfully.
# Otherwise actual data from backup target may get cleaned. 

rm -rf /var/lib/nova/NetBackupOpenStack-mounts

Clean NetBackup for OpenStack datamover service conf directory.

rm -rf /var/lib/config-data/puppet-generated/nbosdm/
rm /var/lib/config-data/puppet-generated/nbosdm.md5sum

Clean log directory of NetBackup for OpenStack datamover service.

rm -rf /var/log/containers/nbosdm/