Document ID: 308027
http://support.veritas.com/docs/308027
E-Mail Colleague IconE-Mail this document to a colleague

Usage Parameters for the SCSI Tracercli.exe Utility

Details:
The various parameters for the SCSI Tracer CLI Utility can be viewed via a command prompt. Open a command prompt window (Start, Run, CMD), change the directory to the location of where tracercli.exe resides, and type the following.


C:\Program Files\Symantec\Backup Exec>tracercli /?
tracercli: [-k(s|t)] [-t time] [-s size] [-1] [-i] [-o binfile] [-u] [-q]


Command line interface to the SCSI capture library:


-ks   Start capturing to the provider's internal queue.

-kt    Stop capturing to the provider's internal queue.

       -ks and -kt only apply to configurable capture sources
       (i.e. TpFilter on Win32).

-t    Trace for a time interval. `time' may be an integer
       in which case it is in seconds, or it may be followed
       by a unit; e.g. `-t 1 day' means to capture for one day.

-s    Trace until the event data reaches a given size. `size'
       may be in bytes, or may have the suffix `k', `m', or `g',
       with the usual meanings.

-0    Do not enter the capture loop. Useful with -ks and -kt, to
       just start and stop the driver without capturing any events.

-1    Trace once. Traces all events currently in the queue
       and immediately exits.

-i     Trace until idle. Idleness is defined as one second with
       no new events.

-o    Specify the name of a binary file to capture to. If -o
       is not specified, then no binary data will be saved.
       This file may be viewed in the Win32 tracer utility.

-u    Use user-mode capture hooks even if kernel mode hooks
       are available.

-q     Do not print any event or target information to stdout.



Products Applied:
 Backup Exec for Windows Servers 12.0

Last Updated: August 31 2008 10:19 AM GMT
Expires on: 08-29-2018
Subscribe Via E-Mail IconSubscribe to receive critical updates about this document

Subjects:
 Backup Exec for Windows Servers
   Application: Troubleshooting

Languages:
 English (US)

Operating Systems:
Windows Server 2003

Enterprise SP2, Enterprise Server