IBM Support

Collecting Data for Spectrum Protect Data Protection: Performance

Troubleshooting


Problem

Collecting data for Spectrum Protect for Data Protection clients with performance problems. This document applies to all the Data Protection products using the API.

Resolving The Problem

Collecting Data: Read First table of contents:

Gathering general information
Preparing the client and server for data collection
Gathering performance information
Submitting information to IBM Support
Online Self-Help Resources
Related Information


 
Gathering general information

Troubleshooting performance problems can be a time consuming and complex process. Consulting the Performance section of the Spectrum Protect Knowledge Center is often a good start. Especially the Configuration best practices and Solving performance problems sections.

For environments using container pools, adhering to the Blueprint is also beneficial.


 
Preparing the client and server for data collection


Data collection for Data Protection performance problems is done by collecting data from the Spectrum Protect Client and the Spectrum Protect Server. This is because all operations (backup/restore/archive/retrieve) also involve interaction with the server.

For APIs at 7.1.6 and above, instrumentation is collected by default in dsminstr.log. If it was disabled, then comment out or delete "ENABLEINSTRUMENTATION NO" from the API option file. It can be commented out by putting an * in front.

APIs older than 7.1.6 will need the following option in the API option file:
TESTFLAG INSTRUMENT:API

For the server portion, the Servermon script is used to collect data. The script and the instructions can be found here: http://www-01.ibm.com/support/docview.wss?uid=swg21432937
 
Gathering performance information
  1. Before recreating the problem, Servermon needs to be enabled.  If running on a server version 8.1.10 or later, built-in Servermon is on by default and it creates an archive at midnight daily.  If running a server older than 8.1.10, use Perl Servermon and start it in the foreground or background. The default is to run continuously in 24 hour increments, creating a new .zip file at 17:00 daily.
    If this is a LanFree backup, it will be necessary to also start Perl Servermon on the Storage Agent (note: Built-in Servermon is not available on Storage Agents).
  2. Recreate the problem by starting the backup or restore manually, or by letting the scheduled operation start automatically.
  3. Once the backup/restore has completed, wait for Perl Servermon to finish on the server and also on the storage agent if LanFree. Optionally, it can be cancelled using CTRL+C or "kill -2". It will not stop right away as it will finish the last data collection cycle. Do not do a "kill -9" on Unix or "End process" from Windows Task Manager as this will cause the script to stop immediately and not perform a proper clean-up.  For Built-in Servermon, you can wait the next day to extract the latest extract, or use the -archive to force an archive mid-day, than use the -list and -extract options to retrieve it.  More info here:  https://www.ibm.com/support/pages/ibm-spectrum-protect-always-servermon-commands
  4. Also complete the performance questionnaire. The questionnaire is very important to help understand the problem and the environment.


 
Submitting information to IBM Support

After the data collection is complete, upload the following to ECuRep or to Blue Diamond referencing the PMR number:

From the data protection node: From the server:
  • the data generated by servermon
  • completed performance questionnaire
 
Online Self-Help Resources
   
Related Information

[{"Product":{"code":"SSER7G","label":"IBM Spectrum Protect for Databases"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Not Applicable","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB26","label":"Storage"}}]

Product Synonym

TSM

Document Information

Modified date:
22 September 2020

UID

swg22013239