Dell PowerProtect Data Manager Appliance 5.12.0.1 SAP HANA User Guide

Agent registration

On Windows, if the agent fails to establish a connection with the PowerProtect Data Manager Appliance 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 Appliance 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 Appliance.
2. Start the packet tracing between the source IP of the agent system and the destination IP of PowerProtect Data Manager Appliance.
3. Start the network traffic between the agent system and PowerProtect Data Manager Appliance.

   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 Appliance is blocking the connection.

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

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.

PowerProtect Data Manager Appliance UI display of localhost.localdomain hostname

In the PowerProtect Data Manager Appliance 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 Appliance 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 Appliance UI windows, instead of the actual FQDN:

127.0.0.1 localhost.localdomain localhost6 localhost6.localdomain6
127.0.0.1 blrv027d233.blr.lab.emc.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 Appliance 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 Appliance 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 Appliance UI

SAP HANA assets might appear to be missing because the assets are not visible in the PowerProtect Data Manager Appliance 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 Appliance 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 Protection Storage change in protection policy

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

After you change the Protection Storage in a protection policy:

• The PowerProtect Data Manager Appliance 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 Appliance 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 Protection Storage system. Subsequent backups are displayed correctly in the PowerProtect Data Manager Appliance UI, and you can properly delete the subsequent user-specified backup copies as expected.

Auto-configuration failure in multinode environment

PowerProtect Data Manager Appliance 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.

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 onboarded backup copies

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

PowerProtect Data Manager Appliance does not delete any SAP HANA backup copies that are onboarded 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.