NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
- Introduction
- Section I. NetBackup Snapshot Manager for Cloud installation and configuration
- Preparing for NetBackup Snapshot Manager for Cloud installation
- Deploying NetBackup Snapshot Manager for Cloud using container images
- Deploying NetBackup Snapshot Manager for Cloud extensions
- Installing the NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager for cloud providers
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Prerequisites for configuring the GCP plug-in using Credential and Service Account option
- Microsoft Azure plug-in configuration notes
- Microsoft Azure Stack Hub plug-in configuration notes
- OCI plug-in configuration notes
- Configuration for protecting assets on cloud hosts/VM
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Snapshot Manager for cloud catalog backup and recovery
- NetBackup Snapshot Manager for cloud assets protection
- Volume encryption in NetBackup Snapshot Manager for cloud
- NetBackup Snapshot Manager for Cloud security
- Preparing for NetBackup Snapshot Manager for Cloud installation
- Section II. NetBackup Snapshot Manager for Cloud maintenance
- NetBackup Snapshot Manager for Cloud logging
- Upgrading NetBackup Snapshot Manager for Cloud
- Migrating and upgrading NetBackup Snapshot Manager
- Post-upgrade tasks
- Uninstalling NetBackup Snapshot Manager for Cloud
- Troubleshooting NetBackup Snapshot Manager for Cloud
Status 49 error appears
When attempting to backup large number of blob containers with NetBackup Snapshot Manager configured, the Status 49 error occurs as follows in the activity monitor:
Feb 06, 2024 8:17:44 AM - Info nbjm (pid=14024) started backup (backupid=azure_azure-obj-account_perfobjectacct.obj-poc6_1707229064) job for client azure_azure-obj-account_perfobjectacct.obj-poc6, policy policy-100, schedule full on storage unit azure-poc-msdp-c-stu Feb 06, 2024 8:25:47 AM - Error bpbrm (pid=19853) Failed to spawn DataMover container on host:obj-nbsm-server.internal.cloudapp.net Feb 06, 2024 8:25:47 AM - Info bpbkar (pid=0) done. status: 49: client did not start Feb 06, 2024 8:25:47 AM - Error nbpem (pid=14068) backup of client azure_azure-obj-account_perfobjectacct.obj-poc6 exited with status 49 (client did not start) Feb 06, 2024 8:25:47 AM - end writing client did not start(49)
When attempting large number of backups if
process is running and consumes more CPU space, then the status error code 49 is displayed. The is a daemon process that runs on systems using SELinux (Security-Enhanced Linux). This daemon monitors system events and logs generated by SELinux and provides notifications and recommendations to the administrator when it detects potential problems or policy violations.Workaround:
Disable the
process to stop it from running and generating notifications or recommendations related to SELinux by disabling the audit plugin in the following respective files:On RHEL7:
/etc/audisp/plugins.d/sedispatch.conf
On RHEL8 and later:
/etc/audit/plugins.d/sedispatch.conf
The following procedure considering RHEL7 as an example provides steps to disable
process:Modify the configuration file as follows:
sed -i "s/active = yes/active = no/" /etc/audisp/plugins.d/sedispatch.conf
Restart the auditd service:
service auditd restart
The dbus launches
process by D-Bus API request.To disable the
process, remove the following definitions and reload dbus:mv /usr/share/dbus-1/system-services/org.fedoraproject.SetroubleshootFixit.service /usr/share/dbus-1/system-services/org.fedoraproject.SetroubleshootFixit.service.back ## RHEL 8 and 9 only mv /usr/share/dbus-1/system-services/org.fedoraproject.SetroubleshootPrivileged.service /usr/share/dbus-1/system-services/org.fedoraproject.SetroubleshootPrivileged.service.back mv /usr/share/dbus-1/system-services/org.fedoraproject.Setroubleshootd.service /usr/share/dbus-1/system-services/org.fedoraproject.Setroubleshootd.service.back
Reload dbus: systemctl reload dbus
Note:
This is not a persistent change. By updating /usr/share/dbus-1/system-services/
files are recovered.