PowerProtect: VMware Instant Access Restore en FLR fails Mount failed

Summary: Virtual Machine (VM) Instant Access (IA) of File Level Recovery (FLR) mislukt met foutmelding "Mount failed: Kan Sysinfo-bewerking niet voltooien"

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

 

Instant Access Restore of FLR mislukt met de volgende fout in het VM Direct Engine (VMDE)-koppellogboek.

Logboek: mount-xxxxxxxxxx.log

Locatie van logboek: (Ingesloten VMDE) /opt/emc/vproxy/runtime/logs/recycle/vproxyd/ | /opt/emc/vproxy/runtime/logs/recycle/vbackupd/ (Externe VMDE)

YYYY-MM-DDThh:mm:ss.270Z NOTICE: [8d389cdc46ece06b;96ae9dbd0918a908] "Text": "Session '07fae483-61e9-43da-acca-b32f48656db0' is unsuccessful: Unable to create datastore: Unable to create datastore 'DELL-vProxy-ppdm01.fqdn 1682513359' using '*.*.*.*:/data/col1/Dev-Test-ppdm01-71b45/PLCTLP-XXXX/Restores/yyyy/zzzz-zzzz/1683583862592975399/1682025362/vProxy-ppdm01.fqdn xxxxxxx': ServerFaultCode: An error occurred during host configuration. Operation failed, diagnostics report: Mount failed: Unable to complete Sysinfo operation. Please see the VMkernel log file for more details.: Unable to query remote mount point's attributes",

In nieuwere versies van PowerProtect Data Manager, bijvoorbeeld 19.18 of 19.19, wordt er geen koppelingslogboek gemaakt en kan de onderstaande fout worden waargenomen tijdens de hersteltaak.

PowerProtect Data Manager UI met details over taak mislukt

Het vmdm-logboek van PowerProtect Data Manager bevat de volgende fout.

Logboek: vmdm.log

Locatie van logboek: /var/log/brs/vmdm

2025-04-11T11:58:16.470Z WARN [] [request-dispatch-service-1] [][][][][] [c.e.b.v.r.c.StreamCountService.exchange(282)] - Exception Response Body {"code":500,"reason":"Cannot invoke \"com.emc.brs.datadomain.
ddboost.DdConnectionInfo.getConnDesc()\" because \"ddConnection\" is null","remediation":null,"timestamp":1744372696467,"path":"/api/v2/copies/a33f6343-85a8-4044-a992-dc4b8487d9fe/recovery-stream-counts","ex
tendedInfo":null}
2025-04-11T11:58:16.471Z ERROR [] [request-dispatch-service-1] [][][][][] [c.e.b.v.r.d.InstantAccessDispatchService.isRequestDispatchable(75)] - Exception checking allowance
com.emc.brs.vmdm.error.ComponentException: Cannot invoke "com.emc.brs.datadomain.ddboost.DdConnectionInfo.getConnDesc()" because "ddConnection" is null
        at com.emc.brs.vmdm.vpe.service.clients.RestClientBase.exchange(RestClientBase.java:284)
        at com.emc.brs.vmdm.vpe.service.clients.RestClientBase.get(RestClientBase.java:201)
        at com.emc.brs.vmdm.recovery.clients.StreamCountService.getStreamCounts(StreamCountService.java:51)
        at com.emc.brs.vmdm.recovery.dispatch.InstantAccessSessionService.exceedsAllowance(InstantAccessSessionService.java:90)
        at com.emc.brs.vmdm.recovery.dispatch.InstantAccessDispatchService.isRequestDispatchable(InstantAccessDispatchService.java:73)
        at com.emc.brs.vmdm.recovery.dispatch.InstantAccessDispatchService.isRequestDispatchable(InstantAccessDispatchService.java:31)
        at com.emc.brs.vmdm.recovery.dispatch.BaseRequestDispatchService.getRequestFromWaiting(BaseRequestDispatchService.java:301)
        at com.emc.brs.vmdm.recovery.dispatch.BaseRequestDispatchService.getRequest(BaseRequestDispatchService.java:232)
        at com.emc.brs.vmdm.recovery.dispatch.BaseRequestDispatchService.checkRequests(BaseRequestDispatchService.java:120)
        at com.emc.brs.vmdm.recovery.dispatch.BaseRequestDispatchService.lambda$startChecking$2(BaseRequestDispatchService.java:101)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
        at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)

Cause

De herstelfout heeft te maken met de NFS-configuratie die is ingeschakeld op de PowerProtect DD (DD). ESXi-host kan de NFSv4-export niet koppelen. Op het moment van dit artikel kan de ESXi-host alleen NFSv3- of NFSv4.1-exports koppelen.

 

Scenario één:

DD heeft zowel NFSv3- als NFSv4-versies ingeschakeld en NFSv4 is ingesteld als de standaardinstelling op DD.

DD NFS-versie ingeschakeld 1

De opdracht DD toont de standaardserver.

nfs option show

NFS-optie Uitvoer weergeven

 

Scenario twee:

DD heeft alleen NFSv4 ingeschakeld.

DD NFS-versie ingeschakeld 2 


 

Resolution

Afhankelijk van de huidige DD NFS-configuratie, schakelt u NFSv3 in en zorgt u ervoor dat de standaard NFS-exportversie op de DD naar NFSv3 wordt gebruikt:
 

  1. Maak verbinding met DD via SSH.
  2. Bevestig uw huidige NFS-configuratie.
nfs option show

Voorbeeld: NFSv3 is ingeschakeld, maar NFS-standaardserver is NFSv4.

NSFV4 standaard

  1. Als deze optie is uitgeschakeld, schakelt u NFSv3 in.
nfs disable version 3
    1. Als NFS versie 4 is, stelt u NFSv3 in.
nfs option set default-server-version 3
  1. Voer Instant Access of File Level Restore opnieuw uit.
     

Affected Products

PowerProtect Data Manager Appliance, PowerProtect Data Manager, PowerProtect Data Manager Software
Article Properties
Article Number: 000214971
Article Type: Solution
Last Modified: 18 Jul 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.