HP Storage Mirroring V5 Software - Manual (Page 196)

13 - 28
DTStat statistics
The following statistics appear in the statistic.sts file. If you convert that file to an ASCII, comma-delimited file using the
dtstat -s option, the heading labels may appear slightly different.
Category Statistic Description
Date/Time
Stamp The date and time that the snapshot was taken. This is the date and time that each
statistic was logged. By default, these are generated once a second, as long as there
are statistics being generated. If mirroring/replication is idle, then DTStat will be idle
as well.
System
Allocator The number of bytes currently allocated to the system pagefile
IQ Allocator The number of bytes currently allocated to the intermediate queue
Security Logins The number of successful login attempts
Failed
Logins The number of failed login attempts
Kernel Source
State 0 —Source is not running
1 —Source is running without the replication driver
2 —Source is running with the replication driver
Target
State 0 —Target is not running
1 —Target is running
Start Time Date and time stamp indicating when the Storage Mirroring daemon was loaded
RepOps
Generated The number of replication operations generated by the file system driver. An op is a
file system operation. Storage Mirroring replicates data by sending the file system
operations across the network to the target. RepOpsGenerated indicates the
number of file system operations that have been generated by replication.
RepBytes
Generated The number of replication bytes generated by the file system driver. This is the
number of bytes generated during replication. In other words, this is roughly the
amount of traffic being sent across the network that is generated by replication. It
does not take into account TCP/IP overhead (headers and such).
MirOps
Generated The number of mirror operations transmitted to the target. Mirroring is completed
by transmitting the file system operations necessary to generate the files on the
target. This statistic indicates the number of file system operations that were
transmitted during the initial mirror. It will continue to increase until the mirror is
complete. Any subsequent remirrors will reset this field to zero and increment from
there.
MirBytes
Generated The number of mirror bytes transmitted to the target. This is the number of bytes
generated during mirroring. In other words, this is roughly the amount of traffic being
sent across the network that is generated by the mirror. It does not take into
account TCP/IP overhead (headers and such). Again, any subsequent remirror will
reset this field to zero and increment from there.
Failed
Mirror
Count The number of mirror operations that failed due to an error reading the file from the
disk
FailedRep
Count The number of replication operations that failed due to an error reading the file from
the disk
ActFail
Count The number of activation code failures when loading the source or target. Activation
codes can be bad for reasons such as: expiration of evaluation codes, duplicate codes,
incorrect codes, etc.