PowerProtect: Os backups de VM falham com ABV0016 indicando "types". Estado inválido"

Summary: Os backups de máquina virtual (VM) falham com o status de saída ABV0016 durante a criação da etapa de snapshot Light Weight Delta (LWD).

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

O PowerProtect Data Manager é usado para proteger o ambiente vSphere com a solução Transparent Snapshot Data Mover (TSDM). Os backups de máquina virtual (VM) falham com o status de saída ABV0016 durante o "Creating LWD snapshot" passo. Os detalhes do trabalho da interface do PowerProtect Data Manager mostram: 
ABV0016: VM Direct engine 'localhost' is unable to back up the virtual machine '<my-vm>' on vCenter 'my-vcenter.domain.local' because of a vCenter API issue.

The VM Direct engine cannot complete the backup of this virtual machine because 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

taskInfo.Error.Fault = '*types.InvalidState', &{VimFault:{MethodFault:{FaultCause:<nil> FaultMessage:[]}}}


O vSphere Web Client mostra tarefas para a VM afetada e mostra tarefas de erro contínuas ao criar o snapshot baseado em LWD.

Captura de tela do vSphere Web Client mostrando erros contínuos de snapshot do LWD.


O log de exportação de backup mostra:

YYYY-MM-DD HH:MM:SS DEBUG:  [a2aaedf09233d1a7;b0db985f58505615] SDM Data Mover: Create LWD Snapshot: vCenter SOAP call 'DpSnapshot' was accepted.
YYYY-MM-DD HH:MM:SS DEBUG:  [a2aaedf09233d1a7;b0db985f58505615] SDM Data Mover: Create LWD Snapshot: taskInfo.Error.Fault = '*types.InvalidState', &{VimFault:{MethodFault:{FaultCause:<nil> FaultMessage:[]}}}
YYYY-MM-DD HH:MM:SS ERROR:  [a2aaedf09233d1a7;b0db985f58505615] SDM Data Mover: Create LWD Snapshot: vCenter task 'task-1960194' failed.
YYYY-MM-DD HH:MM:SS ERROR:  [a2aaedf09233d1a7;b0db985f58505615] SDM Data Mover: Create LWD Snapshot: Unable to create LWD snapshot.
YYYY-MM-DD HH:MM:SS DEBUG:  [a2aaedf09233d1a7;b0db985f58505615] SDM Data Mover: Create LWD Snapshot: Retrying in 15s...

O tsdm.log host do ESXi mostra uma falha contínua ao tentar se comunicar com o Data Protection Daemon (DPD).

YYYY-MM-DD HH:MM:SS tsdm[2099213]: IPCMGR: Unable to connect to UDS at /var/run/vmwarelwd/daemon: No such file or directory
YYYY-MM-DD HH:MM:SS tsdm[2099213]: IPCMGR: Error creating a connection to add to pool 'dpd': No such file or directory
 

Cause

O DPD é um estado inválido no servidor ESXi que hospeda as VMs afetadas. O vSphere Web Client mostra o daemon DPD em um status Parado.
 

Status do daemon dpd do servidor ESXi

A causa do DPD ser inválido e mostrar um estado interrompido é desconhecida. O dpd.log host do ESXi mostra uma exceção há alguns dias e, em seguida, interrompe o registro. 
YYYY-MM-DD HH:MM:SS error dpd[2147513] [Originator@6876 sub=vmomi.soapStub[0]] Resetting stub adapter: service state request failed; /sdk/vimService, <last binding: <<TCP '127.0.0.1 : 31138'>, <TCP '127.0.0.1 : 80'>>>, N7Vmacore15SystemExceptionE(Host not found (authoritative))
--> [context]zKq7AVICAgAAABAEVQEOZHBkAAAtoUJsaWJ2bWFjb3JlLnNvAADiZx0ALdEbANJCFwAcoC0AwG8zAD9zMwDhTTQAy1wuAMzHLQBUAy4AAhE/ATt9AGxpYnB0aHJlYWQuc28uMAACbdEObGliYy5zby42AA==[/context]

Resolution

O DPD deve ser reiniciado no host do ESXi afetado. O DPD pode ser iniciado usando uma sessão SSH do 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 320 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


O DPD também pode ser iniciado usando o vSphere Web Client para o host do ESXi afetado em "Configure >Services":
 

Iniciar dpd por meio do vSphere Web Client


Se necessário, entre em contato com o suporte da VMware para investigar mais a fundo se o DPD é inválido e mostra um estado Parado.

Article Properties
Article Number: 000223336
Article Type: Solution
Last Modified: 21 Nov 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.