none
Secondary DPM reflects incorrect Primary DPM RRS feed

  • Question

  • DPM 2010 v3.0.7707.0

    I have a server PS that was originally protected by primary DPM1 and secondary SDPM.  Protection was changed to use primary DPM2. I'm not sure how the protection was changed on the secondary(I wasn't involved), but SDPM still thinks that PS is protected by DPM1. This generates errors on SDPM stating that the datasource is not available on DPM1.  Also in trying to set up secondary protection for PS, it's not listed under the DPM2 in the gui when selecting Group members. Its does, however, show up under DPM1.

    In looking at the table tbl_AM_Server on SDPM, the DPMServerID points to DPM1. Is there a proper way to correct this without just updating this table?

    Thursday, February 21, 2013 4:54 PM

Answers

  • HI,

    We have customer facing documentation stating that moving a PS between DPM servers are not supported under that Scenario.
     
    See COMMUNITY COMMENT under the following technet article:
     
    Setting up DPM Chaining
     http://technet.microsoft.com/en-us/library/gg410636.aspx
     
    Under the heading: "Moving protected servers between DPM servers while under secondary protection is not supported"
     
    If you call MS support, they can clean up secondary DPM server to allow the protected server to be re-protected. 


    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.

    Thursday, February 21, 2013 7:07 PM
    Moderator

All replies

  • HI,

    We have customer facing documentation stating that moving a PS between DPM servers are not supported under that Scenario.
     
    See COMMUNITY COMMENT under the following technet article:
     
    Setting up DPM Chaining
     http://technet.microsoft.com/en-us/library/gg410636.aspx
     
    Under the heading: "Moving protected servers between DPM servers while under secondary protection is not supported"
     
    If you call MS support, they can clean up secondary DPM server to allow the protected server to be re-protected. 


    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.

    Thursday, February 21, 2013 7:07 PM
    Moderator
  • Would this scenario work if SDPM protection was removed first, then DPM1 protection, then the DPM1 agent from PS?   And then DPM2 agent on PS, DPM2 protection of PS, and finally SDPM of PS?
    Thursday, February 21, 2013 7:38 PM
  • Hi Afraid not - SDPM knows about all protected servers on all primary DPM Servers, and the problem (and the reason why you need to call support) is that SQL records are not cleaned up entirely when a PS moves between primary DPM Servers, or is un-installed entirely.

    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.

    Thursday, February 21, 2013 9:33 PM
    Moderator
  • thanks

    I've got a case going.

    Thursday, February 21, 2013 9:41 PM