Gathering trace and log files for Data Protection for SQL Server

Edit online

IBM Storage® Protect SnapshotData Protection for Exchange ServerData Protection for SQL Server uses several components. Each component is in its own directory along with its respective troubleshooting files. By using the Trace and Log Files view, you can easily view these files in a central location.

About this task

The following files are examples of the files that you can view, including default log and trace files:
Examples of IBM Storage Protect Snapshot default log and trace files:
  • Installation directory: C:\Program Files\Tivoli\FlashCopyManager
  • dsierror.log
  • Log file for custom applications and file systems workloads: fcm.log
  • TraceFm.trc
  • TraceUx.trc
  • TraceManagedCapacityHistory.trc
  • TraceSchedLaunch.trc
  • VssProvisioning.log
  • TraceFileFS.trc
  • TraceFileExc.trc
  • TraceFileSql.trc
If the fcm.log is defined in a path other than the default C:\Program Files\Tivoli\FlashCopyManager\fcm.log, the reports does not include the following information for scheduled backup and restore operations:
  • Task completion
  • Type of data protection activity
  • Amount of data protection activity
The charts and reports display only information that is present in the default log file fcm.log.
Examples of Data Protection for SQL Server default log and trace files:
  • Installation directory: C:\Program Files\Tivoli\TSM\TDPSql
  • dsierror.log
  • tdpsql.log
  • TraceFileSql.trc
If the tdpsql.log is defined in a path other than the default c:\program files\tivoli\TSM\TDPSql\tdpsql.log, the reports do not include the following information for scheduled backup and restore operations:
  • Task completion
  • Type of data protection activity
  • Amount of data protection activity
The charts and reports display only information that is present in the default log file tdpsql.log.
Examples of Data Protection for Exchange Server default log and trace files:
  • Installation directory: C:\Program Files\Tivoli\TSM\TDPExchange
  • dsierror.log
  • tdpexc.log
  • TraceFileExc.trc
If the tdpexc.log is defined in a path other than the default C:\Program Files\Tivoli\TSM\TDPExchange\tdpexc.log, the reports do not include the following information for scheduled backup and restore operations:
  • Task completion
  • Type of data protection activity
  • Amount of data protection activity
The charts and reports display only information that is present in the default log file tdpexc.log.
Examples of trace logs and scripts to quiesce custom applications:
  • Default directory: %ALLUSERSPROFILE%\Application Data\Tivoli\FlashCopyManager\custom-application

    where custom-application can be a variety of applications. For example, an IBM® Domino® mail server, or MySQL or Oracle server.

Examples of VSS requestor default log and trace files:
  • Installation directory: C:\Program Files\Tivoli\TSM\baclient
  • dsmerror.log
Examples of IBM VSS provider for SAN Volume Controller, Storwize® V7000, and DS8000® log files
  • IBMVDS.log
  • IBMVss.log

Procedure

  1. When you encounter a problem in Microsoft™ Management Console (MMC), create trace files by using the Diagnostics property page.
    1. Click Properties > Diagnostics, and click Begin.
    2. Close the property page and reproduce the problem.
    3. Open the Diagnostics property page and click Stop.
      Clicking the Diagnostics button is the preferred method for gathering information to send to your service representative. This method gathers all the information that is needed. Even if a problem occurs only on the command-line interface, command, you can always gather information by using the Automate tab.
      The log files are displayed in the Trace and Log Files view.
  2. Click the trace or log file that you want to view.
    The contents of the file are displayed in the results pane.