none
moving exchange dag protection to a new dpm server RRS feed

  • Question

  • Hi,

    Im trying to migrate from my older win 2008r2 with dpm 2012 sp1 server to a newer 2012 server with dpm 2012 sp1. The way i plan to do this is to stop protection on the old server, uninstall the agent on the proctected server from the old server, reinstall the protection agent from the new server to the protected server then recreate the protection group on the new server. 

     

    Im now trying to re create my exchange protection but im getting an error selecting the group members from my DAG. the error is "You have chosen to protect replicas on another DPM server (primary DPM server) id 148. later on it complains again "one or more of the selected data sources are already configured for protection on the primary DPM server. Id 31162

     

    This new server is a brand new install so it shouldn't know about the existing primary server. I checked on the exchange server in the DPM installer folders and there was an activeowner folder which had details of my old DPM server, so i uninstalled the agent, deleted the whole DPM folder on the exchange server and reinstalled the agent from the new primary but i still get this error, i ran the setdpmserver command to point to my new server with no luck

    Tuesday, March 19, 2013 11:30 AM

Answers

  • Hi,

    OK - that explains the error.  When you deploy an agent from one dpm server to another, that basically enables secondary protection capability and from that point on, the second DPM Server knows about all data sources that the primary DPM server is protecting.  Because of that you cannot move any PS from dpm1 to dpm2.

    If you have not yet starting protection on DPM2, then yes - uninstall DPM and re-install DPM to start with a fresh database and you will then have the ability to protect the DAG on that server.


    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, March 19, 2013 8:52 PM
    Moderator

All replies

  • Hi,

    It sounds like you deployed an agent from the new DPM Server to the Old DPM Server ?  IE: Are you protecting anything on the old dpm server (like DPMDB) or secondarily protecting anything using the new DPM server ?


    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, March 19, 2013 5:05 PM
    Moderator
  • I did have thoughts about turning the new server into a secondary then switching the protection, I only got as far as installing the agent from the new onto the old and vice versa but then uninstalled both an hour later Should I reinstall the new?
    Tuesday, March 19, 2013 8:41 PM
  • Hi,

    OK - that explains the error.  When you deploy an agent from one dpm server to another, that basically enables secondary protection capability and from that point on, the second DPM Server knows about all data sources that the primary DPM server is protecting.  Because of that you cannot move any PS from dpm1 to dpm2.

    If you have not yet starting protection on DPM2, then yes - uninstall DPM and re-install DPM to start with a fresh database and you will then have the ability to protect the DAG on that server.


    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, March 19, 2013 8:52 PM
    Moderator
  • after a reinstall of DPM exchange protection is ok now.

    thank you!

    Tuesday, March 19, 2013 11:50 PM