PowerProtect Data Manager 19.15 Microsoft SQL Server User Guide

The centralized restore of multiple Microsoft SQL Server databases supports the following use cases:

• Performing disaster recovery of the original Microsoft SQL Server instance.
• Performing a restore rehearsal by restoring a Microsoft SQL Server instance database to an alternate host to validate the backups.

For disaster recovery to the original host, you can select all the databases for the Microsoft SQL Server instance. Once the restore job starts, the application agent automates the disaster recovery procedures as outlined by Microsoft. The disaster recovery includes a restart of the Microsoft SQL Server instance in single user mode to restore the master database.

For disaster recovery to an alternate host, ensure that the alternate host is a Microsoft SQL Server Application Direct host that is a discovered asset of PowerProtect Data Manager.

PowerProtect Data Manager applies the following concurrency rules for jobs associated with either a single-database or multi-database centralized restore, including any backup, restore, and manual agent installation jobs that you run on the same host:

• If an asset backup is in progress, the Microsoft SQL Server restore against the same asset is queued.
• If the Microsoft SQL Server restore against an asset is in progress, the backup against the same asset is queued.

Application agent manual installation and configuration

When you want to restore to a host that is not part of a protection policy, you must manually install and configure the Microsoft application agent on the target host of the restore.

Ensure that the target host meets the following prerequisites:

• A Windows OS is running.
• The Microsoft SQL Server is installed and running.
• The SYSTEM account has the same security configuration as required for backup.
• The network ports are configured as required for backup.

Before you manually install and configure the application agent, ensure that the Windows account credentials are set at the asset level, not the protection policy level.

To set the credentials at the asset level, select Infrastructure > Assets > SQL, select the required asset, and select More Actions > Set Credential.