none
Protect new server with same name as old server RRS feed

  • Question

  • Does anybody know, if it's possible to protect a new server with the same name as an already protected server? We want to install a new server to replace an old one, don't want to delete the old server backups from tapes, but want to keep the DNS name of the server, because it is tied to many applications. Is it possible?
    Monday, February 16, 2015 7:36 AM

Answers

  • Hi,

    Yes, that is possible - what you should do is shutdown the original server, re-set the machine account in active directory then when you clean install the new server and joint it to the domain it should re-claim that machine in active directory. DPM should recognize it as the same machine once you install the Agent and re-attach the protected server.    However, since volume GUIDS are now going to be different, you may need to use Migrate-Datasource powershell script to re-associate that new volume to the DPM replica volume.

    Using Migrate-Datasource

    Migrate-Datasource is a command-line script that lets you continue protecting a data source (file, folder, volume, or share) to the same replica volume even after it has been migrated to a different volume on the same protected computer. You have to run the Migrate-Datasource script even if you have not changed the drive letters of the volume because DPM recognizes volumes by the GUID and not the drive letter.

    For application data - you may need to stop protection and retain replica / tapes and re-protect.


    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.

    Monday, February 16, 2015 7:56 PM
    Moderator

All replies

  • Hi,

    Yes, that is possible - what you should do is shutdown the original server, re-set the machine account in active directory then when you clean install the new server and joint it to the domain it should re-claim that machine in active directory. DPM should recognize it as the same machine once you install the Agent and re-attach the protected server.    However, since volume GUIDS are now going to be different, you may need to use Migrate-Datasource powershell script to re-associate that new volume to the DPM replica volume.

    Using Migrate-Datasource

    Migrate-Datasource is a command-line script that lets you continue protecting a data source (file, folder, volume, or share) to the same replica volume even after it has been migrated to a different volume on the same protected computer. You have to run the Migrate-Datasource script even if you have not changed the drive letters of the volume because DPM recognizes volumes by the GUID and not the drive letter.

    For application data - you may need to stop protection and retain replica / tapes and re-protect.


    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.

    Monday, February 16, 2015 7:56 PM
    Moderator
  • Thank you Mike, that helps a lot.
    Tuesday, February 17, 2015 9:41 AM