none
DPM 2012 R2 - P2V, Rename and Merge RRS feed

  • Question

  • Hello Experts,

    Just another day and another set of queries.

    I need some inputs around DPM provisioning in an environment, probably one of you can throw some light on this subject. A batch of tasks  would / need to be performed on two separate DPM servers. One of them needs to be P2V'd and possibly merged with the second one..

    Queries :

    1.  Is there a successful track where DPM has been P2V'd and performed well?
    2.  There would be a need to rename the DPM server once it is converted to a VM, following Naming convention guidelines. Is renaming the server supported and if yes, what are the follow-up actions to ensure DPM DB stays in sync?
    3.    There are two DPM servers. Can they be merged into one server or should be maintained as separate deployments attending to different infra apps.? (example DB merge or moving protection groups from one DB to another etc.)
    4.  If the above options are not suitable, would a new deployment be advised and if yes, we would need to retain the older protection groups and relevant data. That would require merge/converge of old data from old DB’s to new DB, how to achieve this, if any leads can be shared that'd be great.

    Thanks in advance


    SG


    • Edited by Saurabh.G Wednesday, August 10, 2016 3:51 AM one change
    Tuesday, August 9, 2016 8:23 PM

Answers

  • Hello,

    Got the answers, closing the question.

    1.       There would be a need to rename the DPM server once it is converted to a VM, following Naming convention guidelines. Is renaming the server supported and if yes, what are the follow-up actions to ensure DPM DB stays in sync?

    Renaming of DPM server is not supported. The supported and unsupported scenarios are covered here

    1.       There are two DPM servers. Can they be merged into one server or should be maintained as separate deployments attending to different infra apps.? (example DB merge or moving protection groups from one DB to another etc.)

    In my opinion, two DPM servers including their DB & storage pools can’t be merged. Even if it was possible, why don’t you try this: Stop the protection of the datasources on the DPM that you want to decommission, choose the option to RETAIN the recovery points, and start the protection of these datasources from the second DPM server. The disks and DB on the other DPM server would be freed up upon the retention expiry. This should be quite straight forward against the possibility to ‘merge’ two DPM server, disks and DBs.

    1.       If the above options are not suitable would a new deployment be advised, and if yes we would need to retain the older protection groups and relevant data. That would require merge/converge of old data from old DB’s to new DB.

    In case the renaming of DPM servers is absolutely necessary, new deployment is the only option. You can set up a new server as per the naming convention, stop protection of the datasources on the existing servers and reprotect them using the newly built DPM server

    Thanks again.


    SG


    • Marked as answer by Saurabh.G Wednesday, August 10, 2016 2:45 PM
    • Edited by Saurabh.G Wednesday, August 10, 2016 2:46 PM
    Wednesday, August 10, 2016 2:45 PM