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.

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

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.

The operation cannot be allowed at the current time because the virtual machine has a question pending.

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 NetWorker representational state transfer (REST) application program interface (API) is used to request information (HTTP GET) from a NetWorker Server in the environment. The REST API queries intermittently time-out, and the restapi.log shows an internal server error message due to a Socket Timeout.

This article describes a condition related to Dynamic World Wide Naming leading to device mismatches.

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

Volume Shadow Copy Service (VSS) snapshot creation stops responding on a Windows client during NetWorker backups.

NetWorker VMware Protection (NVP) vProxy VM backups fail with an error message "Backup has FAILED:  Unable to find identity (MORef) of vProxy's virtual machine: Unable to determine network interface"

NetWorker VMware Protection (NVP) restores are slow compared to backup.

NetWorker VMware Protection (NVP) Virtual Machine (VM) backups fail with "VDDK Error: 3014: Insufficient permissions in the host operating system."

The NetWorker VMware Protection (NVP) vProxy is used to backup Microsoft SQL Virtual Machines (VM). The environment consists of multiple vCenter environments, and the SQL VM was copied to another vCenter outside of NetWorker practices. SQL VM restores are performed from the Data Protection Restore Client (DPRC). The DPRC wizard does not show SQL backups for a VM, no error is returned.

A Zimbra server on a Red Hat Hyper‑V Virtual Machine (VM) shows processor and memory exhaustion during backup. The VM becomes unresponsive and must be rebooted.

This article describes how to increase the /data01 partition size on a NetWorker Virtual Edition (NVE) server.

NetWorker VMware Protection (NVP) vProxy Virtual Machine (VM) backups fail reporting "function "curl_easy_perform" returned error 35: "error:0407006A:rsa routines:RSA_padding_check_PKCS1_type_1:block type is not 01"