Replaced a protected server with a new protected server -- how to migrate replica on DPM server to new protected server? RRS feed

  • Question

  • Using DPM2012 SP1, I've been running protection on a server-- let's call it "NYC."  The protection was assigned to 3 directories; COMMON, DEPARTMENT and USERS.

    NYC is an old server and was recently replaced by a new server;  the tech named the new server NYC, and renamed the original server "NYC-old."  The tech copied all the data from COMMON, DEPARTMENT and USERS (retaining all respective file structures and permissions) to the new server.

    All this data has already been replicated to the DPM server.  Now how do get our DPM server to use this data for the new server so I don't have to recopy all the data again?

    There's a lot of talk over using a script called "MigrateDatasource.ps1" but I haven't been able to find a good example for syntax or even find if it's really the script I need.

    The DPM client is still installed on the old NYC server (now called "NYC-old.")  It is now showing an error on the Management / Protected Computers window.

    The DPM client is NOT installed on the new NYC server. 

    Any assistance would be appreciated!


    Matthew J. Fazio

    Thursday, January 16, 2014 4:31 PM

All replies

  • Hi,

    Since the new NYC is physically a different server, DPM is going to consider it a new machine and want to protect it's volumes as separate data source.  If you want to avoid the initial replication during re-protection, you can chose the option to perform a manual replica.

    Once that is complete, you can xcopy the data from the old REPLICA to the new REPLICA volume, then perform a consistency check to reconcile any differences.  Once completed and you have a few new RP's made, you can stop protection and delete the old replica.

    To copy the data from old to new replica.

    1) From an administrative command prompt run:  DPMBACKUP -REPLICAS
    2) Get the paths to both the old and new replicas by clicking on the "path to replica" link in the properties of both data sources.
    3) Copy the links and paste them into notepad.
    4) Just note the path information that points to the mount point of the OLD AND NEW replica.  Note the Vol_guid will be different.

       IE: C:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\Replica\File System\vol_c311095c-59d4-4e6b-b273-63f7254f77d2
           C:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\Replica\File System\vol_4f44e0ff-1f79-11e2-be82-2c768ae16487

    5) Run mountVol.exe >mountvol.txt
    6) Open mountvol.txt and search for the NEW REPLICA mountpoint path: 
         Search for:  Replica\File System\vol_4f44e0ff-1f79-11e2-be82-2c768ae16487
    7) Note the \\?\Volume{GUID}\  associated with that mountpoint.

        C:\Program Files\Microsoft System Center 2012\DPM\Volumes\Replica\File System\vol_4f44e0ff-1f79-11e2-be82-2c768ae16487\

    8) Assign a drive letter to the NEW replica guid.
         Mountvol x: \\?\Volume{1f5ccee9-7c69-11e3-95c9-0019b9f81999}\  (where x: is any available drive letter)
    9)  Use xcopy Old_ShadowCopy_path\...\FULL to the new replica volume under  X:\...\Full

      Xcopy "C:\Program Files\Microsoft System Center 2012\DPM\DPM\Volumes\ShadowCopy\File System\vol_c311095c-59d4-4e6b-b273-63f7254f77d2\b922f0cf-a7e8-4510-8fc3-7561a8e5486d\Full" X:\6ad7aed8-9eb3-11e1-a426-806e6f6e6963\Full /e /o

    NOTE: The old replica is being copied from under the ShadowCopy folder that was made when you ran DPMBACKUP -REPLICAS command.  You need to "mirror" the contents frum under the FULL folder which represents the ROOT of the protecte volume to the FULL folder under the NEW replica.  Any deviation from that and DPM will delete the invalid path and end up bringing over a new replica and not save you the re-transmit.

    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, January 16, 2014 9:29 PM