- #DATA DOMAIN OS 2017 INSTALL#
- #DATA DOMAIN OS 2017 UPDATE#
- #DATA DOMAIN OS 2017 UPGRADE#
- #DATA DOMAIN OS 2017 WINDOWS#
You can select a size for the DPM virtual machine using the DPM Azure virtual machine size calculator.
#DATA DOMAIN OS 2017 WINDOWS#
BitLocker on volumes hosting VHD files used for the storage pool.NTFS compression for volumes hosting VHD files used in the DPM storage pool.Windows 2012 iSCSI targets (which use virtual hard drives) as a DPM storage pool.Enabling Disk Dedupe on volumes hosting virtual hard drives.Local or remote hosting of VHDX files on Windows 2012 storage space also isn't supported. Windows 2012 Storage Spaces or virtual hard drives built on top of storage spaces.Virtual DPM installations don't support:.SMB 3.0 is required for scaled-out file servers. For high availability DPM storage, virtual hard drives should be placed on scaled-out file servers (SOFS).
#DATA DOMAIN OS 2017 UPDATE#
From DPM 2012 R2 with Update 3 onwards you can run DPM as a Hyper-V virtual machine with support for tape drives using synthetic FC.For dynamic and fixed virtual hard drives, VHD and VHDX files are supported on remote SMB shares.Both VHD and VHDX files are supported in the DPM storage pool.Ī virtual DPM installation is required to support adding virtual hard drives to the storage pool.Therefore, for scaled up environments we don't recommend using VHDX.īoth fixed and dynamically expanding VHDX files are supported. Performance can suffer in scaled up (Hyper-V on CSV) environments using VHDX files compared to SAN. Instead, use direct attach/SAN-based storage. Virtual DPM installation isn't for scaled up environments.If you're installing DPM as a Hyper-V virtual machine note that: You can't use an on-premises SQL server in this deployment, and Azure SQL database isn't currently supported. If you deploy DPM as an Azure virtual machine (VM), use an Azure VM running SQL server as a remote SQL server instance. You can't use a SQL server Always-On deployment. You can't run SQL server on a domain controller. If SQL server is clustered, Reporting server and SQL server should be on different computers. SQL server can be standalone or running in a cluster. If you're running a remote database, make sure to run SQL Prep tool on the remote SQL computer before installing DPM.
#DATA DOMAIN OS 2017 INSTALL#
If you install the database remotely, the computer running the remote instance must be in the same domain and time zone as the DPM server. Have SQL installed locally or remotely before you install DPM. You can install SQL server on the DPM server or on a remote server. Verify supported SQL server versions for the DPM database. PowerShell 3.0 (included with Windows Server 2012 R2 or 2012) Microsoft Visual C++ 2012 Redistributable Microsoft Visual C++ 2010 Redistributable Microsoft Visual C++ 2008 Redistributable. Installed as part of the operating system but can also be installed as an administrator from DPM\setup\redist\WindowsInstaller\INSTMSI45.EXE.
Install with Add Features in Server Manager if it doesn't install automatically. NET Framework 4.6 required for SQL installation (SQL 2016 onwards).
NET Framework 3.5 required for SQL installation (Before SQL 2016). These are installed automatically during setup: Follow these instructions if you want to Install DPM on a domain controllerĭetails or specifics for the installationĪ number of components are needed on the DPM server.
You can Install DPM from the user interface, or Run an unattended install.
#DATA DOMAIN OS 2017 UPGRADE#
This version of Data Protection Manager (DPM) has reached the end of support, we recommend you to upgrade to DPM 2019.