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

PowerProtect Data Manager 19.14 SAP HANA User Guide

Troubleshooting installation and operation

You might encounter the following issues during installation or operation.

Agent registration

On Windows, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping. 

1.	If the ping command is blocked in the environment, the agent registration can still complete successfully. 
Review the agent service logs at INSTALL_DIR\DPSAPPS\AgentService\logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI.
2.	If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

On Linux or AIX, if the agent fails to establish a connection with the PowerProtect Data Manager server, agent registration might fail with the following error message:

During a network connectivity test, the agent is unable to reach the PowerProtect Data Manager server by using ping and curl. 

1.	If the ping command is blocked in the environment and curl is not installed, the agent registration can still complete successfully. 
Review the agent service logs at /opt/dpsapps/agentsvc/logs to verify that the registration is successful. If the registration is successful, the status of the agent host indicates Registered in the PowerProtect Data Manager UI.
2.	If the ping command is not blocked in the environment, the agent registration might not complete successfully because a network connection cannot be started. If this occurs, complete the following steps to troubleshoot the issue:

If agent registration fails with these error messages, complete the following operation:

  1. Use any network packet tracing tool to trace the packets from the agent system to PowerProtect Data Manager.
  2. Start the packet tracing between the source IP of the agent system and the destination IP of PowerProtect Data Manager.
  3. Start the network traffic between the agent system and PowerProtect Data Manager.

    Wait 10 to 15 seconds.

  4. Analyze the captured packets.
  5. Look for SYN and SYN_ACK packets to see if a 3-way handshake is being performed.

    Determine whether the source agent or the destination PowerProtect Data Manager is blocking the connection.

    If network traffic is blocked, contact your network security team to resolve the port communication issue.

Agent host is registered with short name instead of FQDN

Application agent registration using the short name of the agent host is not supported after updating to PowerProtect Data Manager 19.11 or later versions.

If the agent host was previously registered with the short name, and you attempt to reregister the host with the short name after updating PowerProtect Data Manager to version 19.11 or a later version, registration fails with the following error:

Unable to register the agent host <hostName> because short name is not allowed for agent registration.

To resolve the issue, do not remove the host. Configure the host with the Fully Qualified Domain Name (FQDN), and then retry the registration.

If you try to register a new host with the short name after updating PowerProtect Data Manager to version 19.11 or a later version, registration fails with the following error:

Unable to register the agent host <hostName> because short name is not allowed for agent registration.

To resolve this issue, remove the application agent host in the PowerProtect Data Manager UI:

  1. Go to Infrastructure > Application Agents.
  2. Select the entry for the application agent host and click Remove.

    After the removal, the host is in a "Deleted" state.

    NOTE:The application agent host is automatically removed from the Application Agents window within 24 hours after the deletion.
  3. After the removal process is complete, configure the host with the Fully Qualified Domain Name (FQDN), and then retry the registration.

PowerProtect agent service operations

To troubleshoot PowerProtect agent service operations, you can check the PowerProtect agent service log file OpAgentSvc-<timestamp>.log, which is created in <agent_service_installation_location>\logs on Windows and <agent_service_installation_location>/logs on AIX or Linux. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

To modify the log level and retention of temporary files, you can perform the following steps:

  1. Stop the agent service.
  2. Open the config.yml file in an editor.
  3. Modify the log-level settings in the following parameters, as required:
    • DEBUG
    • INFO
    • WARNING
    • ERROR
    • CRITICAL
    NOTE:These parameters are listed in order of decreasing number of messages in the debug information output. The default log-level is INFO.
  4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.
    NOTE:The agent service and application agent communicate through the temporary files, which are typically deleted after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True permanently, or the temporary files can use excessive space on the file system.
  5. Start the agent service.

Uninstalling the PowerProtect agent service results in "Segmentation fault(coredump)" error on AIX platforms

After updating the application agent from version 19.12 to 19.13, uninstalling the PowerProtect agent service results in the following error:

/usr/sbin/rpm_share [470]: 19005466 Segmentation fault(coredump)

This behavior does not impact reinstallation of the PowerProtect agent service.

The core dump error is due to a faulty rpm.rte file with version 4.13.0.3. For more information, see update rpm.rte to the latest version to resolve rpm errors and core dumps.

To resolve this issue, either update the rpm.rte file to the latest version or update the AIX Technology Level (TL) version. The following article provides more information about TL versions:

Fileset information for: rpm.rte

PowerProtect Data Manager UI display of localhost.localdomain hostname

