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.

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

NetWorker VMware Protection (NVP) File Level Restore (FLR) fails to mount disks on Windows hosts with using Veritas Virtual Disk Service Dynamic Provider.

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.

In a multi-homed environment, the installation of either Flash or html-5 vProxy plugin fails due to the network restrictions across the different VLANs the NetWorker server and vCenter are configured with.

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.

An issue has been observed following an upgrade from NMC version 19.12 to 19.13, where the GST service shuts down shortly after starting.

As part of the upgrade of NetWorker Virtual Edition (NVE), the NetWorker Runtime Environment (NRE) is installed. This step fails and the upgrade stalls.

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.

Overview of which parallelism settings must be configured for NetWorker VMware Protection (NVP) vProxy backups.

NetWorker: Troubleshooting Media Waiting Events - waiting for 1 writable volume or no matching devices

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

This article discusses the steps to delete old save sets automatically because volume was 'manual recycle' at the time of backup.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy Appliance. The virtual machine (VM) FULL recovers, and instant access recovers fails with "Error: Could not update vmx file's 'uuid.bios' entry."

The NetWorker solution is configured with the NetWorker Virtual Edition (NVE) Appliance. The NVE upgrade package is used, and it reaches step 14 of 45 to reboot the NVE. The NVE upgrade does not resume after the NVE reboot and services (avi and nsr) do not start.

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.

Possible orphan files in the CloudBoost file system leading in over usage of cloud space

The NetWorker Jobs Database (JOBSDB) reports "database disk image is malformed" at the start of backups. The backup completes successfully.

Randomly backup done using CloudBoost devices are aborted with the common error CONNECTION_DISCONNECTED.

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