SCDPM 2019 The storage involving the current operation could not be read from or written to (ID 40003)

Question

Hi all,

We have SC DPM 2019, on Server 2019, RU3, and through all the RU's we have had a repeated issue, which was an issue in DPM 2016 - but was resolved - but using DPM 2016 won't work for us, as we have other Server 2019 systems that we need to protect and DPM 2016 does not protect Server 2019.

The specific error we now get is:
The storage involving the current operation could not be read from or written to. (ID 40003)

But we also used to get an error that mentioned about not being able to mount or unmount the volume that was being processed during the protection job.

This has been affecting a small amount of SQL volumes repeatedly, then a larger amount, and now it's affected all SQL instances and RCT backups of VM's too. Reboot the server with the DPM on (i.e. not the host servers, the VM's or anything else that hosts the volumes or storage devices) and then the failed jobs can be re-run and most of the time the jobs will then succeed, successfully backing up all types of protection points. But we don't want to have to always be rebooting our DPM server (nothing else runs on the server, FYI) just to resolve this issue. I must add that this is an inconsistant error, it has been happening roughly once a week, sometimes multiple times a week, but sometimes, not for a few weeks.

We have tried changing the volumes, where the data is backed up from, and the DPM volume, where the data is backed up to, but no change, error still occurs.

We don't want to live like this, it's an added pressure that we don't have time for, we just want DPM to work, please help.

Answer 1

Hello

https://social.technet.microsoft.com/Forums/en-US/30f8ef3f-1d20-42ae-bffb-dab49fdea0fc/quoterror-40003-the-storage-involving-the-current-operation-could-not-be-read-from-or-written?forum=dataprotectionmanager

https://social.technet.microsoft.com/Forums/en-US/79853ec4-1659-4434-b008-006e24c044d6/dpm-2016-the-storage-involving-the-current-operation-could-not-be-read-from-or-written-to-id?forum=dataprotectionmanager

Answer 2

Hello,

in DPM This issue occurs if the input/output (I/O) latency is greater than the standard SMB time-out (60 seconds).

On the protected server, open Registry Editor, and then add the SessTimeout registry entry as shown under the following subkey:

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters SessTimeout REG_DWORD 1200

Note : The 1,200 seconds (20 minutes) time-out is a recommended value. Adjust the value as appropriate. You can review the Resilient File System (ReFS) event logs on the DPM or Azure Backup Server server to find any suspected I/O latency.

---

--If the reply is helpful, please Upvote and Accept as answer--