In the PowerProtect Data Manager UI, the Application Agents, Asset Sources, and Protection Jobs windows might list the asset primary hostname as localhost.localdomain instead of the expected FQDN.

The display of localhost.localdomain as the hostname in the PowerProtect Data Manager UI windows might occur when you specify the host's actual FQDN setting for the loopback address in the /etc/hosts file. For example, when you add the following settings in the /etc/hosts file, the first setting value, localhost.localdomain, appears as the hostname in the PowerProtect Data Manager UI windows, instead of the actual FQDN:

127.0.0.1 localhost.localdomain localhost6 localhost6.localdomain6
127.0.0.1 blrv027d233.blr.lab.dell.com blrv027d233

Ensure that the host's actual FQDN is not specified for the loopback address and do not specify hostnames that start with "local" in the /etc/hosts file.

Application agent update failure in PowerProtect Data Manager UI on Linux

On a Linux OS that uses /etc/init.d instead of systemd to start the OS services, an update of a previous application agent version in the PowerProtect Data Manager UI might fail with the following error message:

Upgrade operation failed with error 'tuple' object has no attribute 'lower', errorcode: .

As a workaround, update the application agent by using the appropriate update commands and command-line procedure as described in this guide.

Missing assets in PowerProtect Data Manager UI

SAP HANA assets might appear to be missing because the assets are not visible in the PowerProtect Data Manager UI.

To identify any faults in the system environment, perform the following actions:

  1. Ensure that the saphostexec service is running.
  2. Run the following commands from the console, and ensure that the command output does not include any errors:

    /usr/sap/hostctrl/exe/saphostctrl -function ListDatabases
    /usr/sap/hostctrl/exe/saphostctrl -function ListInstances

Negative Reduction % value for self-service catalog backup

When the backup size of a self-service SAP HANA catalog backup is less than a megabyte, a negative Reduction % value might appear for the backup job in the details section of the Job ID Summary window in the PowerProtect Data Manager UI.

You can access the Job ID Summary window by selecting Jobs > Protection Jobs and clicking the job ID next to the job name.

Issues after DD change in protection policy

You might encounter specific issues after you change the DD in an SAP HANA protection policy.

After you change the DD in a protection policy:

  • The PowerProtect Data Manager UI does not display any of the log backups.
  • Scheduled incremental and differential backups are not started until the next scheduled or manual full backup is started.
  • Incremental and differential backups can be started manually from SAP HANA Studio or the command line.
  • The PowerProtect Data Manager UI displays the following status for the incremental and differential backups:

    A copy this copy depends on was deleted.
  • Manual deletion of any of these backups does not produce the expected results.
  • Backups between the two storage units can be recovered without errors. Performing restore with dependency chaining or replication storage provides details.

As a workaround, perform a full backup to the new DD system. Subsequent backups are displayed correctly in the PowerProtect Data Manager UI, and you can properly delete the subsequent user-specified backup copies as expected.

Auto-configuration failure in multinode environment

PowerProtect Data Manager might not discover a newly created SAP HANA database until the database is operational. As a result, auto-configuration might fail in a multinode SAP HANA environment.

NOTE:Once the database is operational, PowerProtect Data Manager will automatically discover the database in subsequent scheduled discovery calls.

As a workaround, once the database is operational, you can retry the auto-configuration. You can use one of the following methods to trigger the auto-configuration:

  • Click the set lockbox option on the protection policy.
  • Add a new asset with the same SID to the protection policy.
  • Re-create the protection policy from scratch.

Issue with imported backup copies

You might encounter an issue with imported SAP HANA backup copies.

PowerProtect Data Manager does not delete any SAP HANA backup copies that are imported but not associated with a protection policy, even when the backup copies are expired.

Issue with protection policy in multihost configuration

You might encounter an issue when you create or edit a protection policy in a multihost configuration.

If you create a protection policy for an asset that is spanned across only some, but not all, nodes in a multihost configuration, you might see a complete with failures warning in the user interface.

If you edit an existing protection policy and add the same type of asset, you might see a valid assets are not provided for configuration error in the adm.log file.

You can ignore the warning and error messages.

Edit Retention button is disabled for asset copies

On the Infrastructure > Assets page > Asset <asset name> page, the Edit Retention button is disabled.

The Edit Retention button is enabled only when the copy status of the asset source is Available. In detail, if deleting a copy of a protected asset fails, the Copy Status will be updated to another state from Available, and the Edit Retention button is disabled.

Workarounds are:

  • Edit the retention period of an asset copy if its status is Available.
  • Do not try deleting an asset copy before its retention period.

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: <>()\