IBM Support

Collecting Data for IBM Spectrum Protect for Virtual Environments - Data Protection for VMware on Windows

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 Windows environment. For a Linux environment, use this knowledge document.

Resolving The Problem

Collecting troubleshooting data early, and entering general information into an electronically opened Problem Case (previously called PMRs) helps IBM® Support quickly determine whether:
Symptoms match known problems (rediscovery).
There is a nondefect 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
Gathering IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Windows Information
Troubleshooting IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Windows
Capturing a Trace of IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Windows
Submitting Information to IBM Support
Online Self-Help Resources
Related Information

 

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 Windows Information
Gather the datamover configuration by using this command run from the BAclient installation directory:
  • dsmc query systeminfo –optfile=<datamover option file name> - Generates the ‘dsminfo.txt’ file
Gather the web client log:
  • dsmwebcl.log in the BAclient directory
Gather the VM output for the environment by using this command:
  • dsmc show vm all –optfile=<datamover option file name> -asnode=<datacenter node name> > sh_vm.out

In addition to the previous information, gather the following items based on where the problem, or failing, operation was initiated from.

For operations initiated from the Graphical web or File Level Restore User Interface:
The <vmcli directory> depends on the operating system type:
  • Windows 32-bit = C:\Program Files\Common Files\Tivoli\TDPVMware\
    Windows 64-bit = C:\Program Files (x86)\Common Files\Tivoli\TDPVMware\
    C:\Program Files\IBM\SpectrumProtect\Framework\VEGUI\logs
Collect the contents of the following directories:
  • <vmcli directory>\VMwarePlugin\logs
For version 6.3 and 6.4:
  • C:\IBM\tivoli\tsm\tdpvmware\ewas\logs
    C:\IBM\tivoli\tsm\tdpvmware\ewas\profiles\TSMProfile\logs
For version 7.1.x and higher:
  • C:\IBM\tivoli\tsm\tdpvmware\webserver\usr\servers\veProfile
Or
  • C:\IBM\SpectrumProtect\webserver\usr\servers\veProfile

Collect the following files:
  • <vmcli directory>\VMwarePlugin\scripts\vmcliprofile

Collect the text output of the command:
  • <vmcli directory>\VMwarePlugin\scripts\vmcli -f inquire_config > inquire_config.out
    Starting with 8.1.6 and higher, the vmcli command is under: C:\Program Files\IBM\SpectrumProtect\Framework\VEGUI\scripts

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 option file name>’ gathered in the general section might contain the error log and schedule log 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 error log for the datamover – The datamover option file specifies the location in the 'errorlogname' parameter.
    Collect the scheduler log for the datamover – The datamover option file specifies the location in the 'schedlogname' parameter.

From the server, collect the ‘query actlog’ output that covers the schedule event time.

For operations that involve the Recovery Agent, or Mount operations:
The default value of %ALLUSERSPROFILE% environment variable depends on the operating system. In Windows 2003 and XP the default value of %ALLUSERSPROFILE% environment variable is C:\Documents and Settings\All Users, while on Windows 7, Vista, 2008 and 2012 it is C:\ProgramData.

Collect the contents of the following directory for Windows:
  • Windows 2003 and XP:
    • %ALLUSERSPROFILE%\Application Data\Tivoli\TSM\TDPVMware
    Windows 7, Vista, 2008, 2012:
    • %ALLUSERSPROFILE%\Tivoli\TSM\TDPVMware
    For version 7.1.1.x and higher:
    • %ALLUSERSPROFILE%\Tivoli\TSM\RecoveryAgent

For installation issues:
Gather the following:
  • %ALLUSERSPROFILE%\TDPVMwareInstallation.log

For file restore operations use the following link:
Troubleshooting file restore operations

 
Troubleshooting IBM Spectrum Protect for Virtual Environments: Data Protection for VMware on Windows
Note: This section is used 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:
  • Review the vmcli logs:
    • <vmcli directory>\VMwarePlugin\logs
    Review the outputs from the eWAS or WebSphere directories.

For manual or server scheduled backup operations:
  • Review the scheduler log to determine the overall statistics of the backup event and which VMs failed to process. Then, review the datamover 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 error log 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 Windows operations
Note: In either of these sections, a path to sufficient empty disk space is needed for tracing. Tracing of VM operations can be extensive. If the operation you are tracing processes a number of VMs, determine whether the behavior can be duplicated on a smaller subset so that data collection is not cumbersome.

For operations that are initiated from the web user interface:
- Edit the dsmvddk.opt. This file is on the datamover in the following location:
  • IBM Spectrum Protect 7.1: C:\Program Files\Tivoli\TSM\baclient
    IBM Spectrum Protect 8.1: C:\Program Files\Common Files\Tivoli\TSM\IBMVDDK
Change the following options to be 6:
  • vixDiskLib.transport.LogLevel = "6"
    vixDiskLib.nfc.LogLevel = "6"
- Edit the option file used by the datamover (in the BAclient folder). Add the following:
  • traceflag tid pid enter exit general vm
    tracefile <Path with available empty disk space>\datamvr.trace
- Edit the vmcliprofile (<vmcli directory>\VMwarePlugin\scripts):
  • Change the VMCLI_TRACE value to YES
    Remove the # from in front of VE_TRACE_FILE and VE_TRACE_FLAGS
- Re-create the problem.
- Reverse the changes made to prevent tracing from running
- Gather the following for review:
  • <Path with free disk space>\datamvr.trace
    Entire <vmcli directory>\VMwarePlugin\logs folder
    Entire <vmcli directory>\TSM\tsmcli folder
    dsmwebcl.log from BAclient folder
    Datamover dsminfo.txt file (See General Gather section for details)

For operations that are initiated manually from the CLI or during scheduled events:
- Edit the dsmvddk.opt. This file is on the datamover in the following location:
  • IBM Spectrum Protect 7.1: C:\Program Files\Tivoli\TSM\baclient
    IBM Spectrum Protect 8.1: C:\Program Files\Common Files\Tivoli\TSM\IBMVDDK
Change the following options to be 6:
  • vixDiskLib.transport.LogLevel = "6"
    vixDiskLib.nfc.LogLevel = "6"
- Edit the option file used by the datamover (in the BAclient folder). Add the following:
  • traceflag tid pid enter exit general vm
    tracefile
    <Path with available empty disk space>\datamvr.trace
- Re-create the problem either manually or with the scheduler
- 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 is automatically updated to acknowledge that data was received. If you are still working with older Problem Management Records, you need to update the PMR to indicate that you sent the data.
 
Online Self-Help Resources

Related Information
  • 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":"PF033","label":"Windows"}],"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":"PF033","label":"Windows"}],"Version":"6.3;6.4;7.1","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Product Synonym

TSM

Document Information

Modified date:
13 December 2021

UID

swg21985463