Collecting Diagnostic Information for Veeam Plugin for SAP HANA

KB ID:
2872
Product:
Veeam Plug-in for SAP HANA
Version:
Published:
Last Modified:
2020-02-11

Challenge

This KB article shows how to collect the diagnostic information that may be needed if you create a Veeam Plugin for SAP HANA support case.
 

Solution

Gather logs according to sections below.

Once logs have been gathered, upload them to the FTP provided by the Veeam Support engineer. After the upload is completed, please notify the Veeam Support engineer.
If you need to use a secure FTP, KB1661 contains secure FTP instructions.

1. Veeam Plugin source logs

This step should be done on source SAP HANA server.
Navigate to and archive the contents of this folder:

/tmp/veeam_plugin_logs
Example:
tar -czvf veeam_plugin_logs.tar.gz /tmp/veeam_plugin_logs

File veeam_plugin_logs.tar.gz will contain the necessary logs.

2. Veeam Plugin target logs

This step should be done on both Veeam Backup and Veeam Repository servers.:
Navigate to and archive the contents of this folder:

%ProgramData%\Veeam\Backup\Endpoint
 

3. External backups list

Save information about available backup files and their EBID values. This can be done using the following query:

SELECT BACKUP_ID,SOURCE_TYPE_NAME,HOST,BACKUP_SIZE,DESTINATION_PATH,EXTERNAL_BACKUP_ID FROM M_BACKUP_CATALOG_FILES WHERE DESTINATION_TYPE_NAME='backint'
Run the same query against each database in question. Save the output of this query in a text file for Veeam Support.

4. System information

Save information about available systems running on your server. This can be done using the following approach:
Login to user shell and issue the following one-liner:

ps -eo pid,command | grep -v grep | grep -v sapstartsrv | grep sapstart | awk '{print $3}'

Save the output of this query in a text file for Veeam Support.

Rate the quality of this KB article: 
2.1 out of 5 based on 8 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit