none
Secondary DPM 2012 Server - cannot see protected member servers on Primary DPM Server RRS feed

  • Question

  • We recently setup a new DPM 2012 server (physical) running on Windows 2012. This is currently working well and we're succesfully backing up our other member servers to disk.

    Yesterday we setup another DPM 2012 server (again physical and also running Windows 2012). The plan is to have this server protect the primary DPM server from a DR site (we have a fast fibre connection between the two sites). So we installed the DPM agent from the secondary to primary server. However, when we go to setup a new protection group on the secondary DPM server, we are able to see the primary DPM server but the only items listed are:

    - All Shares
    - All Volumes (C: only)
    - System Protection

    We're new to DPM but were under the impression we should also see a list of servers protected by the primary DPM server?

    Any help would be appreicated.

    Tuesday, October 23, 2012 12:11 PM

Answers

  • Thank to Mike and Stephane for your help on this.

    We eventually managed to get it working... under the Management > Agents Tab, some how all our servers were showing as 'protected computers with agent installed', not only on the primary DPM server but on the secondary too. We had to uninstall the agents from the secondary DPM servers and then had to repoint the DPM agent to the primary DPM server (ie: run setupdpm.exe -setdpmname DPM-SVR01 cmd on each member server).

    Also, in AD we checked the following groups:

    DPMRADmTrustedMachines$DPM-SVR01
    DPMRADmTrustedMachines$DPM-SVR02
    DPMRADCOMTrustedMachines$DPM-SVR01
    DPMRADCOMTrustedMachines$DPM-SVR02

    We had to add DPM-SVR01 and 02 as members to all four groups listed above. Also, we found and removed another member (DPM-TEST01 - this was our test VM we'd previously used to evaluate DPM 2012). After a restart of the DPM services we were then able to see the protected computers from the secondary DPM server.

    Wednesday, October 24, 2012 2:15 PM

All replies

  • Hi Phil,

    In your Secondary DPM server, go to Management TAB and verifiy that your Primary DPM server is present.

    If not click on install and choose "attach agents\Computer on trusted domain".

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Tuesday, October 23, 2012 2:03 PM
  • Hi Phil,

    On the Primary DPM Server, make sure that the DPM Writer service is started. Open the DpmMetadata.xml found in the ...DPM\Backup Documents folder using internet explorer and make sure it can be parsed without errors.  Special characters like & in the protection group name can break XML parsing which breaks secondary protection.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 23, 2012 2:38 PM
    Moderator
  • Hi Mike and Stephane, thanks for your help so far.

    I can confirm our primary DPM server is listed under the Management section on the secondary DPM server and the agent status is showing as ok.

    The DPM Writer service is started and set to auto on both DPM servers. Also, the dpmmetadata.xml file looks fine.
    Our protection group names are:

     - Disk Protection Group 1 (On Primary DPM Server)
     - Tape Protection Group 1 (On Primary DPM Server)
     - Disk Replicated Protection Group 1 (On Secondary DPM Server)

    As mentioned our Primary DPM server is working fine and backing up our production servers each day without any problems. The problem is when we come to setup a new PG on the secondary DPM server, we select our primary DPM server as a group member but only see "All Shares", "All SQL", "All Volumes" and "System Protection" listed. According to the MS whitepapers we should see a list of computers which are protected by the primary DPM server too, is this correct or are we missing something?

    Tuesday, October 23, 2012 3:26 PM
  • Hi,

    You should see an object named "Protected Servers".

    Stephane


    Please remember to click “Mark as Answer” on the post that helps you. This posting is provided "AS IS" with no warranties. knowledge is valid only if it is shared by All.

    My DPM blog Yet Another DPM Blog

    Tuesday, October 23, 2012 3:38 PM
  • yeah that's what i thought but its not listed? just:

    - domainname.local
     -    -  DPM-SVR01
       -    -    - All Shares
       -    -    - All SQL Servers
       -    -    - All Volumes
       -    -    - System Protection

    have full patched both servers with MS updates and rebooted but still no luck. any further advise would be greatly appreciated.

    Tuesday, October 23, 2012 4:01 PM
  • Phil,

    From an administrative command prompt, please run:  Dpmbackup -replicas    This will check the dpmwriter and verify the mount points are good to the replicas. If you get any errors let me know.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 23, 2012 4:06 PM
    Moderator
  • Hi Mike, just ran the command and every snapshot was reported as successful.

    Tuesday, October 23, 2012 4:32 PM
  • Ok, So there is nothing obvious that is causing the enumeration to fail, would need to look at DPM logs from both servers to troubleshoot further, please open a support ticket for further analysis.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, October 23, 2012 5:11 PM
    Moderator
  • Thank to Mike and Stephane for your help on this.

    We eventually managed to get it working... under the Management > Agents Tab, some how all our servers were showing as 'protected computers with agent installed', not only on the primary DPM server but on the secondary too. We had to uninstall the agents from the secondary DPM servers and then had to repoint the DPM agent to the primary DPM server (ie: run setupdpm.exe -setdpmname DPM-SVR01 cmd on each member server).

    Also, in AD we checked the following groups:

    DPMRADmTrustedMachines$DPM-SVR01
    DPMRADmTrustedMachines$DPM-SVR02
    DPMRADCOMTrustedMachines$DPM-SVR01
    DPMRADCOMTrustedMachines$DPM-SVR02

    We had to add DPM-SVR01 and 02 as members to all four groups listed above. Also, we found and removed another member (DPM-TEST01 - this was our test VM we'd previously used to evaluate DPM 2012). After a restart of the DPM services we were then able to see the protected computers from the secondary DPM server.

    Wednesday, October 24, 2012 2:15 PM