NetWorker Module for Microsoft

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.

This article documents the solution to the NetWorker Management Console (NMC) installation failure to start the gstdbinit process.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy Appliance. The vProxy deployment had some issues with name resolution and DNS. The virtual machine (VM) backups for some Virtual Machines fail with an invalid name resolution error message.

The File Level Restore (FLR) user account can install the FLR agent and browse most directories. The user account is not able to browse the /root directory from the NetWorker Management Console (NMC) recover wizard.

NetWorker VMware Protection (NVP) Virtual Machine (VM) backups fail in configuration using Direct Fiber Channel (DFC) with Data Domain error 5008.

The NetWorker Virtual Edition (NVE) Installation Manager stops updating around 80%. There are no errors observed, the web page has not updated for a long time.

The NetWorker VMware Protection integration is configured with the vProxy Appliance, and the nsrvproxy_mgmt command-line utility is being used to upgrade the existing appliances. The upgrade fails with an error.

The vCenter server account used by NetWorker keeps getting locked. The issue is tracked to login attempts from one NetWorker VMware Protection (NVP) vProxy appliance.

Upgrading to the latest vProxy version causes backups to fail with Error: "Failure," "Description": "Backup has failed: Unable to open session to target device \"DD_HOSTNAME\.""

Backups of large save sets intermittently fail when writing to Data Domain. The error observed is "5057-File handle is stale." This may be observed on various data types but is specific to large backups that span many hours.

Backups directed to the Data Domain fail when Retention Lock is enabled in the workflow action but is not configured on the target Data Domain device.

A NetWorker backup job fails because the selected protection group in the workflow does not have any enabled clients associated with it.

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

The NetWorker VMware Protection (NVP) vProxy appliance does not currently support the Trusted Platform Module (TPM).

NetWorker does not have a vSphere Installation Bundle (VIB) to open ports needed for FLR on the VMware ESXi hosts.

The Instant Recover succeeds, but the Virtual Machine (VM) fails to boot with "Cannot open the disk /vmfs/volumes/<VOLUME_UUID>/<myvmname>/<myvmname>_1.vmdk' or one of the snapshot disks it depends on."

Virtual Machine "Image Recover" consistently failing using recently upgraded vCenter. NetWorker vProxy Image Recover has stopped working after recent vCenter upgrade.

This KB provides an overview of the methods that can be used to identify the NetWorker software. The purpose of this KB is to assist NetWorker administrators and Customer Support Team (CST) with collecting information when opening a NetWorker Service Request (SR).

NetWorker VMware Protection (NVP) is configured to backup a VM which contains Independent disks. The backup completes successfully. VMs with a mixture of independent and dependent disks are reported as successful backups, but the independent disk was not backed up.

The Generic Services Toolkit (GST) Web Service demonstrates delayed initialization and then terminates unexpectedly after a period of runtime, without any user‑initiated action.

A Virtual Machine (VM) FLR is attempted using the NetWorker VMware Protection (NVP) vProxy Solution. The vProxy FLR agent fails to install "Unable to transfer file vProxy-FLRAgent to VM"

After upgrading the NetWorker client software on a system, the client's "NetWorker version" is not updated in the client properties.

You have a VM which is configured with multiple disks. VM backups have been completing successfully. When recovering the VM, not all the VM disks are available for recovery. The missing disks are configured in VMware as Independent or RDM disks. VMware will not snapshot Independent disks, this is required for backing up the disk. RDM disks are bypassed during backup as they are not supported.

Customers may request the NetWorker GPG public key because NetWorker RPM packages are signed and the public key must be imported on the Linux host before the RPM signature can be validated during installation.

Updating an Action fails when a pool contains devices from different Data Domains.

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

The NetWorker VMware Protection (NVP) vProxy appliance upgrade fails indicating that there is insufficient space in the VMware datastores.

After installing or upgrading the NetWorker server software on a Linux host, RabbitMQ initialization fails immediately.

Upgrading the NetWorker VMware Protect (NVP) vProxy appliance fails with "Permission to perform this operation was denied."

NetWorker VMware Protection (NVP) Virtual Machine (VM) backups failing with "HTTP Get request failed to download config file" HTTP Status code: 401."