Troubleshooting
Problem
Collecting data documents aid in problem determination and save time resolving Problem Cases (previously called PMRs).
Environment
This document is intended for VE operations in a Linux environment. For operations in a Windows environment use this knowledge document.
Resolving The Problem
Collecting troubleshooting 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 work around to reduce severity.
Locating root cause can speed development of a code fix.
Collecting Data: Table of contents:
Entering general information into an electronically-opened Problem Case (previously called PMRs) eliminates waiting on the phone to provide general information to support.
The following information must be obtained to accurately determine problem resolution:
Gather the datamover configuration by using this command run from the BAclient installation directory:
In addition to the above information, gather the following items based on where the problem/failing operation was initiated from.
For operations initiated from the Graphical Web or File Level Restore User Interface:
Collect the contents of the following directories:
For versions 6.2, 6.3 and 6.4:
Collect the following files:
Collect the text output of the command:
Collect the text output of the server command:
For operations scheduled with the IBM Spectrum Protect Server:
The output of ‘dsmc query systeminfo –optfile=<datamover optfile name>’ gathered in the general section may contain the errorlog and schedlog from the datamover used.
If there are multiple datamover nodes, or if the dsminfo.txt does not contain these outputs, manually collect them:
From the server collect the ‘query actlog’ output which covers the schedule event time.
For operations which involve the Recovery Agent, or Mount operations:
Collect the contents of the following directories:
Collect the following file:
Collect the following Linux shell outputs:
For installation issues:
Gather the following:
For file restore operations use the following link:
Troubleshooting file restore operations
Note: This section is used in conjunction with the outputs previously gathered. Review the log gathering section for details on where these outputs are located.
For any operation initiated from the user interface:
For restore operations:
For Recovery Agent/Mount issues:
For file restore operations use the following link:
Note: In either of these sections a path to free disk space will be needed for tracing. Tracing of VM operations can be extensive. If the operation you are tracing processes a number of VMs, determine if the behavior can be duplicated on a smaller subset so that data collection is not cumbersome.
For operations which are initiated via the Web user interface:
- Edit the dsmvddk.opt (in the BAclient folder). Change the following options to be 6:
- Reverse the changes made to prevent tracing from running
- Gather the following for review:
For operations which are initiated manually from the command line, or during scheduled events:
- Edit the dsmvddk.opt(in the BAclient folder). Change the following options to be 6:
- Reverse the changes made to prevent tracing from running
- Gather the following for review:
<Path with free disk space>/datamvr.trace
dsmwebcl.log from BAclient folder
datamover dsminfo.txt file (See General Gather section for details)
Symptoms match known problems (rediscovery).
There is a non-defect problem that can be identified and resolved.
There is a defect that identifies a work around to reduce severity.
Locating root cause can speed development of a code fix.
Collecting Data: Table of contents:
Gathering General Information |
The following information must be obtained to accurately determine problem resolution:
- Version of IBM Spectrum Protect Virtual Environments: Data Protection for VMware in use
Operating system level the application is running on
vCenter version and build number
ESX host version and build number
Operation being attempted and the resulting output
Gathering IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Linux Information |
- dsmc query systeminfo –optfile=<datamover optfile name> - Generates the ‘dsminfo.txt’ file
- dsmwebcl.log in the BAclient directory
- dsmc show vm all –optfile=<datamover optfile name> -asnode=<datacenter node name> > sh_vm.out
In addition to the above information, gather the following items based on where the problem/failing operation was initiated from.
For operations initiated from the Graphical Web or File Level Restore User Interface:
Collect the contents of the following directories:
- /opt/tivoli/tsm/tdpvmware/common/logs
For versions 6.2, 6.3 and 6.4:
- /opt/tivoli/tsm/tdpvmware/common/ewas/profiles/logs
/opt/tivoli/tsm/tdpvmware/common/ewas/profiles/TSMProfile/logs
- /opt/tivoli/tsm/tdpvmware/common/webserver/usr/servers/veProfile
Collect the following files:
- /opt/tivoli/tsm/tdpvmware/common/regtool.log
/opt/tivoli/tsm/tdpvmware/common/scripts/vmcliprofile
Collect the text output of the command:
- /opt/tivoli/tsm/tdpvmware/common/scripts/vmcli -f inquire_config > inquire_config.out
Collect the text output of the server command:
- query proxy
For operations scheduled with the IBM Spectrum Protect Server:
The output of ‘dsmc query systeminfo –optfile=<datamover optfile name>’ gathered in the general section may contain the errorlog and schedlog from the datamover used.
If there are multiple datamover nodes, or if the dsminfo.txt does not contain these outputs, manually collect them:
- Collect the errorlog for the datamover – The datamover optfile will specify this in the 'errorlogname' parameter.
Collect the scheduler log for the datamover – The datamover optfile will specify this in the 'schedlogname' parameter.
From the server collect the ‘query actlog’ output which covers the schedule event time.
For operations which involve the Recovery Agent, or Mount operations:
Collect the contents of the following directories:
- <user.home>/tivoli/tsm/ve/mount/log
/opt/tivoli/tsm/tdpvmware/mount/engine/var
/opt/tivoli/tsm/tdpvmware/common/logs
Collect the following file:
- /opt/tivoli/tsm/tdpvmware/mount/Mount.cfg
Collect the following Linux shell outputs:
- df -h
mount
ps -ef
rpm -qa | grep iscsi
For installation issues:
Gather the following:
- For versions 6.2, 6.3 and 6.4, Collect the data in the following directories:
- /opt/tivoli/tsm/tdpvmware/_uninst
/usr/ibm/common/acsi/logs
- TDPVMwareInstallation.log
- /opt/tivoli/tsm/tdpvmware/_uninst
For file restore operations use the following link:
Troubleshooting file restore operations
Troubleshooting IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Linux |
For any operation initiated from the user interface:
- Review the vmcli logs:
- Linux - /opt/tivoli/tsm/tdpvmware/common/logs
- Review the scheduler log to determine the overall statistics of the backup event and which VMs failed to process. Then review the error log to understand why each VM failed. For issues around snapshots or consolidation of a VM, check the ‘vmware.log’ files for the impacted VM.
For restore operations:
- Review the datamover errorlog to determine why the restore operation failed.
For Recovery Agent/Mount issues:
- Review the ‘Recovery_Agent040.sf’ file.
For file restore operations use the following link:
Capturing a trace of IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Linux operations |
For operations which are initiated via the Web user interface:
- Edit the dsmvddk.opt (in the BAclient folder). Change the following options to be 6:
- vixDiskLib.transport.LogLevel = "6"
vixDiskLib.nfc.LogLevel = "6"
- traceflag tid pid enter exit general vm
tracefile <Path with free disk space>/datamvr.trace
- Change the VMCLI_TRACE value to YES
Remove the # from in front of VE_TRACE_FILE and VE_TRACE_FLAGS
- Reverse the changes made to prevent tracing from running
- Gather the following for review:
- <Path with free disk space>/datamvr.trace
Entire /opt/Tivoli/tsm/tdpvmware/common/logs folder
Entire /opt/Tivoli/tsm/tdpvmware/tsmcli folder
dsmwebcl.log from BAclient folder
datamover dsminfo.txt file (See General Gather section for details)
For operations which are initiated manually from the command line, or during scheduled events:
- Edit the dsmvddk.opt(in the BAclient folder). Change the following options to be 6:
- vixDiskLib.transport.LogLevel = "6"
vixDiskLib.nfc.LogLevel = "6"
- traceflag tid pid enter exit general vm
tracefile <Path with free disk space>/datamvr.trace
- Reverse the changes made to prevent tracing from running
- Gather the following for review:
<Path with free disk space>/datamvr.trace
dsmwebcl.log from BAclient folder
datamover dsminfo.txt file (See General Gather section for details)
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
- Latest Spectrum Protect Server and Client Downloads - Fixpacks and Interim Fixes
- Instructions for tracing VMware (vCenter and ESXi) along with Data Protection for VMware operations can be found here.
[{"Product":{"code":"SSERB6","label":"IBM Spectrum Protect for Virtual Environments"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for VMware","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}},{"Product":{"code":"SS8TDQ","label":"Tivoli Storage Manager for Virtual Environments"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Data Protection for VMware","Platform":[{"code":"PF016","label":"Linux"}],"Version":"6.3;6.4;7.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]
Product Synonym
tsm tsm4ve ve tdp4ve
Was this topic helpful?
Document Information
Modified date:
22 October 2019
UID
swg21497489