NVP vProxy: VM Resurrection Restore from an AFTD device fails with "nsrvproxy_recover: Encountered memory allocation error"

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

Este artículo se aplica a Este artículo no se aplica a Este artículo no está vinculado a ningún producto específico. No se identifican todas las versiones del producto en este artículo.
Consulte estos recursos

Síntomas

  • A NetWorker VMware Protection (NVP) restore of a Virtual Machine (VM) is performed. The save set selected is a clone copy, residing on an Advanced File Type Device (AFTD).
  • The recovery process automatically initiates a "resurrection" restore. This is an automated process that clones the save set back to a Data Domain clone pool.
NOTE: NetWorker VMware Protection (NVP) only supports backups directly to a Data Domain (ddboost) disk device. After the backup has been completed, it can be cloned to other devices (for example: AFTD, Tape, CloudBoost); however, this means that to recover the clone copy, it must first be cloned back to Data Domain.
  • The resurrection (clone) job fails, reporting a memory allocation error:
165713:nsrvproxy_recover: Attempting to automatically resurrect clone SSID with 7 days retention to DD volume in pool vmrestorestaging
MM/DD/YYYY HH:mm:SS No callback registered on session channel 1 for user-defined message: (message type: 170, request type: 0)
MM/DD/YYYY HH:mm:SS Resurrection clone job created
MM/DD/YYYY HH:mm:SS Resurrection clone job started
166711:nsrvproxy_recover: Encountered memory allocation error while monitoring progress of resurrection clone job.
  • The clone job has completed successfully, but the restore job does not start. The NetWorker server's /nsr/logs/daemon.raw shows that the job was completed successfully:
204502 MM/DD/YYYY HH:mm:SS  1 5 0 2332022528 30776 0 NetWorker_ServerName nsrd NSR notice The requested pool for the clone operation is 'vmrestorestaging'
204503 MM/DD/YYYY HH:mm:SS  1 5 0 2332022528 30776 0 NetWorker_ServerName nsrd NSR notice The target pool 'vmrestorestaging' for the clone operation has DD-type volumes.
70896  MM/DD/YYYY HH:mm:SS 0 0 0 4056053568 30776 0 NetWorker_ServerName nsrd NSR info NetWorker_ServerName:cloning session saving to pool 'vmrestorestaging' (vmrestorestaging.001)
71659  MM/DD/YYYY HH:mm:SS 0 0 0 4056053568 30776 0 NetWorker_ServerName nsrd NSR info NetWorker_ServerName:cloning session done saving to pool 'vmrestorestaging' (vmrestorestaging.001) 661 GB
71193  MM/DD/YYYY HH:mm:SS 0 0 0 4056053568 30776 0 NetWorker_ServerName nsrd NSR info Write completion Notice: Writing to volume vmrestorestaging.001 completed
NetWorker: How to use nsr_render_log
  • The cloned save set can be seen on a ddboost device using the mminfo command on the NetWorker server:
mminfo -avot -q ssid=SSID
NOTE: If the save set has the flag cr (recoverable), this means that the clone operation was successful; however, the resurrection process encountered an error which prevents the restore from proceeding.
  • This issue may only appear during resurrections of larger VMs. When a resurrection is performed on smaller VMs, the issue is not observed.
  • The NetWorker server is 19.8.0.x or older.

Causa

NetWorker engineering identified a code defect.

Resolución

A code fix for this issue was released in NetWorker 19.9.0.2; upgrade the NetWorker server to this release (or later).

 

Workaround:

Start the restore again; however, this time, select the save set which was cloned to the ddboost device in the previous attempt. The resurrection process is skipped since the save set is on a ddboost device. The restore process begins. 

Información adicional

This issue was observed on AFTD devices; however, the issue may also appear when resurrecting VMs save sets from other non-ddboost devices (tape, CloudBoost). 

The following KB details how a staging pool should be configured prior to performing VM resurrection restores: NetWorker vProxy: VM Restore resurrection from tape fails with "Unable to resurrect clone SSID to a Data Domain volume in a staging pool"

Productos

NetWorker Family, NetWorker, NetWorker Series
Propiedades del artículo
Número del artículo: 000219129
Tipo de artículo: Solution
Última modificación: 04 nov 2025
Versión:  3
Encuentre respuestas a sus preguntas de otros usuarios de Dell
Servicios de soporte
Compruebe si el dispositivo está cubierto por los servicios de soporte.