Secondary DPM protection Group member errors RRS feed

  • Question

  • Hi,

    Got two DPM 2010 servers. Primairy and secondary topology. The Primairy server is in the main office. And the secondary server is in a branch location connected through dedicated VLAN connection towards the main office. The primairy DPM server has several members of branch offices to back-up.

    When I want to back-up a protected server from the primairy dpm server on the secondary dpm server only the servers within the main office may be added. When a protected server of a branch office is selected, the proces fails when calculating the storage requirements. It gives a error id 31 in return, which indicates that the protected server is not reachable.

    From the specified branch office where the secondary server runs there isn't direct connectivity towards other branch offices possible. The main reason of the second dpm server is DR and get rid of tape back-up.

    Anyone got a similar issue? Or a solution?

    Thanks in advance,


    yours sincerly, Robin E. Turpijn Microsoft Technical Specialist @ triNext, Nieuwegein NL.
    Wednesday, November 23, 2011 3:20 PM


  • Hi,

    I am not sure if I understand correctly but it seems that one of the prerequisits for Primary/Secondary scenario is not fullfilled. You mentioned that for servers in branch office not direct connectivitity towards others is possible.

    Now for Primary/Secondary DPM to work both servers must be able to reach all backed up servers. Reason behind is the scenario that Primary/Secondary DPM is developed for. What I want to say is that the Primary -> Secondary server architecture is something like a HA scenario. Meaning in case your Primary DPM gets broken you are able to switch protection of all Servers which are backed up by Primary DPM server and synchronized to Secondary DPM server with just one klick ("Switch Protection"). For this scenario to work the Secondary DPM must be able to contact all servers that the Primary protects otherwise this scenario would not work because the agents on the backed up servers would not be able to switch to the Secondary DPM server without any re-configuration.

    So if you go with the Primary/Secondary scenario I don't see a solution as both DPM servers must be able to reach the backed up servers.


    Tuesday, November 29, 2011 3:26 PM