Volume shadow copy service reports

NTDEV
1

Hello all,
I had a doubt in the volume shadow copy service of M$. This service provides
a tool which is used to trace vss. This tool temporarily enables vss tracing
and generates several logs files. I had a doubt in the format of the
trace.txt file.
Can some one help me in identifying the first four values in the trace
statements. I have put down some of trace statements here…

[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0376):
****************************************************************
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0378):
** TRACING STARTED - ProcessId: 0x19c0, ContextId: 0x5fa4e2bc
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0389):
** Current time: 3/14/2006 6:40:07 PM
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0390):
** Command-line: “C:\Program Files (x86)\VERITAS\VERITAS Object
Bus\bin\vxsvc.exe”
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0391):
** Product version: 5.2.3790.1830
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0392):
** VSS SKU ID: 0x02
[1136779734,0x0019c0:0x1af8:0x5fa4e2bc] modules\tracing\vs_trace.cxx(0393):
****************************************************************
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER {CreateVssBackupComponents}:
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER {HasPrivilege}:
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER {GetCurrentAccessToken}:
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] EXIT {GetCurrentAccessToken}: hr:
0x00000000
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] EXIT {HasPrivilege}: hr: 0x00000000
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER {IsInGroup}:
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] EXIT {IsInGroup}: hr: 0x00000000
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER {IsInGroup}:
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] EXIT {IsInGroup}: hr: 0x00000000
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] EXIT {CreateVssBackupComponents}:
hr: 0x00000000
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER
{CVssBackupComponents::InitializeForBackup}:

What I understand is the following:
1136779734, -> time in milliseconds?
0x0019c0: -> process ID ?
0x1af8: -> may be thread id
0x5fa4e2bc -> context Id.

Can some one confirm wether what I understand from the four values is
correct or not. ?
I believe this could be some standard tracing format of M$ !!

-Shailesh

2

Shailesh Birari wrote:

I had a doubt in the volume shadow copy service of M$. This service
provides a tool which is used to trace vss. This tool temporarily
enables vss tracing and generates several logs files. I had a doubt in
the format of the trace.txt file.
Can some one help me in identifying the first four values in the trace
statements. I have put down some of trace statements here…

[1136779734,0x0019c0:0x1af8:0x5fa4e2bc]
modules\tracing\vs_trace.cxx(0376):
****************************************************************
…
[1136783078,0x0019c0:0x1ac4:0x5fa4e2bc] ENTER
{CVssBackupComponents::InitializeForBackup}:

What I understand is the following:
1136779734, -> time in milliseconds?
0x0019c0: -> process ID ?
0x1af8: -> may be thread id
0x5fa4e2bc -> context Id.

Has it been about two weeks since your system was rebooted? If so, that
answers the “time in milliseconds” part. As for the other three
numbers, who knows. I can believe process ID and thread ID, although I
might guess the third number was the return address of the routine that
called the logging function.

However, I cannot think of a reason why it would be important to know
that. You can look up the process ID in task manager or
ProcessExplorer, if you want to double-check.

Can some one confirm wether what I understand from the four values is
correct or not. ?
I believe this could be some standard tracing format of M$ !!

Not as far as I am aware.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.