Menu
![](/uploads/1/2/6/6/126618525/277970033.png)
What's supported and what isn't for DPM?. 14 minutes to read.In this articleThis topic summarizes some of the common support information you might need when deploying and maintaining System Center - Data Protection Manager. Installation and deployment issues DPM deployment optionsIssue: DPM can be installed in physical and virtual environments.More information: DPM can be installed as follows:.As a standalone physical server - DPM can't be deployed in a physical cluster, but you can manage multiple DPM servers from a single location using Central Console in Operations Manager.As an on-premises virtual machine - You can deploy DPM as a Hyper-V virtual machine as a single server or virtual machine cluster. You install DPM in the same way as a physical installation. For detailed information, see the row, in the Setup prerequisites table.As an Azure virtual machine - From DPM 2012 R2 Update 3 onwards you can install DPM as an Azure virtual machine. There are a number of restrictions in this deployment.
For detailed information, see the row in the Setup prerequisites table.As a Windows virtual machine in VMWare - From DPM 2012 R2 Update 5 onwards you can install DPM on a Windows virtual machine in a VMWare environment. In this configuration DPM can protect Microsoft workloads that are all running as Windows virtual machines in VMWare.Sharing a library between different DPM versions isn't supportedIssue: Different versions of DPM (for example, DPM 2012 R2 and DPM 2016) can't function as clients sharing the same library.Workaround: None. All DPM servers sharing a library must be running the same version of DPM. Upgrading System Center 2010 directly to System Center 2016 isn't supportedIssue: Upgrade isn't supported.Workaround: You'll need to upgrade to DPM 2012 R2 first. DPM doesn't run on the Turkish language version of Windows 2012 operating systemsIssue: No language supportWorkaround: None DPM 2010 and later versions can't run on a server running a 32-bit operating systemIssue: Operating system limitation.Workaround: Install on 64-bit only. For a full list of system requirements, see.
![Drivers Drivers](/uploads/1/2/6/6/126618525/141800542.jpg)
If you guarantee a backup every five hours but actually back up every other hour in a specific data source, the DPM 2012 server for each failed. Write down this path so the executable file can be found later. 3.The Self-Extractor window appears. 5.Click the Start button and then click Run. 6.Type C: DELL DRIVERS in the Open textbox and then click OK. 7.Follow the on-screen installation instructions.
Underscore not supported in SQL Server nameIssue: If you specify a remote SQL Server that has an underscore in the name during DPM installation, the installation might fail.Workaround: Specify a SQL Server name that doesn't include the underscore character. NTFS compression isn't supported on DPM volumesIssue: NTFS not supported.Workaround: None Renaming the DPM server isn't supportedIssue: Renaming not supported.Workaround: None Moving the DPM server domain isn't supportedIssue: Moving the DPM server to a different domain after deployment isn't supported.Workaround: None DPM on a domain controller can only protect local data sourcesIssue: Deployment not supported.Workaround: If you want to install the DPM protection agent on other computers in order to protect them, don't install DPM on a domain controller.
DPM can't use SQL Server running on a domain controllerIssue: Database deployment not supported.Workaround: If you want to use a remote instance of SQL Server as your DPM database, ensure that the SQL Server instance isn't running on a domain controller. You cannot install DPM 2016 on SQL 2016 SP1 (or later release)Issue: Installation on SQL 2016 SP1 (or a later release) is not supported.Workaround: None.
Moving protected servers with DPM secondary serversMoving protected servers between DPM servers that are under secondary protection isn't supported.
![](/uploads/1/2/6/6/126618525/277970033.png)