El respaldo de VM de PowerProtect falla ABV0016 "La operación no está permitida en el estado actual"

Summary: Los respaldos de Transparent Snapshot Data Mover (TSDM) de máquinas virtuales (VM) fallan intermitentemente con el código de error ABV0016.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

PowerProtect Data Manager se utiliza para proteger el entorno de vSphere con la solución Transparent Snapshot Data Mover (TSDM). El paquete de instalación de vSphere (VIB) se implementó correctamente en los hosts ESXi del clúster. Los respaldos de máquinas virtuales (VM) fallan intermitentemente con el código de error ABV0016. La interfaz de usuario de PowerProtect Data Manager muestra lo siguiente:

ABV0016: VM Direct engine 'localhost' is unable to back up the virtual machine 'my-vm-name' on vCenter 'my-vcernter-name' because of a vCenter API issue.

The VM Direct engine cannot complete the backup of this virtual machine because of a vCenter API operation did not complete successfully.

To troubleshoot this issue: 1) Verify that the vCenter can be reached. 2) If the vCenter is busy, wait for some activities to complete and then retry the operation. 3) Verify that the virtual machine exists on the vCenter.

Read Less

Unable to successfully complete SDM Full Sync operation.  Unsuccessful after 41 attempts over 7m39.351435799s.  The vCenter task for 'SDM Snapshot Sync fullSync' completed with state 'error'.  The vCenter task failed.  The operation is not allowed in the current state.


El registro de la sesión de respaldo muestra lo siguiente:

...
YYYY-MM-DD HH:MM:SS TRACE:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: vCenter SOAP call 'DpSnapshot' was accepted.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: The vCenter task failed.  The operation is not allowed in the current state.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: The vCenter task for 'Create SDM Snapshot' completed with state 'error'.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: Unable to create SDM snapshot.
YYYY-MM-DD HH:MM:SS TRACE:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: Retrying in 500ms...
...
YYYY-MM-DD HH:MM:SS TRACE:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: Retrying in 500ms...
YYYY-MM-DD HH:MM:SS TRACE:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: vCenter SOAP call 'DpSnapshot' was accepted.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: The vCenter task failed.  The operation is not allowed in the current state.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: The vCenter task for 'Create SDM Snapshot' completed with state 'error'.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: Unable to create SDM snapshot.
YYYY-MM-DD HH:MM:SS ERROR:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Create LWD Snapshot: Unsuccessful after 99 attempts over 1m0.536375553s.
YYYY-MM-DD HH:MM:SS TRACE:  [ab2a1fb6155aefd7;be89174dd4d08446] SDM Data Mover: Snapshot failure can't be remedied by a Full sync.
...

Las tareas de vSphere Web Client para la VM muestran lo siguiente:

vsphere_error.jpg

 

 

Cause

El hipervisor ESXi que aloja la máquina virtual afectada no tiene iniciado el servicio Demonio de protección de datos (DPD). El problema se producía de forma intermitente, ya que vMotion transfirió las VM afectadas al hipervisor ESXi con el servicio DPD detenido.
vSphere_stopped.jpg
 

Resolution

Asegúrese de que el servicio DPD esté iniciado en todos los hosts ESXi del clúster. Si el servicio está detenido, seleccione el servicio DPD y la opción de inicio.
vSphere_start.jpg

El servicio DPD también se puede reiniciar mediante una sesión de SSH al host ESXi. 
[root@my_esx:~] /etc/init.d/dpd status
dpd is stopped
[root@my_esx:~] /etc/init.d/dpd start
Starting dpd:Setting the memory limit for dpd resource pool on this host to 300 MB
Setting max number of file descriptors to 800
Setting MALLOC_ARENA_MAX to 20
success
[root@my_esx:~] /etc/init.d/dpd status
dpd is running

Additional Information

Si el servicio DPD no permanece en ejecución, póngase en contacto con el soporte de VMware para determinar la causa del problema del servicio DPD.
Article Properties
Article Number: 000212050
Article Type: Solution
Last Modified: 03 Dec 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.