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.

Unable to log in to NetWorker Web User Interface (NWUI) launched from the NetWorker server. "Failed to authenticate user administrator with the provided password on Authentication Server <server name>

This article discusses how best to use the NSRGet utility to expedite NetWorker troubleshooting.

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 Active Sessions panel in NetWorker Management Console (NMC) Monitoring displays 0 percent completion. The sessions are observed on DISK devices (Advanced File type device, optical, DD) only.

Sybase database backup starts but fails during the completion phase.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy Appliance. The Dell NetWorker plug-in was successfully installed using the NetWorker Management Console (NMC) or NetWorker Web User Interface (NWUI). The vSphere Web Client Dell NetWorker plug-in is added to vSphere, but is unable to display the page with "no healthy upstream" or "Error message is: 503 Service Unavailable."

Sybase server backup through NetWorker/NMDA fails with I/O errors ending with the crash of the Sybase sybmultbuf process.

NMC UI Title bar is not getting updated with the Capacity License even after applying the Capacity License successfully.

Rapid7 scan identified security vulnerabilities on various ports of NetWorker.

NetWorker service does not start on the NetWorker client.

NetWorker Runtime Environment (NRE) installs files with world writable permissions on Linux servers

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. While performing a file-level restore (FLR) of a Linux virtual machine (VM), the save set cannot be mounted to the target VM properly because the /var/run/vflragentd.sock file does not exist. The /var/run/vflragentd.sock file has not been created because the vflragentd is not running on the target Linux VM.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. The vProxy registration process fails, reporting a timeout when communicating with the vCenter over port 443. The NMC Alerts section shows the vProxy is unavailable. Enabling communication between vProxy and vCenter over port 443 allows proper vProxy registration.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. Backups are unable to run properly, they fail with the error message "User does not have sufficient access rights." The DD Boost user has all proper permissions configured, but is still unable to proceed. A simple reboot of the NetWorker Server and resetting the DD Boost account failed login attempts resolves this issue.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. Particular virtual machines (VMs) consistently fail. Review of the Full Log in the NetWorker Management Console (NMC) shows that the VM has a SCSI controller with bus-sharing enabled. This is common when working with Raw Device Mapping (RDM) volumes.

NetWorker VMware Protection (NVP) is configured. During Virtual Machine (VM) backups, a VM backup fails, reporting that it fails to download the VM's .vmx file. HTTP Status code: 500 (internal server error) is returned.

NetWorker VMware Protection (NVP) vProxy Virtual Machine (VM) backup workflows fail. The error observed in the workflow log reports: "Unable to start backup on vProxy 'vProxy_Name': Received an HTTP code: 500,"

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. vProxy file-level recovery (FLR) mounts without issue but fails quickly on the next step. vProxy FLR with Windows Virtual Machines (VM) uses the robocopy utility to copy files from the FLR mount to the location you specify. The robocopy utility is in the C:WindowsSystem32 directory, which is not in the VM's environment variables path. Add the System32 directory to the VM's environment variables to allow the use of robocopy during vProxy FLR operation.

nsrexecd SYSTEM critical Failed to bind socket for NSR authentication service: Cannot assign requested address.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. The NetWorker server option for "Manual Saves" has been disabled, causing manually initiated vProxy backups to fail.

Unable to create a client using the New Client Wizard in NMC.

The NetWorker server nsrmmdbd is being killed by the operating systems "Out of Memory" (OOM) monitor.

Backups of a Windows client are failing due to Microsoft Volume Shadow copy Service (VSS) issues. There are several different reasons that could result in VSS failing to process a snapshot on the client operating system; e.g: Unstable VSS writer, or insufficient space to create a snapshot. VSS is required for SYSTEM STATE or DISASTER RECOVERY: save sets or when completing Block-Based Backups (BBB). VSS must be stable and working correctly on the host operating system before it can be used with NetWorker backups.

Windows client backup fails with the following Volume Shadow copy Service (VSS) error "Insufficient storage available to create either the shadow copy storage file or other shadow copy data"

Launching NetWorker Management Console (NMC) 19.13 (or later) fails. A keystore error appears stating "C:\Users\USERNAME\.config\icedtead-web\security\trusted.cacerts (Access is denied) during operation 'load keystore'.

During installation of the NetWorker Management Console (NMC) server software on a standalone Windows host, the installer fails to connect to the NetWorker AUTHC server. The error reported is "Unable to verify Authentication Server's hostname and or port." There are no communication issues between the two hosts.

This article explains how to enable core dump (Linux and UNIX) and crash dump (Windows) capture on Linux, UNIX, and Windows systems.

The "Unable to decrypt: BAD_DATA" error can occur due to lockbox issues, such as corruption or when the NetWorker server is migrated, moved, or reinstalled without restoring the lockbox. The current lockbox does not have the passwords stored that match the user/passwords in the nsrdb, hence the BAD_DATA error.

Active Directory users cannot log in to NetWorker and to NMC. The error generated is "incorrect username or password".