PowerProtect Data Manager SQL Server Backup Fails After Several Restarts

Summary: PowerProtect Data Manager (PPDM) SQL server backup failed even after restarting it several times.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Wrong host names are reflected in the PowerProtect Data Manager logs for the affected host whereas the hostname is different on the SQL end.

SQL configuration for the reported host has been checked and they all appear normal.

Ran the Protection Policy backup and it failed with the following error message: 
ABA0002 - Unknown host “XXXXX”
Error messages from the PowerProtect Data Manager log: 
2023-07-22T07:22:33.950Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]163851  ddbmsqlsv PowerProtect Data Manager info Set the client for federated worker process
2023-07-22T07:22:35.382Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]28848  ddbmsqlsv PowerProtect Data Manager error Unknown host “XXXXXX”
2023-07-22T07:22:35.382Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]43709  ddbmsqlsv PowerProtect Data Manager notice Stop time: Sat Jul 22 10:22:35 2023
Error message from the PowerProtect Data Manager UI for the respective SQL backup job: 
ABA0002: XXXXXX: Unable to backup MICROSOFT_SQL_DATABASE asset XXXXXXXXXX  on host "XXXXXXX" to storage target SQL because of an agent issue.
The protection policy backup was unsuccessful because of an agent issue.
Review the error message for a resolution. If there is no resolution, and the issue persists, contact Dell Customer Support.
Read Less
The protection policy backup was unsuccessful because the Agent failed with the following error: 023-07-22T07:22:33.637Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]43708 ddbmsqlsv PowerProtect Data Manager notice Start time: Sat Jul 22 10:22:33 2023 2023-07-22T07:22:33.637Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]153897 ddbmsqlsv PowerProtect Data Manager notice Computer name: XXXXXX User name: XXXXXX   2023-07-22T07:22:33.793Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]163849 ddbmsqlsv PowerProtect Data Manager info Setting federated worker process=true 2023-07-22T07:22:33.793Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]163850 ddbmsqlsv PowerProtect Data Manager info Setting Index name for federated worker process 2023-07-22T07:22:33.950Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]163851 ddbmsqlsv PowerProtect Data Manager info Set the client for federated worker process 2023-07-22T07:22:35.382Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]28848 ddbmsqlsv PowerProtect Data Manager error Unknown host XXXXXXX  2023-07-22T07:22:35.382Z [TRACE_ID:b751d18e694a3827;EXEC_ID:a0e61b27c6dc433d]43709 ddbmsqlsv PowerProtect Data Manager notice 

Cause

The hostname found on the log file was different from the actual hostname.

This issue is due to the client behavior as the nslookup for this host is not getting resolved.

Ran the nslookup for the problematic hostname that is recorded in the log file and it was not resolvable. This issue is due to the client behavior and the infrastructure.

Resolution

The PowerProtect Data Manager administrator has to engage the Windows or the Network Administrator to fix the name resolution, communication issue for the problematic host. Once the hostname issue is fixed and the hostname is resolvable by performing nslookup, run the protection policy for the host and initiate a manual backup on the host.

Affected Products

PowerProtect Data Protection Software, PowerProtect Data Protection Hardware
Article Properties
Article Number: 000218344
Article Type: Solution
Last Modified: 30 Apr 2025
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.