PowerProtect: TSDM-sikkerhedskopieringer mislykkes med ABV0016 mod en bestemt ESXi-vært

Summary: Beskyttelsespolitikken for den virtuelle maskine (VM) støder på periodiske sikkerhedskopieringsfejl under den planlagte kørsel med kritisk meddelelses-id 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 TSDM-løsningen (Transparent Snapshot Data Mover) beskytter vSphere-miljøet. Politikken for beskyttelse af virtuelle maskiner (VM) støder på periodiske sikkerhedskopieringsfejl under den planlagte udførelse. PowerProtect-grænsefladen viser et kritisk meddelelses-id ABV0016:
 
PPDM-brugergrænsefladen (UI) viser kritisk meddelelses-id ABV0016
 
Den fulde meddelelsestekst lyder: 
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 create LWD snapshot.  vCenter task 'task-#####' failed:  VimFault: dp.vpx.fault.DpdThrottleLimitExceeded.summary' 
Logfilen over sikkerhedskopieringssessioner viser: 
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: SDM Full Sync: Closed file 'VM_Image_Daily_NON-SQL-uklpdtsbk001-f4723/PLCTLP-2832693c-377a-4f7e-952f-ffc1fdade2b1/Backups/c57b4143-f4c3-4760-86f5-7448429205ae/501efcd4-1f7e-5c9d-b98c-43633d01aa4c/lastSdmDiskBackupPath.json'.
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: SDM Full Sync: Checking if the last path exists which was used as a baseline for each disk ...
YYYY-MM-DD HH:MM:SS INFO:   [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: SDM Full Sync: Full sync is not needed, skipping.
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: vCenter SOAP call 'DpSnapshot' was accepted.
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: The vCenter task failed:  dp.vpx.fault.DpdThrottleLimitExceeded.summary
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: The vCenter task for 'Create SDM Snapshot' completed with state 'error'.
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: Unable to create SDM snapshot.
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: Retrying in 500ms...
...
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: vCenter SOAP call 'DpSnapshot' was accepted.
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: The vCenter task failed:  dp.vpx.fault.DpdThrottleLimitExceeded.summary
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: The vCenter task for 'Create SDM Snapshot' completed with state 'error'.
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: Unable to create SDM snapshot.
YYYY-MM-DD HH:MM:SS ERROR:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Create LWD Snapshot: Unsuccessful after 98 attempts over 1m0.158271936s.
YYYY-MM-DD HH:MM:SS TRACE:  [a30a8b8946958a4e;8d8911578980c3ff] SDM Data Mover: Snapshot failure can't be remedied by a Full sync.
vSphere-webklienten viser mindst én ESXi-vært med kontinuerlige LWD-baserede fejl under den planlagte kørsel.

vSphere-webklienten viser mindst én ESXi-vært med kontinuerlige LWD-baserede fejl under den planlagte kørsel

Outputtet i vCenter Support-pakken /var/log/vmware/vsan-health/vsanvcmgmtd-*.log viser, at ESXi-værten identificeres som en ældre DPD-vært: 
YYYY-MM-DD HH:MM:SS warning vsanvcmgmtd[11593] [vSAN@6876 sub=dps] [opId=0849c23c] Found legacy DPD on host: host-29. Applying legacy throttle limit: '10', instead of regular throttle limit: '20'
 

Cause

DPD-tjenesten har afhængigheder med vCenter vSAN Health Service, selv når vSAN-storage ikke er konfigureret i miljøet. vCenter vSAN Health Service leverer oplysninger om ESXi-versionen for at bestemme antallet af samtidige SDM-sessioner (Snapshot Data Mover), der understøttes af ESXi-værten. Antallet af samtidige SDM-sikkerhedskopieringssessioner pr. ESXi-vært er 20 med vSphere version 7.0 U3d (ESXi og vCenter). vSphere-versionerne før vSphere 7.0 U3d (ældre versioner) kunne kun udføre 10 samtidige SDM-sikkerhedskopieringssessioner.  

Hvis vCenter vSAN Health Service-cachen har forældede versionsoplysninger eller en null-post, kategoriseres ESXi-værten som ældre. Standardbegrænsningen i PowerProtect Data Manager sender 18 SDM-sikkerhedskopieringssessioner pr. ESXi-vært. ESXi-værten behandler de første 10 SDM-sikkerhedskopier, men vCenter vil svigte alle efterfølgende SDM-sikkerhedskopieringer, der angiver, at DPD-grænsen er overskredet.

Resolution

Der er forbedringer i vSphere 8.0 U1, som automatisk opdaterer vSAN Health Service-cachen under visse forhold. Det anbefales at opgradere til vSphere 8.0 U1 for at drage fordel af disse forbedringer og forhindre visse symptomer på vSAN Health-tjenestens cache. 

VMware-løsning:
Sørg for, at vCenter-serveren og alle ESXi-værterne i klyngen har version 7.0 U3d eller nyere. Ryd cachen ved at genstarte vCenter Server Appliance (VCSA) vSAN Health-tjenesten over en SSH-session:

service-control --restart vsan-health

Kontakt om nødvendigt VMware Support for at få yderligere indsigt eller hjælp til vSAN Health-tjenesten.

Additional Information

Løsning i PowerProtect Data Manager:
Der findes en metode i PowerProtect Data Manager til at reducere begrænsningsværdien for TSDM-sikkerhedskopieringssessioner i forhold til alle ESXi-værter. Dette kan bruges som en midlertidig løsning, mens du opgraderer ESXi-værterne eller arbejder med VMware Support.

  • Sørg for, at der ikke kører beskyttelsesjob
  • Log på PowerProtect Data Manager, og opgrader til sudo: sudo su –
  • Lav en kopi af filen vmdirect.env: cp vmdirect.env vmdirect.env.orig
  • Åbent miljø vmdirect.env fil: vi / opt / emc / vmdirect/unit / vmdirect.env
  • Skift værdien for miljøvariablen "MAX_SDM_BACKUP_SESSIONS_PER_HOST" til 10 (i stedet for 18), og gem filen.
  • Genstart VISD-tjenesten :  
    systemctl restart visd.service

Eksempel på output:

my-ppdm:/opt/emc/vmdirect/unit # cp vmdirect.env vmdirect.env.orig
my-ppdm:/opt/emc/vmdirect/unit # ls -l
total 20
-rwxr-xr-x 1 root root  397 Nov  2 22:48 visd.service
-rwxr-xr-x 1 root root 2225 Nov  2 22:48 vmdirect.env
-rwx------ 1 root root 2225 Apr 21 09:39 vmdirect.env.orig
-rwxr-xr-x 1 root root  360 Nov  2 22:48 vpod-nas.service
-rwxr-xr-x 1 root root  334 Nov  2 22:48 vpod.service
my-ppdm:/opt/emc/vmdirect/unit # vi vmdirect.env
my-ppdm:/opt/emc/vmdirect/unit # cat vmdirect.env | grep SDM
SDM_ENABLED_EXTERNAL_PROXIES=false
export SDM_ENABLED_EXTERNAL_PROXIES
MAX_SDM_SESSIONS_PER_HOST=20
export MAX_SDM_SESSIONS_PER_HOST
MAX_SDM_BACKUP_SESSIONS_PER_HOST=10
export MAX_SDM_BACKUP_SESSIONS_PER_HOST
MAX_ESX_SDM_TOTAL_DISKS=40
export MAX_ESX_SDM_TOTAL_DISKS
my-ppdm:/opt/emc/vmdirect/unit # systemctl restart visd.service
my-ppdm:/opt/emc/vmdirect/unit # systemctl status visd.service
● visd.service - VMDirect Infrastructure Services Daemon
   Loaded: loaded (/usr/lib/systemd/system/visd.service; enabled; vendor preset: disabled)
   Active: active (running) since Fri YYYY-04-21 09:42:38 PDT; 7s ago
Main PID: 67488 (visd)
    Tasks: 16 (limit: 512)
   Memory: 23.2M
      CPU: 317ms
   CGroup: /system.slice/visd.service
           └─67488 /opt/emc/vmdirect/bin/visd -user admin -group app -p 9097 -nodemgmt -proxymgmt -vmdeployment -installclient -l

Apr 21 09:42:38 my-ppdm.my-domain.com systemd[1]: Started VMDirect Infrastructure Services Daemon.
Apr 21 09:42:38 my-ppdm.my-domain.com visd[67488]: INFO:   Found GID 2000 (app) for group 'app'.
Apr 21 09:42:38 my-ppdm.my-domain.com visd[67488]: NOTICE: Effective group ID is set to 2000 (app).
Apr 21 09:42:38 my-ppdm.my-domain.com visd[67488]: INFO:   Found UID 500 (admin) for user 'admin'.
Apr 21 09:42:38 my-ppdm.my-domain.com visd[67488]: NOTICE: Effective user ID is set to 500 (admin).
my-ppdm:/opt/emc/vmdirect/unit #
Article Properties
Article Number: 000213170
Article Type: Solution
Last Modified: 18 Nov 2025
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.