PowerProtect: Falha no backup da VM indicando que uma sincronização do DPD está em andamento

Summary: Alguns backups de ativos de máquina virtual (VM) começaram a falhar depois que foram concluídos com sucesso. Os detalhes da falha indicam que a tarefa do vCenter apresenta falha com um erro TSDM indicando "DPD Sync in progress". ...

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). Alguns backups de ativos de VM começaram a falhar quando eram concluídos com sucesso no passado. Os detalhes da falha indicam que a tarefa do vCenter falhou com um erro TSDM indicando "DPD Sync in progress." Os detalhes ABV0016 e ABV0006 mostram:

Caixa de diálogo de detalhes de erros de falha no backup do host 
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 cleanup from earlier backup attempt.  Unable to cleanup session 'Backup:6755cb99-3de5-4731-8b6f-6c64bb809f0b' from virtual machine 'my-vm-name' (MORef = 'vm-241').  Unable to cancel TSDM / LWD snapshot.  The vCenter task for 'Cancel SDM Snapshot' completed with state 'error':  DPD Sync in progress.
ABV0006: 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

vCenter task 'task-943698' failed:  VimFault: 'dp.vpx.fault.SnapshotInProgress.summary': DPD Snapshot in progress
A sessão de backup pode mostrar as seguintes saídas de status: 
...
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]   },
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]   "Status": {
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]     "State": "Failure",
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]     "Description": "Backup is unsuccessful:  Unable to cleanup from earlier backup attempt.  Unable to cleanup session 'Backup:6755cb99-3de5-4731-8b6f-6c64bb809f0b' from virtual machine 'vm-vm-name' (MORef = 'vm-241').  Unable to cancel TSDM / LWD snapshot.  The vCenter task for 'Cancel SDM Snapshot' completed with state 'error':  DPD Sync in progress",
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]     "Progress": 0,
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]     "Error": {
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]       "Text": "Unable to cleanup from earlier backup attempt.  Unable to cleanup session 'Backup:6755cb99-3de5-4731-8b6f-6c64bb809f0b' from virtual machine 'vm-vm-name' (MORef = 'vm-241').  Unable to cancel TSDM / LWD snapshot.  The vCenter task for 'Cancel SDM Snapshot' completed with state 'error':  DPD Sync in progress",
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]       "Code": 0,
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]       "Classifications": [],
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]       "Retryable": false,
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]       "Remedy": null
YYYY-MM-DD HH:MM:SS INFO:   [acae20b6ae1ca9c8;aac63ea8d0fb1d9e]     },
...
...
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]   },
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]   "Status": {
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]     "State": "Failure",
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]     "Description": "Backup is unsuccessful:  vCenter task 'task-943698' failed:  VimFault: 'dp.vpx.fault.SnapshotInProgress.summary': DPD Snapshot in progress, TSDM snapshot UUID = '52031978-18dd-444a-37fd-9c070de84cc5'",
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]     "Progress": 0,
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]     "Error": {
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]       "Text": "vCenter task 'task-943698' failed:  VimFault: 'dp.vpx.fault.SnapshotInProgress.summary': DPD Snapshot in progress, TSDM snapshot UUID = '52031978-18dd-444a-37fd-9c070de84cc5'",
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]       "Code": 0,
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]       "Classifications": [],
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]       "Retryable": false,
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]       "Remedy": null
YYYY-MM-DD HH:MM:SS INFO:   [a3f45e322add25ec;bb6e18b9d1e8178c]     },
...

Cause

A VM afetada tem uma tarefa órfã do vSphere Snapshot Data Mover (SDM) que o fluxo de trabalho de backup do TSDM não pode cancelar devido a inconsistências no daemon dpd . O motivo da inconsistência da tarefa órfã ou dpd permanece não identificado.

Resolution

O daemon dpd deve ser reiniciado no host do ESXi, e o recurso SDM deve ser desativado e ativado na VM afetada. Certifique-se de que não há backups de máquinas virtuais antes de reiniciar o daemon dpd :

  • Abra uma sessão ssh para o host do ESXi.
  • Reinicie o daemon dpd : /etc/init.d/dpd restart
