PowerProtect Data Manager 19.15 Microsoft SQL Server User Guide

Troubleshooting restores of multiple databases from multiple policies

During a centralized restore of multiple databases from multiple policies, with the backup copies located on separate DD systems, the Select Copy page displays the following message for one of the databases:

No copies are available for the listed assets. The restore operation will not include these assets.

You also cannot perform the centralized restore of multiple databases from multiple policies when the backup copies are located on separate storage units in the same DD system.

As a workaround, perform the centralized restore of each database separately.

Troubleshooting centralized Microsoft SQL Server Application Direct restore operations

You can use the following information to troubleshoot issues with the centralized Microsoft SQL Server Application Direct restore operations.

• Inspect the ADM logs in /var/log/brs/adm/adm.log in PowerProtect Data Manager.
• Inspect the Microsoft application agent logs in C:\Program Files\DPSAPPS\MSAPPAGENT\logs.
• Enable advanced debugging output for the PowerProtect agent service by setting the DEBUG parameter in the file config.yml in the agent service installation directory.
• Enable advanced debugging output for the Microsoft application agent by setting the debug option in the PowerProtect Data Manager restore wizard. The preceding topics about how to perform the centralized restores describe how you can set the Troubleshooting option, which causes the application agent to generate the diagnostic logs.

Remove option fails to remove a new database name during centralized restore to new database

During a centralized database restore to a new database, the Remove option does not remove the new database name that you add for the restore in the PowerProtect Data Manager UI.

During the centralized restore, you select Restore to Alternate on the Location page. After you click Restore as new database next to the required instance name and add a new database name, clicking Remove next to the new database name does not remove the name. The Next button is disabled as expected on the Location page, but the new database name is still listed in the UI.

As a workaround, collapse and expand the parent node of the new database name, which removes the database name.

Application Direct self-service restore jobs are missing in Asset Jobs window

In the PowerProtect Data Manager UI, Application Direct self-service restore jobs are not displayed in the Jobs > Asset Jobs window. The Application Direct self-service restore jobs are displayed in the Jobs > Protection Jobs window and in the Restore Jobs Summary report in the Reports > Report Browser window.

Troubleshooting centralized Microsoft SQL Server Application Direct restore of backup tiered to the cloud

During a centralized restore of a Microsoft SQL Server Application Direct backup that is tiered to the cloud, the full backup copy is not browsable in the PowerProtect Data Manager UI. However, the backup copy is browsable in the SQL Server Management Studio (SSMS) UI.

This issue applies to both Amazon Web Services (AWS) and Elastic Cloud Storage (ECS) tiered copies.

As a workaround, perform a manual recall of the cloud tiered backup copies in the PowerProtect Data Manager UI, and then perform the centralized restore operation.

Centralized Microsoft SQL Server virtual machine restore failure after VM Direct update

If registration fails during a VM Direct update, the silent installation completes (it is not rolled back) and an error message is recorded in the installation log. A subsequent centralized restore might fail.

To resolve this issue, configure the Microsoft SQL Server host by using the Install Agent option in the PowerProtect Data Manager UI, and then restart the centralized restore.

Centralized Microsoft SQL Server virtual machine restore failure to Windows or CIFS shared path

A centralized restore of a Microsoft SQL Server virtual machine backup to a Windows or CIFS shared path fails with PowerProtect Data Manager.

To resolve this issue, perform a self-service restore to the Windows or CIFS shared path by using either the SQL Server Management Studio (SSMS) UI or the restore command on the command line.

VM Direct SSMS restore failure with enabled UAC

A VM Direct self-service restore might fail with the following error message when you use the SQL Server Management Studio (SSMS) plug-in to perform the restore as a domain or local user with enabled UAC and vmtools 11.x or later. This error message appears for a database restore, table restore, or instant access restore operation when you do not launch the SSMS plug-in by selecting Run as administrator:

Unable to initialize the generic information context: Cannot create shared memory mapping, permission denied: ERROR_ACCESS_DENIED.

As a workaround, launch the SSMS plug-in by selecting Run as administrator and rerun the self-service restore operation.

VM Direct SSMS restore failure after PowerProtect Data Manager server update

After an update of the PowerProtect Data Manager server, if no protection policy operations have run since the update, a VM Direct restore of an old backup through the SQL Server Management Studio (SSMS) UI might fail. The restore failure produces the following type of message in the error logs:

158905:msagentrc: A failure occurred trying to mount the backup images: (Failed to login, please check your configuration and/or credentials).
102437:msagentrc: Recovery operation failed.  Refer to log file(s) and Windows event logs for details.

As a workaround, perform at least one successful protection policy operation after the update of the PowerProtect Data Manager server. Then perform the VM Direct restore of an old backup through the SSMS UI.

Troubleshooting VM Direct centralized restore of replicated AAG log backup

In an AAG replica configuration, when you perform a centralized restore of a replicated log backup for an AAG database to the original file location, the restore might fail with the following error message:

ddbmsqlrc PowerProtect Data Manager critical The file '<file_name>' cannot be moved by this RESTORE operation.

The centralized restore is configured in the PowerProtect Data Manager UI by selecting Restore > Assets and the SQL tab. Proceeding through the restore wizard screens, the option Restore to Original is selected on the Location screen and the option Original file location is selected on the Select File Location screen.

As a workaround, check whether the replica's file location is different on the two AAG nodes. For example, the file location C:\data of Node1\Instance1 is different from the file location D:\data of Node2\Instance2. If the replica's file location is different on the AAG nodes, then reconfigure the centralized restore by selecting one of the following options on the Select File Location screen in the PowerProtect Data Manager UI restore wizard:

• Default file location as set by Microsoft SQL Server
• User-specified file location

Troubleshooting VM Direct SSMS restore of replicated log backup

In a federated configuration, you can create replication backups on a secondary DD by replicating the VM Direct Microsoft SQL Server full and transaction log backups located on a primary DD. When you try to restore the replicated backups by using the SQL Server Management Studio (SSMS) UI, the SSMS UI displays only the replicated full backup, not the replicated transaction log backup.

You cannot restore the replicated VM Direct transaction log backup on the secondary DD by using the SSMS UI.

As a workaround, you can perform a centralized restore of the replicated transaction log backup in the PowerProtect Data Manager UI.

SSMS UI crash after switch from table restore to database restore tab

During a restore using the SQL Server Management Studio (SSMS) UI, the SSMS UI might crash after you perform the following sequence of operations in the UI:

1. You select a database on the database restore tab.
2. You select a different storage unit on the table restore tab.
3. You switch quickly to the database restore tab to try to check a preloaded database.

The SSMS UI crashes when the switch from table restore tab to database restore tab occurs so quickly that the database list has not yet been updated before you try to check the preloaded database. An Assertion Failed exception message window is displayed.

As a workaround, clear the SSMS cache and retry the operation.