DPM server migrate to a new domain

PoonNathaniel-2902 0 Reputation points
2026-03-10T13:40:08.5666667+00:00

Hi, we have a DPM server, DPM SQL server and a virtual tape server that need to be migrated to a new domain. DPM is running on 2022, SQL is on 2019 and the OS is Windows 2022. The DPM server also has an attached disk array. The DPM agents are connected to the servers on the new domain and the old domain.

What is the best way to do the migration without lossing the data?

Here is what we plan to do:

  1. Uninstall DPM on DPM server and retain the data after stopping all the jobs
  2. Migrate DPM server, DPM SQL server and the Virtual tape unit server to the new domain
  3. Reinstall DPM, point it to the data on the DPM SQL server.
  4. The attached disk array should be detected automatically. As for the virtual tape server, I am not sure how to connect DPM to it since we will be using a different domain account.

Question:

  1. Should I remove the protected servers from the protected groups and disable protection before the migration? After the migration, do I need to go to each protected server and run this cmd: SetDpmServer.exe -dpmServerName YourNewDPMserver? Then attach the agent to the DPM server?
  2. I assume I dont have to re-create the protection groups. Do I need to put the protected server back to the protection groups?
  3. How to connect DPM to the virtual tape server? And where in DPM to change the domain account for the connection?
  4. DPM backs up to a folder with its FQDN in the disk array. After DPM is migrated to a new domain, I assume it will create a new folder in the disk array. How can I move the backups from the old FQDN to the new FQDN folder? Or all the backups will be lost after the migratrion?

Thanks!

Microsoft System Center | Other
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest

  1. AI answer

    2026-03-10T13:40:32.9233333+00:00

    Renaming or moving a DPM server to a different domain after deployment is explicitly unsupported. The same applies to using a DPM SQL instance on a domain controller or moving the DPM server domain.

    Because of this, the planned “migrate the existing DPM server and SQL instance into a new domain and just reconnect everything” approach is not supported and cannot be relied on to preserve data and configuration.

    The supported options from the provided information are:

    1. Rebuild a DPM server with the same name and restore the DPM database
      • One supported recovery pattern is to rebuild a failed/removed DPM server with the same name and restore the DPM database so that DPM can resume primary protection.
      • This requires:
        • A DPM installation that matches the version and update rollup of the DPMDB backup.
        • Restoring the DPMDB to SQL and then using DPMSYNC -RESTOREDB followed by DPMSYNC -SYNC to attach the restored database to the new DPM server.
      • However, moving the DPM server to a different domain is still listed as unsupported, so this pattern is only supported when the server identity (including domain context) is preserved.
    2. Use a new DPM server and move protection there
      • When a DPM server is effectively removed from the infrastructure, supported options include:
        • Rebuild the DPM server with the same name and restore the DPM database (as above), or
        • Move protection for workloads to a different DPM server that the old DPM server does not know about.
      • In practice for a domain change, this means:
        • Deploy a new DPM server in the new domain.
        • Install agents and configure new protection groups on that new server.
        • Existing disk/tape backups on the old DPM server remain associated with the old DPM instance and are not supported to be “migrated” across domains.
    3. DPM database handling
      • The DPM database (DPMDB) contains configuration and backup metadata.
      • Restoring DPMDB requires the DPM installation version (including update rollup) to match the database version.
      • The documented restore flow is:
        • Back up DPMDB from the original SQL instance.
        • Restore it to the target SQL instance.
        • On the DPM server, run DPMSYNC -RESTOREDB and then DPMSYNC -SYNC to attach and synchronize.
      • This is intended for recovery/upgrade scenarios, not for changing the DPM server’s domain, which is explicitly unsupported.
    4. Storage pool and tape
      • DPM storage pool disks must be ReFS-formatted volumes and are managed by DPM; USB/removable drives are not supported.
      • There is no supported method in the provided information to “repoint” an existing storage pool and its replicas from one DPM server/domain identity to another.
      • Tape libraries (including virtual tape libraries) are supported only when configured with supported hardware; there is no documented, supported procedure here to move an existing tape configuration across a domain change while preserving catalog state.

    Given the above, the specific sub‑questions cannot be answered with supported, detailed steps from the context:

    1. Whether to remove protected servers from protection groups, run SetDpmServer.exe, and reattach agents as part of a domain migration is not covered. The only supported patterns are rebuilding with the same identity or moving protection to a new DPM server.
    2. Reusing existing protection groups after a domain move is not documented as supported. Protection groups are tied to the DPM server and its database, and domain moves are unsupported.
    3. How to reconnect to the virtual tape server with a different domain account is not covered in the provided material.
    4. How to move or reuse backups stored under a folder named with the old FQDN after a domain change is not documented. The context does not provide a supported method to remap those backups to a new FQDN or new DPM identity.

    The only supported guidance available is:

    • Do not move the DPM server to a different domain after deployment.
    • If the DPM server is effectively replaced, either rebuild it with the same name and restore DPMDB, or move protection to a new DPM server and treat existing backups as belonging to the old environment.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.