Iologsum Remarks
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
IOLogSum Remarks
Before Using IOLogSum
If Perl is not installed on your system, if you are connected to the Internet, you can download a free version from the ActiveState Web site.
IOLogSum Report
When used with NtfrsUtl inlog and NtfrsUtl outlog, the IOLogSum report can be used to determine which files are involved in FRS replication, and what has caused them to replicate. When used with NtfrsUtl idtable, IOLogSum can generate a report describing the state of all files and folders known to an FRS member.
Familiarity with FRS concepts and terminology is required in order to interpret IOLogSum reports.
Each IOLogSum report starts by identifying the name of the file that it processed, and the sort options used to generate the report. Then, for every replica set in which the computer participates, the report lists one row per change order.
The following table lists and describes each column in the report.
Column Heading | Description |
---|---|
SeqNumber |
Specifies the unique sequence number for the change order. For NtfrsUtl idtable reports, this is always reported as 00000000. |
EventTime |
Specifies the USN Journal Entry Timestamp; in other words, the time the file was changed on the originating machine. |
FileVersNum |
Specifies the file version number, incremented each time the file is closed. |
FileUsn |
Specifies the USN that the file must match on the Fetch request. |
FileSize |
Specifies the file size (in KB). |
FileGuid |
Specifies the object ID of the file or directory. For brevity, only the last 8 digits are printed. |
OriginatorGuid |
Specifies the GUID of the originating member. For brevity, only the last 8 digits are printed. The originator GUID can be mapped back to the server name by searching the NtfrsUtl sets output. |
Cxtion |
Specifies the GUID of the remote connection – for brevity, only the last 8 digits are printed |
FileName |
Specifies the Unicode file name. |
Flags |
Specifies a valid Change Order Flag. Valid flags are shown in the following list.
|
LocationCmd |
Specifies the Change Order Location command. Valid Location Commands are shown in the following list.
|
ContentCmd |
Specifies the Change Order content changes from the USN reason. Flags set in the NTFS change log describing modifications to the file.
|
By default, the records are sorted by sequence number, but it is possible to sort by other columns.
Sorting by File GUID makes it easy to detect repetitive changes to single files and the times at which they occurred (for example, once per hour).
Sorting by Event Time is useful for identifying older change orders that may indicate a particular partner has been unavailable for a while. The IOLogSum report, coupled with the report that Connstat Overview generates, can tell you what change orders are pending for the delinquent partner.
See Also
Concepts
Iologsum Overview
Iologsum Syntax
Alphabetical List of Tools
Topchk.cmd
Rsdir Overview
Rsdiag Overview
Health_chk Overview
Ftonline Overview
Filever Overview
Efsinfo Overview
Dmdiag Overview
Dskprobe Overview
Diruse Overview
Dfsutil Overview
Connstat Overview
Cabarc Overview
Bitsadmin Overview