PowerProtect 虛擬機器 TSDM 組態失敗，並顯示ABV0025「資源不足」

PowerProtect Data Manager 用於透過虛擬機器 （VM） Direct Engine 解決方案保護 vSphere 環境。虛擬機器正新增至 VM 保護原則，但無法使用ABV0025啟用篩選器驅動程式。

ABV0025: VM Direct engine is unable to configure protection for the virtual machine 'MY-VM-NAME' on vCenter 'MY-VCENTER-NAME'.

The VM Direct engine cannot complete protection of this virtual machine because the protection configuration was unsuccessful.

Review the error details and summary log in the Jobs window, or review the log files at /var/log/brs/vmdm for more detailed information to troubleshoot the issue.

Read Less
Unable to ENABLE LWD on MY-VM-NAME - SPIF filters change failure: Not enough resources..Failed to attach IO Filter vmwarelwd: Not enough resources. 

vmdm.log顯示：

...
YYYY-MM-DD HH:MM:SS INFO [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.patchDisksWithLWDEnabled(573)] -  Disk: [PFA-X70R2-DAK-01_Production_248] MY-VM-NAME/MY-VM-NAME.vmdk, LwdEnabled: false, Excluded: null 
YYYY-MM-DD HH:MM:SS INFO [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.patchDisksWithLWDEnabled(573)] -  Disk: [PFA-X70R2-DAK-01_Production_248] MY-VM-NAME/MY-VM-NAME_1.vmdk, LwdEnabled: false, Excluded: null 
YYYY-MM-DD HH:MM:SS INFO [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.patchDisksWithLWDEnabled(573)] -  Disk: [Isilon DAK VM Stasis] MY-VM-NAME/MY-VM-NAME.vmdk, LwdEnabled: false, Excluded: null 
...
YYYY-MM-DD HH:MM:SS INFO [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.waitForVsanTask(399)] -  Task Task-task-9141788 state=ERROR name=null 
YYYY-MM-DD HH:MM:SS WARN [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.configureProtect(374)] -  Unable to ENABLE LWD on MY-VM-NAME 
YYYY-MM-DD HH:MM:SS WARN [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.u.SdmEnableProtectUtil.configureProtect(381)] -  DpSetProtection error message: SPIF filters change failure: Not enough resources..Failed to attach IO Filter vmwarelwd: Not enough resources.  
YYYY-MM-DD HH:MM:SS WARN [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.a.VPEConfigureOp.logErrorStack(64)] -  Unable to configure MY-VM-NAME
com.emc.brs.vmdm.error.ComponentException: Unable to ENABLE LWD on MY-VM-NAME - SPIF filters change failure: Not enough resources..Failed to attach IO Filter vmwarelwd: Not enough resources. 
	at com.emc.brs.vmdm.vpe.util.SdmEnableProtectUtil.configureProtect(SdmEnableProtectUtil.java:386)
	at com.emc.brs.vmdm.vpe.util.SdmEnableProtectUtil.configureProtection(SdmEnableProtectUtil.java:204)
	at com.emc.brs.vmdm.vpe.util.SdmEnableProtectUtil.configureProtection(SdmEnableProtectUtil.java:216)
	at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.chooseDataMoverType(VPEConfigureOp.java:223)
	at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.createConfig(VPEConfigureOp.java:152)
	at com.emc.brs.vmdm.vpe.actions.VPEConfigureOp.execute(VPEConfigureOp.java:105)
	at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.execute(VPEActionDispatcher.java:367)
	at com.emc.brs.vmdm.vpe.service.VPEActionDispatcher.lambda$executeOp$1(VPEActionDispatcher.java:333)
	at com.emc.brs.vmdm.vpe.util.ResourceUtils$JobExecutorImpl.lambda$createWorkflowTask$0(ResourceUtils.java:151)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
 
YYYY-MM-DD HH:MM:SS ERROR [vpe-thread-1084] [00000000-0000-4000-a000-000000000000][][][TRACE_ID:b7ad8bc8de550939;JOB_ID:85288865f56e08a6][] [c.e.b.v.v.a.VPEConfigureOp.buildWorkflowException(383)] -  Unable to create configuration -- Unable to ENABLE LWD on MY-VM-NAME - SPIF filters change failure: Not enough resources..Failed to attach IO Filter vmwarelwd: Not enough resources. 
Parameters: {
  "asset" : "MY-VM-NAME",
  "plc" : "VMware Production Cluster",
  "dataConsistency" : "CRASH_CONSISTENT",
  "storage" : "MY-DD-STORAGE",
  "storageUnit" : "MY-STORAGE-UNIT",
  "replicationStorage" : "MY-REPLICATION-STORAGE",
  "replicationStorageUnit" : "MY-REPLICATION-STORAGE-UNIT",
  "taskId" : "9ed662ac-cc58-4eab-8362-6c3c7b1ceb75",
  "vcenter" : "MY-VCENTER-NAME"
}
Result: {
  "status" : "Failure",
  "error" : "Unable to ENABLE LWD on MY-VM-NAME - SPIF filters change failure: Not enough resources..Failed to attach IO Filter vmwarelwd: Not enough resources. "
}

vSphere Web Client 會顯示類似的錯誤訊息：