DPM 2016 Volume Missing alert RRS feed

  • Question

  • Good Afternoon,

    We are running DPM 2016 on windows server 2016 standard with 2 HPE MSA 2050 SAN for the Storage Pool.

    Recently "Volume missing" occurred twice on our DPM server for different protection group.

    For the fist time, we guess the reason may due to the unstable disk status, and clear the alert by running a rescan on DMP Management section.

    But it happened again last weekend and caused backup job failed by that protection group. When checked, there is nothing in the event logs(administrative/system/hardware) showing an error at the time the message appears.

    We did rescan again, and the missing volume is found back.

    My question are

    1) Is there any potential reason for this ID:3010 alert.

    2) Is there any good idea to prevent this kind alert in the future.

    Thank you for taking the time to read my question.

    Best Regards,


    Monday, April 15, 2019 9:44 PM

All replies

  • Hello Ivy,

    It is difficult to say what it could be with so little information, there could be multiple causes to why this is happening.

    Do you see anything in the HPE SAN?

    The Windows operating system usually sees "some" event, but rarely something useful when it's hardware issues.

    You could also check if the DPM logs say anything:

    DPM Server log

    • C:\Program Files\Microsoft System Center 2016\DPM\DPM\Temp\MSDPMCurr.errlog

    Could you also post the full description of the ID:3010 alert?

    Best regards,

    Blog: LinkedIn:

    Monday, April 15, 2019 9:54 PM
  • Hello, Leon,

    Thank you very much for your response. And sorry for the limited information, because I couldn't upload a picture right now.

    Here is the general description of the event on our server:

    Event 3101, DPM-EM

    Recovery data for Volume C:\ on XXXX in protection group YYYY resides on a volume that cannot be detected. All subsequent protection activities relating to C:\ will fail until this volume is brought back online or the replica is re-created.(ID:3101)

    And I'm checking DPM server log now to see whether I could find something.

    Thank you & best regards,


    Tuesday, April 16, 2019 3:06 PM
  • Sorry, I wrote a wrong event ID number in my former message, the correct one is 3101.
    Tuesday, April 16, 2019 3:11 PM
  • Clearly the volume has been lost and DPM complains about it, but this doesn't seem to be an issue caused by DPM itself.

    How are these SAN volumes mapped to the DPM server? Do these volumes have multiple SAN paths for each volume (fault tolerance)?

    Blog: LinkedIn:

    Tuesday, April 16, 2019 5:04 PM
  • We have one virtual disk, which is a collection of two HPE MAS 2050 SAN physical disks, used as DPM disk storage. And when I checked properties of that virtual disk, it shows three "HPE MSA 2050 SAN Multi-Path Disk Device" records (LUN is different). So I guess we have multiple SAN paths for each volume.

    Besides, thank you for the path of DMP error log, I found that there is a "(ComponentCode)16, JobManger.cs(709), NORMAL Jobmanager is idle" record happened 2 to 4 times just a little before the time of "Event 3101, DPM-EM" alert occurred for three times. Do you know what is meaning of "Jobmanager is idle" and how I could check more for it.

    Thank you very much.

    Tuesday, April 16, 2019 7:18 PM
  • These log events don't say much, it simply states that there are no current jobs.

    Is the DPM server a physical or a virtual server?

    I would check the HPE SAN system if there's any more clues to why the volume becomes missing.

    Also make sure you have your DPM 2016 updated to the latest Update Rollup, and the Windows is patched fully.

    Blog: LinkedIn:

    Tuesday, April 16, 2019 8:48 PM
  • Our DPM server is a physical server. Maybe we need to contact HPE if we meet this problem again.

    And thank you very much for your suggestions. I will discuss with my colleagues whether to make a update.

    Wednesday, April 17, 2019 7:44 PM
  • Yes I suggest you check with HPE to see if they could find anything, since both your server and storage is from HPE they might have some good tools/ways of finding out what could be the cause for the volume going missing.

    Blog: LinkedIn:

    Wednesday, April 17, 2019 7:52 PM
  • Hello Ivy,

    Just wanted to check in with you if you have any update on your issue?

    Blog: LinkedIn:

    Friday, April 26, 2019 6:56 AM