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.

Changing the log level to 'debug' may be necessary in order to troubleshoot an issue with NetWorker VMware Protection (NVP) with vProxy Appliance solution (NVP-vProxy). This article explains how to change the log level.

This article defines the diagnostic approach of troubleshooting Virtual Machine (VM) backup or restore performance issues when using the NetWorker VMware Protection (NVP) vProxy solution.

When auditing disk usage, it is often necessary to check expired save sets on specific volumes; this article explains how.

NetWorker server workflow backup completed successfully, but skipped connection failed clients without error/warning.

NetWorker VMware Protection (NVP) backup workflows intermittently fail with the error "Unable to bind socket to port 0 from connection port range 0-0: Cannot assign requested address." The same socket bind error also appears for other NetWorker processes and workflows on the server. The failure occurs because the NetWorker server operating system has exhausted its available sockets, leaving no open sockets for NetWorker processes to bind to.

In Dell NetWorker environments where backup and clone actions are configured within the same workflow, the nsrim process may prematurely delete both full and incremental save sets from the clone volume even though dependent save sets still exist and have not yet expired. This breaks the backup chain on the clone device, rendering recovery from the clone impossible if the primary backup volume becomes unavailable.

The Recover tab in NetWorker Management Console (NMC) does not display any recovery job information, including both historical and active recovery sessions.

The vProxy appliance is deployed with a static IPv4 address that never appears on the VM and does not respond; wickedd reports duplicate‑IP errors because the address is in use on the network.

Dell NetWorker vProxy backup for a VM fails due to failing VMware snapshot. ERROR: Snapshot creation task failed: An error occurred while taking a snapshot: Invalid change tracker error code

When recovering a VM via the Instant Access restore method, the recovery completes successfully but the VM will not power on. VMware reports one or more of the VMDK files are invalid: Failed to open (The file specified is not a virtual disk). An Image recovery of the same backup will also be successful. But the recovered VM will power on and function.

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