NetWorker

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

NetWorker Server’s or Client’s service disruption in HA (High Availability) cluster nodes that are installed with RHEL (Red Hat Enterprise Linux) 8.2, 8.3, 8.4, 8.6 operating system versions.

After upgrading to Dell NetWorker 19.14 on Windows Server 2022 Standard, the GST (NetWorker Management Console) service may fail to start. When attempting to start the service, an entry point error is displayed indicating a conflict between the OpenSSL libraries installed on the operating system and those bundled with NetWorker.

NetWorker Staging is failing for Block Based Backup (BBB)

This KB provides instructions on how to configure Secure Lightweight Directory Access Protocol (LDAPS) integration with NetWorker authentication. This process can be used for integrating Microsoft Active Directory (AD), or Linux LDAP external authentication services.

NetWorker Web User Interface (NWUI) services was crashing and not working properly after installation on Linux RHEL 9.6 and later versions.

GST was crashing after NetWorker Management Console (NMC) installation on Linux RHEL 9.6 and later versions.

After migrating a production NetWorker server to a Disaster Recovery (DR) or alternate site, the DR NetWorker server's Management Console (NMC) is inaccessible. Lockbox signing errors are observed in the DR NetWorker server's daemon.raw.

The recommendation process finishes, yet the ESXi hosts and already‑deployed Avamar proxies are absent from the view. This is caused by a software defect in the topology manager WAR file.

The NetWorker Management Console (NMC) server installation includes PostgreSQL for the NMC databases.

This KB serves as an overview of the rabbitmq service, associated log files, and additional debugging that can be applied.

The NetWorker server includes a RabbitMQ and Erlang. The RabbitMQ and Erlang versions change throughout NetWorker releases.

This article details the different PostgreSQL versions used by the NetWorker Management Console (NMC) and NetWorker Web User Interface (NWUI) servers. It also demonstrates how to identify the PostgreSQL version used by the active NMC and NWUI databases.

Error fetching vCenter information for ESXi vCenter hostname: Reason Dispatcher Request timed out NetWorker

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

NetWorker VMware Protection (NVP) vProxy backups fail when they run against a specific vProxy appliance in the environment. The NetWorker server reports the vProxy as "unavailable," and the vProxy logs show continuous errors indicating the AMQP message bus connection is refused on port 5672. The RabbitMQ message bus process on the vProxy appliance cannot start because it is unable to reach the Erlang Port Mapper Daemon (epmd), which can be caused by incorrect /etc/hosts entries, DNS resolution failures, or a disabled IPv6 configuration on the vProxy. This issue is environmental and can affect any NetWorker and vProxy version.

This article outlines how to manually change the hostname and network settings on an NVP vProxy appliance.

This article provides an overview of how to perform an Azure Virtual Machine (VM) File Level Restore (FLR) using the nsrazure_flr_recover command.

After adding or updating the NetWorker "Datazone Pass Phrase," previously configured 'Azure Subscription' resources are no longer visible to NetWorker. This

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."

The NetWorker Virtual Edition (NVE) Installation Manager Is accessible from a web browser; however, the history tab shows no contents.

Welcome to the Avamar Data Migration enabler (ADMe) landing page.

Secure Connect Gateway (SCG) not working after upgrade to NetWorker version 19.13.x.

A saveset in the clone list is expired and deleted causing the job to loop. Message received is 'Cannot find the volume needed.' A NetWorker bug when using recover_space_anytime may lead to clone jobs stalling when savesets in the list are expired deleted while the job is running.

NetWorker Management Console 19.13.0.2 and Later Fails to Install or Upgrade on Windows system.

A virtual machine file-level restore (FLR) performed through the NetWorker VMware Protection (NVP) vProxy appliance fails with the error "The guest operations agent could not be contacted." The vProxy cannot communicate with the guest operating system because VMware Tools is not installed, not running, or running an outdated version on the target virtual machine. This issue applies to all NetWorker and vProxy versions and can affect virtual machines running any guest operating system. Installing or updating to the latest available version of VMware Tools on the target VM resolves the issue.

This article describes how to enable debug-level logging for the vRealize Data Protection Extension for NetWorker in the edp_4_vcac.log file. By default, the edp_4_vcac.log file uses the INFO log level, which matches the default level configured in the vRealize Orchestrator (vRO) Control Center. Administrators can override the default level by modifying the log4j.xml configuration file directly to set debug-level logging for the com.emc.edp4vcac category.

This article explains the procedure to open a Service Request (SR) using the Dell support page. Get help fast for your Dell device. No more waiting on hold. No more tech headaches. Dell makes it simple to fix problems, schedule repairs, or get support—right from your device or our support website.

The NetWorker VMware Protection (NVP) VMware View refresh fails with the error "Unable to fetch data from vCenter: TCP/UDP IP error ‑1" even though DNS resolution and port 443 connectivity between the NetWorker server and the vCenter server are working correctly. The failure occurs because the NetWorker nsrvim process resolves the vCenter hostname using the /etc/hosts file before falling back to DNS. Corruption or extra special characters in the /etc/hosts file prevent the hostname resolution from completing, which causes the nsrvim process to fail with a get host by name failed in tcp_connect() error.

Intermittent NetWorker outages observed in large cluster environments due to brief monitoring interruptions. By default, the monitor function retries three times. There is no "retry count" parameter available. This KB article defines potential workarounds, and Request For Enhancement (RFE) details for a NetWorker enhancement opportunity.