NetWorker Module for Databases and Applications

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. When performing a backup, the vProxy is unable to open the VM's source VMDK with transport mode hot add.

NetWorker VMware group with Dynamic Association failing with error "Sessions count is limited"

This article provides an overview of how to perform an Azure Virtual Machine (VM) restore that was backed up using NetWorker Azure VM snapshot protection.

The NetWorker Management Console (NMC) server is upgraded to a newer NetWorker release. The upgrade completes successfully, but the NMC is inaccessible. The NMC servers gstd log reports IM003: The specified driver could not be loaded due to system error 126: The specified module could not be found. (PostgreSQL ANSI(x64), C:\program files\emc networker\management\GST\postgres_latest

NMDA DB2 backups failed last night with Error 3. Problem was resolved after creating a new device and scattering backups in two storage nodes, and setting up DB2 retry and timeout parameters.

The NetWorker client service fails to start on a Linux system.

This article provides a general overview for backup administrators and NetWorker support for troubleshooting vSphere plugin and VCUI issues.

This article provides a general overview for backup administrators and NetWorker support for troubleshooting the Data Protection Restore Client (DPRC) used to perform VMware File Level Restore (FLR) and SQL application data.

Unable to create NMDA oracle client backup configuration in NMC. Oracle client backup configuration fails with error: The NMC server could not obtain the required memory for the requested operation. the gst log provides the detail

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

This article explains how NetWorker Module for Microsoft (NMM) uses advanced encryption standard (AES) encryption for backups and restores.

Error:" The authentication credential was corrupted on decoding the credential, the checksums do not match" is generated when changing the retention of a backup save set.

The NetWorker VMware Protection (NVP) solution is used to backup VMware Virtual Machines (VM). The web-based Data Protection Restore Client (DPRC) is used to perform File Level Restore (FLR) or Microsoft SQL app-consistent (MSVMAPPAGENT) restores. Some or all save sets are not visible from the DPRC.

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.

The NetWorker server is configured with external authentication; Lightweight Directory Access Protocol (LDAP) or Microsoft Active Directory (AD). After upgrading the NetWorker server to 19.13.0.0, external user accounts fail to log in, reporting HTTP 404.

The NetWorker VMware Protection (NVP) integration is configured with the vProxy appliance. When attempting to perform file-level restore (FLR) of a Virtual Machine (VM) save set, we are unable to browse into a compressed partition and encounter an "Access is denied" error. The folder that prompts the "Access is denied" error is compressed. NetWorker vProxy FLR has known limitations, which include compressed partitions. This is documented in the vProxy FLR Limitations section of the NetWorker VMware Integration Guide. You cannot perform FLR of compressed partitions.

The NetWorker server daemon.raw posts a warning stating that it detected orphaned save set records on a disk volume.

Error message displays when viewing workflow details in NetWorker Administration "Message bus unable to open socket connection to host "Networkerserver_hostname" on port 5672: A socket error occurred."

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

In NetWorker 19.13.0.3, RabbitMQ overwrites CA‑signed certificates with self‑signed certificates when the NetWorker service restarts. This occurs due to a hostname mismatch in the rabbitmq-server script.

Rapid7 scan identified security vulnerabilities on various ports of NetWorker.

nsr commands fail while logged as root, or when running nsr commands from an Administrator command prompt.

NetWorker server that is deployed on a Red Hat 8.x failover cluster fails to start with "Can't start nsrd because /nsr/res (/nsr) is local, and NetWorker is configured as a cluster server."

NetWorker is configured to backup Azure Virtual Machine (VM) snapshots. During the backup workflow, successful Azure VM disk backups are performed; however, the 'Azure' save set fails.

Unable to view the recovery logs from the NetWorker Web User Interface (NWUI) monitoring tab by clicking the three dot icon and selecting "View Messages," although there is no impact on recovery job.

Empty VMware groups report failure in backups.

A Virtual Machine (VM) resurrection restore is performed using the NetWorker VMware Protection (NVP) vProxy appliance. The save set selected does not reside on a Data Domain device; it is a clone copy on an AFTD device. The resurrection (clone) process exits reporting "nsrvproxy_recover: Encountered memory allocation error while monitoring progress of resurrection clone job."

Virtual Machine (VM) backups are configured through the NetWorker VMware Protection (NVP) vProxy appliance. The VMs reside on vSAN Express Storage Architecture (ESA) datastores. VM backups complete successfully but restores fail returning an "unsupported format" error.

Virtual Machine (VM) Revert restores performed through the NetWorker Web User Interface (NWUI) do not start. The recovery job gets stuck in the NWUI Monitoring "Recover Jobs" window and cannot be cancelled.