Getting ready

You can deploy Microsoft SQL Server in a VM or in a physical machine. In either case, you must install the DPM agent on the SQL Server machine. If SQL Server is deployed in a clustered mode or as a SQL AlwaysOn, then the DPM agent must be installed on all the nodes that are part of the failover cluster for the SQL Server instance. And if you add any node to the cluster in the future, then the DPM agent must be installed on the newly added cluster node(s) as well.

Please note that DPM cannot protect SQL Server when it has database files stored on remote SMB shares or on Windows Server Scale-out File Server (SOFS), as well as on Clustered Shared Volumes (CSV). DPM also cannot protect SQL Servers whose databases are stored on Microsoft Azure Blob storage.

Before you enable SQL Server protection, you must explicitly add the system account NTAuthoritySystem to the Sysadmin group on the SQL Server, as shown in the following screenshot:

If you forget to add the system account NTAuthoritySystem to the Sysadmin group on SQL Server, then the DPM server will generate a critical alert stating Unable to configure protection, as shown in the following screenshot:

Table of Contents for Getting ready

Create new playlist

Sign In

Sign Up

Table of Contents for
Getting ready