Gathering trace and log files for remote systems

Edit online

Collecting diagnostic data for a remote system, by using IBM Storage Protect Snapshot, is different to collecting data for a local system. You can update the Diagnostics property page to collect the correct log and trace files for remote systems.

Before you begin
On the local system, verify the following system requirements:
  • Windows 7, Windows 8, Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2 is installed
  • PowerShell version 3.0 or later is installed, if you are running Windows 7, Windows 8, Windows 2008, or Windows 2008 R2. With Windows 2012, PowerShell version 4.0 is installed by default.
  • IBM Storage Protect Snapshot version 4.1.4 is installed
On the remote system, verify the following system requirements:
  • Windows 2008, Windows 2008 R2, Windows 2012, Windows 2012 R2, or a later version is installed
  • Windows PowerShell version 3.0 or later is installed, if you are running Windows 2008, or Windows 2008 R2. With Windows 2012, PowerShell version 4.0 is installed by default.
  • IBM Storage Protect Snapshot version 4.1.4 is installed
  • The required workload is configured.
Procedure
  1. In the Actions pane, click Properties>Diagnostics, and select the mode that you require as follows.
    • For a smaller trace file, select Normal.
    • For a larger trace file, select Complete.
    • For full control over the trace flags that are set, select Custom.
  2. Click Begin.
  3. Click OK to close the window.
  4. Reproduce the issue that you are seeing on the remote server. For example, back up or restore data on the remote Exchange Server.
  5. Open the Diagnostics property page and click Screenshot.
    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.
  6. In the Diagnostic Screen Shot Tool window, click Add New Screen Shot. An image is displayed. When you use the Diagnostic Screen Shot Tool on the remote system, the screen capture files are on the local system.
  7. Close the Diagnostic Screen Shot Tool window.
  8. Click End.
Results
Log, configuration, and trace files are detected and displayed, such as those files in the following example. The diagnostic log files are on the remote system.
  • Microsoft Management Console (MMC): TraceFm.trc and TraceUx.trc
  • Data Protection: TraceFileFs.trc, TraceFileSql.trc, TraceFileExc.trc
  • Agent: TraceFileAgent.trc
  • API: TraceFileFsAPI.trc
  • Other: Hardware provider logs, System information

The files and traces are stored in the following folder on the remote system: C:\Program Files\Tivoli\FlashCopyManager\ProblemDetermination. Use the Copy function to copy the files locally.

If you enable command-line interface tracing, the command-line interface generates trace files for the local and remote systems. On the local system you can view the file that you specified. In addition, on the local and remote systems, a trace file is also created. This file has the same name as the file stored on the local system and the file name concludes with the following suffix appended to the file type extension: _remote

For example, on the local system, the following files are created after you enable command-line interface tracing:
  • filename.trc
  • filename.trc_remote
On the remote system, the following file is created after you enable command-line interface tracing, filename.trc_remote.
Related tasks