PPDM - NAS Restore fails with error ARN0010 NAS asset does not have an address configured

From PowerStore, the NAS server was decommissioned and so deleted. As a result, the asset was shown as "Not Detected."

A copy of that deleted share from the NAS server was needed, so a restore was triggered from PowerProtect Data Manager, but failed with the following error:

Error from the UI:

From the nasdm.log JobLogs, the following error can be seen:

nasdm.2026-04-03.0.log.gz: 2026-04-03T10:12:21.907Z ERROR [] [pool-55065-thread-1] [][][TASK_ID:b84a03c0f638133a][TRACE_ID:acb0e52b213ac307;JOB_ID:9299e34155d0c00f][] [c.e.d.e.n.a.ActivityUtility.failTask(47)] -  Error :Source NAS asset NAS_ASSET does not have an address configured. 
com.emc.dpsg.ecdm.nasdm.exception.ServerInfoException: Source NAS asset NAS_ASSET does not have an address configured.
	at com.emc.dpsg.ecdm.nasdm.utils.RequestProcessorUtil.lambda$validateSourceAsset$20(RequestProcessorUtil.java:1080)
	at com.emc.dpsg.ecdm.nasdm.appManager.BaseNotificationMessageHandler.throwIf(BaseNotificationMessageHandler.java:78)
	at com.emc.dpsg.ecdm.nasdm.utils.RequestProcessorUtil.validateSourceAsset(RequestProcessorUtil.java:1077)
	at com.emc.dpsg.ecdm.nasdm.service.NasFlrProcessorService.prepareFlrRestoreRequest(NasFlrProcessorService.java:151)
	at com.emc.dpsg.ecdm.nasdm.service.restore.NasFLRJobHandler.execute(NasFLRJobHandler.java:126)
	at com.emc.dpsg.ecdm.nasdm.service.restore.NasFLRJobGroupHandler.lambda$executeFLRTask$14(NasFLRJobGroupHandler.java:347)
	at com.emc.brs.tracing.api.LogTracingRunnableWrapper.run(LogTracingRunnableWrapper.java:36)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	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)

The original NAS server was deleted from PowerStore, after which the user reran discovery. As a result, the shares that were originally discovered under that NAS server were marked as Not Detected. During restore operations, this led to failures at the NASDM layer due to strict Source Asset validation, which expected the original NAS server to be present.

This issue will be fixed in the next PowerProtect Data Manager version 20.2 and above.

In the meantime, if it is encountered in version 20.1 or lower, please raise a Support Service request and quote this article to get a HotFix.