NetWorker

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

After a reboot, Windows non-clustered devices were not coming online when using PowerShell to online the devices. Coincidentally, the AppSync plugin was recently installed.

NetWorker 18.x VM restore fails indicating the vmdk is not found.

The NetWorker Installation Manager repository tab shows that the package was rejected as it failed to retrieve the package metadata.

Sybase backup fails because of group permission issue.

Runtime rendering (daemon.log) no longer works after upgrade to NW 19.3.0.4

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

The backups intermittently fail with a resource not found message in the NetWorker Management Console (NMC) and the backup session logs.

Vproxy VM Recovery fails when clone copy is on Tape. Restore fails at cloning part of the recover command. Manual clone from CLI and NMC also fails.

NetWorker VMware Protection (NVP) Virtual Machine (VM) backups were running slow after setting up a new vCenter server in linked mode.

The NetWorker Virtual Edition (NVE) appliance is not accessible over SSH. The NVE is otherwise up and running with no impact to data protection operations.

This article provides a way of restoring database from a primary or a secondary Data Domain using product such as Oracle Recovery Manager (RMAN) Agent and DDBEA.

VM backup is failing with the below error: 2021-04-14T17:46:35Z ERROR: [@(#) Build number: 51] Failed to complete removal of snapshot "snapshot-347817": Another task is already in progress. 2021-04-14T17:46:35Z ERROR: [@(#) Build number: 51] Unable to delete pre-existing snapshots: Another task is already in progress.

The system report "Backup SLA Summary By Client" is only showing the colour red for all columns instead of green and red.

Target Stack listing is no longer available on the dell.com website.

The NvePlatformOsRollup_2020-R4plus-v6.avp Security Rollup package is being applied to the NetWorker Virtual Edition (NVE) appliance. The rollup stops at 45% with the message "Install Operating System Patches with Selected SuSE RPMs (9 of 18) Failed".

NetWorker Virtual Edition (NVE) is not sending backup Email Notifications after upgrading.

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

When configured to write to decommissioned devices, backups fail with "unable to read volume label," and unable to load VTL tapes.

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.

This KB gives a brief overview of how to perform VMware Virtual Machine (VM) image restores from the REST API.

How to collect NetWorker logs, NetWorker support requires for problem analysis.

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.

Changing the log level to 'debug' may be necessary in order to troubleshoot an issue with NetWorker VMware Protection (NVP) with vProxy Appliance solution (NVP-vProxy). This article explains how to change the log level.

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.

You are attempting to perform a Virtual Machine (VM) FLR of a Windows VM using the local administrator account of the target VM. The FLR mount fails to install the FLR agent on the target VM stating "exit code 1603" or "exit code 1625"

mminfo does not work with short date format (mm/dd/yy), it works only with long format (mm/dd/yyy)

This article helps in understanding the hardware issue configured in NetWorker.