Collecting Data for IBM Spectrum Protect: Server Storage Pool Reclamation

Collecting data early, even before opening the Case, helps IBM® Support quickly determine if:
Symptoms match known problems (rediscovery).
There is a non-defect problem that can be identified and resolved.
There is a defect that identifies a workaround to reduce severity.
Locating root cause can speed development of a code fix.

Collecting Data: Table of contents:

	Gathering General information
	Gathering Storage Pool Reclamation Process Information
	Submitting Information to IBM Support
	Online Self-Help Resources
	Related Information

 

Gathering General Information

From a Server Admin command line client (dsmadmc), enter the following commands:

• QUERY SYSTEM > querysys.out
• QUERY ACTLOG begind=<mm/dd/yyyy> begint=<hh:mm> endd=<mm/dd/yyyy> endt=<hh:mm> > actlog.out

- where begind and begint are the beginning date and time for the actlog entries being collected
- where endd and endt are the ending date and time for the actlog entries being collected
- the actlog gather should cover the full time frame of the issue/problem/scenario being diagnosed

Explicitly using the above commands will redirect the output to files called querysys.out and actlog.out in the IBM Spectrum Protect Server's working directory. The names of these files can be changed and a full path can be specified to place the output in any desired directory using any desired name.

These files along with the following files/info should be included as general information:

• dsmserv.opt
• dsmserv.err
• details of operating system levels
• IBM Spectrum Protect Server specific version (ex: 7.1.4.100)

 

Gathering Storage Pool Reclamation Process Information

Capture trace and performance data of the storage pool reclamation process with the following IBM Spectrum Protect server administrative commands :

• trace disable *
• if the storage pool is sequential access but not deduplicated:
  trace enable AFMOVE
• if the storage pool is sequential and enabled for deduplication:
  trace enable AFMOVE DEDUP DEDUP1 DEDUP2
• trace begin <filename1> ...where filename1 is a full path file name to write trace data

After issuing the trace commands, then start the reclamation process and wait for error to occur
To stop the tracing issue the following commands:

• trace end
• trace disable *

The trace file <filename1> will be needed for analysis.

If you report a hang or a performance related symptom for the storage pool reclamation process, download and activate the perl script for monitoring the server (based on the server version). Have the script collect a full day of monitoring data including the storage pool reclamation operation. See Related Information for a link to the script files.

Also, the output from the following IBM Spectrum Protect server administrative commands will be needed :

• QUERY STGPOOL F=D
• QUERY VOLUME F=D
• QUERY LIBV F=D
• SHOW TRANSFERSTATS <poolname> ...where poolname is the storage pool name

Submitting Information to IBM Support

After a Case is open, you can submit diagnostic troubleshooting data to IBM.

When data is uploaded to the Case, the status will be automatically be updated to acknowledge that data has been received. If you are still working with older Problem Management Records, you will want to update the PMR to indicate that you have sent the data.

 

Online Self-Help Resources

• Review up-to-date product information at the IBM Spectrum Protect page.

• Sign into your account on the Spectrum Protect Product page, to access additional resources or to open a Case with the Support team.

 

Related Information

• Exchanging information with IBM Technical Support
• IBM Spectrum Protect Downloads - Latest Fix Packs and Interim Fixes
• Perl script to collect IBM Spectrum Protect server monitoring data
• Collecting Data for IBM Spectrum Protect: Server Storage Pool Migration
• Collecting Data for Spectrum Protect: Server Storage Pool Backup