Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager Appliance 5.16.0.0 Microsoft SQL Server User Guide

Considerations for centralized Microsoft SQL Server application-aware restores

Ensure that you review the following information before you perform the centralized restores of Microsoft SQL Server application-aware virtual machine backups.

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 virtual machine that is a discovered asset of PowerProtect Data Manager Appliance.

NOTE:During the centralized restore to an alternate host, if the alternate host is not included in the list of available hosts, follow the instructions in Application agent manual installation and configuration to ensure that the application agent is properly installed and configured.

PowerProtect Data Manager Appliance 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 virtual machine, VM1:

  • If an agent installation for VM1 is in progress, the VM1 backup is queued and the Microsoft SQL Server restore against target VM1 is queued.
  • If a VM1 backup is in progress, the agent installation for VM1 is queued and the Microsoft SQL Server restore against target VM1 is queued.
  • If the Microsoft SQL Server restore against target VM1 is in progress, the agent installation for VM1 is queued and the VM1 backup is queued.

Application agent manual installation and configuration

NOTE:

Ensure that the Microsoft SQL Server host was not previously registered to PowerProtect Data Manager Appliance using the Application Direct option.

For example, if the Microsoft SQL Server host was previously registered to PowerProtect Data Manager Appliance with Application Direct during a Microsoft application agent installation, the protection type for that host may not be changed to VM Direct, even if the Microsoft application agent is uninstalled.

In either of the following cases, you must manually install and configure the Microsoft application agent on the target virtual machine host of the restore:

  • The PowerProtect Data Manager Appliance has been updated.

    NOTE:If PowerProtect Data Manager Appliance has been updated from a pre-19.6 version, then you must use the following steps to manually install and configure the application agent. You must install the application agent on all the client machines.
  • You want to restore to a virtual machine that is not part of a protection policy.

Ensure that the target virtual machine meets the following prerequisites:

  • A Windows OS is running.
  • The VMware Tools are installed at the same version as required for backup.
  • 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.

Perform the following steps to manually install and configure the application agent:

  1. Ensure that the Windows account credentials for the virtual machine are set at the virtual machine asset level, not the protection policy level.

    To set the credentials at the asset level, select Infrastructure > Assets > Virtual Machine, select the virtual machine, and select More Actions > Set Credential.

  2. To install the application agent, select Infrastructure > Assets > Virtual Machine, select the virtual machine, and select More Actions > Install Agent.

    After you confirm to start the installation, you can monitor the installation job status on the Jobs page.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\