Modify Protection Group adding BMR Error 40009 The specified operation requires the associated storage to be mounted first

Chau Le 101 Reputation points
2022-10-11T23:46:22.57+00:00

a have a protection group with domain controllers and backing up system state.

When i try to modify protection group to add BMR, I get the following error. DPM 2019 Rollup 4

249571-image.png

I have searched thru the google and very little information that I can see it. Can someone help me here? I have attached 4 TB drive with 80% free. Everything looks fine in "review disk storage allocation" ... 10 days retention ... the System state is backing up just fine...

What....is...going ...on? Please help

Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 44,751 Reputation points
    2022-10-12T09:50:28.687+00:00

    Hello there,

    The first suggestion would be to Update to the latest rollup for DPM 2019 and update your Windows Server to the latest cumulative update.

    The next thing that you should do is verify that the DNS name resolution is working properly for both the DPM server and the target computers. Even if the DNS name resolution seems to be working properly, you should compare the IP address that is returned during the name resolution test with the actual IP address that the target computer is using.

    The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue. https://social.technet.microsoft.com/Forums/en-US/3a0e62aa-7a46-455f-9a1a-06c79c15a67d/dpm-2016-error-40009-the-specified-operation-requires-the-associated-storage-to-be-mounted-first?forum=dpmstorage

    ------------------------------------------------------------------------------------------------------------------------------------------

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

    1 person found this answer helpful.

  2. KurtBMayer 841 Reputation points
    2022-11-14T17:36:10.613+00:00

    @Chau Le

    What I did to remediate this situation was “Stop Protection of Group” but “Retain Protected Data.” This moved it to “Inactive Protection for Previously Protected Data.” I made note of all the PG settings then went back through and recreated the PG the same manner, except I added BMR back this time.

    Doing it this way picked up the “Inactive Protection” and dropped it back into the PG, retaining all “Recovery Points” of the “System State” while re-adding BMR into the job. A “Consistency Check” started to run on the data volume, but after that all was green!

    Please upvote and accept this thread as answered if it's helpful, thanks!

    1 person found this answer helpful.
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.