Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide
  3. Section II. NetBackup Snapshot Manager for Cloud maintenance
  4. Troubleshooting NetBackup Snapshot Manager for Cloud
  5. Status 49 error appears
NetBackup™ Snapshot Manager for Cloud Install and Upgrade Guide

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 setroubleshootd process is running and consumes more CPU space, then the status error code 49 is displayed. The setroubleshootd 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 setroubleshootd process to stop it from running and generating notifications or recommendations related to SELinux by disabling the sedispatch 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 setroubleshootd process:

  1. Modify the configuration file as follows:

    sed -i "s/active = yes/active = no/" /etc/audisp/plugins.d/sedispatch.conf

  2. Restart the auditd service:

    service auditd restart

    The dbus launches setroubleshootd process by D-Bus API request.

  3. To disable the setroubleshootd 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 setroubleshoot-server package, the /usr/share/dbus-1/system-services/ files are recovered.

Feedback

Was this page helpful?
Previous

MS SQL application backup, restore, or SFR job on Windows cloud VM fails with an error

Next

Restore from backup fails with an error

Feedback

Was this page helpful?