Usage Parameters for the SCSI Tracercli.exe Utility
| Article:TECH62932 | | | Created: 2008-01-29 | | | Updated: 2012-04-03 | | | Article URL http://www.symantec.com/docs/TECH62932 |
Problem
Usage Parameters for the SCSI Tracercli.exe Utility
Solution
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 (usually the main Backup Exec installation directory) and type the following.
C:\Program Files\Symantec\Backup Exec> tracercli /?
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.
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.
|
|
Related Articles
Legacy ID
308027
Article URL http://www.symantec.com/docs/TECH62932
Terms of use for this information are found in Legal Notices









Thank you.