NetWorker

This document highlights minimum, recommended, and latest code versions for Dell Technologies Enterprise and Datacenter Infrastructure products. We carefully evaluate and monitor code deployment data to ensure that product releases meet our stringent expectations to provide our customers with reliable products and solutions.

This article documents the solution to the NetWorker Management Console (NMC) installation failure to start the gstdbinit process.

Error message displays when viewing workflow details in NetWorker Administration "Message bus unable to open socket connection to host "Networkerserver_hostname" on port 5672: A socket error occurred."

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. Particular virtual machines (VMs) consistently fail.

This KB provides a general log location for NetWorker Virtual Edition (NVE) upgrade or install failures.

In NetWorker 19.13.0.3, RabbitMQ overwrites CA‑signed certificates with self‑signed certificates when the NetWorker service restarts. This occurs due to a hostname mismatch in the rabbitmq-server script.

After updating the OS or upgrading JAVA on the NetWorker server, the NetWorker server service (nsrd) or the authentication service fail to start. Connecting to the NetWorker server from the NetWorker Management Console may fail, reporting the server is down or cannot reach the authentication service. The JAVA_HOME system environment variable must be updated to reflect the new Java version's installation path.

Error message received after renaming library: "nsrmmgd Cannot find resource `NSR jukebox' named."

Rapid7 scan identified security vulnerabilities on various ports of NetWorker.

nsr commands fail while logged as root, or when running nsr commands from an Administrator command prompt.

NetWorker server that is deployed on a Red Hat 8.x failover cluster fails to start with "Can't start nsrd because /nsr/res (/nsr) is local, and NetWorker is configured as a cluster server."

This KB provides a basic overview for how to add LDAP/AD authentication using the authc_config script template. Microsoft Active Directory (AD) or Linux Lightweight Directory Access Protocol (LDAP) authentication can be used with NetWorker.

NetWorker: New and changed features in NetWorker 18.2

NetWorker is configured to backup Azure Virtual Machine (VM) snapshots. During the backup workflow, successful Azure VM disk backups are performed; however, the 'Azure' save set fails.

Unable to view the recovery logs from the NetWorker Web User Interface (NWUI) monitoring tab by clicking the three dot icon and selecting "View Messages," although there is no impact on recovery job.

Empty VMware groups report failure in backups.

A Virtual Machine (VM) resurrection restore is performed using the NetWorker VMware Protection (NVP) vProxy appliance. The save set selected does not reside on a Data Domain device; it is a clone copy on an AFTD device. The resurrection (clone) process exits reporting "nsrvproxy_recover: Encountered memory allocation error while monitoring progress of resurrection clone job."

Virtual Machine (VM) backups are configured through the NetWorker VMware Protection (NVP) vProxy appliance. The VMs reside on vSAN Express Storage Architecture (ESA) datastores. VM backups complete successfully but restores fail returning an "unsupported format" error.

Virtual Machine (VM) Revert restores performed through the NetWorker Web User Interface (NWUI) do not start. The recovery job gets stuck in the NWUI Monitoring "Recover Jobs" window and cannot be cancelled.

The NetWorker server software is deployed on a Red Hat Enterprise Linux Pacemaker (PCS) cluster. After upgrading NetWorker from 19.6.1.x (or earlier) to 19.7.0.0-19.7.0.3 or 19.8.0.0-19.8.0.1, NetWorker server services do not start.

NetWorker services fail to start on a Red Hat pacemaker (pcs) High Availability cluster after upgrading to a NetWorker 19.7.0.x release (or later).

Guide to demonstrate the details needed to troubleshoot Fiber Channel connectivity from NetWorker clients.

Use mminfo to extract deduplication statistics for a NetWorker save set on a Data Domain; the output follows version:cloneid:backup:pre‑compression:post‑compression and shows deduplicate compression process.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy Appliance. The vProxy deployment had some issues with name resolution and DNS. The virtual machine (VM) backups for some Virtual Machines fail with an invalid name resolution error message.

The File Level Restore (FLR) user account can install the FLR agent and browse most directories. The user account is not able to browse the /root directory from the NetWorker Management Console (NMC) recover wizard.

NetWorker VMware Protection (NVP) Virtual Machine (VM) backups fail in configuration using Direct Fiber Channel (DFC) with Data Domain error 5008.

The NetWorker Virtual Edition (NVE) Installation Manager stops updating around 80%. There are no errors observed, the web page has not updated for a long time.

The NetWorker VMware Protection integration is configured with the vProxy Appliance, and the nsrvproxy_mgmt command-line utility is being used to upgrade the existing appliances. The upgrade fails with an error.

The vCenter server account used by NetWorker keeps getting locked. The issue is tracked to login attempts from one NetWorker VMware Protection (NVP) vProxy appliance.

When refreshing the VMware view, or when running a backup, you might get an error message indicating that NetWorker is unable to fetch data from vCenter.