[root@my-server ~]# ssh root@my-esx
The authenticity of host 'my-esx (192.168.9.111)' can't be established.
ECDSA key fingerprint is SHA256:LHQVSVzDSw7ezlDVG59nyGD+C/Ugcx/jaSLMbzsY18U.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'my-esx' (ECDSA) to the list of known hosts.
(root@my-esx) Password:
The time and date of this login have been sent to the system logs.

WARNING:
   All commands run on the ESXi shell are logged and may be included in
   support bundles. Do not provide passwords directly on the command line.
   Most tools can prompt for secrets or accept them from standard input.

VMware offers powerful and supported automation tools. Please
see https://developer.vmware.com for details.

The ESXi Shell can be disabled by an administrative user. See the
vSphere Security documentation for more information.
[root@my-esx:~] /etc/init.d/dpd restart
Restarting dpd: dpd stopped.
Setting the memory limit for dpd resource pool on this host to 320 MB
Setting max number of file descriptors to 32768
Setting MALLOC_ARENA_MAX to 20
success
[root@my-esx:~]

 

Aqui estão alguns dos métodos disponíveis para desativar e habilitar o SDM na VM afetada.

Método 1

Altere o mecanismo de proteção de ativos da VM afetada.

  1. Abra uma sessão do navegador no PowerProtect Data Manager e autentique-se com uma conta de administrador.
  2. Navegue até Infrastructure>Assets >Virtual Machines.
  3. Selecione a máquina virtual afetada.
  4. Selecione a lista suspensa More Actions>Protection Mechanism>Migrate to VADP.
  5. O vSphere Web Client mostra uma tarefa para que a máquina virtual desative o filtro LWD (Lightweight Delta).
  6. Selecione a lista suspensa More Actions>Protection Mechanism>Migrate to Transparent Snapshots.
  7. O vSphere Web Client mostra uma tarefa para a máquina virtual habilitar o filtro LWD.
  8. Execute um backup ou monitore a execução do backup agendado.

Método 2

Remova e adicione a VM afetada da política de proteção.

  1. Abra uma sessão do navegador no PowerProtect Data Manager e autentique-se com uma conta de administrador.
  2. Navegue até Infrastructure>Assets >Virtual Machines.
  3. Selecione a máquina virtual afetada.
  4. Selecione a lista suspensa More Actions>Remove from Policy.
  5. O vSphere Web Client mostra uma tarefa para que a máquina virtual desative o filtro LWD (Lightweight Delta).
  6. Selecione a lista suspensa More Actions>Add to Policy e siga o assistente para adicionar à política de proteção.
  7. O vSphere Web Client mostra uma tarefa para a máquina virtual habilitar o filtro LWD.
  8. Execute um backup ou monitore a execução do backup agendado.

Método 3

O PowerProtect Data Manager vmconfig O utilitário de linha de comando pode ser usado para alterar a configuração do recurso SDM da VM afetada.

  • Faça log-in no equipamento PowerProtect Data Manager usando SSH com a conta de administrador: 
     ssh admin@my-ppdm-name
  • Mude para o usuário root: 
    sudo su 
  • Carregue as variáveis de ambiente: 
    source /opt/emc/vproxy/unit/vproxy.env
  • Mude para o diretório bin do vProxy: 
    cd /opt/emc/vproxy/bin/
  • Construa o vmconfig substituindo as informações entre colchetes:
    • Verifique o status da VM:
./vmconfig -v <vcenter-ip-fqdn> -u '<vcenter-user-name>' -p '<vcenter-user-pwd>' -l dns -k <VM DNS name> -c info
  • Desative o SDM na VM:
./vmconfig -v <vcenter-ip-fqdn> -u '<vcenter-user-name>' -p '<vcenter-user-pwd>' -l dns -k <VM DNS name> -c disable-sdm
  • Habilite o SDM na VM:
./vmconfig -v <vcenter-ip-fqdn> -u '<vcenter-user-name>' -p '<vcenter-user-pwd>' -l dns -k <VM DNS name> -c enable-sdm
  • Execute um backup do TSDM do PowerProtect Data Manager para confirmar se o problema foi resolvido.

Additional Information

Houve aprimoramentos do VMware no daemon dpd para ajudar a resolver inconsistências com a operação de sincronização. Certifique-se de que o ambiente esteja executando o ESXi 7.0 U3o (22348816), ESXi 8.0 Ub (21203435) ou uma versão mais recente.
Article Properties
Article Number: 000210949
Article Type: Solution
Last Modified: 14 Mar 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.