NetWorker Module for Databases and Applications

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.

Virtual Machine (VM) image and instant recoveries are failing with "Could not update vmx file's 'nvram' entry"

The NetWorker Management Console (NMC) software is updated on a Linux host. After performing the upgrade. The NMC's GST service is not starting up and reporting certificate validation errors.

NetWorker vProxy (NVP) Virtual Machine (VM) backups cancel with snapshot errors, reporting a failed digest operation; log shows corrupt digest metadata causing snapshot failure on Horizon clone VMs.

NetWorker is configured to perform Azure Virtual Machine (VM) snapshot backups. The backup policy fails, reporting "nsrazure_save: Command not found"

A NetWorker VMware Protection (NVP) Virtual Machine (VM) File Level Restore (FLR) fails to mount. Instant Access restore may also fail. The error logging returns that the vProxy failed to log in in to the Data Domain because the REST service on the Data Domain is disabled.

NetWorker "Rules" are configured to identify VMware Virtual Machines (VM) in a NetWorker Protection Group. This dynamically backs up new VMs based on the rule definitions defined and VMs that meet the rule criteria. Some or no VMs are listed. The approach outlined in this article outlines how to diagnose potential configuration issues that result in rules not identifying expected VMware resources correctly.

Network Data Management Protocol (NDMP) incremental backups always promote to full because BASE_DATE = 0. Problem was caused by NSM for NAS client for the same NAS and saves set was running in parallel with the traditional NDMP backup client. Problem was resolved after removing the NSM for NAS client from the configuration.

NetWorker by default uses "SYSTEM@<NW-server-name>" as the sender in email notifications.

Virtual Machine (VM) FLR performed through the NetWorker VMware Protection (NVP) vProxy appliance fails with "cannot create handle .. the system cannot find the path specified" when the file path exceeds 260 characters.

NetWorker VMware Protection (NVP) vProxy redeployment fails because of a firewall port issue.

Package Manager (nsrpush) command fails to upgrade clients with NetWorker Modules installed. The nsrpush upgrade succeeds when performed from the NetWorker Management Console (NMC).

NetWorker Module for Microsoft (NMM) backups are configured for an Exchange server. The nsrnmmsv command fails reporting that it failed to start on the client.

NetWorker devices are in a write-protected (read-only) state. Backups or clone jobs writing to the "read-only" do not start or fail.

VM backups performed through the NetWorker VMware Protection (NVP) vProxy appliance fail stating "curl_easy_perform" returned error 28: "Operation timed out after 1,800,735 milliseconds with 0 out of -1 bytes received"

NetWorker is configured on a Red Hat Pace Maker (pcs) cluster. The NetWorker server services fail to start with a connection error.

A NetWorker server is configured with Simple Network Management Protocol (SNMP) traps using the nsrtrap command. The command is set on the backup action with "On Failure." After upgrading to 19.11.x from a previous release, the traps receiver only receives a nwServerNotification, the failedActionNotification is no longer received.

In a Windows Cluster, NetWorker Client 19.9 or 19.8 floods daemon.raw with messages such as nsrpurge_adhoclog: get_lc_fspath_vhost_map: lg_getnameinfo failed vhost "cluster_name."

NetWorker Module for Microsoft (NMM) 19.9 Hyper-V incremental backup fails with error "Fails to retrieve information for virtual disk." This results in the incremental backup either promoted to full or fails.

NetWorker is upgraded to 19.13.0.0 or 19.13.0.1 from a prior release. The server is Windows based. The NetWorker Management Console (NMC) launches but crashes immediately after entering credentials.

A Linux server is configured as both the NetWorker server and NetWorker Management Console (NMC) server. The gstclreport command is used to generate NMC Reports from command line. This cases the NetWorker server daemon (nsrd) to crash with a core dump.

Linux NetWorker Server fails to start the authentication service with a permission denied error.

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

In a Network Data Management Protocol (NDMP) backup, the job stops due to a SnapSure file system creation error. Causes include low NAS space, wrong file system name, SnapSure timeout, file system corruption.

This article provides a general overview of the differences between the different NetWorker license file types.

Users see 401 Unauthorized errors and SSL handshake failures when launching the NetWorker Management Console (NMC), caused by a corrupted AUTHC directory and mismatched keystore truststore credentials.

Advanced Migration (AM) staging on Block-Based Backup (BBB) save sets is not supported; the nsrclone -m option and nsrstage skip BBB save sets, allowing only full backup clones, not incremental.

The NetWorker nsrimportclient process fails with the following error message: 204879:nsrimportclient: Failed to import client 'client_name_1': Name 'server_name_destination' is not a valid host name as it cannot be resolved in DNS. Please add it to DNS or the hosts file and flush the NetWorker server's DNS cache (dbgcommand -p <NetWorker server pid> FlushDnsCache).

Networker Twinning enabled on the Sybase database causes DD stream to exhaust

Signal 11 error occurs when PATH_MAX/FILE_MAX exceeds OS limits