NetWorker Module for SAP

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.

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 VMware Protection (NVP) vProxy backup actions complete successfully. However, the clone action fails with "no available devices to clone." The disk volumes in the target clone pool are not set to "Appendable" mode. Without this mode, the clone action cannot write to the volumes.

A restore failed with error 11015, invalid VMDK filename; logs show cancelled browse tasks and failures, caused by a version mismatch between the Avamar proxy (19.7) and server.

Dell Avamar, Dell Networker Virtual Edition (NVE) and Dell PowerProtect DP Series Appliance / Dell Integrated Data Protection Appliance (IDPA) remediation is available for multiple vulnerabilities that could be exploited by malicious users to compromise the affected system.

This is a general overview of monitoring NetWorker Logs from Grafana

Welcome to the Avamar Data Migration enabler (ADMe) landing page.

This article details the steps required to access the NetWorker Management Console (NMC) after upgrading to 19.13 or later.

This KB provides an alternative method for performing a VMware File Level Restore (FLR) which does not require an available vProxy appliance. This method can be used if the standard NetWorker VMware Protection (NVP) FLR process is failing, unsupported Virtual Machine's (VM) configuration, or Operating System. The steps outlined in this KB must be performed with the involvement of the NetWorker Backup Administrator, VM's System Administrator, and VMware Administrator.

This article provides a general overview of how VMware Virtual Machine (VM) backup levels and sizes that are reported in NetWorker when using the NetWorker VMware Protection (NVP) solution.

Does NetWorker Virtual Edition (NVE) support Azure Zone-Redundant Storage (ZRS) for the NVE OS disk and data disks to provide cross-zone disk replication and recovery during an Azure Availability Zone failure?

This KB is intended to aid backup administrators and support agents who are unfamiliar with the NetWorker VMware Protection (NVP) solution. It gives a general overview of vProxy components and logs, additional relevant articles are also provided. This KB can be used to perform initial diagnoses when engaging support to ensure that an accurate issue statement is provided.

A VMware vCenter server is added to NetWorker using an AD account. The vCenter is integrated with Azure Entra ID and the account used within NetWorker is from Entra ID. NetWorker Authentication with the VMware vCenter fails, resulting in failed inventory processing and NetWorker VMware Protection (NVP) backups.

The NetWorker nsrimportclient process fails with a DNS resolution error when importing clients to a destination server.

A FLR Mount fails with the error: "NFS has reached the maximum number of supported volumes" on Dell NVP vProxy.

NetWorker Management Console 19.13.0.2 and later fails to install or upgrade on Windows system.

The NetWorker command `nsrcapinfo` is used to collect information about backups performed on the NetWorker server. It is observed that it is reporting the provisioned size of VM backups.

NetWorker may incorrectly report LTO-7, LTO-8, and LTO-9 tape volumes as 100% utilized or full before their native capacity is reached. No "prematurely full" errors are observed in the daemon logs, and the issue does not affect actual tape usage, backup operations, cloning, or recoveries.

These instructions describe how to replace the default NetWorker self-signed certificate with a CA-signed certificate on a NetWorker Management Console (NMC) server.

These are the general steps to replace the default NetWorker self-signed certificate with a Certificate Authority (CA)-signed certificate for the "AUTHC" and "NWUI" services. This KB applies when the NetWorker server and NetWorker Web User Interface (NWUI) server are installed on Windows operating systems.

This KB details the process that is required for configuring "AD over SSL" (LDAPS) from the NetWorker Web User Interface (NWUI).

These are the general steps to replace the default NetWorker self-signed certificate with a Certificate Authority (CA)-signed certificate for the "AUTHC" and NetWorker Web UI (NWUI) services.

Overview of configuring AD or Secure Lightweight Directory Access Protocol (LDAPS) with NetWorker using the NMC's external authority wizard. This KB can also be used for instructions on updating an existing external authority configuration.

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.

This article provides an overview of how to clear Java cache, enable Java console, and configure Java debug on Microsoft Windows systems using NetWorker Runtime Environment (NRE) to access the NetWorker Management Console (NMC).

This KB provides a general log location for NetWorker Virtual Edition (NVE) upgrade or install failures.

This KB provides an overview of how to clear Java cache, enable java console, and configure Java debug on Microsoft Windows systems using NetWorker Runtime Environment (NRE) to access the NetWorker Management Console (NMC).

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.