Understanding DFSR Debug Logging (Part 1: Logging Levels, Log Format, GUID’s) Ned here again. Today begins a 21-part series on using the DFSR debug logs to further your understanding of Distributed File System Replication. While there are specific troubleshooting scenarios that will be covered, the most important part of understanding any products logging is making sure you are comfortable with it before you have errors. That way you have some point of reference if things go wrong. As you can probably guess, these posts were a long time in development. They are based on an internal DFSR whitepaper I have worked on for six months, and which went through review by a number of excellent folks here in Support, Field Engineering, and the Product Group itself. Except for the removal of all private source code references, this series is otherwise unchanged. I'll start with a couple posts on the logs themselves, how they are formatted, how they can be controlled, etc. Then I'll dig into scenarios in detail, for both Windows Server 2003 R2 and Windows Server 2008. Don't feel like you have to read and memorize everything – this series is a reference guide as well. And yes, there will be a complete downloadable copy of this series in a few common file formats when the series is done. Logging levels DFSR writes circular log files in %systemroot%\debug that automatically compress with the GZ archive format. The debug logs can have varying levels of detail verbosity, to control how much or how little data you want written. It is also possible to control how many logs to maintain before overwriting the oldest ones, how many entries to store in each log, where the logs are stored, and whether or not logging should run. Under default log settings they should never occupy more than ~50MB of space on Windows Server 2003 R2 servers. The following controls the log settings and describes the defaults: SETTING: Debug Log Severity Default: 4 Range: 1-5 WMIC syntax: wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set debuglogseverity=5 SETTING: Debug Log Messages Default: 200000 Range: 1000 to 4294967295 (FFFFFFFF) WMIC syntax: wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set maxdebuglogmessages=500000 SETTING: Debug Log Files Default: 100 Range: 1 to 10000 WMIC syntax: wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set maxdebuglogfiles=200 SETTING: Debug Log File Path Default: %windir%\debug WMIC syntax: wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set debuglogfilepath="d:\dfsrlogs" NOTE: The path must be created manually; if not, at service restart, the default value %windir%\debug will be used. SETTING: Enable Debug Logging (NOTE: Debug logging is enabled by default) Default: TRUE Range: TRUE or FALSE WMIC syntax: wmic /namespace:\\root\microsoftdfs path dfsrmachineconfig set enabledebuglog=true The WMIC.EXE commands above are actually modifying the DfsrMachineConfig.XML file that is stored in the %systemdrive%\system volume information\dfsr\config. It will populate the DfsrDebug tags. If running with defaults, these would not be populated – in the example below debug log severity is now at 5: - <DfsrDebug> <EnableDebugLog>true</EnableDebugLog> <DebugLogFilePath>C:\WINDOWS\debug</DebugLogFilePath> <MaxDebugLogFiles>100</MaxDebugLogFiles> <DebugLogSeverity>5</DebugLogSeverity> <MaxDebugLogMessages>200000</MaxDebugLogMessages> </DfsrDebug> When setting Debug Log Severity you are influencing how verbose the logs are – i.e. what do we consider important enough to write. Here is a brief table: Level 0 1 2 3 4 5 Setting in DFSR LogLevelNone LogLevelAlways LogLevelError LogLevelWarn LogLevelInfo LogLevelTrace Flag Logged N/A N/A [ERROR] [WARN] N/A N/A Explanation Write nothing Write log header information only Write error events and all others above Write warning events and all others above Write informational events and all others above Write special tracing events and all others above Since the default is 4, DFSR will log everything that occurs except for tracing details. Tracing details are called out further in this guide, and are only necessary to activate under very specific troubleshooting scenarios. The debug log format The DFSR debug logs use a consistent, predictable format that consists of: Header – written at the top of each log file and contains (for example): * FRS Log Sequence:1 Index:1 Computer:2003MEM20 TimeZone:Eastern Standard Time (GMT-05:00) Build:[Feb 16 2007 20:14:20 built by: srv03_sp2_rtm] Enterprise=1 * Configuration logLevel:4 maxEntryCount:200000 maxFileCount:100 logPath:\\.\C:\WINDOWS\debug\ Field FRS Log Sequence & Index Computer TimeZone Build Configuration loglevel Maxentrycount Maxfilecount Logpath Description Describe which logs these are relative to the circular wrapping Describes Describes Describes Describes Describes one Describes Describes the server where this log was written the local time zone of the server and its relation to GMT what OS is being used and if it is Enterprise edition or higher the current log verbosity settings the number of lines that can be written to the debug log before it starts a new the total number of circular logs maintained at any one time the output folder of the logs Header lines always start with an asterisk (*). The header information is always written and cannot be turned off without disabling logging altogether. Single-line messages – written throughout the logs and always map back to one discrete operation in DFSR. So for example: 20080111 15:12:30.996 3876 JOIN 1171 Join::SubmitUpdate Sent: uid:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v33846 gvsn:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v33846 name:USRSTAT.EXE connId:{CC694D38-7E97-467C-A963-B3D9B6E308B9} csId:{1697E5EB-BBD0-45B7-AC2F-11EBE7B3FD47} csName:dfsrprestaged Field DateTime Thread Module ID Line Class Method Data Description Stamps local time YYYYMMDD HH:MM:SS:MS The thread executing within DFSR.EXE The sub-component of DFSR The line in source code The class being executed The method (function) being executed by the class All the information being described by the logging Example from above 20080111 15:12:30.996 3876 JOIN 1171 Join SubmitUpdate Sent: uid:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v33846 gvsn:{AC759213-00AF-45789C6E-EA0764FDC9AC}-v33846 name:USRSTAT.EXE connId:{CC694D38-7E97-467C-A963B3D9B6E308B9} csId:{1697E5EB-BBD0-45B7-AC2F-11EBE7B3FD47} csName:dfsrprestaged Single-line messages always start with a date-time stamp entry. The above sample line is wrapped for readability. Nested messages – written throughout the logs and always map back to one discrete operation in DFSR that generates a multi-line response for better readability. So for example: 20080111 11:44:28.873 1640 INCO 4378 InConnection::UpdateProcessed Received Update. updatesLeft:237 processed:1171 sessionId:1 open:1 updateType:0 processStatus:0 connId:{D0BF5598-9457-4C32-8C50-7558BCD76610} csId:{1697E5EB-BBD0-45B7AC2F-11EBE7B3FD47} csName:dfsrprestaged update: + present 1 + nameConflict 0 + attributes 0x10 + gvsn {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v29102 + uid {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v29102 + parent {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v28024 + fence 16010101 00:00:00.000 P + clock 20080110 19:05:43.167 + createTime 20080110 19:05:43.157 GMT + csId {1697E5EB-BBD0-45B7-AC2F-11EBE7B3FD47} + hash 37123A73-30C1AFF0-B4EE5252-46212327 + similarity 00000000-00000000-00000000-00000000 + name acctsid Nested messages follow single line messages that are ended with a colon. The nested messages always start with a plus sign (+). The nested lines can change depending on the class and method/function being executed so they are described in their own section below for 'File and Folder Field Information'. The common GUID fields Globally Unique Identifiers (GUID's) are used throughout the DFSR system to map the friendly names of the topology to unique entries used by the DFSR service. This can make reading the DFSR debug logs very challenging, as not all GUID's in the environment are defined in the logs. When examining the DFSR debug logs it is important to understand how to map GUID's to real objects for troubleshooting purposes. Sample log entry: 20080403 11:19:54.349 1660 SRTR 329 SERVER_EstablishConnection Succeeded on connId:{097BFFAA-99FB-4A4D-9590-C102985A55C6} replicaSetId:{D3558FFB-1E46-483F-AE89-E840E4A6A97B} partnerAddress:2003MEM21.contoso.com 20080403 11:19:55.710 3360 JOIN 1171 Join::SubmitUpdate Sent: uid:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 gvsn:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 name:samplefile.txt connId:{097BFFAA-99FB-4A4D-9590-C102985A55C6} csId:{B269F903-539D-42F2-9D33-935590097578} csName:ihaterobocopy 20080403 11:19:55.891 572 OUTC 588 OutConnection::OpenFile Received request for update: + present 1 + nameConflict 0 + attributes 0x20 + gvsn {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 + uid {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 + parent {B269F903-539D-42F2-9D33-935590097578}-v1 + fence 16010101 00:00:00.000 + clock 20080403 15:17:17.233 + createTime 20080403 15:17:17.193 GMT + csId {B269F903-539D-42F2-9D33-935590097578} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name samplefile.txt Field ReplicaSetId CSID ConnID Parent UID GVSN Description Replication Group GUID Replicated Folder GUID Connection GUID Folder holding the file Original file record Modified file record Example from above {D3558FFB-1E46-483F-AE89-E840E4A6A97B} {B269F903-539D-42F2-9D33-935590097578} {097BFFAA-99FB-4A4D-9590-C102985A55C6} {B269F903-539D-42F2-9D33-935590097578}-v1 {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 {AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 There are a few tools that can be used to map the GUID's: DFSRADMIN.EXE and DFSRDIAG.EXE - You can use the DFSRADMIN and DFSRDIAG tools included with DFSR to enumerate the topology and determine the GUID's. Below is a sample of doing this through a CMD prompt with the data provided by the above logs: Dfsradmin.exe rg list /attr:rgname,rgguid RgName RgGuid SteveLovesFRS d3558ffb-1e46-483f-ae89-e840e4a6a97b The above command is used to return the Replication Group name, which you will see below is necessary to complete a number of further lookups. This maps to REPLICASETID. Dfsradmin.exe rf list /rgname:SteveLovesFRS /attr:rfname,rfguid RfName RfGuid ihaterobocopy b269f903-539d-42f2-9d33-935590097578 The above command is used to get the GUID of the Replicated Folder so that CSID is known. Dfsradmin.exe conn list /rgname:SteveLovesFRS /attr:sendmem,recvmem,connguid SendMem RecvMem ConnGuid 2003MEM20 2003MEM21 097bffaa-99fb-4a4d-9590-c102985a55c6 2003MEM21 2003MEM20 d2e396a5-837b-4103-b8a2-b8fc2c71d388 The above command is used to return the Connection GUID's that can be mapped to CONNID. Dfsrdiag.exe guid2name /guid:AC759213-00AF-4578-9C6E-EA0764FDC9AC /rgname:stevelovesfrs Object Type : DfsrVolumeInfo Computer : 2003MEM20.contoso.com Volume Guid : B8B42506-BF98-11DC-B176-0003FF3813C5 Volume Path : E: Volume SN : 108172604 DB Guid : AC759213-00AF-4578-9C6E-EA0764FDC9AC Finally, the above command is used to retrieve the GUID of the actual DFSR database and therefore the server it is running on. When files and folders are created or modified, the originating server is used to form the GUID portion of the name, and then the current version vector from that server is appended to complete the unique file mapping in the database. These are used for UID and GVSN. So having retrieved all the GUID's, we can now see that our debug log entry actually means: 20080403 11:19:54.349 1660 SRTR 329 SERVER_EstablishConnection Succeeded on connId: 2003MEM20 replicaSetId:SteveLovesFRS partnerAddress:2003MEM21.contoso.com 20080403 11:19:55.710 3360 JOIN 1171 Join::SubmitUpdate Sent: uid: 2003MEM20-v137449 gvsn: 2003MEM20-v137449 name:samplefile.txt connId: 2003MEM20 csId: ihaterobocopy csName:ihaterobocopy 20080403 11:19:55.891 572 OUTC 588 OutConnection::OpenFile Received request for update: + present 1 + nameConflict 0 + attributes 0x20 + gvsn 2003MEM20-v137449 + uid 2003MEM20-v137449 + parent 2003MEM20-v1 + fence 16010101 00:00:00.000 + clock 20080403 15:17:17.233 + createTime 20080403 15:17:17.193 GMT + csId {B269F903-539D-42F2-9D33-935590097578} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name samplefile.txt Next up – nested debug log fields and module ID's. Understanding DFSR debug logging (Part 2: Nested Fields, Module ID's) Ned here. Part two today covers the nested debug field format and what module ID's mean. If Part 2 makes no sense, you probably haven't read Part 1. Nested Field Format When examining the nested (+) entries it is important to understand all of the fields that can be displayed in the debug logs. These fields give detailed information about file and folder replication, especially regarding database entries, USN changes, and RDC data. These are implemented through LogNewLine. Below is a table describing all of these nested fields and their data output that you will see in the debug logs. All entries marked with an asterisk (*) are Windows Server 2008 only. Otherwise they apply to both Windows Server 2003 R2 as well as 2008. There is also an example of the log entry for each table. File information (defined in DFSR source code and GetFileAttributes) (Severity 4) Field Description fid File ID Record stored in the DFSR database usn The USN ID record in the journal and DFSR database uidVisible Has the UID file record been replicated? Is the file filtered by an administrator to prevent filtered replication? journalWrapped Is the file in USN journal wrap recovery? Is the file being checked after a journal wrap recovery slowRecoverCheck completed? Is the file in the process of being tombstoned in the pendingTombstone database? Displays time/date of local changes to file (only on the recUpdateTime originating server – on downstream will show garbage) present Is the file live or tombstoned (deleted)? Was there a conflict on the file (modified on upstream nameConflict and downstream servers before replication attributes Attributes on the file Global Version Sequence Number of the file, used to gvsn track changes and server origination uid Unique ID of the file, used to identify original file Data Unique hex value Unique hex value 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 YYYYMMDD HH:MM:SS.MS GMT 0 or 1 0 or 1 Hex value GUID of originating server +Version # GUID of modifying parent Folder containing the file fence Authoritative data flag (not used) clock Time of the last change to the file on this server createTime Time the file was created on the server csId Replicated Folder Salted SHA1 checksum of the file and its size (not a true SHA1 of the file itself) Salted SHA1 checksum information about the RDC similarity data hash similarity Name Name of the file ghostedHeader* <reserved for future use> Data* <reserved for future use> clockDecrementedInDirtyShutdown* <reserved for future use> + fid 0x100000000094A + usn 0x0 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080318 20:58:37.190 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {AF8C06FD-E1B8-4044-8FE1-51A9E30F18AD}-v2353 + uid {AF8C06FD-E1B8-4044-8FE1-51A9E30F18AD}-v2353 + parent {5D5D914C-F585-4117-8477-7F8B37B27B01}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080318 19:28:17.026 GMT (0x1c8892e375afac0) + createTime 20080318 17:36:47.960 GMT + csId {5D5D914C-F585-4117-8477-7F8B37B27B01} + hash 02F98A2C-31F58E81-E8598E22-DA9F8F95 + similarity 00000000-00000000-00000000-00000000 + name 0c0df164-715a-4674-bfb2-0a926eed1791 USN update Information (defined in USN_RECORD structure and GetFileAttributes) (Severity 4) Field Description Data RecordLength Size of file record in the USN journal in bytes Numeric value server + Version # GUID of originating server + Version # N/A YYYYMMDD HH:MM:SS.MS YYYYMMDD HH:MM:SS.MS GMT GUID Hex value Hex value Text string MajorVersion MinorVersion FileRefNumber ParentFileRefNumber TimeStamp Reason SourceInfo SecurityId FileAttributes FileNameLength FileNameOffset FileName USN journal underlying major version USN journal underlying major version USN journal internal file reference USN journal internal folder parent reference USN journal timestamp of last change to file Information about an actual change Information about the source of the change Unique security identifier assigned to the file Attributes on the file Size of file record in the USN journal in bytes The offset of the FileName member Name of the file + USN_RECORD: + RecordLength: 136 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000B103 + ParentFileRefNumber: 0x1000000000023 + USN: 0xb69dd0 + TimeStamp: 20080331 20:05:52.176 Eastern Standard Time + Reason: Close File Delete + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 72 + FileNameOffset: 60 + FileName: e7d74249-6092-475b-8e73-909516f93bdd Always 0x2 Always 0x0 Unique Hex value Hex value YYYYMMDD HH:MM:SS.MS TZ Text string Hex value Unique hex value Hex value Numeric value Numeric value Text string Content Set and Database Information (Severity 4) Field contentSetId memberId state startVersion authRebuilding stageVolumeSerialNumber stageFid isTombstone beingDeleted dbLossRecover Description Replicated Folder Computer referenced for this Content Set The current state of the Content Set (may be: Last version vector for chaining if the number is lost due to a problem Rebuilding Content Set authoritatively Volume serial number for the drive containing staged data File ID of the staged data. Is the Content Set tombstoned (deleted) Is the Content Set in the process of being deleted Are we recovering from a lost Data GUID GUID May return: Normal, InitialSync(Cleanup), InitialSync(Sync), InitialBuilding, RestoreInitialSync(Cleanup), RestoreInitialSync(Sync), RestoreBuilding, Unknown Numeric value 0 or 1 Unique value Unique hex value 0 or 1 0 or 1 0 or 1 tombstoneTime* expirationTime* readOnlySince* database When was the content set tombstoned When the tombstone will expire and the database will purge the content set info Date that the content set was changed from Read-Write to Read-Only (unsupported) + contentSetId: {FEB21D85-154D-4AE9-AB31-32A524F1E6F7} + memberId: {13828A03-E1BA-4E51-9F6F-F790671C450A} + state: Normal + startVersion: v150040 + authRebuilding: 0 + stageVolumeSerialNumber: ea40899d408970dd + stageFid: 0x2000000000031 + isTombstone: 1 + tombstoneTime: 20080411 13:47:07.267 + expirationTime: 20080610 13:47:07.267 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 YYYYMMDD HH:MM:SS.MS YYYYMMDD HH:MM:SS.MS (tombstonetime+60 days) YYYYMMDD HH:MM:SS.MS RDC and XPRESS Assembler Statistics Downstream (Severity 5) Field Compression Ratio Target Uncompress Size Target Compress Size Description % of bandwidth savings over the wire (with RDC and XPRESS compression) Total byte count of data Total byte count of data after accounting for compression with XPRESS and RDC Bytes Received Byte count actually received (broken into signature bytes and data bytes) Signature Bytes Received Signature bytes received RPC calls used to receive data (broken into signature, needs, and data requests) Number of bytes copied through RDC Number of XPRESS-compressed RDC blocks copied Number of remote calls RDC Need Size Xpress Blocks Uncompressed Xpress Blocks Blocks copied to target Data 0-100% Numeric value Numeric value Numeric values Numeric value Numeric value Numeric value Numeric value Number of non-XPRESS-compressed RDC blocks copied Numeric value RDC Blocks copied Numeric value + TOTAL + Compression Ratio 49 % + Target Uncompress Size 480012 + Target Compress Size 249546 + Bytes Received 254732 Signatures: 4182 Data: 250550 + Signature Bytes Received 4182 4182 + Number of remote calls 15 Signatures: 1 Needs: 1 Data: 13 + SEED + Rdc Need Size 0 0 + Xpress Blocks 0 0 + Uncompressed Xpress Blocks 0 0 + Blocks copied to target 0 0 + SOURCE + Rdc Need Size 480012 0 + Xpress Blocks 59 0 + Uncompressed Xpress Blocks 1 0 + Blocks copied to target 58 0 RDC and XPRESS Needs Statistics Upstream (Severity 5) Field Compression Ratio Description % of bandwidth savings over the wire (with RDC and XPRESS compression) RDC Need Size Total bytes covered by requests Bytes sent to downstream Actual bytes sent over the wire Uncompressed XPRESS blocks RDC blocks from non-compressed (by XPRESS) data Compressed XPRESS blocks RDC blocks from compressed data (by XPRESS) data Copied XPRESS Blocks Number of compressed blocks sent Bytes read using async I/Os* Number of bytes read in using Async I/o calls + TOTAL + Compression Ratio 47 % + RDC Need Size 480012 + Bytes sent to downstream 254732 + Uncompressed XPRESS blocks 0 + Compressed XPRESS blocks 0 + Copied XPRESS Blocks 59 Data 0-100% Numeric value Numeric value Numeric value Numeric value Numeric value Numeric value RPC Information (Defined in RPC_EXTENDED_ERROR_INFO Structure and Extended Errors, Severity 5) Field Description Data Process ID PID of the DFSR service on this machine. Numeric value System Time Date-time on this machine YYYYMMDD HH:MM:SS.MS Generating Code for component generating the error Numeric value component Numeric error mapped within Status Error returned to RPC WINERROR.H that can be translated with NET HELPMSG <error #> A n entry in the Extended Error Information Detection location Numeric value Detection Locations table Specifies whether SystemTime or FileTime is used. Flags Set to zero to use SystemTime, or 0 or 1 EEInfoUseFileTime to use FileTime. Parameter count to function (with nested data being NumberOfParameters Numeric value passed) + Process ID : 1676 + System Time : 20080318 21:49:51.310 + Generating component : 2 + Status : 1115 + Detection location : 102 + Flags : 0 + NumberOfParameters : 1 USN Consumer Statistics (Severity 5) Field Description usnTotal Total number of USN records consumed usnTotalNotFilteredByReason Total number of USN records (that are not filtered by USN reason attribute) usnTotalDbUpdated Total number of USN records that caused database update txTotal Total number of transactions usnLastAverage usnLastAverageNotFilteredByReason usnLastAverageDbUpdated txLastAverage Number of USN records consumed per second in last sampling period Number of USN records per second that are not filtered by USN reason attribute in last sampling period Number of USN records per second that caused database update in last sampling period Number of transaction per second in last sampling period + usnTotal 67433 + usnTotalNotFilteredByReason 54111 + usnTotalDbUpdated 50002 + txTotal 11813 + usnLastAverage 7 + usnLastAverageNotFilteredByReason 3 + usnLastAverageDbUpdated 0 + txLastAverage 0 Data Numeric value Numeric value Numeric value Numeric value Numeric value Numeric value Numeric value Numeric value USN Recovery Information (Severity 5) Field usnId nextUsn checkpointUsn Description USN ID record in the journal Next USN record A special USN record to allow recovery from disk failures; used to detect whether a journal wrap or complete database rebuild will be triggered after service startup. checkpointTimestamp Last time a checkpoint recovery was set journalWrapped If the USN journal is wrapped If the USN journal ID has been changed (due to recreation of journal) Are we still doing a slow recover due to journal wrap journalIdChanged slowRecoverNotFinished Data Unique Hex value Unique Hex value Unique Hex value YYYYMMDD HH:MM:SS.MS 0 or 1 0 or 1 0 or 1 dirtyRecoveryMode Are we recovering from a dirty database shutdown currently dirtyShutdownRecoveryTimestamp When a dirty database shutdown recovery was last done. dirtyRecoveryRecordsMarkedFinished Was a dirty database recovery just performed + usnId: 0x1c8893ad4b938d0 + nextUsn: 0xbbe0 + checkpointUsn: 0xacd8 + checkpointTimestamp: 20080318 21:11:52.614 + journalWrapped: 1 + journalIdChanged: 0 + slowRecoverNotFinished: 1 + dirtyRecoveryMode: 1 + dirtyShutdownRecoveryTimestamp: 20080318 21:11:52.614 + dirtyRecoveryRecordsMarkedFinished: 0 0 or 1 YYYYMMDD HH:MM:SS.MS 0 or 1 History Information * (Severity 5) Field syncGuid* Description Synchronization GUID State* Current state of replication for this Replication Group initReason* Reason that synchronization occurred connectionGuid* replicationGroupGuid* replicationGroupName* memberGuid* memberName* updatedNotTransferred* updatedTransferred* updatedToBeTransferred* byteTransferred* tombstonesGenerated* conflictsGenerated* currentForceReplicationEndTime* currentForceReplicationBandwidthlevel* Connection GUID Replication group GUID Replication Group friendly name GUID of server Friendly name of server Number of updates not replicated Number of updates replicated Number of updates to be replicated Bytes replicated Number of tombstones created Number of conflicts that occurred When a forced update window (when using DFSRDIAG SYNCNOW) will close Bandwidth level is of a forced replication + syncGuid {CE6DF7C4-5AB4-48A4-871F-344D168DA7B9} + state In Sync + initReason Schedule + connectionGuid {3AA17575-BA9B-43B3-B4C1-9DC4D90307A1} + replicationGroupGuid {4D251274-283B-46DF-81EF-570801B80D90} Data GUID May return: Initialized,Connecting, In Progress, Completed, In Sync, Interrupted, In Error, UnknownSyncState May return: Schedule,Force Replication, Paused, Force Until in Sync, UnknownSyncInitReason GUID GUID Text string GUID Text string Numeric value Numeric value Numeric value Numeric value Numeric value Numeric value YYYYMMDD HH:MM:SS.MS + replicationGroupName LHtest + memberGuid {1CEA93F6-41D7-4BF1-9AFC-7A2502308540} + memberName 2008SRV40 + updatedNotTransferred 0 + updatedTransferred 0 + updatedToBeTransferred 0 + byteTransferred 0 + tombstonesGenerated 0 + conflictsGenerated 0 + currentForceReplicationEndTime 16010101 00:00:00.000 + currentForceReplicationBandwidthlevel * * Windows Server 2008 only Understanding DFSR Module ID's Examining the third entry in any non-nested line of the DFSR debug logs can give you quick insight into what overall type of component functionality DFSR is working on. These are referred to as "Module ID's". Note the highlighted sections below in the sample log entries: 20080403 11:19:55.710 3360 JOIN 1171 Join::SubmitUpdate Sent: uid:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 gvsn:{AC759213-00AF-4578-9C6E-EA0764FDC9AC}-v137449 name:samplefile.txt connId:{097BFFAA-99FB-4A4D-9590-C102985A55C6} csId:{B269F903-539D-42F2-9D33-935590097578} csName:ihaterobocopy 20080409 11:17:21.649 3180 CFAD 8873 Config::AdReader::Peek Connection to AD is down, request full poll The first example is in a synchronization module organized under the 'JOIN' component of DFSR. The next example is in a configuration module under the 'CFAD' component. Below are all the module ID entries that can be mapped back to more general functional areas of DFSR. By getting to know these we can tell at a glance roughly what a given line is referencing and if it bears further attention based on what we are troubleshooting. All entries with an asterisk (*) are Windows Server 2008 only. Entries with two asterisks (**) are Windows Server 2003 R2 only. Functional Area MODULE_ID References Description Configuration CFAD, CCTX, CPAR, CREG, CREP, CVOL, CXML, CMGR, ADWR*, HIST*, SYSM* Database DBCJ, DBGC, DIRW, JRWP, LDBX, PDBX, DBSR, USNC File System MRSH, NTFS, FHAN,FUTL, ASYN*, OPLC* Main FSVC, SCFG, MAIN, VSSW, SCNT Functions related to the configuration of DFSR in LDAP, the registry, WMI, and in the XML files Functions related to the USN journal and the DFSR JET database Functions related to NTFS, file handles, and (in Win2008) Asynchronous I/O handling. Functions for DFSR service control and data backup through VSS. Functions related to DFSRMIG.EXE for SYSVOL migration in Win2008. Functions wrapper for PerflibV2 in Win2008. Functions for DCOM and WMI providers. SYSVOL Migration Performance Provider MIGM* Transport PFV2* FCFG, FWMI, FWMH, PINF, PVMG, WMIC, WMIM CONF, CSMG, CRED, FREP, RDCS, INCO, ISYN, JOIN, MEET, OUTC, RDCX, RDCC, RSMG, SSYN, STAG, UPLK, UPMG, VLMG, XPRN, XPRS, XRNA, SLVS* DOWN, RPCN, SRTR, UPST Utility EVNT, PERF**, TASK, IMPE*, SRVC*, P2P*. SETT* Synchronization * Windows Server 2008 only ** In Windows Server 2003 R2 only Functions related to replicating files between DFSR nodes. Functions that implement DFSR's RPC transports. Miscellaneous utility functions that cover event logging, performance logging in Win2003 R2, and other areas. Next up, we begin the various debug log real-world scenarios, with understanding new files being added to a replicated folder. Understanding DFSR debug logging (Part 3: The Log Scenario Format, File Added to Replicated Folder on Windows Server 2008) Ned here. Today's post is part three in the series, where begin examining specific scenarios in the debug logs. This post is a critical read as it explains how I will go through all the debug logs; without reviewing this section below the remaining logs will be more difficult to understand. Various logging scenarios Now we will dissect DFSR debug logs from Windows Server 2003 R2 and Windows Server 2008. These cover a number of scenarios including both normal operations as well as common error states. It is critical that an engineer become familiar with the working scenarios of DFSR in order to see problem states more clearly. Review the two previous posts on the debug log format (Part 1 and Part 2) before continuing. All logs referenced here are in default debug log severity 4 mode unless otherwise stated. All logs are included as downloads with each blog post. All analysis done on Windows Server 2003 R2 Enterprise x86 with SP2 with hotfixes KB948833 and KB944804 installed or on Windows Server 2008 Enterprise x86 RTM with no hotfixes installed. IMPORTANT NOTES An artificial field called <upstream> has been added to every full line for the upstream log file and will be highlighted yellow – these indicate the beginning of a new full line. An artificial field called <downstream> has been added to every full line for the downstream log file will be highlighted pink – these indicate the beginning of a new full line. Note: When reading the sample logs below, keep in mind that they are actually a combination of two actual debug logs. Hopefully this improves the understanding of the 'give and take' nature of file replication between nodes. Sections that are highlighted turquoise are notable for that line. Comments on a given line are called out with arrowed () red text and are not included in the logs. Not all debug file lines are necessarily included as some will be irrelevant or are repeated several times through looping. Remember to review previous sections for details on all fields shown below. The logs here are unrealistic in their time synchronization (all scenarios were reproduced using a single virtual host). Keep in mind that time could be off by up to five minutes of relative skew in a real world scenario, and that debug logs are written using local time of the server, not GMT/UTC time. File Added to Replicated Folder on Windows Server 2008 (addedlargefileupstream - Dfsr00011 - 2008.log and addedlargefiledownstream - Dfsr00008 - 2008.log) In this scenario we will see a file copied into the replicated folder and how it is replicated between two servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 where the file is created (upstream) and from 2008MEM02 where it is replicated (downstream). Both servers are participating in the TESTRG replication group for the TESTRF replicated folder. The file is called "bigdoc.rtf". It is larger than 64KB so it will be staged for RDC usage; it is not on the compression exclusion list so it will be compressed in staging with XPRESS. <Upstream> 20080625 11:50:03.505 3676 USNC 2612 UsnConsumer::CreateNewRecord LDB Inserting ID Record: the file is created in the replicated folder on 2008MEM01. This has caused the USN journal to be updated and information about the file to be sent to the DFSR JET database. + fid 0x300000000A7DA unique File ID used to track this file in the database and USN journal + usn 0x9ed8a8 + uidVisible 0 because the file is still being processed for the first time, its UID is not yet visible and the file is not yet considered ready for replication. + filtered 0 the file does not match any filtering exclusions + journalWrapped 0 we are not writing the USN update to recover from a USN journal wrap + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 we are not replicating this file in from some other DFSR server + meetReanimated 0 this file was not reanimated (i.e. restored from recycle bin or a backup) + recUpdateTime 16010101 00:00:00.000 GMT + present 1 the file exists + nameConflict 0 + attributes 0x20 this is a file, not a folder, per the rules of GetFileAttributes. Do not assume that because the name field below has (or lacks) an extension that the object is a file or folder; attributes always tells truth + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 this file has never been modified in the RF so the GVSN is the same as the UID. + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 this is the files original UID + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 this is the parent folder (which is c:\testrf) + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.505 GMT the file was 'created' (i.e. added to this replicated folder) at this time + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 00000000-00000000-00000000-00000000 the file does not yet have a hash associated at this point + similarity 00000000-00000000-00000000-00000000 the file does not yet have similarity data at this point + name bigdoc.rtf this is the actual file name in question + <Upstream> 20080625 11:50:03.555 3676 USNC 2615 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: extended information about the actions on the file is written into the USN journal + USN_RECORD: + RecordLength: 80 amount of data in bytes needed to store information about this file in the journal + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000A7DA The File ID. This is useful to ensure you are looking at the same update as above. + ParentFileRefNumber: 0x100000000A6EE + USN: 0x9ed8a8 + TimeStamp: 20080625 11:50:03.505 Eastern Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite File Create what change has happened to the file. In this case it was 'created' (keeping in mind that creation is relative to DFSR; if a file is copied in to an RF, it is created in USN terms) + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 20 + FileNameOffset: 60 + FileName: bigdoc.rtf more confirmation that this is the same file as above. + <Upstream> 20080625 11:50:03.575 2372 SRTR 1880 SERVER_RequestVersionVector Received from connId:{F5A520C4-154C-460E-B8EF0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} seqNumber:4 changeType:all <Upstream> 20080625 11:50:03.575 2372 SRTR 1927 SERVER_AsyncPoll Received from connId:{F5A520C4-154C-460E-B8EF0867D4F92AAE} the upstream 2008mem01 server receives a poll asking for any updates in response to a change notification. <Downstream> 20080625 11:50:03.582 3768 INCO 4619 InConnection::RequestUpdates Requesting updates. credits:32 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 41} downstream server 2008mem02 sends a request for list of pending update (new/changed/deleted files) and states that he has 32 credits free currently and should be considered for downloads. + <Downstream> 20080625 11:50:03.582 4068 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00F4C978 downstream server 2008mem02 receives a positive response that his request is being evaluated. <Upstream> 20080625 11:50:03.595 2372 SRTR 882 SERVER_RequestUpdates Received from connId:{F5A520C4-154C-460E-B8EF0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} credits:32 requestType:all Upstream 2008mem01 receives the request for list of updates. <Upstream> 20080625 11:50:03.595 2372 SRTR 1927 SERVER_AsyncPoll Received from connId:{F5A520C4-154C-460E-B8EF0867D4F92AAE} <Upstream> 20080625 11:50:03.595 288 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: the file is now being truly committed to the content set and made available for replication + fid 0x300000000A7DA + usn 0x9ed8a8 + uidVisible 1 ready to be replicated out + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080625 15:50:03.515 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 still the same file (always check – there may be hundreds of files being updated simultaneously in a content set after all, with the same name) + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.475 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name bigdoc.rtf + <Downstream> 20080625 11:50:03.602 4068 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf creditsUsed:1 creditsAvailable:32 The downstream server starts the process of getting the list of pending file updates <Downstream> 20080625 11:50:03.602 4068 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 fileName:bigdoc.rtf session:2 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf The downstream server receives update information about the replication-pending file. This includes the UID, GVSN, name, and content set it belongs to. <Downstream> 20080625 11:50:03.602 3768 MEET 1207 Meet::Install Retries:0 updateName:bigdoc.rtf uid:{EDE2D64E-1306-4C7CB568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csName:testrf updateType:remote downstream creates its actual pulling session as a prelude to transferring the file <Downstream> 20080625 11:50:03.602 4068 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:2 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf downstream has all the information about the file update to take place. <Downstream> 20080625 11:50:03.602 3080 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00F954C8 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf changeType:notify <Downstream> 20080625 11:50:03.602 4068 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:UpdateRequest reqState:Completed status:0 ptr:00F4CA70 downstream server now actually requests the file through RPC <Upstream> 20080625 11:50:03.605 288 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 name:bigdoc.rtf connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf the upstream is satisfied that the downstream needs the file. The upstream server now prepares the file for being replicated by the downstream. <Upstream> 20080625 11:50:03.625 3104 OUTC 784 OutConnection::OpenFile Received request for update: the file is opened for copying into staging directory + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 same file + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.475 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name bigdoc.rtf + rdcDesired:1 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} rgName:TestRG RDC can be used if possible (not RDC will be used) <Upstream> 20080625 11:50:03.625 3104 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 metadata about file marshaled for RPC <Upstream> 20080625 11:50:05.388 3104 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: as we stage the file, it must be compressed with XPRESS and the hash/similarity information added. This happens below. + fid 0x300000000A7DA + usn 0x9ed8a8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080625 15:50:03.515 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.475 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash F91CD2BD-989749DC-EC8012D0-742AB147 + similarity 2008271D-2E11290A-2A212F0C-0E301F3F + name bigdoc.rtf + We will see slightly more detail in the staging process if we enable debuglogseverity=5. <Upstream> 20080625 11:50:05.648 3104 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Upstream> 20080625 11:50:05.648 3104 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 41{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41-Downloaded.frx the staged version of the file is ready. Note how the staged name is based on concatenation of the UID and GVSN names of the file. <Upstream> 20080625 11:50:05.648 3104 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080625 11:50:05.648 3104 OUTC 1534 OutConnection::OpenFile Sent file uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 name:bigdoc.rtf fileSize:1318071 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} rgName:TestRG the upstream side of the RPC connection lets the file be pulled to the downstream <Upstream> 20080625 11:50:05.648 3104 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} rdc:1 context:00F585B0,0101B728,00000000 uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v41 gvsn{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 ptr:00F53C90 the file is actually transferred over (from the upstream server's perspective. Remember that replication is pull-based from the downstream server and that it will appear that the replication is actually done in the upstream debug logs before the downstream, as the downstream has more work to do for the replication to complete. <Downstream> 20080625 11:50:06.006 3768 INCO 5610 InConnection::LogTransferActivity Received RAWGET uid:{EDE2D64E-13064C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 fileName:bigdoc.rtf connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} stagedSize:1318071 log the statistics about how the transfer proceeded <Upstream> 20080625 11:50:06.009 2372 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080625 11:50:06.156 3768 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080625 11:50:06.156 3768 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 41{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41-Downloaded.frx the file has been replicated into the staging directory on the downstream server. <Downstream> 20080625 11:50:06.156 3768 MRSH 3959 MarshalContext::Initialize Create file:[bigdoc-{EDE2D64E-1306-4C7C-B568449A98371AA2}-v41.rtf] with attributes:0x20 the file is un-marshaled <Downstream> 20080625 11:50:06.156 3768 MEET 2585 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:bigdoc.rtf uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v41 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csName:testrf the file is copied from staging into the Installing directory <Downstream> 20080625 11:50:07.398 3768 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080625 11:50:07.398 3768 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080625 11:50:07.398 3768 MEET 2032 Meet::Download Download Succeeded : true updateName:bigdoc.rtf uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csName:testrf csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} downstream server now has the file in its entirety and is ready to move it into the replicated folder content set. <Downstream> 20080625 11:50:07.398 3768 MEET 2837 Meet::InstallRename File moved. rootVolume:{3EA8BD01-416E-11DD-A317806E6F6E6963} parentFid:0x100000000A6D1 fidInInstalling:0x600000000A5EB usn:0x8c4858 updateName:bigdoc.rtf uid:{EDE2D64E1306-4C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 connId:{F5A520C4-154C-460E-B8EF0867D4F92AAE} csName:testrf the file is moved from Installing into the actual replicated folder c:\testrf <Downstream> 20080625 11:50:07.398 3768 MEET 6759 Meet::InsertIdRecord LDB Inserting ID Record: the above move necessitates a USN journal update and write into the DFSR database + fid 0x600000000A5EB we have a new downstream server-specific File ID + usn 0x8c4858 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 update occurred because the file was replicated in + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.475 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash F91CD2BD-989749DC-EC8012D0-742AB147 + similarity 2008271D-2E11290A-2A212F0C-0E301F3F + name bigdoc.rtf + <Downstream> 20080625 11:50:07.468 3768 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:bigdoc.rtf uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csName:testrf csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} completed moving file into the true RF location <Downstream> 20080625 11:50:07.468 3768 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 failures:0 sessionId:2 open:0 updateType:0 processStatus:0 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf update: completed replicating in this pending batch of files. + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v41 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080625 15:50:03.505 GMT (0x1c8d6db21e76e97) + createTime 20080625 15:50:03.475 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash F91CD2BD-989749DC-EC8012D0-742AB147 + similarity 2008271D-2E11290A-2A212F0C-0E301F3F + name bigdoc.rtf + <Downstream> 20080625 11:50:07.468 3768 INCO 6194 InConnection::CommitSession Connection in sync connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf commitedSessionsWithUpdateFailures:0 replication session completed with no errors <Downstream> 20080625 11:50:07.468 3768 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csName:testrf csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} downstream does not need any further updates to files from upstream. <Downstream> 20080625 11:50:07.468 3080 INCO 3779 InConnection::ContentSetContext::Hibernate Hibernating: connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} downstream server hibernates its connection until next time. Next up, I'll go through what a small (under 64KB) file looks like during replication, when RDC will not be used. Understanding DFSR debug logging (Part 4: A Very Small File Added to Replicated Folder on Windows Server 2008) In this scenario we will see a small file copied into the replicated folder and how it is replicated between two servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. If you haven't read Part 3, this isn't going to make as much sense, so make sure you review that. (tinyfiledownstream - Dfsr00005 - 2008.log and tinyfiledownstream - Dfsr00005 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 where the file is created (upstream) and from 2008MEM02 where it is replicated (downstream). Both servers are participating in the TESTRG replication group for the TESTRF replicated folder. The file is called "tinyfile.txt". It is smaller than 64KB so it will not need to be staged for RDC usage nor will it be XPRESS compressed. <Upstream> 20080624 12:04:56.359 3196 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: this should start looking familiar by now. + fid 0x200000000A752 + usn 0x930508 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080624 16:04:56.339 GMT + present 1 + nameConflict 0 + attributes 0x20 file, not a folder + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 file is new, as the UID and GVSN match + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080624 16:04:56.339 GMT (0x1c8d6140ba94250) + createTime 20080624 16:04:56.258 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name tinyfile.txt the file we will replicate + <Downstream> 20080624 12:04:56.362 3932 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf creditsUsed:1 creditsAvailable:32 <Downstream> 20080624 12:04:56.362 3932 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 fileName:tinyfile.txt session:11 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf <Downstream> 20080624 12:04:56.362 3284 MEET 1207 Meet::Install Retries:0 updateName:tinyfile.txt uid:{EDE2D64E-1306-4C7CB568-449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csName:testrf updateType:remote <Downstream> 20080624 12:04:56.362 3932 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:11 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf <Downstream> 20080624 12:04:56.362 1940 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00AB85B0 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf changeType:notify <Downstream> 20080624 12:04:56.362 3932 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:UpdateRequest reqState:Completed status:0 ptr:00B316E0 <Downstream> 20080624 12:04:56.362 3932 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:VvUpRequest reqState:Completed status:0 ptr:00AB85B0 <Downstream> 20080624 12:04:56.362 3284 MRSH 3959 MarshalContext::Initialize Create file:[tinyfile-{EDE2D64E-1306-4C7CB568-449A98371AA2}-v29.txt] with attributes:0x20 File transfer process begins from the downstream server <Upstream> 20080624 12:04:56.369 980 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{DEDD774B-4094-40BF-987AB38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 10..28} + + {910170E6-8BD6-49A9-85F1-A2F3FF43C76B} |-> { 10} <Upstream> 20080624 12:04:56.369 980 INCO 3966 InConnection::ReceiveVvUp Creating new session:6 requestState:00872A98 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 10..29} + {910170E6-8BD6-49A9-85F1-A2F3FF43C76B} |-> { 10} <Upstream> 20080624 12:04:56.369 980 OUTC 784 OutConnection::OpenFile Received request for update: File transfer process begins from the downstream server + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080624 16:04:56.339 GMT (0x1c8d6140ba94250) + createTime 20080624 16:04:56.258 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name tinyfile.txt + rdcDesired:1 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} rgName:TestRG <Upstream> 20080624 12:04:56.369 980 OUTC 1534 OutConnection::OpenFile Sent file uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 name:tinyfile.txt fileSize:346 connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} rgName:TestRG the file is going into the replication phase. This is going to be much simpler than a large file send as the file will not be staged upstream (no RDC, no compression) <Upstream> 20080624 12:04:56.369 980 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: + fid 0x200000000A752 + usn 0x930508 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080624 16:04:56.339 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080624 16:04:56.339 GMT (0x1c8d6140ba94250) + createTime 20080624 16:04:56.258 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 2F14F066-27FB1C64-8ED4E567-10B71F79 + similarity 00000000-00000000-00000000-00000000 + name tinyfile.txt + <Upstream> 20080624 12:04:56.369 980 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} rdc:1 context:00000000,00000000,00000000 uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v29 gvsn{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 ptr:00853DD0 the file is in transit <Downstream> 20080624 12:04:56.372 3284 INCO 5610 InConnection::LogTransferActivity Received RAWGET uid:{EDE2D64E-13064C7C-B568-449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 fileName:tinyfile.txt connId:{F5A520C4-154C460E-B8EF-0867D4F92AAE} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} stagedSize:362 performance counter data being updated. Note the RAWGET showing the file was copied without RDC. In this case it was not compressed either as it was never staged upstream. <Downstream> 20080624 12:04:56.372 3284 MEET 2032 Meet::Download Download Succeeded : true updateName:tinyfile.txt uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csName:testrf csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} the transfer was successful. <Downstream> 20080624 12:04:56.372 3284 MEET 2837 Meet::InstallRename File moved. rootVolume:{3EA8BD01-416E-11DD-A317806E6F6E6963} parentFid:0x100000000A6D1 fidInInstalling:0x100000000A72C usn:0x8a41b8 updateName:tinyfile.txt uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 connId:{F5A520C4-154C-460EB8EF-0867D4F92AAE} csName:testrf the file is moved directly into the replicated folder without entering the downstream staging or installing directory. <Downstream> 20080624 12:04:56.372 3284 MEET 6759 Meet::InsertIdRecord LDB Inserting ID Record: database updated from USN update + fid 0x100000000A72C + usn 0x8a41b8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 file exists through inbound replication + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 it is now in the replicated folder + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080624 16:04:56.339 GMT (0x1c8d6140ba94250) + createTime 20080624 16:04:56.258 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 2F14F066-27FB1C64-8ED4E567-10B71F79 + similarity 00000000-00000000-00000000-00000000 there is no RDC similarity data, it was never staged + name tinyfile.txt + <Downstream> 20080624 12:04:56.372 3284 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:tinyfile.txt uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csName:testrf csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} done moving file into replicated folder <Downstream> 20080624 12:04:56.372 3284 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 failures:0 sessionId:11 open:0 updateType:0 processStatus:0 connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} csId:{175F2B6A289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf update: done replicating any files from the upstream server. + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v29 + parent {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080624 16:04:56.339 GMT (0x1c8d6140ba94250) + createTime 20080624 16:04:56.258 GMT + csId {175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} + hash 2F14F066-27FB1C64-8ED4E567-10B71F79 + similarity 00000000-00000000-00000000-00000000 + name tinyfile.txt + Understanding DFSR debug logging (Part 5: File Modified on Windows Server 2003 R2) In this scenario we will see a file modified and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. (modifiedlargefileupstream - Dfsr00003 - 2003.log and modifiedlargefileupstream - Dfsr00003 - 2003.log) These are two Windows Server 2003 servers called 2003MEM01 and 2003MEM02 in the contoso.com domain. The logs are from 2003MEM01 where the file is created (upstream) and from 2003MEM02 where it is replicated (downstream). Both servers are participating in the TESTRG2 replication group for the TESTRF2 replicated folder. The file is called "setuplog.txt". The file was already staged previously. <Upstream> 20080625 17:42:30.805 1244 LDBX 3684 Ldb::Update Updating idRecord: the file is modified upstream so we must update the Jet database + fid 0x3000000002FBF + usn 0x68778 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080625 21:33:05.008 GMT + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 GVSN is higher than UID from the same server (same GUID); it's been modified + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 file original version is this + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:42:30.805 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 because file has been modified we must discard old hash/similarity main checksums from the database + similarity 00000000-00000000-00000000-00000000 + name setuplog.txt + <Upstream> 20080625 17:42:30.805 1244 USNC 2202 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: our existing USN journal record must be updated + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x3000000002fbf + ParentFileRefNumber: 0x1000000002f92 + USN: 0x68778 + TimeStamp: 20080625 17:42:30.805 Eastern Standard Time + Reason: Close Data Extend Data Overwrite the file has been modified, where data was extended and the file was saved. + SourceInfo: 0x0 + SecurityId: 0x1c7 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: setuplog.txt + <Upstream> 20080625 17:42:30.805 1244 LDBX 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00ADF478 <Downstream> 20080625 17:42:30.836 2416 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86340 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:all <Downstream> 20080625 17:42:30.836 2492 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Downstream> 20080625 17:42:30.846 2492 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86340 <Downstream> 20080625 17:42:30.876 2492 INCO 2947 InConnection::ReceiveVvUp Received VvUp connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 vvUp:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 10..21} current version on downstream is 10; current on upstream is 21. + <Downstream> 20080625 17:42:30.876 2492 INCO 2954 InConnection::ReceiveVvUp Creating new session:3 requestState:00A86340 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080625 17:42:30.876 2416 INCO 3347 InConnection::RequestUpdates Requesting updates. credits:32 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 21} downstream server learns current version vector from upstream + <Downstream> 20080625 17:42:30.876 2492 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Upstream> 20080625 17:42:30.885 1196 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:6 changeType:all Upstream server receives request for VV updates from the downstream server. Note how in Windows Server 2003 R2 the debug logs do not show as much information about the polling process as 2008 logs did in the File Add scenario. This can be mitigated somewhat by enabling debuglogseverity=5. <Upstream> 20080625 17:42:30.885 1196 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} <Upstream> 20080625 17:42:30.895 1196 SRTR 498 SERVER_RequestUpdates Received from connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} credits:32 requestType:all upstream has received the request for updates from downstream partner <Upstream> 20080625 17:42:30.895 1196 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} <Downstream> 20080625 17:42:30.896 2492 INCO 3534 InConnection::ReceiveUpdates Upstream credits:32 connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080625 17:42:30.896 2492 INCO 3597 InConnection::ReceiveUpdates Received: uid:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 fileName:setuplog.txt session:3 connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 we get the list of updates we intend to replicate over <Downstream> 20080625 17:42:30.896 2416 MEET 1190 Meet::Install Retries:0 updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401EADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 <Downstream> 20080625 17:42:30.896 2492 INCO 3661 InConnection::ReceiveUpdates Session has been closed. sessionId:3 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 We know of the updates now and are ready to transfer files <Downstream> 20080625 17:42:30.896 2492 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:UpdateRequest reqState:Completed status:0 ptr:00A86E70 <Downstream> 20080625 17:42:30.896 2532 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86E70 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:notify <Upstream> 20080625 17:42:30.905 1696 JOIN 1171 Join::SubmitUpdate Sent: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 name:setuplog.txt connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 This implies upstream server is satisfied that the file has been sent. We are still moving the file at this point though. <Upstream> 20080625 17:42:30.905 556 OUTC 588 OutConnection::OpenFile Received request for update: + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:42:30.805 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name setuplog.txt + rdcDesired:1 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} rgName:TestRG2 <Upstream> 20080625 17:42:30.905 556 MRSH 3487 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080625 17:42:30.915 556 LDBX 3684 Ldb::Update Updating idRecord: + fid 0x3000000002FBF + usn 0x68778 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080625 21:42:30.805 GMT + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:42:30.805 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 32B91C5A-74967572-4ABBC3A8-C319BB64 + similarity 3F193518-2F152E2B-36262037-05111237 since the file was restaged after being modified we now have our hash and similarity signatures again on the upstream server. + name setuplog.txt + <Upstream> 20080625 17:42:30.925 1196 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:7 changeType:notify <Upstream> 20080625 17:42:30.925 1696 STAG 102 StagingCleanupTask::Run Start to cleanup staging directory. csId:{5666BB91265D-42E8-9F57-1B49F4E581B7} <Upstream> 20080625 17:42:30.925 556 STAG 727 StageWriter::CompleteDownloadStage Completed download or stage file 21{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16-{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21-Downloaded.frx the file hs been staged upstream <Downstream> 20080625 17:42:30.926 2492 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86E70 <Upstream> 20080625 17:42:30.935 556 OUTC 1056 OutConnection::OpenFile Sent file uid:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 name:setuplog.txt fileSize:80823 connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} rgName:TestRG2 Upstream server is now ready to serve file and downstream is pulling across the data <Upstream> 20080625 17:42:30.935 556 SRTR 1730 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} rdc:1 context:00A7FE58,00B0F118,00000000 uid:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v16 gvsn{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 ptr:00AE49E0 data is transfered <Downstream> 20080625 17:42:30.946 2416 RDCX 1777 Rdc::SyncClientState::Flush Rdc Need Assembler Statistics: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 fileName:setuplog.txt connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} log stats about RDC and compression usage (this is only seen with debuglogseverity=5 in Win2008) + TOTAL + Compression Ratio 87 % + Target Uncompress Size 597424 this is the true file size when in the replicated folder + Target Compress Size 79943 this the file size compresses in staging + Bytes Received 6001 Signatures: 4254 Data: 1747 out of 597,424 bytes true size, only 6001 bytes sent over the wire because of XPRESS compressed RDC blocks + Signature Bytes Received 4254 4254 + Number of remote calls 3 Signatures: 1 Needs: 1 Data: 1 + SEED + Rdc Need Size 590437 590437 0 + Xpress Blocks 73 73 0 + Uncompressed Xpress Blocks 73 73 0 + Blocks copied to target 0 0 0 + SOURCE + Rdc Need Size 6987 0 + Xpress Blocks 1 0 + Uncompressed Xpress Blocks 1 0 + Blocks copied to target 0 0 <Downstream> 20080625 17:42:30.946 2416 INCO 4112 InConnection::LogTransferActivity Received RDCGET uid:{B0DAFB7F-1E6D401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 fileName:setuplog.txt connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} stagedSize:80823 transfer data logged in performance counter. Note the RDCGET rather than the RAWGET seen in the 'file add' scenario. This is because when we could not use RDC in that scenario the entire 'raw' file was copied. <Downstream> 20080625 17:42:30.946 2416 STAG 727 StageWriter::CompleteDownloadStage Completed download or stage file 21{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16-{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21-Downloaded.frx the file has ben written to the downstream staging directory successfully. <Downstream> 20080625 17:42:30.946 2416 MRSH 2957 MarshalContext::Initialize Create file:[setuplog.txt-{B0DAFB7F-1E6D401E-ADEC-2494F4A345A6}-v21] with attributes:0x20 <- the file is unmarshalled <Upstream> 20080625 17:42:30.955 1196 RDCX 2763 Rdc::SyncServerState::~SyncServerState RDC Need Reader Statistics: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} upstream we also log the sends for the performance counters. + TOTAL + Compression Ratio 15 % + RDC Need Size 6987 + Bytes sent to downstream 6001 matches what we sent above. + Uncompressed XPRESS blocks 0 + Compressed XPRESS blocks 0 + Copied XPRESS Blocks 1 <Downstream> 20080625 17:42:30.956 2416 MEET 1978 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 file is copied into the Installing directory. <Downstream> 20080625 17:42:30.956 2416 MEET 1898 Meet::Download Download Succeeded : true updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} the actual replication phase is over. <Downstream> 20080625 17:42:30.956 2416 MEET 2166 Meet::InstallRename Move out previous version of same file updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 the file must be replaced in the actual replicated folder now. DFSR does not use RDC 'on disk' – what ends up in staging/installing must overwrite what is in the actual RF. <Downstream> 20080625 17:42:30.956 2416 MEET 3700 Meet::MoveOut Moving contents and children out of replica. newName:setuplog.txt-{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v20 updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2record: the previous file is purged. Hence why if this file is locked, replication for a file cannot be completed either upstream or downstream. + fid 0x4000000002FCA + usn 0x6f318 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080625 21:33:05.774 GMT + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v20 previous version + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:33:04.888 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 06D3EAE4-7287AF33-9C7FE62A-F8EFE21C + similarity 3F193518-2F152E2B-36262037-05111237 + name setuplog.txt + <Downstream> 20080625 17:42:30.956 2416 MEET 3741 Meet::MoveOut Purge existing file in Deleted updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csName:testrf2 the file must go. <Downstream> 20080625 17:42:30.956 2416 MEET 3747 Meet::MoveOut RenameDelete file fid:0x4000000002FCA updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 the file is deleted and gone. <Downstream> 20080625 17:42:30.956 2416 MEET 2190 Meet::InstallRename File moved. rootVolume:{05853FA6-411C-11DD-A156806E6F6E6963} parentFid:0x1000000002F8C fidInInstalling:0x4000000002FCC usn:0x70850 updateName:setuplog.txt uid:{B0DAFB7F1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csName:testrf2 the updated file is moved in. <Downstream> 20080625 17:42:30.956 2416 LDBX 3684 Ldb::Update Updating idRecord: the DFSR jet database I updated to reflect that the updated version of the file is now in the content set. + fid 0x4000000002FCC + usn 0x70850 + uidVisible 1 It's available for further replication + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 the file exists in the content set. + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 GVSN now matches the originating server information + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:42:30.805 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 32B91C5A-74967572-4ABBC3A8-C319BB64 + similarity 3F193518-2F152E2B-36262037-05111237 + name setuplog.txt + <Downstream> 20080625 17:42:30.956 2416 MEET 2233 Meet::InstallRename -> DONE Install-rename completed updateName:setuplog.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} This file is complete <Downstream> 20080625 17:42:30.956 2416 INCO 4378 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 sessionId:3 open:0 updateType:0 processStatus:0 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E89F57-1B49F4E581B7} csName:testrf2 update: successfully replicated the file. + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v21 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v16 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 21:42:30.805 + createTime 20080625 21:27:21.734 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 32B91C5A-74967572-4ABBC3A8-C319BB64 + similarity 3F193518-2F152E2B-36262037-05111237 + name setuplog.txt + <Downstream> 20080625 17:42:30.966 2532 INCO 2787 InConnection::ContentSetContext::Hibernate Hibernating: connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} Understanding DFSR debug logging (Part 6: Microsoft Office Word 97-2003 File Modified on Windows Server 2008) In this scenario we will see a Microsoft Word 2003 file modified using MS Word 2003 and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. This also covers a practice often used by MS Office (and to a lesser extent other) applications that use transitional and temporary files in the main file's working directory. Note that other Office file types like Excel, PowerPoint, etc. may behave differently. (word2003modifyupstream - Dfsr00015 - 2008.log and word2003modifydownstream - Dfsr00012 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 where the file is modified (upstream) and from 2008MEM02 where it is replicated (downstream). Both servers are participating in the TESTRG3 replication group for the TESTRF3 replicated folder. The file is called "word2003large.doc". The file was already replicated previously. <Upstream> 20080626 11:32:31.284 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: the real file "word2003large.doc" was opened and Word automatically creates a temporary working file. Because it is both temporary and covered by the $ default filter in DFSR it will not be a candidate for replication. + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC61 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2e688 + TimeStamp: 20080626 11:32:31.274 Eastern Standard Time + Reason: Close Data Extend File Create file created new + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x22 0x20+0x2 means hidden file, per GetFileAttributes function. + FileNameLength: 34 + FileNameOffset: 60 + FileName: ~$rd2003large.doc name of file + <Upstream> 20080626 11:33:51.191 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: Word creates a pseudo-temporary file + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2f108 + TimeStamp: 20080626 11:33:51.181 Eastern Standard Time + Reason: Close Data Extend Data Overwrite File Create file created new with data added + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 not temporary + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0002.tmp marked with tilde (~) and TMP extension so still filtered out by DFSR by default + <Upstream> 20080626 11:33:51.191 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: Word deletes the temporary file (pretty much instantly) + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC66 same file ID as above. Important to watch FID's with apps that create lots of temporary and pseudo-temporary working files, as the UID/GVSN will not be created most of the time because the file is excluded from replication. + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2f160 + TimeStamp: 20080626 11:33:51.181 Eastern Standard Time + Reason: Close File Delete deleted + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0002.tmp same file as above + <Upstream> 20080626 11:33:51.861 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: Word does this again with yet another pseudo-temporary file + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 remember to watch FID's with unreplicated files; there's no guarantee that there won't be lots of files with the same name present in the replicated folder, especially as we can see that Word is not attempting to randomize the name. + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2f9d0 + TimeStamp: 20080626 11:33:51.861 Eastern Standard Time + Reason: Close Data Extend Data Overwrite File Create created, added some data + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 not temporary + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0003.tmp + <Upstream> 20080626 11:33:51.982 3128 USNC 1995 UsnConsumer::UpdateUsnOnly LDB Updating ID Record: the real document has an entry added in DFSR database due to USN update (next full line) + fid 0x70000000000B9 note for later in log entries that do not include UID/GVSN + usn 0xa2fb88 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:30:22.932 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 original file has not yet been modified (UID and GVSN match); this is because Word will use the temporary working file for most of its transactions in order to provide 'auto recover document' functionality + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:30:22.932 GMT (0x1c8d7a18ca3f2b2) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 4992549E-7564D836-ED346C90-D5FD88B3 + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc the file + <Upstream> 20080626 11:33:51.982 3128 USNC 1997 UsnConsumer::UpdateUsnOnly USN-only update from USN_RECORD: a USN only update means the file is not actually modified in a way that will trigger any form of replication (including metadata) + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x70000000000B9 same file as above + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2fb88 + TimeStamp: 20080626 11:33:51.972 Eastern Standard Time + Reason: Close Object ID Change the file is closed without being modified + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 34 + FileNameOffset: 60 + FileName: word2003large.doc same file as above + <Upstream> 20080626 11:33:51.982 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 this is the FID from the working file + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2fc40 + TimeStamp: 20080626 11:33:51.972 Eastern Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite Data truncation data has been added to the file + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0003.tmp the pseudo-temporary working file + <Upstream> 20080626 11:33:51.982 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2fcf0 + TimeStamp: 20080626 11:33:51.972 Eastern Standard Time + Reason: Close Security Change the file is closed with a security change + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0003.tmp + <Upstream> 20080626 11:33:51.982 3128 USNC 2777 UsnConsumer::TombstoneOrDelete LDB Updating ID Record: file deleted + fid 0x70000000000B9 + usn 0xa2ff68 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:30:22.932 GMT + present 0 deleted + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v65 version goes up (even during a deletion, as a deletion counts as a modification) + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceab9) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 4992549E-7564D836-ED346C90-D5FD88B3 + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc Word is renaming the original file. This is a prelude to copying data from the pseudo- temporary working files into a new file named the same as the original. This operation is considered a delete/tombstone because the file is being renamed to a filtered extension that will not replicate. + <Upstream> 20080626 11:33:51.982 3128 USNC 2782 UsnConsumer::TombstoneOrDelete ID record tombstoned from USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x70000000000B9 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2ff68 + TimeStamp: 20080626 11:33:51.972 Eastern Standard Time + Reason: Close Rename New Name the word2003large.doc file is renamed to a file named ~wrl004.tmp. Note how the File Reference Number never changed! + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRL0004.tmp new name + <Upstream> 20080626 11:33:51.982 3128 USNC 3341 UsnConsumer::UidTunnelReanimate LDB Updating ID Record: the UID is reused from previous due to the same file name/path + fid 0x200000000AC66 note that File ID is same as ~WRD0003.tmp + usn 0xa30000 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:33:51.982 GMT + present 1 added back into the replicated folder + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 new GVSN when file recreated + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 Old UID reused + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name word2003large.doc was ~WRD0003.tmp + <Upstream> 20080626 11:33:51.982 3128 USNC 3346 UsnConsumer::UidTunnelReanimate UID tunnelling: ID record reanimated because of UID tunnelling: the renaming of the file back into a previous one is counted as a USN reanimation + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa30000 + TimeStamp: 20080626 11:33:51.972 Eastern Standard Time + Reason: Basic Info Change Close Object ID Change Rename New Name Security Change ~WRD0003.tmp is renamed to word2003large.doc + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 34 + FileNameOffset: 60 + FileName: word2003large.doc + <Upstream> 20080626 11:33:51.992 3128 USNC 1995 UsnConsumer::UpdateUsnOnly LDB Updating ID Record: + fid 0x200000000AC66 + usn 0xa301c8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:33:51.982 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name word2003large.doc + <Upstream> 20080626 11:33:51.992 3128 USNC 1997 UsnConsumer::UpdateUsnOnly USN-only update from USN_RECORD: + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa301c8 + TimeStamp: 20080626 11:33:51.982 Eastern Standard Time + Reason: Close Object ID Change file closed + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 34 + FileNameOffset: 60 + FileName: word2003large.doc + <Downstream> 20080626 11:33:51.996 3616 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00A4CCE8 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:all downstream server requests version vectors <Downstream> 20080626 11:33:51.996 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A501C0 <Upstream> 20080626 11:33:52.062 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x70000000000B9 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa30388 + TimeStamp: 20080626 11:33:52.062 Eastern Standard Time + Reason: Basic Info Change Close Object ID Change closed the tmp file + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x2 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRL0004.tmp + <Upstream> 20080626 11:33:52.062 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x70000000000B9 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa303e0 + TimeStamp: 20080626 11:33:52.062 Eastern Standard Time + Reason: Close File Delete deleted the tmp file + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x2 + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRL0004.tmp + <Upstream> 20080626 11:33:52.062 3128 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC61 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa30438 + TimeStamp: 20080626 11:33:52.062 Eastern Standard Time + Reason: Close File Delete deleted the original renamed temporary file for the document + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x22 + FileNameLength: 34 + FileNameOffset: 60 + FileName: ~$rd2003large.doc + <Downstream> 20080626 11:33:52.286 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00A4CCE8 finished processing version vectors <Downstream> 20080626 11:33:52.286 1092 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 49..66} have received the VV's + <Downstream> 20080626 11:33:52.286 1092 INCO 3966 InConnection::ReceiveVvUp Creating new session:6 requestState:00A4CCE8 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 49..64} calculating the version vector delta + <Downstream> 20080626 11:33:52.286 3616 INCO 4619 InConnection::RequestUpdates Requesting updates. credits:32 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 65, 66} requesting the actual files from the upstream server based on missing versions + <Downstream> 20080626 11:33:52.286 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId {00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A501C0 <Upstream> 20080626 11:33:52.292 4052 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:15 changeType:all <Upstream> 20080626 11:33:52.292 4052 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} <Downstream> 20080626 11:33:52.296 1092 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{D7E7B14C-8DE94198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 creditsUsed:1 creditsAvailable:32 <Downstream> 20080626 11:33:52.296 1092 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 fileName:word2003large.doc session:6 connId:{D7E7B14C8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 <Downstream> 20080626 11:33:52.296 3616 MEET 1207 Meet::Install Retries:0 updateName:word2003large.doc uid:{EDE2D64E-13064C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 updateType:remote the file is ready to be received downstream <Downstream> 20080626 11:33:52.296 1092 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:6 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 <Downstream> 20080626 11:33:52.296 3976 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00A4CBF0 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:notify <Downstream> 20080626 11:33:52.296 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:UpdateRequest reqState:Completed status:0 ptr:00A42780 <Upstream> 20080626 11:33:52.302 4052 SRTR 882 SERVER_RequestUpdates Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} credits:32 requestType:all <Upstream> 20080626 11:33:52.302 4052 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} <Upstream> 20080626 11:33:52.302 2688 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 name:word2003large.doc connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 upstream acknowledges that it is ready to have the file pulled <Upstream> 20080626 11:33:52.302 1516 OUTC 784 OutConnection::OpenFile Received request for update: upstream serving file + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 this the version of the file to be replicated + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name word2003large.doc this is our file to be replicated + rdcDesired:1 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 <Downstream> 20080626 11:33:52.306 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00A4CBF0 <Upstream> 20080626 11:33:52.312 4052 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:16 changeType:notify <Upstream> 20080626 11:33:52.342 1516 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 file attributes marshaled <Upstream> 20080626 11:33:53.703 1516 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: + fid 0x200000000AC66 + usn 0xa301c8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:33:51.982 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + <Upstream> 20080626 11:33:53.903 1516 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Upstream> 20080626 11:33:53.903 1516 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 66{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66-Downloaded.frx the file has been staged (compressed, RDC signatures calculated) on the upstream server <Upstream> 20080626 11:33:53.903 1516 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080626 11:33:53.903 2688 STAG 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Upstream> 20080626 11:33:53.963 1516 OUTC 1534 OutConnection::OpenFile Sent file uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 name:word2003large.doc fileSize:4821514 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 the file is truly ready for replication upstream <Upstream> 20080626 11:33:53.963 1516 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rdc:1 context:00AB0248,00AA1BA8,00000000 uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 ptr:00AA3EC0 outbound RPC session ready on the upstream server, file can be replicated anytime now <Downstream> 20080626 11:33:54.169 3616 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080626 11:33:55.524 3128 USNC 2361 UsnConsumer::UpdateIdRecord LDB Updating ID Record: Word touched the file again for some reason. + fid 0x200000000AC66 + usn 0xa32330 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:33:51.982 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 Upstream, Word changes the file one more time as part of its internal workings. This is going to force the download process to happen all over again below unfortunately. This highlights how applications are often the cause of DFSR replication inefficiencies. Fortunately we will see below that the file was not altered materially and will not need to be restaged. + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:55.524 GMT (0x1c8d7a20b5b0f15) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name word2003large.doc + <Upstream> 20080626 11:33:55.524 3128 USNC 2364 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: + USN_RECORD: + RecordLength: 96 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x200000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa32330 + TimeStamp: 20080626 11:33:55.524 Eastern Standard Time + Reason: Close Data Overwrite file closed again. + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa2f9d0 + TimeStamp: 20080626 11:33:51.861 Eastern Standard Time + Reason: Close Data Extend Data Overwrite File Create ß created, added some data + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 ß not temporary + FileNameLength: 24 + FileNameOffset: 60 + FileName: ~WRD0003.tmp + FileNameLength: 34 + FileNameOffset: 60 + FileName: word2003large.doc + <Downstream> 20080626 11:33:55.531 3976 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:04569008 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:all <Downstream> 20080626 11:33:55.531 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A501C0 <Downstream> 20080626 11:33:55.531 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:04569008 <Downstream> 20080626 11:33:55.531 1092 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 49..67} we had to send the higher version vector info to downstream again + <Downstream> 20080626 11:33:55.531 1092 INCO 3966 InConnection::ReceiveVvUp Creating new session:7 requestState:04569008 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 49..64} + <Downstream> 20080626 11:33:55.531 1092 INCO 3982 InConnection::ReceiveVvUp Adding difference from previous session connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvDiff:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 65, 66} + vvDown:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 49..66} + <Downstream> 20080626 11:33:55.531 3976 INCO 4619 InConnection::RequestUpdates Requesting updates. credits:32 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 67} downstream rerequests the update again (the other –v66 update is still ongoing) + <Downstream> 20080626 11:33:55.531 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A501C0 <Upstream> 20080626 11:33:55.535 4052 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:17 changeType:all <Upstream> 20080626 11:33:55.535 4052 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} <Upstream> 20080626 11:33:55.535 4052 SRTR 882 SERVER_RequestUpdates Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} credits:32 requestType:all <Upstream> 20080626 11:33:55.535 4052 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} <Upstream> 20080626 11:33:55.535 2688 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 name:word2003large.doc connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 <Downstream> 20080626 11:33:55.541 1092 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{D7E7B14C-8DE94198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 creditsUsed:1 creditsAvailable:32 <Downstream> 20080626 11:33:55.541 1092 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 fileName:word2003large.doc session:7 connId:{D7E7B14C8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 downstream ready to pull the updates again. <Downstream> 20080626 11:33:55.541 3976 UPMG 413 UpdateWorker::ConsumeUpdates Available updates were locked. connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Downstream> 20080626 11:33:55.541 1092 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:7 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 the file updates have been transferred over the wire <Downstream> 20080626 11:33:55.541 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:UpdateRequest reqState:Completed status:0 ptr:00A4CBF0 <Downstream> 20080626 11:33:55.541 3976 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00A4CBF0 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:notify <Downstream> 20080626 11:33:55.541 1092 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00A4CBF0 <Upstream> 20080626 11:33:55.545 4052 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:18 changeType:notify <Downstream> 20080626 11:33:55.721 3616 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 11:33:55.721 3616 RDCX 1811 Rdc::SyncClientState::Flush Rdc Need Assembler Statistics: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 fileName:word2003large.doc connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} the downstream server can now gather statistics about what happened during the file transfer process. + TOTAL + Compression Ratio 2 + Target Uncompress Size 4905740 the true file size + Target Compress Size 4814322 file size after being XPRESS compressed in staging directory. Note how the size difference is not great here. In this scenario, the Word document was filled with JPG images which are already compressed. + Bytes Received 49704 Signatures: 4718 Data: 44986 actual bytes to be sent over the wire thanks to savings from RDC. The breakout here is total bytes, then the number of bytes that are just signature checksums, then the actual data blocks. + Signature Bytes Received 4718 1616 3102 + Number of remote calls 5 Signatures: 3 Needs: 1 Data: 1 + SEED + Rdc Need Size 0 0 0 + Xpress Blocks 589 589 0 + Uncompressed Xpress Blocks 7 7 0 + Blocks copied to target 0 0 0 + SOURCE + Rdc Need Size 113076 0 + Xpress Blocks 17 0 + Uncompressed Xpress Blocks 4 0 + Blocks copied to target 11 0 <Downstream> 20080626 11:33:55.721 3616 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 11:33:55.721 3616 INCO 5610 InConnection::LogTransferActivity Received RDCGET uid:{EDE2D64E-13064C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 fileName:word2003large.doc connId:{D7E7B14C8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} stagedSize:4821514 the file transfer over the wire is complete and the file now exists in staging on the downstream server. <Downstream> 20080626 11:33:55.721 3616 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 11:33:55.721 3976 STAG 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Upstream> 20080626 11:33:55.725 4052 RDCX 2833 Rdc::SyncServerState::~SyncServerState RDC Need Reader Statistics: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} statistics are now written to show what actually was sent over the wire (as opposed to the previous stats which were planned work) + + Compression Ratio 57 TOTAL + RDC Need Size 113076 + Bytes sent to downstream 49704 + Uncompressed XPRESS blocks 0 + Compressed XPRESS blocks 2 + Copied XPRESS Blocks 13 + Bytes read using async I/Os 0 <Upstream> 20080626 11:33:55.725 4052 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 11:33:55.781 3616 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 66{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66-Downloaded.frx we leave the staging functions and the name of the staged file is written to log <Downstream> 20080626 11:33:55.781 3616 MRSH 3959 MarshalContext::Initialize Create file:[word2003large-{EDE2D64E-13064C7C-B568-449A98371AA2}-v66.doc] with attributes:0x20 data is unmarshalled <Downstream> 20080626 11:33:55.781 3616 MEET 2585 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 the staged file is decompressed as a copy into the Installing directory <Downstream> 20080626 11:33:56.542 3976 UPMG 413 UpdateWorker::ConsumeUpdates Available updates were locked. connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Downstream> 20080626 11:33:56.542 3616 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 11:33:56.542 3616 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 11:33:56.542 3616 MEET 2032 Meet::Download Download Succeeded : true updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} the copy of the file in the Installing directory is now moved into the replicated folder, replacing an existing copy of the file <Downstream> 20080626 11:33:56.542 3616 MEET 2772 Meet::InstallRename Move out previous version of same file updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 since this was a modification of an existing file that exists on both servers, the downstream copy must be overwritten. So the older copy downstream is deleted. <Downstream> 20080626 11:33:56.542 3616 MEET 4867 Meet::MoveOut Moving contents and children out of replica. newName:word2003large-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61.doc updateName:word2003large.doc uid:{EDE2D64E-1306-4C7CB568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 record: indicates the deletion is occurring downstream + fid 0x200000000A6D1 + usn 0x903d38 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 20080626 15:30:27.557 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 note the old unmodified version + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:30:22.932 GMT (0x1c8d7a18ca3f2b2) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 4992549E-7564D836-ED346C90-D5FD88B3 + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + <Downstream> 20080626 11:33:56.542 3616 MEET 4989 Meet::MoveOut Purge existing file in Deleted updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 the older file is moved into the Deleted folder, then purged from the disk <Downstream> 20080626 11:33:56.542 3616 MEET 4995 Meet::MoveOut RenameDelete file fid:0x200000000A6D1 updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 DFSR notes that the old file is gone now. <Downstream> 20080626 11:33:56.542 3616 MEET 2837 Meet::InstallRename File moved. rootVolume:{3EA8BD01-416E-11DD-A317806E6F6E6963} parentFid:0xC00000000A514 fidInInstalling:0x900000000A5D4 usn:0x906ec0 updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csName:testrf3 the new copy of the file is copied into the replicated folder. <Downstream> 20080626 11:33:56.542 3616 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: Database is updated to reflect the file now existing in the replicated folder + fid 0x900000000A5D4 + usn 0x906ec0 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 indicates the update was due to replication and not an originating change + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 file is present and accessible by users + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D note that we have a new hash for the file after it was modified + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + <Downstream> 20080626 11:33:56.552 3616 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}v66 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} the process of moving file into the replicated folder is complete <Downstream> 20080626 11:33:56.552 3616 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 failures:0 sessionId:6 open:0 updateType:0 processStatus:0 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD1219491A1-4227-AB6B-9C252C6EACB8} csName:testrf3 update: + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v66 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:51.972 GMT (0x1c8d7a2093ceaba) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + <Downstream> 20080626 11:33:56.552 3616 MEET 1207 Meet::Install Retries:0 updateName:word2003large.doc uid:{EDE2D64E-13064C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 updateType:remote note the GVSN changed. This is the subsequent update that occurred when Word re-closed the file as part of its internal processing. <Downstream> 20080626 11:33:56.562 3620 SRTR 1880 SERVER_RequestVersionVector Received from connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:12 changeType:all <Downstream> 20080626 11:33:56.562 2716 SRTR 1927 SERVER_AsyncPoll Received from connId:{44747D15-9628-4CA2-8D1999CE2D1B02E9} <Downstream> 20080626 11:33:56.572 2716 SRTR 1927 SERVER_AsyncPoll Received from connId:{44747D15-9628-4CA2-8D1999CE2D1B02E9} <Downstream> 20080626 11:33:56.572 2716 SRTR 1880 SERVER_RequestVersionVector Received from connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:13 changeType:notify <Upstream> 20080626 11:33:56.575 1516 OUTC 784 OutConnection::OpenFile Received request for update: the subsequent file change is now being requested + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:55.524 GMT (0x1c8d7a20b5b0f15) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 note that the change is causing us to recalculate the hash (this is by design) + similarity 00000000-00000000-00000000-00000000 + name word2003large.doc + rdcDesired:1 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 <Upstream> 20080626 11:33:56.575 1516 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080626 11:33:56.585 752 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00AB0058 <Upstream> 20080626 11:33:56.585 2688 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00AA2038 connId:{44747D15-9628-4CA2-8D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:all <Upstream> 20080626 11:33:56.585 752 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00AA2038 <Upstream> 20080626 11:33:56.585 752 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{44747D15-9628-4CA2-8D1999CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 49..66} + <Upstream> 20080626 11:33:56.585 752 INCO 3966 InConnection::ReceiveVvUp Creating new session:6 requestState:00AA2038 connId:{44747D15-9628-4CA2-8D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 49..67} <- version vector information updated + <Upstream> 20080626 11:33:56.585 752 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00AB0058 <Upstream> 20080626 11:33:56.585 2688 INCO 3779 InConnection::ContentSetContext::Hibernate Hibernating: connId:{44747D159628-4CA2-8D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Upstream> 20080626 11:33:56.585 2688 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00AB0150 connId:{44747D15-9628-4CA2-8D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:notify <Upstream> 20080626 11:33:56.585 752 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{44747D15-9628-4CA28D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00AB0150 <Downstream> 20080626 11:33:57.543 3976 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{D7E7B14C-8DE94198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Upstream> 20080626 11:33:57.927 1516 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: the file info is re-added into the database, now with hash below, on the upstream server. + fid 0x200000000AC66 + usn 0xa32330 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 15:33:55.524 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:55.524 GMT (0x1c8d7a20b5b0f15) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D hash is the same as the –v66 version of the file. So the file did not actually change, it was just Word opening, making some non-data change, then closing for reasons unknown. + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + <Upstream> 20080626 11:33:58.077 1516 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Upstream> 20080626 11:33:58.077 1516 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 67{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67-Downloaded.frx the file is staged upstream. <Upstream> 20080626 11:33:58.077 1516 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080626 11:33:58.077 2688 STAG 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Downstream> 20080626 11:33:58.124 3616 RDCX 808 Rdc::SeedFile::Initialize The hashes coincide. The download is redundant, uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 fileName:word2003large.doc csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} after exchanging hash information, the downstream server now realizes that there is no need to replicate the file as it is unchanged upstream. <Upstream> 20080626 11:33:58.147 1516 OUTC 1534 OutConnection::OpenFile Sent file uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 name:word2003large.doc fileSize:4821514 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 <Upstream> 20080626 11:33:58.147 1516 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rdc:1 context:00AB0248,00AA1BA8,00000000 uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v61 gvsn{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 ptr:00AA3EC0 <Downstream> 20080626 11:33:58.184 3616 DOWN 5186 [ERROR] DownstreamTransport::RdcGet Failed on connId:{D7E7B14C-8DE94198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} rgName:TestRG3 update: failed is not an error in this case – it is an acknowledgment that there is no need to replicate the file downstream after all. However the version vector info is sent to keep the DFSR-related metadata about the file in sync going forward. + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 version updated + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:55.524 GMT (0x1c8d7a20b5b0f15) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D hash unchanged + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + Error: + [Error:9047(0x2357) RpcFinalizeContext downstreamtransport.cpp:1096 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SyncClientState::Download rdc.cpp:2546 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SeedFile::Initialize rdc.cpp:944 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SeedFile::Initialize rdc.cpp:810 3616 C The download is redundant] More spurious 'errors' – a redundant download is not a true error. <Downstream> 20080626 11:33:58.184 3616 INCO 5599 InConnection::LogTransferActivity Failed to receive RDCGET uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 fileName:word2003large.doc connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} stagedSize:0 Error: + [Error:9047(0x2357) DownstreamTransport::RdcGet downstreamtransport.cpp:5201 3616 C The download is redundant] + [Error:9047(0x2357) RpcFinalizeContext downstreamtransport.cpp:1096 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SyncClientState::Download rdc.cpp:2546 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SeedFile::Initialize rdc.cpp:944 3616 C The download is redundant] + [Error:9047(0x2357) Rdc::SeedFile::Initialize rdc.cpp:810 3616 C The download is redundant] more info that file download did not need to occur <Downstream> 20080626 11:33:58.184 3616 MEET 2032 Meet::Download Download Succeeded : false updateName:word2003large.doc uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}v67 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Downstream> 20080626 11:33:58.194 3616 NTFS 1257 NtfsFileSystem::SetAttributes oldFileAttributes:0x20 newFileAttributes:0x20 <Downstream> 20080626 11:33:58.194 3616 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: The database is updated to cover the new version info, regardless of the fact that file contents are unchanged + fid 0x900000000A5D4 + usn 0x907280 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v67 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v61 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 15:33:55.524 GMT (0x1c8d7a20b5b0f15) + createTime 20080626 15:30:22.912 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 66E49D5D-344B5F47-D192C5EA-6C30377D + similarity 2C131C03-12383C0B-15071E36-131A0C27 + name word2003large.doc + Understanding DFSR debug logging (Part 7: Microsoft Office Word 2007 File Modified on Windows Server 2008) In this scenario we will see a Microsoft Word 2007 file modified and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. This also covers a practice often used by MS Office and other applications that use transitional and temporary files in the main file’s working directory. (word2007modifiedupstream - Dfsr00018 - 2008.log and word2007modifieddownstream Dfsr00015 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 where the file is modified (upstream) and from 2008MEM02 where it is replicated (downstream). Both servers are participating in the TESTRG3 replication group for the TESTRF3 replicated folder. The file is called “modifiedword2007.docx”. The file was already replicated previously. <Upstream> 20080626 13:46:11.290 4040 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: A temporary working file is created upstream, which is related to the real file the user just opened. The file is filtered because it has temporary attribute set as well as starts with a tilde (which is filtered by default) + USN_RECORD: + RecordLength: 104 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000AC68 note file ID for later, since a number of files will be created/renamed/overwritten in the Word 2007 processing + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a270 + TimeStamp: 20080626 13:46:11.290 Eastern Standard Time + Reason: Close Data Extend File Create file created + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x22 hidden bit set on a file + FileNameLength: 42 + FileNameOffset: 60 + FileName: ~$difiedword2007.docx temporary working file name for autorecovery + <Upstream> 20080626 13:46:38.485 4040 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: 27 seconds later another pseudo-temporary file is created (not truly temporary but has a TMP extension that will be filtered by default by DFSR) + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC69 different File ID so we know it’s a different file + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a438 + TimeStamp: 20080626 13:46:38.485 Eastern Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite File Create created and wrote data + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 not truly temporary + FileNameLength: 24 + FileNameOffset: 60 + FileName: 4ED0A5C5.tmp temporary working file name + <Upstream> 20080626 13:46:38.485 4040 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC69 same file as above + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a4e8 + TimeStamp: 20080626 13:46:38.485 Eastern Standard Time + Reason: Close Security Change security change on the file + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: 4ED0A5C5.tmp same file name as above (and it’s the same real file as File ID matches) + <Upstream> 20080626 13:46:38.505 4040 USNC 2612 UsnConsumer::CreateNewRecord LDB Inserting ID Record: this file is created ‘new’. However this is actually a rename of the ‘4ED0A5C5.tmp’ file. Because this was previously filtered, it was not counted as a creation so the UID and GVSN will reflect a new file below. + fid 0x100000000AC69 note File ID matches the tmp file above + usn 0xa5a7c8 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 now live in the replicated folder + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 GVSN and UID match, so this is considered a new file (again, even though not truly new, previous version was filtered out) + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080626 17:46:38.505 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name modifiedword2007.docx Note the name is the original file name now. 20080626 17:46:38.505 GMT (0x1c8d7b495a970e4) + <Upstream> 20080626 13:46:38.555 4040 USNC 2615 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: + USN_RECORD: + RecordLength: 104 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x100000000AC69 note file ID same as the previous tmp file + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a7c8 + TimeStamp: 20080626 13:46:38.505 Eastern Standard Time + Reason: Basic Info Change Close Object ID Change Rename New Name Security Change the 4ED0A5C5.tmp file is renamed to modifiedword2007.docx, and other data is changed in the file + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 42 + FileNameOffset: 60 + FileName: modifiedword2007.docx + <Upstream> 20080626 13:46:38.555 4040 USNC 2361 UsnConsumer::UpdateIdRecord LDB Updating ID Record: the file is being closed after modification. + fid 0x100000000AC69 + usn 0xa5a898 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 17:46:38.505 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 Version incremented due to modification. + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:46:38.505 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name modifiedword2007.docx + <Upstream> 20080626 13:46:38.555 4040 USNC + USN_RECORD: + RecordLength: 104 + MajorVersion: 2 2364 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: + MinorVersion: 0 + FileRefNumber: 0x100000000AC69 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a898 + TimeStamp: 20080626 13:46:38.515 Eastern Standard Time + Reason: Close Security Change + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 42 + FileNameOffset: 60 + FileName: modifiedword2007.docx + <Upstream> 20080626 13:46:38.555 4040 USNC 2777 UsnConsumer::TombstoneOrDelete LDB Updating ID Record: the original copy of the file is being deleted as it gets overwritten by the copy of the file upstream (this is still Word’s internal behavior, we have not yet done any replication obviously) 0x300000000AC66 the file ID is different because this was the older file + fid + usn 0xa5a900 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 17:34:11.530 GMT + present 0 no longer in the replicated folder + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 Deletion still counts as a version increase + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 note the old UID + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 22894EE1-C5DBE0DE-F63EF65F-B42162E4 + similarity 3622212A-1A3A3706-23381636-00212E2E + name modifiedword2007.docx + <Upstream> 20080626 13:46:38.555 4040 USNC 2782 UsnConsumer::TombstoneOrDelete ID record tombstoned from USN_RECORD: USN journal updated to reflect the ‘deletion’ of the original word file, as it is now filtered. + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000AC66 old file ID + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a900 + TimeStamp: 20080626 13:46:38.515 Eastern Standard Time + Reason: Close Object ID Change Rename New Name note how Word is renaming the file again prior to deletion. + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: 52E1E902.tmp + <Upstream> 20080626 13:46:38.555 4040 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: the original word file is now finally truly deleted + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000AC66 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a958 + TimeStamp: 20080626 13:46:38.515 Eastern Standard Time + Reason: Close File Delete delete flag + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: 52E1E902.tmp + <Upstream> 20080626 13:46:38.595 4040 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: the temporary working file is now deleted as well. + USN_RECORD: + RecordLength: 104 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000AC68 + ParentFileRefNumber: 0xF00000000A781 + USN: 0xa5a9b0 + TimeStamp: 20080626 13:46:38.585 Eastern Standard Time + Reason: Close File Delete deleted flag + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x22 + FileNameLength: 42 + FileNameOffset: 60 + FileName: ~$difiedword2007.docx + <Downstream> 20080626 13:46:38.637 4036 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00B4D7A8 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:all downstream requests outstanding changes <Downstream> 20080626 13:46:38.637 3980 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00BCA1B0 <Upstream> 20080626 13:46:38.935 2284 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:4 changeType:all <Upstream> 20080626 13:46:38.935 2284 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51- B8D13867171D} upstream receives the version vector request <Upstream> 20080626 13:46:38.945 3132 SRTR 882 SERVER_RequestUpdates Received from connId:{D7E7B14C-8DE9-4198-BA51- B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} credits:32 requestType:all <Upstream> 20080626 13:46:38.945 3132 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51- B8D13867171D} <Upstream> 20080626 13:46:38.945 2072 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 name:modifiedword2007.docx connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 information about the update is sent to downstream server <Upstream> 20080626 13:46:38.945 2072 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: upstream sends change info + fid 0x100000000AC69 + usn 0xa5a898 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 17:46:38.555 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 note the GVSN matches the final copy of file that was modified upstream + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 note UID as well + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name modifiedword2007.docx the file + <Upstream> 20080626 13:46:38.945 2072 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 name:modifiedword2007.docx connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 update info was sent successfully <Upstream> 20080626 13:46:38.955 2284 SRTR 1880 SERVER_RequestVersionVector Received from connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} seqNumber:5 changeType:notify <Downstream> 20080626 13:46:38.957 3980 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00B4D7A8 <Downstream> 20080626 13:46:38.957 3980 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 49..81} the VV update + <Downstream> 20080626 13:46:38.957 3980 INCO 3966 InConnection::ReceiveVvUp Creating new session:2 requestState:00B4D7A8 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 49..78} + <Downstream> 20080626 13:46:38.957 4036 INCO 4619 InConnection::RequestUpdates Requesting updates. credits:32 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 79..81} + <Downstream> 20080626 13:46:38.957 3980 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00BCA1B0 <Downstream> 20080626 13:46:38.967 3980 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{D7E7B14C-8DE9- 4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 creditsUsed:2 creditsAvailable:32 <Downstream> 20080626 13:46:38.967 3980 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568- 449A98371AA2}-v76 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 fileName:modifiedword2007.docx session:2 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 <Downstream> 20080626 13:46:38.967 3980 INCO 4868 InConnection::ReceiveUpdates Received: uid:{EDE2D64E-1306-4C7C-B568- 449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 fileName:modifiedword2007.docx session:2 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 note how DFSR is trying to replicate two versions of the original file, with two separate UID’s. This is due to how Word 2007 makes copies of the files and overwrites them, leading to two distinct replication change packages being done. One is a delete and one is a replicate. <Downstream> 20080626 13:46:38.967 3980 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:2 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 <Downstream> 20080626 13:46:38.967 3980 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:UpdateRequest reqState:Completed status:0 ptr:00B4D8A0 <Downstream> 20080626 13:46:38.967 4036 MEET 1207 Meet::Install Retries:0 updateName:modifiedword2007.docx uid:{EDE2D64E- 1306-4C7C-B568-449A98371AA2}-v76 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csName:testrf3 updateType:remote <Downstream> 20080626 13:46:38.967 2928 MEET 1207 Meet::Install Retries:0 updateName:modifiedword2007.docx uid:{EDE2D64E- 1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csName:testrf3 updateType:remote <Downstream> 20080626 13:46:38.967 2880 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00B53398 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:notify <Downstream> 20080626 13:46:38.977 3980 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{D7E7B14C-8DE9-4198- BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} reqType:VvUpRequest reqState:Completed status:0 ptr:00B53398 <Downstream> 20080626 13:46:38.987 4036 MEET 4867 Meet::MoveOut Moving contents and children out of replica. newName:modifiedword2007-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v77.docx updateName:modifiedword2007.docx uid:{EDE2D64E1306-4C7C-B568-449A98371AA2}-v76 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 connId:{D7E7B14C-8DE9-4198-BA51B8D13867171D} csName:testrf3 record: Original version of the file that was previous replicated is deleted, because the original one was truly deleted upstream (not modified – Word 2007 does not truly modify files). A moveout is a delete in DFSR. + fid 0x100000000A766 + usn 0x929d88 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 20080626 17:34:12.343 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v77 previous version of the file + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 different UID than our new file we just ‘modified’ + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 22894EE1-C5DBE0DE-F63EF65F-B42162E4 + similarity 3622212A-1A3A3706-23381636-00212E2E + name modifiedword2007.docx 20080626 17:34:11.530 GMT (0x1c8d7b2d86e2ef4) + 784 OutConnection::OpenFile Received request for update: file is being <Upstream> 20080626 13:46:38.996 4032 OUTC served upstream + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 this is our new version of the file + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name modifiedword2007.docx same file name + rdcDesired:1 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 <Upstream> 20080626 13:46:38.996 4032 MRSH <Downstream> 20080626 13:46:38.997 4036 MEET 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 6746 Meet::UpdateIdRecord LDB Updating ID Record: + fid 0x100000000A766 previous file’s FID + usn 0x92d188 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 0 the previous file is being deleted. + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 UID is for the older file + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 22894EE1-C5DBE0DE-F63EF65F-B42162E4 + similarity 3622212A-1A3A3706-23381636-00212E2E + name modifiedword2007.docx + <Downstream> 20080626 13:46:38.997 4036 MEET 4794 Meet::InstallTombstone -> DONE Install Tombstone complete updateName:modifiedword2007.docx uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v81 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} The file is tombstoned in the database. This means that a reference to the file remains for 30 days in the DFSR DB downstream but the actual file has now been removed. <Downstream> 20080626 13:46:38.997 4036 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:1 processed:1 failures:0 sessionId:2 open:0 updateType:0 processStatus:0 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 update: the update (which was a delete) has been processed + present 0 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v81 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v76 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 22894EE1-C5DBE0DE-F63EF65F-B42162E4 + similarity 3622212A-1A3A3706-23381636-00212E2E + name modifiedword2007.docx + <Downstream> 20080626 13:46:38.997 4036 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{D7E7B14C-8DE9- 4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} <Upstream> 20080626 13:46:39.106 4032 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: the database is updated to reflect the file hash of the later version of the file. Apparently the file has changed somewhat as we have a new hash. + fid 0x100000000AC69 + usn 0xa5a898 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080626 17:46:38.555 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 5FE417F1-498E8A23-73693A0F-6D8FA626 note how hash differs from previous + similarity 3622212A-1A2D3706-23381636-00212E2E + name modifiedword2007.docx 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + <Upstream> 20080626 13:46:39.276 4032 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Upstream> 20080626 13:46:39.276 4032 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 80- {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80-Downloaded.frx the v80 version of the file is staged upstream <Upstream> 20080626 13:46:39.276 4032 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080626 13:46:39.276 4032 OUTC 1534 OutConnection::OpenFile Sent file uid:{EDE2D64E-1306-4C7C-B568- 449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 name:modifiedword2007.docx fileSize:397852 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rgName:TestRG3 the v80 version of the file is now being served from upstream <Upstream> 20080626 13:46:39.276 4032 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} rdc:1 context:00E69008,00EBAD08,00000000 uid:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v79 gvsn{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 ptr:00DF62C8 <Downstream> 20080626 13:46:39.378 2928 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 13:46:39.378 2928 STAG 987 StageWriter::AbortDownloadStage Successfully aborted staging file 1- {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v1-Downloading.frx. Deleted. downstream, the previously staged copy of the file (v79) must be deleted as it is being superceded by the quickly-sent next version of v80. <Downstream> 20080626 13:46:39.378 2928 RDCX 1590 [WARN] Rdc::SeedFile::UseRelated (Ignored) Failed. uid:{EDE2D64E-1306- 4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 fileName:modifiedword2007.docx csId:{BDD1219491A1-4227-AB6B-9C252C6EACB8} (related: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v1 fileName:modifiedword2007.docx csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8}) Error:[Error:9024(0x2340) Rdc::SeedFile::UseRelated rdc.cpp:1499 2928 C The file meta data is not synchronized with the file system] The RDC signature calculation process must be stopped while it was working on the previously staged file. The message about ‘meta data not synched’ refers to this as well. <Downstream> 20080626 13:46:39.378 2928 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 13:46:39.378 2928 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 13:46:39.378 2928 STAG 987 StageWriter::AbortDownloadStage Successfully aborted staging file 1- {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v1-Downloading.frx. Deleted. the previously staged file has been removed from downstream staging directory. <Downstream> 20080626 13:46:39.378 2928 RDCX 1590 [WARN] Rdc::SeedFile::UseRelated (Ignored) Failed. uid:{EDE2D64E-1306- 4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 fileName:modifiedword2007.docx csId:{BDD1219491A1-4227-AB6B-9C252C6EACB8} (related: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v1 fileName:modifiedword2007.docx csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8}) Error:[Error:9024(0x2340) Rdc::SeedFile::UseRelated rdc.cpp:1499 2928 C The file meta data is not synchronized with the file system] <Downstream> 20080626 13:46:39.378 2928 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080626 13:46:40.027 2284 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 13:46:40.039 2928 INCO 5610 InConnection::LogTransferActivity Received RAWGET uid:{EDE2D64E-1306- 4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 fileName:modifiedword2007.docx connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} stagedSize:397852 the replication of the newer version of file is complete. Note the RAWGET which shows RDC could not be used in this scenario. <Downstream> 20080626 13:46:40.089 2928 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 13:46:40.089 2928 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 80- {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80-Downloaded.frx <Downstream> 20080626 13:46:40.089 2928 MRSH 3959 MarshalContext::Initialize Create file:[modifiedword2007-{EDE2D64E- 1306-4C7C-B568-449A98371AA2}-v80.docx] with attributes:0x20 the latest version is successfully staged downstream. <Downstream> 20080626 13:46:40.089 2928 MEET 2585 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:modifiedword2007.docx uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v80 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 the file is decompressed from staging into the Installing directory. <Upstream> 20080626 13:46:40.187 2072 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00DFB6B8 connId:{44747D15-9628-4CA2-8D19-99CE2D1B02E9} csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} csName:testrf3 changeType:all <Upstream> 20080626 13:46:40.187 4032 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{44747D15-9628-4CA2- 8D19-99CE2D1B02E9} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00E6C5B8 <Downstream> 20080626 13:46:40.189 2928 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080626 13:46:40.189 2928 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080626 13:46:40.189 2928 MEET 2032 Meet::Download Download Succeeded : true updateName:modifiedword2007.docx uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v80 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} The downstream server considers the file to be fully replicated over and staged and decompressed. <Downstream> 20080626 13:46:40.189 2928 MEET 2837 Meet::InstallRename File moved. rootVolume:{3EA8BD01-416E-11DD-A317- 806E6F6E6963} parentFid:0xC00000000A514 fidInInstalling:0x100000000A76A usn:0x92ee98 updateName:modifiedword2007.docx uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 connId:{D7E7B14C-8DE9-4198BA51-B8D13867171D} csName:testrf3 the file is then written into the actual replicated folder on the downstream server, overwriting any existing <Downstream> 20080626 13:46:40.189 2928 MEET 6759 Meet::InsertIdRecord LDB Inserting ID Record: DFSR database updated downstream with info about the file. + fid 0x100000000A76A + usn 0x92ee98 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 the file exists due to inbound replication + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v80 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 + parent {BDD12194-91A1-4227-AB6B-9C252C6EACB8}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080626 17:46:38.515 GMT (0x1c8d7b495aaf803) + createTime 20080626 17:30:25.894 GMT + csId {BDD12194-91A1-4227-AB6B-9C252C6EACB8} + hash 5FE417F1-498E8A23-73693A0F-6D8FA626 + similarity 3622212A-1A2D3706-23381636-00212E2E + name modifiedword2007.docx + <Downstream> 20080626 13:46:40.189 2928 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:modifiedword2007.docx uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v79 gvsn:{EDE2D64E-1306-4C7C-B568449A98371AA2}-v80 connId:{D7E7B14C-8DE9-4198-BA51-B8D13867171D} csName:testrf3 csId:{BDD12194-91A1-4227-AB6B-9C252C6EACB8} the file is now in the replicated folder and the operation is complete Understanding DFSR debug logging (Part 8: File Deleted from Windows Server 2003 R2) In this scenario we will see a file deleted and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, the staging folder structure, and the network (including RPC) are preventing replication from working correctly. (deletedfileupstream - Dfsr00004 - 2003.log and deletedfiledownstream - Dfsr00005 - 2003.log) These are two Windows Server 2003 servers called 2003MEM01 and 2003MEM02 in the contoso.com domain. The logs are from 2003MEM01 where the file is deleted (upstream) and from 2003MEM02 where it the deletion is replicated (downstream). Both servers are participating in the TESTRG2 replication group for the TESTRF2 replicated folder. The file is called “goodbye.txt”. <Upstream> 20080625 19:55:51.522 800 LDBX 3684 Ldb::Update Updating idRecord: the DFSR jet DB is updated because the file is changing (even a delete is a change to the state of the file; file references stay in the database for 30 days to allow for reanimation) + fid 0x2000000002FED + usn 0x81c50 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080625 23:55:41.318 GMT + present 0 The file does not exist in the content set anymore + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 GVSN goes up (state changed) + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 23:55:51.502 + createTime 20080625 23:55:41.217 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name goodbye.txt + <Upstream> 20080625 19:55:51.532 800 USNC 2599 UsnConsumer::TombstoneOrDelete ID record tombstoned from USN_RECORD: USN journal must be updated to reflect the deletion. + USN_RECORD: + RecordLength: 80 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x2000000002fed + ParentFileRefNumber: 0x5000000002fa7 + USN: 0x81c50 + TimeStamp: 20080625 19:55:51.502 Eastern Standard Time good to know the exact time as deletions are not usually important unless it was unexpected and root cause is being analyzed. + Reason: Close Rename New Name + SourceInfo: 0x0 + SecurityId: 0x1c7 + FileAttributes: 0x20 + FileNameLength: 14 + FileNameOffset: 60 + FileName: goodbye.txt + <Upstream> 20080625 19:55:51.532 800 LDBX 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00AD6308 <Downstream> 20080625 19:55:51.546 3832 INCO 3347 InConnection::RequestUpdates Requesting updates. credits:32 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 26} downstream server request version vector of upstream server + <Downstream> 20080625 19:55:51.546 3928 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Upstream> 20080625 19:55:51.582 1624 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:6 changeType:all VV request received. <Upstream> 20080625 19:55:51.582 1624 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Downstream> 20080625 19:55:51.586 3928 INCO 3534 InConnection::ReceiveUpdates Upstream credits:32 connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 downstream server request <Downstream> 20080625 19:55:51.586 3928 INCO 3597 InConnection::ReceiveUpdates Received: uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v25 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 fileName:goodbye.txt session:3 connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 the ‘data’ is replicated. Keep in mind that when replicating metadata changes (file rename, attribute data, security data, or file deletion) the actual file is not sent over the wire. There is no staging in or out. Only information necessary to describe the metadata is sent via RPC; in this case, just the ‘delete’. <Downstream> 20080625 19:55:51.586 3832 MEET 1190 Meet::Install Retries:0 updateName:goodbye.txt uid:{B0DAFB7F-1E6D-401E- ADEC-2494F4A345A6}-v25 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 the update was received on the downstream. <Downstream> 20080625 19:55:51.586 3832 MEET 3700 Meet::MoveOut Moving contents and children out of replica. newName:goodbye.txt-{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 updateName:goodbye.txt uid:{B0DAFB7F-1E6D-401E-ADEC2494F4A345A6}-v25 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2record: in content set terms, files are never ‘deleted’. They are moved out of the content set. + fid 0x1000000002FE8 + usn 0x883a0 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080625 23:55:41.331 GMT + present 1 the file is still present on the downstream server, we are in process here (on the upstream a file is just deleted and that’s it. On the downstream servers, it will have to transition its way into the ConflictAndDeleted folder.) + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 23:55:41.227 + createTime 20080625 23:55:41.217 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash CC8863B9-2EAB0BC2-C669B493-00C79510 + similarity 00000000-00000000-00000000-00000000 + name goodbye.txt + <Upstream> 20080625 19:55:51.592 1624 SRTR 498 SERVER_RequestUpdates Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} credits:32 requestType:all <Upstream> 20080625 19:55:51.592 1624 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Downstream> 20080625 19:55:51.596 3832 LDBX 3684 Ldb::Update Updating idRecord: now we update jet database downstream to reflect the deletion. The file has actually now been moved to the ConflictAndDeleted folder and the conflictanddeletedmanifest.xml has been updated (but this is not covered in the deuglogseverity=4 debug logs) + fid 0x1000000002FE8 + usn 0x88608 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 0 the file is no longer present in the content set + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 the deletion necessitates updating the GVSN + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 23:55:51.502 + createTime 20080625 23:55:41.217 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name goodbye.txt + <Downstream> 20080625 19:55:51.596 3832 MEET 3635 Meet::InstallTombstone -> DONE Install Tombstone complete updateName:goodbye.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} the tombstone (deletion) process is completed downstream. The file is completely out of the content set. <Downstream> 20080625 19:55:51.596 3928 INCO 3661 InConnection::ReceiveUpdates Session has been closed. sessionId:3 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080625 19:55:51.596 3832 INCO 4378 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 sessionId:3 open:0 updateType:0 processStatus:0 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91265D-42E8-9F57-1B49F4E581B7} csName:testrf2 update: the single update from upstream was processed with no errors + present 0 file is no longer present + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080625 23:55:51.502 + createTime 20080625 23:55:41.217 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name goodbye.txt + <Downstream> 20080625 19:55:51.596 3928 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:UpdateRequest reqState:Completed status:0 ptr:00A86E70 <Upstream> 20080625 19:55:51.602 820 JOIN 1171 Join::SubmitUpdate Sent: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v25 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v26 name:goodbye.txt connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 upstream server reports completion on the update operation. <Upstream> 20080625 19:55:51.602 1624 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:7 changeType:notify <Downstream> 20080625 19:55:51.606 3832 LDBX 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00ADEE10 <Downstream> 20080625 19:55:51.606 3832 INCO 4617 InConnection::CommitSession Connection in sync connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} <Downstream> 20080625 19:55:51.606 3904 INCO 2787 InConnection::ContentSetContext::Hibernate Hibernating: connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} Understanding DFSR debug logging (Part 9: File is Renamed on Windows Server 2003 R2) In this scenario we will see a file renamed and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, and the network (including RPC) are preventing replication from working correctly. (renamedfileupstream - Dfsr00005 - 2003.log and renamedfiledownstream - Dfsr00006 - 2003.log) These are two Windows Server 2003 servers called 2003MEM01 and 2003MEM02 in the contoso.com domain. The logs are from 2003MEM01 where the file is renamed (upstream) and from 2003MEM02 where it the rename is replicated (downstream). Both servers are participating in the TESTRG2 replication group for the TESTRF2 replicated folder. The file was originally called “mikesdoc.txt” and was then renamed to “davesdoc.txt”. <Upstream> 20080626 15:58:36.910 1440 LDBX 3567 Ldb::Insert Inserting idRecord: the original file creation leads to a DFSR database update. We examine this part of the log in order to understand the later rename operation fully. + fid 0x2000000002FF0 note the file ID as a cross-reference against the UID/GVSN + usn 0x9db60 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 the file is present in the replica set + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 note the UID and GVSN are a perfect match. This is the key indicator that the file was just created on this server upstream + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080626 19:58:36.910 + createTime 20080626 19:58:36.910 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name mikesdoc.txt the file is currently named mikesdoc.txt <snip – removed all the replication debug log churn that this generates> <Upstream> 20080626 16:00:17.124 1440 LDBX 3684 Ldb::Update Updating idRecord: some time later, a user renames the file on the upstream server. This must be recorded in the DFSR database. + fid 0x2000000002FF0 note the file ID is unchanged + usn 0x9e800 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080626 19:58:37.200 GMT + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 GVSN version is incremented to the high watermark on the server. There have been no other changes on the server so the version is only one higher. + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 remember that UID will stay the same forever. This helps us track the file. + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080626 20:00:17.114 + createTime 20080626 19:58:04.143 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash CE2505D3-E4669977-250B31C1-100B67DE + similarity 2A242410-2E100D1A-191A340E-041A1018 + name davesdoc.txt note the file name has changed. + <Upstream> 20080626 16:00:17.124 1440 USNC 2202 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: the USN journal has been updated (it is an idiosyncrasy of a multi-threaded DFSR service logging that this does not write before the database update above. Technically the USN journal update *must* have happened first. + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x2000000002ff0 note the matching file ID to the above records. Tracking this allows you to cross reference USN and DB record updates in the log. + ParentFileRefNumber: 0x1000000002f92 + USN: 0x9e800 + TimeStamp: 20080626 16:00:17.114 Eastern Standard Time + Reason: Close Rename New Name the rename operation is made clearer + SourceInfo: 0x0 + SecurityId: 0x1b5 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: davesdoc.txt + <Upstream> 20080626 16:00:17.124 1440 LDBX 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00ADF868 <Upstream> 20080626 16:00:17.134 1456 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:6 changeType:all the upstream server is asked by the downstream for version vectors, as the4 upstream had sent a change notification <Upstream> 20080626 16:00:17.134 1456 SRTR earlier (this is not logged) 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Upstream> 20080626 16:00:17.144 1456 SRTR 498 SERVER_RequestUpdates Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} credits:32 requestType:all upstream server receives a request for pending updates <Upstream> 20080626 16:00:17.144 1456 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Upstream> 20080626 16:00:17.154 1644 JOIN 1171 Join::SubmitUpdate Sent: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 name:davesdoc.txt connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 information about the updated is sent to the downstream server <Upstream> 20080626 16:00:17.164 1832 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:7 changeType:notify <Upstream> 20080626 16:00:17.164 1644 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86E70 connId:{37048901-9F48-4AD8-ADA4-04D4DC682FD8} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:all <Upstream> 20080626 16:00:17.164 1424 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{37048901-9F48-4AD8- ADA4-04D4DC682FD8} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Upstream> 20080626 16:00:17.164 1424 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{37048901-9F48-4AD8- ADA4-04D4DC682FD8} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86E70 <Upstream> 20080626 16:00:17.174 1424 INCO 2947 InConnection::ReceiveVvUp Received VvUp connId:{37048901-9F48-4AD8-ADA4- 04D4DC682FD8} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 vvUp:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 10..29} + <Upstream> 20080626 16:00:17.174 1424 INCO 2954 InConnection::ReceiveVvUp Creating new session:3 requestState:00A86E70 connId:{37048901-9F48-4AD8-ADA4-04D4DC682FD8} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Upstream> 20080626 16:00:17.174 1644 INCO 2787 InConnection::ContentSetContext::Hibernate Hibernating: connId:{37048901- 9F48-4AD8-ADA4-04D4DC682FD8} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} <Downstream> 20080626 16:00:17.509 980 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86340 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:all <Downstream> 20080626 16:00:17.509 1472 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Downstream> 20080626 16:00:17.509 1472 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86340 <Downstream> 20080626 16:00:17.519 1472 INCO 2947 InConnection::ReceiveVvUp Received VvUp connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 vvUp:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 10..29} + <Downstream> 20080626 16:00:17.519 1472 INCO 2954 InConnection::ReceiveVvUp Creating new session:3 requestState:00A86340 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080626 16:00:17.519 980 INCO 3347 InConnection::RequestUpdates Requesting updates. credits:32 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 29} + <Downstream> 20080626 16:00:17.519 1472 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Downstream> 20080626 16:00:17.529 1472 INCO 3534 InConnection::ReceiveUpdates Upstream credits:32 connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080626 16:00:17.529 1472 INCO 3597 InConnection::ReceiveUpdates Received: uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v28 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 fileName:davesdoc.txt session:3 connId:{39D5F13D-B2D1484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 all update info about the file name modification has been received. Note in all the logs previous there is no RDCGET, no RAWGET, no staging, and no indications of the file actually being moved. This is because a rename operation only requires metadata to be sent over the wire in RPC. <Downstream> 20080626 16:00:17.529 980 MEET 1190 Meet::Install Retries:0 updateName:davesdoc.txt uid:{B0DAFB7F-1E6D- 401E-ADEC-2494F4A345A6}-v28 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 The ‘installation’ has succeeded (not that anything is actually being installed) <Downstream> 20080626 16:00:17.529 980 LDBX downstream + fid 0x2000000002FEE + usn 0xa3f40 + uidVisible 1 + filtered 0 3684 Ldb::Update Updating idRecord: the DFSR database is updated + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 note the GVSN has been updated + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080626 20:00:17.114 + createTime 20080626 19:58:04.143 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash CE2505D3-E4669977-250B31C1-100B67DE + similarity 2A242410-2E100D1A-191A340E-041A1018 + name davesdoc.txt + <Downstream> 20080626 16:00:17.529 980 MEET 2770 Meet::InstallMove -> DONE Install-move completed updateName:davesdoc.txt uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} at this point the file has been renamed in the replicated folder downstream <Downstream> 20080626 16:00:17.529 1472 INCO 3661 InConnection::ReceiveUpdates Session has been closed. sessionId:3 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 the actual ‘replication’ operation is complete. <Downstream> 20080626 16:00:17.529 980 INCO 4378 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 sessionId:3 open:0 updateType:0 processStatus:0 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91265D-42E8-9F57-1B49F4E581B7} csName:testrf2 update: + present 1 + nameConflict 0 + attributes 0x20 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v29 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v28 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080626 20:00:17.114 + createTime 20080626 19:58:04.143 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash CE2505D3-E4669977-250B31C1-100B67DE + similarity 2A242410-2E100D1A-191A340E-041A1018 + name davesdoc.txt + <Downstream> 20080626 16:00:17.529 1472 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91- Understanding DFSR debug logging (Part 10: File Conflicted between two Windows Server 2008) In this scenario we will see a file that has been changed on two servers in between replication convergence and how that conflict resolution is replicated between servers. This is useful to understand in order to troubleshoot issues (or perception of issues that are actually expected behavior) leading to conflicts. (conflictwinner - Dfsr00001 - 2008.log and conflictloser - Dfsr00001 - 2008.log) These are two Windows Server 2008 servers called 2008x86FSRV10 and 2008x86SRV11 in the contoso.com domain. The logs are from 2008x86FSRV10 (where the conflict is won) and from 2008x86SRV11 (where the conflict is lost). Both servers are participating in the TESTRG3 replication group for the TESTRF3 replicated folder. The file was called “confile.rtf”. <Upstream> 20080908 08:40:20.994 3104 USNC 2361 UsnConsumer::UpdateIdRecord LDB Updating ID Record: File modified and information being added to the DFSR database + fid 0x400000000BA14 File ID for cross-reference purposes with USN journal + usn 0x25f7898 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 15:31:45.162 GMT + present 1 + nameConflict 0 + attributes 0x20 file, not folder + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 version is higher than UID so we know this file has been modified at least once (but remember that versions are not sequential for a file, they are sequential for the file server.) + {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 GUID matches between versions, so uid the file was created and last modified on this server + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:40:20.979 GMT (0x1c911c933ac2f01) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name confile.rtf file name is ‘confile.rtf’ + <Upstream> 20080908 08:40:20.994 3104 USNC 2364 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: USN journal is updated at the same time to show a modification record (technically it happens before the DB update, this is a logging idiosyncrasy’) + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x400000000BA14 note that FID’s match between USN and LDB debug log entries. We know this is the same file. + ParentFileRefNumber: 0x2100000000A77C + USN: 0x25f7898 + TimeStamp: 20080908 08:40:20.979 Pacific Standard Time + Reason: Close Data Extend Data truncation reason code indicates the file has been modified (extend & truncate) + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 file, not folder + FileNameLength: 22 + FileNameOffset: 60 + FileName: confile.rtf same file name + <Upstream> 20080908 08:40:29.682 2824 SRTR 1927 SERVER_AsyncPoll Received from connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} server receives <Upstream> 20080908 08:40:42.339 2352 RSMG 1036 [WARN] ReplicaSetManager::EstablishConnection Shutting down existing connection. connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} rgName:ConRG <Upstream> 20080908 08:40:42.339 2352 OUTC 487 OutConnection::Shutdown Shutdown connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} rgName:ConRG <Upstream> 20080908 08:40:42.339 2352 SRTR 712 SERVER_EstablishConnection Succeeded on connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} replicaSetId:{1551E20B-36F1-4EE4-B6D0-3154E5C28E44} rgName:ConRG partnerAddress:2008x86FSRV11.contoso.com <Upstream> 20080908 08:40:42.339 2352 OUTC 2610 OutConnection::EstablishSession Replacing content set. csId:{009349B5- 8677-4352-AC4F-13BCC111BAA0} connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} rgName:ConRG <Upstream> 20080908 08:40:42.339 2352 SRTR 794 SERVER_EstablishSession Established connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} <Upstream> 20080908 08:40:42.339 2824 SRTR 1927 SERVER_AsyncPoll Received from connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} <Upstream> 20080908 08:40:42.339 2824 SRTR 1880 SERVER_RequestVersionVector Received from connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} seqNumber:1 changeType:notify <Upstream> 20080908 08:40:42.339 2824 SRTR 1880 SERVER_RequestVersionVector Received from connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} seqNumber:2 changeType:all <Upstream> 20080908 08:40:42.339 2824 SRTR 1927 SERVER_AsyncPoll Received from connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} <Downstream> 20080908 08:40:42.340 2212 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00D01BF8 <Downstream> 20080908 08:40:42.340 2212 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} reqType:VvUpRequest reqState:Completed status:0 ptr:00C80FE0 <Downstream> 20080908 08:40:42.340 2212 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf vvUp:{5CB120DE-D2C2-452A-8280-B45FC155224F} |> { 10..15} version vector exchange occurs and the (future) loser gets the chain from partner (local is 10, remote is 15) + <Downstream> 20080908 08:40:42.340 2212 INCO 3966 InConnection::ReceiveVvUp Creating new session:5 requestState:00C80FE0 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf vvDown:{0E1F09935130-4BB2-B409-FD13366B9A0C} |-> { 10} + {5CB120DE-D2C2-452A-8280-B45FC155224F} |-> { 10..14} previous chain was local 10, remote 14 + <Downstream> 20080908 08:40:42.340 2596 INCO 4619 InConnection::RequestUpdates Requesting updates. credits:32 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{5CB120DE-D2C2-452A-8280-B45FC155224F} |-> { 15} new high watermark version from remote will be 15, which matches the version on our file upstream + <Downstream> 20080908 08:40:42.340 2212 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00D01BF8 <Downstream> 20080908 08:40:42.340 2212 INCO 4803 InConnection::ReceiveUpdates Upstream credits:32 connId:{2A41E070-E3EF- 4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf creditsUsed:1 creditsAvailable:32 downstream server gets a credit out of his 32 credit pool with partner <Downstream> 20080908 08:40:42.340 2212 INCO 4868 InConnection::ReceiveUpdates Received: uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 fileName:confile.rtf session:5 connId:{2A41E070-E3EF4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf update information has been sent to the downstream server (now it knows about date/time as well, which will be used to break the tie and cause downstream to lose) <Downstream> 20080908 08:40:42.340 2596 MEET 1207 Meet::Install Retries:0 updateName:confile.rtf uid:{5CB120DE-D2C2-452A- 8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf updateType:remote downstream ready to pull file <Downstream> 20080908 08:40:42.340 2596 MEET 5674 Meet::LocalDominates Conflicting gvsn:{0E1F0993-5130-4BB2-B409- FD13366B9A0C}-v10 updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf a somewhat confusing message – the function ‘localdominates’ makes it sound like the downstream server has won, but this is just because the function is called localdominates (i.e. ‘checking IF local dominates’). If DebugLogSeverity=5 here there will additional trace logging that will show “Local version dominates localgvsn” or “"Remote version dominates localgvsn”). In this case, local has lost. <Downstream> 20080908 08:40:42.340 2212 INCO 4932 InConnection::ReceiveUpdates Session has been closed. sessionId:5 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf <Downstream> 20080908 08:40:42.340 2212 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} reqType:UpdateRequest reqState:Completed status:0 ptr:00C80EE8 <Downstream> 20080908 08:40:42.340 3244 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00C805E0 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf changeType:notify <Downstream> 20080908 08:40:42.340 2212 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} reqType:VvUpRequest reqState:Completed status:0 ptr:00C805E0 <Upstream> 20080908 08:40:42.355 2824 SRTR 882 SERVER_RequestUpdates Received from connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} credits:32 requestType:all <Upstream> 20080908 08:40:42.355 2824 SRTR 1927 SERVER_AsyncPoll Received from connId:{2A41E070-E3EF-4F15-8CA0- 4BC0F256D771} <Upstream> 20080908 08:40:42.355 2548 JOIN 1167 Join::SubmitUpdate Sent: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 name:confile.rtf connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf upstream is now serving the file <Upstream> 20080908 08:40:42.355 2824 SRTR 1880 SERVER_RequestVersionVector Received from connId:{2A41E070-E3EF-4F15- 8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} seqNumber:3 changeType:notify <Upstream> 20080908 08:40:42.355 2008 OUTC 784 OutConnection::OpenFile Received request for update: upstream gets an RPC request to serve the file to downstream partner + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:40:20.979 GMT (0x1c911c933ac2f01) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name confile.rtf + rdcDesired:1 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} rgName:ConRG <Upstream> 20080908 08:40:42.355 2008 OUTC 1534 OutConnection::OpenFile Sent file uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 name:confile.rtf fileSize:47783 connId:{2A41E070-E3EF4F15-8CA0-4BC0F256D771} rgName:ConRG file is being replicated. Note the lack of staging process below, this file is only 47KB. <Upstream> 20080908 08:40:42.355 2008 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080908 08:40:42.355 2008 OUTC <Upstream> 20080908 08:40:42.355 2008 CSMG 158 SaveHashReader::Close Saving hash of served file 4844 ContentSetManager::UpdateHash LDB Updating ID Record: DFSR database updated with hash information. + fid 0x400000000BA14 + usn 0x25f7898 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 15:40:20.994 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:40:20.979 GMT (0x1c911c933ac2f01) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00F1C53D-312C1265-D91F9B6A-19316BBA + similarity 00000000-00000000-00000000-00000000 + name confile.rtf + <Downstream> 20080908 08:40:42.356 2596 MRSH 3959 MarshalContext::Initialize Create file:[confile-{5CB120DE-D2C2-452A- 8280-B45FC155224F}-v15.rtf] with attributes:0x20 downstream server is replicating file from partner. The file will bypass local staging due to size and go straight into the Installing directory. <Downstream> 20080908 08:40:42.356 2596 INCO 5610 InConnection::LogTransferActivity Received RAWGET uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 fileName:confile.rtf connId:{2A41E070-E3EF4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} stagedSize:21030 the file has been copied in RAW (i.e. non-RDC) form to the downstream server <Downstream> 20080908 08:40:42.356 2596 MEET 2032 Meet::Download Download Succeeded : true updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F158CA0-4BC0F256D771} csName:conrf csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} copying the file over was successfull <Downstream> 20080908 08:40:42.356 2596 MEET 5674 Meet::LocalDominates Conflicting gvsn:{0E1F0993-5130-4BB2-B409- FD13366B9A0C}-v10 updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf another mention of the conflict being lost on local downstream partner <Downstream> 20080908 08:40:42.356 2596 MEET 2772 Meet::InstallRename Move out previous version of same file updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf The previously existing copy of the file in the replicated folder now needs to be moved into the COnflictANdDeleted folder. <Downstream> 20080908 08:40:42.356 2596 MEET 4867 Meet::MoveOut Moving contents and children out of replica. newName:confile-{0E1F0993-5130-4BB2-B409-FD13366B9A0C}-v10.rtf updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf record: the previous file is now moved into the ConflictAndDeleted folder under dfsrprivate in the replicated folder. The ConflictAndDeletedManifest.XML is updated to reflect this. + fid 0x2100000000A77C + usn 0x25f2990 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 15:38:52.571 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {0E1F0993-5130-4BB2-B409-FD13366B9A0C}-v10 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:38:52.555 GMT (0x1c911c8fef7cd5c) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name confile.rtf + <Downstream> 20080908 08:40:42.356 2596 EVNT 725 EventLog::Report Logging eventId:4412 parameterCount:9 <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter1:009349B5-8677-4352- <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter2:C:\conrf\confile.rtf <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter3:c:\conrf <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter4:{5CB120DE-D2C2-452A- AC4F-13BCC111BAA0 8280-B45FC155224F}-v11 <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter5:conrf <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter6:ConRG <Downstream> 20080908 08:40:42.356 2596 EVNT 745 EventLog::Report eventId:4412 parameter7:1551E20B-36F1-4EE4- 745 EventLog::Report eventId:4412 parameter8:D31217D6-0F05-437A- 745 EventLog::Report eventId:4412 parameter9:confile-{0E1F0993- B6D0-3154E5C28E44 <Downstream> 20080908 08:40:42.356 2596 EVNT 8FDF-84949FD7D2D6 <Downstream> 20080908 08:40:42.356 2596 EVNT 5130-4BB2-B409-FD13366B9A0C}-v10.rtf the following strings are built and written into the 4412 DFSR ‘conflict’ event in the event log. <Downstream> 20080908 08:40:42.356 2596 MEET 2837 Meet::InstallRename File moved. rootVolume:{3C84BB07-22D1-11DD-862B- 806E6F6E6963} parentFid:0x600000000A5B6 fidInInstalling:0x300000000B9FD usn:0x2618560 updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F158CA0-4BC0F256D771} csName:conrf move to C&D folder is complete. <Downstream> 20080908 08:40:42.356 2596 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: The DFSR database must be updated to reflect the new file information on the downstream loser. + fid 0x300000000B9FD + usn 0x2618560 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 marks that the update was caused by inbound replication. + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 the GVSN and UID are now matched to the upstream server + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:40:20.979 GMT (0x1c911c933ac2f01) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00F1C53D-312C1265-D91F9B6A-19316BBA the hash now matches the upstream version + similarity 00000000-00000000-00000000-00000000 + name confile.rtf + <Downstream> 20080908 08:40:42.356 2596 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:confile.rtf uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csName:conrf csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} the newer version of the file has now been moved into the replicated folder downstream <Downstream> 20080908 08:40:42.356 2596 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 failures:0 sessionId:5 open:0 updateType:0 processStatus:0 connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf update: processing of the update is complete. + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v11 + parent {009349B5-8677-4352-AC4F-13BCC111BAA0}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 15:40:20.979 GMT (0x1c911c933ac2f01) + createTime 20080908 15:31:45.131 GMT + csId {009349B5-8677-4352-AC4F-13BCC111BAA0} + hash 00F1C53D-312C1265-D91F9B6A-19316BBA + similarity 00000000-00000000-00000000-00000000 + name confile.rtf + <Upstream> 20080908 08:40:42.370 2008 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{2A41E070-E3EF-4F15-8CA0-4BC0F256D771} rdc:1 context:00000000,00000000,00000000 uid:{5CB120DE-D2C2-452A-8280B45FC155224F}-v11 gvsn{5CB120DE-D2C2-452A-8280-B45FC155224F}-v15 ptr:00981B38 <Downstream> 20080908 08:40:42.387 2596 INCO 6194 InConnection::CommitSession Connection in sync connId:{2A41E070-E3EF- 4F15-8CA0-4BC0F256D771} csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} csName:conrf commitedSessionsWithUpdateFailures:0 <Downstream> 20080908 08:40:42.387 2596 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{2A41E070-E3EF- 4F15-8CA0-4BC0F256D771} csName:conrf csId:{009349B5-8677-4352-AC4F-13BCC111BAA0} Understanding DFSR debug logging (Part 11: Directory created on Windows Server 2003 R2) In this scenario we will see a folder added and how that change is replicated between servers. This is useful to understand in order to troubleshoot issues where problems within the USN journal, the DFSR JET database, and the network (including RPC) are preventing replication from working correctly. (addedfolderupstream - Dfsr00006 - 2003.log and addedfolderdownstream - Dfsr00007 - 2003.log) These are two Windows Server 2003 servers called 2003MEM01 and 2003MEM02 in the contoso.com domain. The logs are from 2003MEM01 where the folder is created (upstream) and from 2003MEM02 where it the creation is replicated (downstream). Both servers are participating in the TESTRG2 replication group for the TESTRF2 replicated folder. The folder was called “subfolder”. <Upstream> 20080627 10:34:47.983 692 LDBX 3567 Ldb::Insert Inserting idRecord: the DFSR database is being updated upstream fid 0x1000000002FF8 note the file ID. This useful for cross referencing with USN updates in the + usn 0xb6370 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + log + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 marks the object as a folder, not a file + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 UID and GVSN match, this shows the change as an original creation on the upstream server + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080627 14:34:47.983 + createTime 20080627 14:34:47.983 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name subfolder the folder is named ‘subfolder’ + <Upstream> 20080627 10:34:48.043 692 USNC 2448 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: the USN journal has been updated. Note that this actually occurred before the database being updated, it is just a log idiosyncrasy that the debug log entry occurs later. + USN_RECORD: + RecordLength: 80 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x1000000002ff8 note that File ID is the same as above + ParentFileRefNumber: 0x1000000002f92 + USN: 0xb6370 + TimeStamp: 20080627 10:34:47.983 Eastern Standard Time + Reason: Close Rename New Name the folder object is newly created. + SourceInfo: 0x0 + SecurityId: 0x1af + FileAttributes: 0x10 it’s a folder, not a file + FileNameLength: 18 + FileNameOffset: 60 + FileName: subfolder named ‘subfolder’ + <Upstream> 20080627 10:34:48.043 692 LDBX 4083 Ldb::InsertWalkerJob Inserting dirWalkerJob:uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v30 moveType:MoveIn (1) at time:20080627 14:34:47.983 a DirWalker job is created. Dirwalker checks that when a folder is created, what sub folders/files it contains. <Upstream> 20080627 10:34:48.063 692 LDBX <Upstream> 20080627 10:34:48.063 692 DIRW 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00ADF8C0 511 DirWalkerTask::QueueMoveinJob Queuing move-in. uid:{B0DAFB7F-1E6D-401E- ADEC-2494F4A345A6}-v30 fid:0x1000000002FF8 name:subfolder the dirwalker job is queued for running <Upstream> 20080627 10:34:48.063 172 DIRW 256 DirWalkerTask::Run Start walking directory. the dirwalker job runs <Upstream> 20080627 10:34:48.063 172 DIRW 937 DirWalkerTask::MoveinStep Starting to process move-in job. uid:{B0DAFB7F- 1E6D-401E-ADEC-2494F4A345A6}-v30 the results of the dirwalker job are evaluated. <Upstream> 20080627 10:34:48.063 172 DIRW 101 DirWalkerTask::Job::Finish MoveIn csId:{5666BB91-265D-42E8-9F57- 1B49F4E581B7} uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 the dirwalker job is complete. This was very fast here as there were no sub-files or folders. <Upstream> 20080627 10:34:48.063 172 DIRW 786 DirWalkerTask::RemoveJob Removing job type:1 uid:{B0DAFB7F-1E6D-401E- ADEC-2494F4A345A6}-v30 the Dirwalker job is ready to be removed. <Upstream> 20080627 10:34:48.063 172 LDBX 4119 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v30 the dirwalker job is removed <Upstream> 20080627 10:34:48.063 172 DIRW 303 DirWalkerTask::Run Exit. <Upstream> 20080627 10:34:48.083 1176 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:4 changeType:all <Upstream> 20080627 10:34:48.083 1176 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Upstream> 20080627 10:34:48.093 1176 SRTR 498 SERVER_RequestUpdates Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} credits:32 requestType:all <Upstream> 20080627 10:34:48.093 1176 SRTR 1304 SERVER_AsyncPoll Received from connId:{39D5F13D-B2D1-484D-B57E- E369C8F8C6DD} <Downstream> 20080627 10:34:48.098 1788 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86E70 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:all the downstream server requests version vector info from the upstream partner <Downstream> 20080627 10:34:48.098 1720 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Upstream> 20080627 10:34:48.103 172 LDBX 3684 Ldb::Update Updating idRecord: DFSR database updated to reflect that the folder is available for replication now, with a visible UID (this is slightly different than files, since folders can contain other objects) + fid 0x1000000002FF8 + usn 0xb6370 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 20080627 14:34:47.983 GMT + present 1 + nameConflict 0 + attributes 0x10 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080627 14:34:47.983 + createTime 20080627 14:34:35.555 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name subfolder + <Upstream> 20080627 10:34:48.103 172 JOIN 1171 Join::SubmitUpdate Sent: uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 name:subfolder connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 the upstream server sends downstream the update information metadata. Since this is a folder an actual ‘folder’ is not sent, just security, name, and parent info. <Upstream> 20080627 10:34:48.103 1176 SRTR 1257 SERVER_RequestVersionVector Received from connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} seqNumber:5 changeType:notify <Upstream> 20080627 10:34:48.103 1620 OUTC 588 OutConnection::OpenFile Received request for update: the upstream server is requested to serve the folder to the downstream + present 1 + nameConflict 0 + attributes 0x10 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080627 14:34:47.983 + createTime 20080627 14:34:35.555 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name subfolder + rdcDesired:1 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} rgName:TestRG2 <Upstream> 20080627 10:34:48.103 1620 OUTC 1056 OutConnection::OpenFile Sent file uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 name:subfolder fileSize:360 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} rgName:TestRG2 the folder is being sent <Upstream> 20080627 10:34:48.103 1620 MRSH 3487 Marshaller::Marshal FileAttrs in metadata : 0x10 the folder data was marshaled for RPC <Downstream> 20080627 10:34:48.108 1720 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86E70 <Downstream> 20080627 10:34:48.108 1720 INCO 2947 InConnection::ReceiveVvUp Received VvUp connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 vvUp:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 10..30} + <Downstream> 20080627 10:34:48.108 1720 INCO 2954 InConnection::ReceiveVvUp Creating new session:2 requestState:00A86E70 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 downstream server has received the version vector info <Downstream> 20080627 10:34:48.108 1788 INCO 3347 InConnection::RequestUpdates Requesting updates. credits:32 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 requestType:all cursor:{00000000-0000-0000-0000-000000000000}-v0 delta::{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6} |-> { 30} the version is 30 + <Downstream> 20080627 10:34:48.108 1720 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:00A8F4A0 <Downstream> 20080627 10:34:48.128 1720 INCO 3534 InConnection::ReceiveUpdates Upstream credits:32 connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080627 10:34:48.128 1720 INCO 3597 InConnection::ReceiveUpdates Received: uid:{B0DAFB7F-1E6D-401E-ADEC- 2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 fileName:subfolder session:2 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 the downstream server receives the marshaled folder metadata information <Downstream> 20080627 10:34:48.128 1788 MEET 1190 Meet::Install Retries:0 updateName:subfolder uid:{B0DAFB7F-1E6D-401E- ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 the new folder is ready to be created in the downstream replicated folder. Note the lack of staging, installing process. There is no RDC or compression used in folder object replication. <Downstream> 20080627 10:34:48.128 1720 INCO 3661 InConnection::ReceiveUpdates Session has been closed. sessionId:2 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 <Downstream> 20080627 10:34:48.128 2008 INCO 2761 InConnection::RequestVvUp Requested upstream version vector. requestState:00A86E70 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} csName:testrf2 changeType:notify <Downstream> 20080627 10:34:48.128 1720 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:UpdateRequest reqState:Completed status:0 ptr:00A86340 <Downstream> 20080627 10:34:48.128 1788 MRSH 2957 MarshalContext::Initialize Create file:[subfolder-{B0DAFB7F-1E6D-401E- ADEC-2494F4A345A6}-v30] with attributes:0x10 the folder is created in the downstream server replicated folder <Downstream> 20080627 10:34:48.128 1788 INCO 4112 InConnection::LogTransferActivity Received RAWGET uid:{B0DAFB7F-1E6D- 401E-ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 fileName:subfolder connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} stagedSize:356 the process of replication is logged as a RAWGET (i.e. no RDC). While there is info on ‘stagedsize’ it is not actually staged, this is a logging idiosyncrasy. <Downstream> 20080627 10:34:48.128 1788 MEET 1898 Meet::Download Download Succeeded : true updateName:subfolder uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 connId:{39D5F13D-B2D1-484DB57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} the replication process has completed and the folder has been successfully ‘downloaded’. <Downstream> 20080627 10:34:48.128 1788 MEET 2190 Meet::InstallRename File moved. rootVolume:{05853FA6-411C-11DD-A156- 806E6F6E6963} parentFid:0x1000000002F8C fidInInstalling:0x1000000002FF3 usn:0xbbe88 updateName:subfolder uid:{B0DAFB7F1E6D-401E-ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 connId:{39D5F13D-B2D1-484D-B57EE369C8F8C6DD} csName:testrf2 the subfolder now fully exists in the replicated folder. <Downstream> 20080627 10:34:48.128 1788 LDBX 3567 Ldb::Insert Inserting idRecord: the DFSR database is updated on the downstream server to track the new subfolder + fid 0x1000000002FF3 + usn 0xbbe88 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080627 14:34:47.983 + createTime 20080627 14:34:35.555 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash BD3BC9A8-67A8EA8B-B5D77ACF-4DBD26A0 + similarity 00000000-00000000-00000000-00000000 + name subfolder + <Downstream> 20080627 10:34:48.128 1720 DOWN 2668 AsyncRpcHandler::ProcessReceive Completion. connId:{39D5F13D-B2D1-484D- B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} reqType:VvUpRequest reqState:Completed status:0 ptr:00A86E70 <Downstream> 20080627 10:34:48.158 1788 MEET 2233 Meet::InstallRename -> DONE Install-rename completed updateName:subfolder uid:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 gvsn:{B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csName:testrf2 csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} the installation process has been completed. <Downstream> 20080627 10:34:48.158 1788 INCO 4378 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 sessionId:2 open:0 updateType:0 processStatus:0 connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91265D-42E8-9F57-1B49F4E581B7} csName:testrf2 update: + present 1 + nameConflict 0 + attributes 0x10 + gvsn {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + uid {B0DAFB7F-1E6D-401E-ADEC-2494F4A345A6}-v30 + parent {5666BB91-265D-42E8-9F57-1B49F4E581B7}-v1 + fence 16010101 00:00:00.000 + clock 20080627 14:34:47.983 + createTime 20080627 14:34:35.555 GMT + csId {5666BB91-265D-42E8-9F57-1B49F4E581B7} + hash BD3BC9A8-67A8EA8B-B5D77ACF-4DBD26A0 + similarity 00000000-00000000-00000000-00000000 + name subfolder + <Downstream> 20080627 10:34:48.168 1788 LDBX 1228 LdbManager::UpdateVersionVectorCache Wake up callback 00AD6080 <Downstream> 20080627 10:34:48.168 1788 INCO 4617 InConnection::CommitSession Connection in sync connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} <Downstream> 20080627 10:34:48.168 1788 UPMG 413 UpdateWorker::ConsumeUpdates No pending updates. connId:{39D5F13D-B2D1- 484D-B57E-E369C8F8C6DD} csName:testrf2 <Downstream> 20080627 10:34:48.168 2008 INCO 2787 InConnection::ContentSetContext::Hibernate Hibernating: connId:{39D5F13D-B2D1-484D-B57E-E369C8F8C6DD} csId:{5666BB91-265D-42E8-9F57-1B49F4E581B7} Understanding DFSR debug logging (Part 12: Domain Controller Bind and Config Polling on Windows Server 2008) In this log we will see the DFSR service being started and follow the process of initialization up to the point where the service is fully functional. This is useful to understand in order to troubleshoot issues where problems within Active Directory, Network Communication, XML reading, or Registry reading are preventing the DFSR service from starting or initializing for replication. (svcstartandpolling - Dfsr00009 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The log is from 2008MEM01 where the DFSR service was started. It’s is participating in the TESTRG replication group for the TESTRF replicated folder and its only partner is 2008MEM02. <Upstream> 20080624 14:41:09.203 852 CREG 733 Config::RegConfig::ReadConfigFilePath Location of valueName:Replica Set Configuration File is location:\\.\C:\SYSTEM VOLUME INFORMATION\DFSR\Config\Replica_7C81CA1E-F956-4A9E-BCE5E3A2D1ACDD1D.XML find the path to XML from registry <Upstream> 20080624 14:41:09.203 852 FCFG 131 Configuration::ReadVolumeConfig Reading all volume configuration files. <Upstream> 20080624 14:41:09.203 852 CREG 733 Config::RegConfig::ReadConfigFilePath Location of valueName:Volume Configuration File is location:\\.\C:\System Volume Information\DFSR\Config\Volume_6A7E9F21-4169-11DD-AF51806E6F6E6963.XML find path to XML from registry <Upstream> 20080624 14:41:09.203 852 CXML 2748 Config::XmlReader::PostProcessVolumeConfig Found volume. path:\\.\C: volumeId:{6A7E9F21-4169-11DD-AF51-806E6F6E6963} <Upstream> 20080624 14:41:09.203 852 CXML 2757 Config::XmlReader::PostProcessVolumeConfig Overwriting dbPath. oldPath:\\.\C:\System Volume Information\DFSR newPath:\\.\C:\System Volume Information\DFSR location of the DFSR database is forced into XML <Upstream> 20080624 14:41:19.208 852 CFAD 317 Config::AdConnection::Connect Binding to dcAddr:\\10.60.0.1 852 CFAD 149 Config::AdConnection::BindToAd Trying to connect. 852 CFAD 168 Config::AdConnection::BindToAd Bound. hostName:2008DC01.fabrikam.com dcDnsName:\\2008DC01.fabrikam.com <Upstream> 20080624 14:41:19.208 hostName:2008DC01.fabrikam.com <Upstream> 20080624 14:41:19.238 <Upstream> 20080624 14:41:19.238 852 CFAD 205 Config::AdConnection::BindToDc Try to bind. hostName:\\2008DC01.fabrikam.com domainName:<null> <Upstream> 20080624 14:41:19.318 852 CFAD 215 Config::AdConnection::BindToDc Bound. hostName:\\2008DC01.fabrikam.com domainName:<null> five lines above cover the bind to DC we will use until DFSR service is restarted (it does not matter if DC goes offline; we will then use the XML files that were read in above instead) <Upstream> 20080624 14:41:19.318 852 CFAD 7530 Config::AdConfig::ReadRootNamingContexts Default Naming Context 852 CFAD 7531 Config::AdConfig::ReadRootNamingContexts Schema Naming Context DN:DC=fabrikam,DC=com <Upstream> 20080624 14:41:19.318 DN:cn=sites,cn=configuration,dc=fabrikam,dc=com <Upstream> 20080624 14:41:19.318 852 CFAD 7533 Config::AdConfig::ReadRootNamingContexts Services DN:cn=services,cn=configuration,dc=fabrikam,dc=com <Upstream> 20080624 14:41:19.318 852 CFAD 7534 Config::AdConfig::ReadRootNamingContexts Domain Controllers DN:ou=domain 852 CFAD 7535 Config::AdConfig::ReadRootNamingContexts Computers controllers,DC=fabrikam,DC=com <Upstream> 20080624 14:41:19.318 DN:cn=computers,DC=fabrikam,DC=com <Upstream> 20080624 14:41:19.318 852 CFAD 7536 Config::AdConfig::ReadRootNamingContexts System 852 CFAD 7537 Config::AdConfig::ReadRootNamingContexts Sites DN:cn=system,DC=fabrikam,DC=com <Upstream> 20080624 14:41:19.318 DN:cn=sites,cn=configuration,dc=fabrikam,dc=com We find the above seven naming contexts, as they may all include DFSRrelated information (including SYSVOL information or DFSN usage). <Upstream> 20080624 14:41:19.328 852 CFAD 7697 Config::AdConfig::CheckSchemaVersion DMD object:CN=Schema,CN=Configuration,DC=fabrikam,DC=com, objectVersion:44 Schema version is checked so that service knows if DFSR is supported by the forest <Upstream> 20080624 14:41:19.368 852 CREG 1207 Config::RegReader::IsSysVolCommitFlagSet key: System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Demoting SysVols valueName:'SysVol Information is Committed' result:0 <Upstream> 20080624 14:41:19.378 852 EVNT 725 EventLog::Report Logging eventId:1206 parameterCount:1 <Upstream> 20080624 14:41:19.378 852 EVNT 745 EventLog::Report eventId:1206 parameter1:\\2008DC01.fabrikam.com event log is updated with 1206 to reflect which DC was bound <Upstream> 20080624 14:41:19.398 852 ADWR 1038 Config::AdWriter::CreateSysVolObjects [SYSVOL] IsDc:0 isSysVolCreated:0 <Upstream> 20080624 14:41:19.398 852 ADWR 1041 Config::AdWriter::CreateSysVolObjects [SYSVOL] Not a DC determine that this server is not a DC and SYSVOL operations will not be possible <Upstream> 20080624 14:41:19.448 852 CFAD 7348 Config::AdConfig::TranslateDn Cracked Domain:fabrikam.com <Upstream> 20080624 14:41:19.448 852 CFAD 7349 Config::AdConfig::TranslateDn Cracked Name :FABRIKAM\2008MEM02$ get NetBIOS SAM name of DFSR partner server given the above domain <Upstream> 20080624 14:41:19.448 852 CFAD 7348 Config::AdConfig::TranslateDn Cracked Domain:fabrikam.com <Upstream> 20080624 14:41:19.448 852 CFAD 7349 Config::AdConfig::TranslateDn Cracked Name :S-1-5-21-2013982821- 2378084203-3048728933-1104 <-get domain SID of DFSR partner server given the above domain <Upstream> 20080624 14:41:19.458 852 CCTX 1251 VolumeIdTable::Rebuild Processing volume:\\?\Volume{6a7e9f21-4169-11dd- af51-806e6f6e6963}\ path:\\.\C: serialNumber:5236588249460846150 find volumes and their serial numbers <Upstream> 20080624 14:41:19.478 852 CCTX 1099 VolumeIdTable::ReadVolumeInfo Ignoring volume:\\?\Volume{6a7e9f24-4169- 11dd-af51-806e6f6e6963}\ (remote, cd-rom or removable) <Upstream> 20080624 14:41:19.478 852 CCTX 1099 VolumeIdTable::ReadVolumeInfo Ignoring volume:\\?\Volume{6a7e9f25-4169- 11dd-af51-806e6f6e6963}\ (remote, cd-rom or removable) <Upstream> 20080624 14:41:19.578 852 CFAD 8625 Config::AdConfig::UpdateSpn Binding to dcAddr:\\10.60.0.1 852 CFAD 8653 Config::AdConfig::UpdateSpn spnList:Dfsr-12F9A27C-BF97-4787-9364- dcDnsName:\\2008DC01.fabrikam.com <Upstream> 20080624 14:41:19.578 D31B6C55EB04/2008mem01.fabrikam.com <Upstream> 20080624 14:41:19.578 852 CFAD 8659 Config::AdConfig::UpdateSpn SPN already registered. spn:Dfsr-12F9A27C- BF97-4787-9364-D31B6C55EB04/2008mem01.fabrikam.com Register the Service Principal Name for the service unless already present <Upstream> 20080624 14:41:19.578 852 CFAD 8653 Config::AdConfig::UpdateSpn spnList:HOST/2008MEM01 <Upstream> 20080624 14:41:19.578 852 CFAD 8653 Config::AdConfig::UpdateSpn spnList:HOST/2008mem01.fabrikam.com get 852 CXML 3225 Config::XmlWriter::CreateSVIDirectory Created System Volume Information the HOST SPN’s for this server <Upstream> 20080624 14:41:19.578 folder under path:\\.\C:\SYSTEM VOLUME INFORMATION\DFSR <Upstream> 20080624 14:41:19.578 852 CXML 3279 Config::XmlWriter::CreateDirectoryW Directory already exists, path:\\.\C:\SYSTEM VOLUME INFORMATION\DFSR <Upstream> 20080624 14:41:19.578 852 CXML 3279 Config::XmlWriter::CreateDirectoryW Directory already exists, path:\\.\C:\SYSTEM VOLUME INFORMATION\DFSR\Config Create the hidden operating system System Volume Information folder structure if it does not already exist <Upstream> 20080624 14:41:19.578 852 CXML 1837 Config::XmlConfig::CreateDocument Create root node: 852 CXML 3922 Config::XmlWriter::WriteReplicaSetConfigFile Reading old replica config DfsrReplicationGroupConfig <Upstream> 20080624 14:41:19.578 file at path:\\.\C:\SYSTEM VOLUME INFORMATION\DFSR\Config\Replica_7C81CA1E-F956-4A9E-BCE5-E3A2D1ACDD1D.XML recreate the replica XML file <Upstream> 20080624 14:41:19.588 852 CXML 3540 Config::XmlWriter::WriteVolumeConfigFile Write volume configure file:\\.\C:\System Volume Information\DFSR\Config\Volume_6A7E9F21-4169-11DD-AF51-806E6F6E6963.XML recreate the volume XML file <Upstream> 20080624 14:41:19.588 852 CXML 1837 Config::XmlConfig::CreateDocument Create root node: DfsrVolumeConfig <Upstream> 20080624 14:41:19.598 852 SYSM 3868 Migration::SysVolMigration::Connect [MIG] Trying to connect to Local or any writable Dc AD <Upstream> 20080624 14:41:19.598 852 CFAD 317 Config::AdConnection::Connect Binding to dcAddr:\\10.60.0.1 852 CFAD 149 Config::AdConnection::BindToAd Trying to connect. <Upstream> 20080624 14:41:19.598 852 CFAD 168 Config::AdConnection::BindToAd Bound. hostName:2008DC01.fabrikam.com <Upstream> 20080624 14:41:19.598 852 CFAD 205 Config::AdConnection::BindToDc Try to bind. dcDnsName:\\2008DC01.fabrikam.com <Upstream> 20080624 14:41:19.598 hostName:2008DC01.fabrikam.com hostName:\\2008DC01.fabrikam.com domainName:<null> <Upstream> 20080624 14:41:19.608 852 CFAD 215 Config::AdConnection::BindToDc Bound. hostName:\\2008DC01.fabrikam.com domainName:<null> <Upstream> 20080624 14:41:19.608 852 CFAD 7697 Config::AdConfig::CheckSchemaVersion DMD object:CN=Schema,CN=Configuration,DC=fabrikam,DC=com, objectVersion:44 <Upstream> 20080624 14:41:19.778 852 CREG 1207 Config::RegReader::IsSysVolCommitFlagSet key: System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Seeding SysVols valueName:'SysVol Information is Committed' result:0 seven previous lines cover a special out-of-band AD connection to see what DFSR SYSVOL migration state is in. <Upstream> 20080624 14:41:19.778 852 SCFG 956 ServiceConfig::ProcessAdPollConfigEvents Received AD Poll event with 1 852 SCFG 959 ServiceConfig::ProcessAdPollConfigEvents Received AD Poll event with 1 Volume configuration changes <Upstream> 20080624 14:41:19.778 Replication Group configuration changes Information has been retrieved from AD via LDAP lookups. This will always be numbered by the actual count of volumes and RG’s, not the number of changes found. <Upstream> 20080624 14:41:19.788 852 RSMG 142 ReplicaSetManager::Initialize Initialize replication group rgName:TestRG 852 RSMG 908 ReplicaSetManager::AddInConnection Creating new inbound connection found one RG called TestRG <Upstream> 20080624 14:41:19.788 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} rgName:TestRG found the one inbound connection reflected by this RG and its GUID <Upstream> 20080624 14:41:19.788 852 RSMG 1273 ReplicaSetManager::AddOrUpdateConnection New or updated outbound connection object. connId:{F5A520C4-154C-460E-B8EF-0867D4F92AAE} rgName:TestRG <Upstream> 20080624 14:41:19.788 852 CCTX 2391 ConfigContext::ApplyDiff Adding new volume to ConfigContext. volumePath:\\.\C: <Upstream> 20080624 14:41:19.788 852 FREP 400 FrsReplicator::UpdateVolume Create Volume:6A7E9F21-4169-11DD-AF51- 806E6F6E6963 <Upstream> 20080624 14:41:19.788 852 CCTX 3237 ConfigContext::DumpReplicaConfig Dumping Replica global config context <Upstream> 20080624 14:41:19.788 852 CPAR 2476 Config::ParamBlock::Print [[ DfsrReplicationGroup ]] now we begin reading the RG global configuration information from cn=TestRG,cn=dfsr-globalsettings,cn=system,dc=fabrikam,dc=com. It is critical to understand that these reads in the log are from the configuration XML files, where the LDAP query results are cached. When troubleshooting both the LDAP queries and the local XML reads must be examined. <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print LastChangeNumber: 12 [Flags:0x1] 1244 Config::DateTimeParam::Print LastChangeTime: 6/24/2008 18:41:19 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print LastChangeSource: 2008DC01.fabrikam.com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print Description: <null> [Flags:0x0] 1050 Config::GuidParam::Print ReplicationGroupGuid: 7C81CA1E-F956-4A9E-BCE5- E3A2D1ACDD1D [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print ReplicationGroupName: TestRG [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print ReplicationGroupDn: CN=TestRG,CN=DFSR- GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print ReplicationGroupType: 0 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print TombstoneExpiryInMin: 86400 [Flags:0x0] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print DefaultScheduleInUtc: FALSE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Sunday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF Tnis represents the schedule in HEX. A hex value (0-F) represents the bandwidth usage for each 15 minute interval in an hour. F=Full, E=256Mbps, D=128Mbps, C=64Mbps, B=32Mbps, A=16Mbps, 9=8Mbps, 8=4Mbps, 7=2Mbps, 6=1Mbps, 5=512Kbps, 4=256Kbps, 3=128Kbps,2=64Kbps, 1=16Kbps, 0=No replication. Note that these are bits per second, not bytes. <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Monday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Tuesday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Wednesday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Thursday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Friday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print DefaultSchedule.Saturday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF The above highlighted XML cached LDAP attribute reads are about the RG configuration, including distinguishedName, description, objectGUID, msDFSR-ReplicationGroupType, msDFSR-TombstoneExpiryInMin, msDFSR-Schedule, and name. Also covers the AD replication metadata information of which DC originated latest change, the originating time, and number of times the RG has been changed. <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print ReplicatedFolderGuid: 175F2B6A-289F-4CA8-AF8B- 852 CPAR 2476 Config::ParamBlock::Print 4D9BF1A2C501 [Flags:0x1] <Upstream> 20080624 14:41:19.788 [[ DfsrMember ]] now we begin reading the member global configuration information cached in XML from cn=<GUID of msDFSR-member>,cn=Topology,cn=TestRG,cn=dfsrglobalsettings,cn=system,dc=fabrikam,dc=com. These are backlink follows. <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print MemberGuid: E1023470-7BF7-403D-B9A6-CBDA8F877F71 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print MemberName: 2008MEM01 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print MemberDn: CN=412d1a14-d5ec-4a0f-ab78- fa17dd0a7537,CN=Topology,CN=TestRG,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print MemberDns: 2008mem01.fabrikam.com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print MemberPeerNetGroupName: <null> [Flags:0x0] <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print Keywords: <null> [Flags:0x0] 2476 Config::ParamBlock::Print [[ DfsrConnection ]] now we begin reading the member global configuration information cached in XML from cn=<GUID of msdfsr-Connection>,cn=<GUID of msDFSR- member>,cn=Topology,cn=TestRG,cn=dfsr-globalsettings,cn=system,dc=fabrikam,dc=com. We will do this twice – once for each connection object between servers. In this case there are two total, as well will see below. <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print ConnectionGuid: DEDD774B-4094-40BF-987A- B38CAFCC86E0 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print ConnectionDn: CN=4b4813da-e705-4f40-b148- e3eab2d55bd8,CN=412d1a14-d5ec-4a0f-ab78-fa17dd0a7537,CN=Topology,CN=TestRG,CN=DFSRGlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print PartnerGuid: EDAE85D2-373F-4526-9153- <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print PartnerName: 2008MEM02 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print PartnerDn: CN=5c8cce4c-c344-4b8f-a5c6- 7535C722C6FE [Flags:0x1] cd040bd625cf,CN=Topology,CN=TestRG,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print PartnerDns: 2008mem02.fabrikam.com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print PartnerPrincName: FABRIKAM\2008MEM02$ 852 CPAR 556 Config::StringParam::Print PartnerSid: S-1-5-21-2013982821-2378084203- <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print Enabled: TRUE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print Inbound: TRUE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print Keywords: <null> [Flags:0x0] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print RdcEnabled: TRUE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print RdcMinFileSizeInKb: 64 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR [Flags:0x1] <Upstream> 20080624 14:41:19.788 3048728933-1104 [Flags:0x1] 390 Config::BoolParam::Print ScheduleInUtc: FALSE [Flags:0x1] 1933 Config::ScheduleParam::Print Schedule.Sunday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Monday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Tuesday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Wednesday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Thursday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Friday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF <Upstream> 20080624 14:41:19.788 852 CPAR 1933 Config::ScheduleParam::Print Schedule.Saturday: FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF,FFFF The above XML-cached LDAP attribute reads return connection-specific configuration information, including objectGUID, DN, msDFSR-ComputerReference, fromServer, msDFSR-Enabled, msDFSR-RdcEnabled, msDFSR-RdcMinFileSizeInKb, msDFSRComputerReference, msDFSR-MemberReferenceBL, and msDFSR-Schedule. We also return Netbios SAM names, DNS names, and SID’s from the crack name operations. <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print ReplicatedFolderGuid: 175F2B6A-289F-4CA8-AF8B- 852 CPAR 2476 Config::ParamBlock::Print 4D9BF1A2C501 [Flags:0x1] <Upstream> 20080624 14:41:19.788 [[ DfsrConnection ]] we will repeat the above operation, but now for the other connection object. (Snipped out for readability). <Upstream> 20080624 14:41:19.788 852 CCTX 3250 ConfigContext::DumpVolumeConfig Dumping Volume global config context <Upstream> 20080624 14:41:19.788 852 CPAR 2476 Config::ParamBlock::Print [[ DfsrVolume ]] now we begin reading the volume configuration machine. This I not stored anywhere in LDAP and is enumerated at DFSR service startup <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print VolumeGuid: 6A7E9F21-4169-11DD-AF51-806E6F6E6963 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 911 Config::PathParam::Print VolumePath: \\.\C: [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 298 Config::QWordParam::Print SerialNumber: 2887331398 [Flags:0x1] volume serial number (internal to DFSR, will not match data in DISKPART) <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print LastChangeNumber: 12 [Flags:0x1] 1244 Config::DateTimeParam::Print LastChangeTime: 6/24/2008 18:41:19 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print LastChangeSource: 2008DC01.fabrikam.com 852 CPAR 911 Config::PathParam::Print DatabasePath: \\.\C:\System Volume 852 CPAR 204 Config::DWordParam::Print MinNtfsJournalSizeInMb: 512 [Flags:0x1] USN [Flags:0x1] <Upstream> 20080624 14:41:19.788 Information\DFSR [Flags:0x1] <Upstream> 20080624 14:41:19.788 Journal size, can be read with FSUTIL.EXE <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print UsnCheckPoint: 10 [Flags:0x0] 204 Config::DWordParam::Print MaxJetSessions: 64 [Flags:0x0] 2476 Config::ParamBlock::Print [[ DfsrReplicatedFolder ]] now we begin reading the XML-cached LDAP RF global configuration information from cn=TestRF,cn=content,cn=TestRG,cn=dfsrglobalsettings,cn=system,dc=fabrikam,dc=com <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print ReplicatedFolderGuid: 175F2B6A-289F-4CA8-AF8B- 4D9BF1A2C501 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print ReplicatedFolderDn: CN=testrf,CN=Content,CN=TestRG,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print ReplicatedFolderName: testrf [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 1050 Config::GuidParam::Print ReplicationGroupGuid: 7C81CA1E-F956-4A9E-BCE5- 852 CPAR 1050 Config::GuidParam::Print MemberGuid: E1023470-7BF7-403D-B9A6-CBDA8F877F71 E3A2D1ACDD1D [Flags:0x1] <Upstream> 20080624 14:41:19.788 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 911 Config::PathParam::Print RootPath: c:\testrf [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print RootSizeInMb: 10240 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 911 Config::PathParam::Print StagingPath: c:\testrf\DfsrPrivate\Staging 852 CPAR 204 Config::DWordParam::Print StagingSizeInMb: 4096 [Flags:0x1] staging 852 CPAR 911 Config::PathParam::Print ConflictPath: [Flags:0x1] <Upstream> 20080624 14:41:19.788 quota size, not real size. <Upstream> 20080624 14:41:19.788 c:\testrf\DfsrPrivate\ConflictAndDeleted [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print ConflictSizeInMb: 660 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print FileFilter: ~*, *.bak, *.tmp [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print DirectoryFilter: <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print Ghosted: FALSE [Flags:0x1] Ghosting is an <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print CacheObeyConnectionSchedule: FALSE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print MinAgeInCacheInMin: 0 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 204 Config::DWordParam::Print MaxAgeInCacheInMin: 0 [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print Enabled: TRUE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print IsPrimary: FALSE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print ReadOnly: FALSE [Flags:0x0] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print DisableSaveDeletes: FALSE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print DisableReanimateDeletes: FALSE [Flags:0x1] <Upstream> 20080624 14:41:19.788 852 CPAR 390 Config::BoolParam::Print SharedStaging: FALSE [Flags:0x0] <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print CompressedExtensions: [Flags:0x0] unshipped feature that still logs WMA,WMV,ZIP,JPG,MPG,MPEG,M1V,MP2,MP3,MPA,CAB,WAV,SND,AU,ASF,WM,AVI,Z,GZ,TGZ,FRX [Flags:0x0] default list of files excluded from staging XPRESS compression, see KB951003 <Upstream> 20080624 14:41:19.788 852 CPAR 556 Config::StringParam::Print Description: <null> [Flags:0x0] the LDAP configuration reads end here. Most of the above entries are self-explanatory. <Upstream> 20080624 14:41:20.299 1848 DBCJ 1903 ChangeJournal::Start Start reading journal on volumeId:\\.\C: at usnNumber:10320448. journalId:128587295648302192 find and read latest information from USN journal <Upstream> 20080624 14:41:20.299 1848 VLMG 1158 VolumeManager::Initialize Volume initialized. volId:\\.\C: done examining the volume’s readiness <Upstream> 20080624 14:41:20.299 1848 CSMG 1757 ContentSetManager::Run csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf state:Normal Good idea to note the GUID and name here for future reference <Upstream> 20080624 14:41:20.299 1848 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{175F2B6A-289F-4CA8- AF8B-4D9BF1A2C501} csName:testrf ptr:008640E0 <Upstream> 20080624 14:41:20.299 1848 CSMG 1757 ContentSetManager::Run csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf state:Normal the replicated folder (content set) is started up <Upstream> 20080624 14:41:20.299 1848 CSMG 837 ContentSetManager::Initialize csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf ptr:008640E0 <Upstream> 20080624 14:41:20.309 1848 CSMG 2262 ContentSetManager::CheckContentSetState Updating content set record csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000 ghosting info should be ignored (unshipped feature tht still has some logging remnants in Win2008). The readonly flag/date refers to the msDFSR-ReadOnly, of which modification is unsupported. <Upstream> 20080624 14:41:20.309 1848 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{175F2B6A-289F- 4CA8-AF8B-4D9BF1A2C501} state:Normal <Upstream> 20080624 14:41:20.309 1848 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 1077248 <Upstream> 20080624 14:41:20.319 1848 DOWN 3181 DownstreamTransport::SetupBinding Setting authentication information for partner: FABRIKAM\2008MEM02$ Kerberos TGS is used here. NTLM is not supported with DFSR. <Upstream> 20080624 14:41:20.319 1848 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{DEDD774B-4094-40BF-987A- B38CAFCC86E0} remoteAddress:2008mem02.fabrikam.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008mem02.fabrikam.com] an RPC outbound connection using RPC_C_AUTHN_LEVEL_PKT_PRIVACY is made to the other DFSR server 2008mem02. We also gain the useful information of what the connection GUID for this replication group is. <Upstream> 20080624 14:41:20.329 1848 DOWN 3900 DownstreamTransport::EstablishConnection Established connId:{DEDD774B- 4094-40BF-987A-B38CAFCC86E0} rgName:TestRG transport:9160536 RPC connection was established successfully. <Upstream> 20080624 14:41:20.329 1848 INCO 2942 InConnection::ConnectNetwork New connection connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} transport:008BC758 unghostTransport:00000000 <Upstream> 20080624 14:41:20.339 1848 INCO 2945 InConnection::ConnectNetwork connId:{DEDD774B-4094-40BF-987A- B38CAFCC86E0} fatalRemoteError:0 <Upstream> 20080624 14:41:20.339 1848 INCO 3040 InConnection::ReConnectAsync transport:008BC758 unghostTransport:00000000 <Upstream> 20080624 14:41:20.339 1848 INCO 3101 InConnection::ReConnectAsync Connection established with partner 2008mem02.fabrikam.com. connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} rgName:TestRG the conection with partner 2008mem02 is done successfully. <Upstream> 20080624 14:41:20.339 1848 DOWN 3431 DownstreamTransport::AttachIn ptr:008BC758 <Upstream> 20080624 14:41:20.339 3332 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:008BC9D8 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf changeType:notify current version vector is requested from the partner server <Upstream> 20080624 14:41:20.349 2920 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:VvUpRequest reqState:Completed status:0 ptr:008BC9D8 <Upstream> 20080624 14:41:20.349 2920 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:008BC8E0 <Upstream> 20080624 14:41:20.349 3332 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:008BC9D8 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf changeType:all server asks upstream partner for its current version vector high watermark number. <Upstream> 20080624 14:41:20.359 3304 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:VvUpRequest reqState:Completed status:0 ptr:008BC9D8 <Upstream> 20080624 14:41:20.369 2920 INCO 3959 InConnection::ReceiveVvUp Received VvUp connId:{DEDD774B-4094-40BF-987A- B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf vvUp:{EDE2D64E-1306-4C7C-B568-449A98371AA2} |-> { 10..40} + {910170E6-8BD6-49A9-85F1-A2F3FF43C76B} |-> { 10} 10 this is the current high watermark version vector on the remote server 2008mem02 (i.e. the next VV will be 11). 40 is the current VV high watermark on the local DFSR server, so its next version will be 41. + <Upstream> 20080624 14:41:20.369 2920 INCO 3966 InConnection::ReceiveVvUp Creating new session:1 requestState:008BC9D8 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf vvDown:{EDE2D64E1306-4C7C-B568-449A98371AA2} |-> { 10..40} + {910170E6-8BD6-49A9-85F1-A2F3FF43C76B} |-> { 10} + <Upstream> 20080624 14:41:20.369 2920 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} csId:{00000000-0000-0000-0000-000000000000} reqType:AsyncPollRequest reqState:Completed status:0 ptr:008BC8E0 <Upstream> 20080624 14:41:20.369 1848 INCO 3779 InConnection::ContentSetContext::Hibernate Hibernating: connId:{DEDD774B- 4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} <Upstream> 20080624 14:41:20.369 1848 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:008BC9D8 connId:{DEDD774B-4094-40BF-987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} csName:testrf changeType:notify the upstream 2008mem02 server is requested to send its current VV <Upstream> 20080624 14:41:20.369 2920 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{DEDD774B-4094-40BF- 987A-B38CAFCC86E0} csId:{175F2B6A-289F-4CA8-AF8B-4D9BF1A2C501} reqType:VvUpRequest reqState:Completed status:0 ptr:008BC9D8 the downstream server 2008mem02 is sent the upstream 2008mem01’s current VV of 40. <Upstream> 20080624 14:41:22.853 3904 SRTR 712 SERVER_EstablishConnection Succeeded on connId:{F5A520C4-154C-460E-B8EF- 0867D4F92AAE} replicaSetId:{7C81CA1E-F956-4A9E-BCE5-E3A2D1ACDD1D} rgName:TestRG partnerAddress:2008mem02.fabrikam.com the RPC replication connection is now fully formed and ready to replicate files. Understanding DFSR debug logging (part 13: A New Replication Group and Replicated Folder between two Windows Server 2008 members) In this scenario we will see a new Replication Group and Replicated Folder created. The upstream replicated folder will contain a few files that do not yet exist on the downstream member. This is useful to understand as one of the most common troubleshooting areas in DFSR is the actual configuration and initial synchronization phase. (newrgrfprimary - Dfsr00020 - 2008.log and newrgrfnonauth - Dfsr00017 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 (which is the Primary, aka authoritative, member) and from 2008MEM02 (which is the non-authoritative member). Both servers are participating in the NEWRG1 replication group for the NEWRF1 replicated folder. This log has a significant portion of data removed for readability – review previous sections for configuration and large file add. <Downstream> 20080627 11:48:55.634 300 RSMG 142 ReplicaSetManager::Initialize Initialize replication group rgName:NewRG1 The replica set manager is initializing the replication group on the downstream partner. Because each member of an RG must find out about the topology from the DC it is bound to, and because each member checks on its own schedule, all members will find out at different times. <Downstream> 20080627 11:48:55.634 300 RSMG 908 ReplicaSetManager::AddInConnection Creating new inbound connection connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rgName:NewRG1 <Downstream> 20080627 11:48:55.634 300 RSMG 1273 ReplicaSetManager::AddOrUpdateConnection New or updated outbound connection object. connId:{AF7B6836-D323-4A01-9448-09680B9ACAF5} rgName:NewRG1 inbound and outbound connections are made. <Downstream> 20080627 11:48:55.634 300 CCTX 2401 ConfigContext::ApplyDiff Updating volume in ConfigContext, volumePath:\\.\C: <Downstream> 20080627 11:48:55.634 300 FREP 450 FrsReplicator::UpdateVolume Update Volume:3EA8BD01-416E-11DD-A317- 806E6F6E6963 <Downstream> 20080627 11:48:55.634 300 VLMG 2327 VolumeManager::AddContentSet Initializing contentSet. csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 the new replicated folder is initialized <Downstream> 20080627 11:48:55.634 300 CSMG 546 ContentSetManager::ContentSetManager csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:48:55.634 300 CCTX 3237 ConfigContext::DumpReplicaConfig Dumping Replica global config context entries below must be evaluated from LDAP lookups and written into the XML config files. These are highlighted for reading but are largely self-explanatory: <Downstream> 20080627 11:48:55.634 300 CPAR 2476 Config::ParamBlock::Print [[ DfsrReplicatedFolder ]] <Downstream> 20080627 11:48:55.634 300 CPAR 1050 Config::GuidParam::Print ReplicatedFolderGuid: 05631532-B65C-45AF-BB49- F237ACB6CF7C [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 556 Config::StringParam::Print ReplicatedFolderDn: CN=NewRF1,CN=Content,CN=NewRG1,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR <Downstream> 20080627 11:48:55.634 300 CPAR 1050 Config::GuidParam::Print ReplicationGroupGuid: 33DACEEE-D60C-4BF1-911C- 556 Config::StringParam::Print ReplicatedFolderName: NewRF1 [Flags:0x1] 300 CPAR 1050 Config::GuidParam::Print MemberGuid: 0C33B8DA-F55A-4F85-BA95- EA5C487A78CB [Flags:0x1] <Downstream> 20080627 11:48:55.634 CCD84C4E7F59 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 911 Config::PathParam::Print RootPath: c:\newrf1 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 204 Config::DWordParam::Print RootSizeInMb: 10240 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 911 Config::PathParam::Print StagingPath: c:\newrf1\DfsrPrivate\Staging <Downstream> 20080627 11:48:55.634 300 CPAR 204 Config::DWordParam::Print StagingSizeInMb: 4096 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 911 Config::PathParam::Print ConflictPath: [Flags:0x1] c:\newrf1\DfsrPrivate\ConflictAndDeleted [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 204 Config::DWordParam::Print ConflictSizeInMb: 660 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 556 Config::StringParam::Print FileFilter: ~*, *.bak, *.tmp [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 556 Config::StringParam::Print DirectoryFilter: <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print Ghosted: FALSE [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print CacheObeyConnectionSchedule: FALSE [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 204 Config::DWordParam::Print MinAgeInCacheInMin: 0 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 204 Config::DWordParam::Print MaxAgeInCacheInMin: 0 [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print Enabled: TRUE [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print IsPrimary: FALSE [Flags:0x1] this server is [Flags:0x0] not authoritative for this replica set <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print ReadOnly: FALSE [Flags:0x0] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print DisableSaveDeletes: FALSE [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print DisableReanimateDeletes: FALSE [Flags:0x1] <Downstream> 20080627 11:48:55.634 300 CPAR 390 Config::BoolParam::Print SharedStaging: FALSE [Flags:0x0] <Downstream> 20080627 11:48:55.634 300 CPAR 556 Config::StringParam::Print CompressedExtensions: WMA,WMV,ZIP,JPG,MPG,MPEG,M1V,MP2,MP3,MPA,CAB,WAV,SND,AU,ASF,WM,AVI,Z,GZ,TGZ,FRX [Flags:0x0] <Downstream> 20080627 11:48:55.634 300 CPAR 556 Config::StringParam::Print Description: <null> [Flags:0x0] <Downstream> 20080627 11:48:55.634 2764 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:Normal content set manager not triggers the RF to be created <Downstream> 20080627 11:48:55.634 2764 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{05631532-B65C-45AF- BB49-F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:48:55.634 2764 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:Normal <Downstream> 20080627 11:48:55.634 2764 CSMG 837 ContentSetManager::Initialize csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 the replica set is initialized <Downstream> 20080627 11:48:55.634 2764 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} state:InitialBuilding 0080627 11:48:55.634 2764 CSMG 3182 ContentSetManager::CreateRootRecord Adding root record csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ghosted:0 a base record must be added to the DFSR database to identify where the replicated folder tree starts. <Downstream> 20080627 11:48:55.634 2764 CSMG 3298 ContentSetManager::CreateRootRecord LDB Inserting ID Record: DFSR DB updated for the RF root record. + fid 0x800000000A751 + usn 0x944b40 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 the object is a folder + ghostedHeader 0 + data 0 + gvsn {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + uid {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 note that the UID/GVSN will match and when creating the very first RF of all time on a server, will start with v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080627 15:48:26.547 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name newrf1 the replicated folder name on the file system 20080627 15:48:26.547 GMT (0x1c8d86d3cf03e5c) + <Downstream> 20080627 11:48:55.644 2764 LDBX 4028 Ldb::Insert Inserting contentSetRecord: the database on this volume is set to initial building status + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {0C33B8DA-F55A-4F85-BA95-CCD84C4E7F59} + state: InitialBuilding + startVersion: v24 + authRebuilding: 0 + stageVolumeSerialNumber: 0 + stageFid: 0x0 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080627 11:48:55.684 2764 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 0 staging space is checked <Downstream> 20080627 11:48:55.684 2764 STAG 6158 StagingManager::RegisterContentSetsOnPath {05631532-B65C-45AF-BB49- F237ACB6CF7C} added to the replicated folder list. the replicated folder GUID is now registered <Downstream> 20080627 11:48:55.684 2764 LDBX 4062 Ldb::Update Updating contentSetRecord: The staging directory file ID is now registered in the database + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {0C33B8DA-F55A-4F85-BA95-CCD84C4E7F59} + state: InitialBuilding + startVersion: v24 + authRebuilding: 0 + stageVolumeSerialNumber: 3a34b62834b5e753 + stageFid: + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 0x100000000A77F + <Downstream> 20080627 11:48:55.694 2764 CSMG 1274 ContentSetManager::Initialize Walk replica set to initialize or fix up database. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 DFSR now needs to initialize the replicated folder by walking the directory to find any child objects. <Downstream> 20080627 11:48:55.694 2764 DIRW 515 DirWalkerTask::QueueMoveinJob Queuing move-in. uid:{05631532-B65C-45AF- BB49-F237ACB6CF7C}-v1 fid:0x800000000A751 name:newrf1 dir walker will walk the replicated folder for objects <Downstream> 20080627 11:48:55.694 480 DIRW 256 DirWalkerTask::Run Start walking directory. replicated folder is dir 480 DIRW 945 DirWalkerTask::MoveinStep Starting to process move-in job. walked <Downstream> 20080627 11:48:55.694 uid:{05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 <Downstream> 20080627 11:48:55.694 480 DIRW 101 DirWalkerTask::Job::Finish MoveIn csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} uid:{05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 dirwalk is done for the replicated folder <Downstream> 20080627 11:48:55.694 480 DIRW 793 DirWalkerTask::RemoveJob Removing job type:1 uid:{05631532-B65C-45AF- BB49-F237ACB6CF7C}-v1 <Downstream> 20080627 11:48:55.694 480 LDBX 4386 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{05631532-B65C-45AF- BB49-F237ACB6CF7C}-v1 <Downstream> 20080627 11:48:55.694 480 EVNT 725 EventLog::Report Logging eventId:4102 parameterCount:6 a 4102 event is logged to show that the downstream (non-authoritative, non-primary) server is ready for initial sync replication to begin. <Downstream> 20080627 11:48:55.694 480 EVNT 745 EventLog::Report eventId:4102 parameter1:05631532-B65C-45AF- <Downstream> 20080627 11:48:55.694 480 EVNT 745 EventLog::Report eventId:4102 parameter2:c:\newrf1 <Downstream> 20080627 11:48:55.694 480 EVNT 745 EventLog::Report eventId:4102 parameter3:NewRF1 <Downstream> 20080627 11:48:55.694 480 EVNT 745 EventLog::Report eventId:4102 parameter4:NewRG1 <Downstream> 20080627 11:48:55.694 480 EVNT 745 EventLog::Report eventId:4102 parameter5:33DACEEE-D60C-4BF1- 480 EVNT 745 EventLog::Report eventId:4102 parameter6:0C33B8DA-F55A-4F85- BB49-F237ACB6CF7C 911C-EA5C487A78CB <Downstream> 20080627 11:48:55.694 BA95-CCD84C4E7F59 <Downstream> 20080627 11:48:55.694 480 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} newState:InitialSync(Sync) (auth:0) the server is now in initial sync state <Downstream> 20080627 11:48:55.694 480 LDBX 4062 Ldb::Update Updating contentSetRecord: database is updated to reflect this state + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {0C33B8DA-F55A-4F85-BA95-CCD84C4E7F59} + state: InitialSync(Sync) + startVersion: v24 + authRebuilding: 0 + stageVolumeSerialNumber: 3a34b62834b5e753 + stageFid: 0x100000000A77F + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080627 11:48:55.704 480 CSMG 2697 ContentSetManager::DbBuildComplete Finished scanning content set and building database info: {05631532-B65C-45AF-BB49-F237ACB6CF7C} Transition from InitialBuilding to InitialSync(Sync) <Downstream> 20080627 11:48:55.704 480 DIRW <Downstream> 20080627 11:48:55.704 2764 CSMG 303 DirWalkerTask::Run Exit. 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:InitialBuilding <Downstream> 20080627 11:48:55.704 2764 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{05631532-B65C-45AF- BB49-F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:48:55.704 2764 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:InitialBuilding <Downstream> 20080627 11:48:55.704 2764 CSMG 837 ContentSetManager::Initialize csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:48:55.704 2764 CSMG 2262 ContentSetManager::CheckContentSetState Updating content set record csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000 <Downstream> 20080627 11:48:55.704 2764 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} state:InitialSync(Sync) <Downstream> 20080627 11:48:55.704 2764 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 0 <Downstream> 20080627 11:48:55.714 3181 DownstreamTransport::SetupBinding Setting authentication information 480 DOWN for partner: FABRIKAM\2008MEM01$ server now tries to start contacting its partner for replication. <Downstream> 20080627 11:48:55.714 480 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{FFC8C463-846D-4C16- 8B37-19978C20FF8B} remoteAddress:2008mem01.fabrikam.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008mem01.fabrikam.com] an RPC connection is attempted to the remote partner <Downstream> 20080627 11:48:55.714 + 480 DOWN 3868 [WARN] DownstreamTransport::EstablishConnection Failed. Try flat name. [Error:9027(0x2343) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 480 C A failure was reported by the remote partner] + [Error:9026(0x2342) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 480 C The connection is invalid] A “connection is invalid” error means that the other server is not yet aware of this replication topology <Downstream> 20080627 11:48:55.714 480 DOWN 3181 DownstreamTransport::SetupBinding Setting authentication information 480 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{FFC8C463-846D-4C16- for partner: FABRIKAM\2008MEM01$ <Downstream> 20080627 11:48:55.714 8B37-19978C20FF8B} remoteAddress:2008mem01.fabrikam.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008mem01] <Downstream> 20080627 11:48:55.714 480 DOWN 3887 [ERROR] DownstreamTransport::EstablishConnection EstablishConnection failed. connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rgName:NewRG1 Error: + [Error:9027(0x2343) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 480 C A failure was reported by the remote partner] + [Error:9026(0x2342) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 480 C The connection is invalid] <Downstream> 20080627 11:48:55.714 480 DOWN 6954 BandwidthThrottler::PrepareForShutdown ptr:00CCB538 <Downstream> 20080627 11:48:55.714 480 DOWN 6963 BandwidthThrottler::PrepareForShutdown Preparing for Shutdown <snipped out constant retries to other member 2008mem01 that has not yet picked up the configuration yet from AD polling> <Upstream> 20080627 11:53:14.698 324 RSMG 142 ReplicaSetManager::Initialize Initialize replication group rgName:NewRG1 the upstream server has now picked up the change from LDAP polling <Upstream> 20080627 11:53:14.698 324 RSMG 908 ReplicaSetManager::AddInConnection Creating new inbound connection connId:{AF7B6836-D323-4A01-9448-09680B9ACAF5} rgName:NewRG1 <Upstream> 20080627 11:53:14.698 324 RSMG 1273 ReplicaSetManager::AddOrUpdateConnection New or updated outbound connection object. connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rgName:NewRG1 <Upstream> 20080627 11:53:14.698 324 CCTX 2401 ConfigContext::ApplyDiff Updating volume in ConfigContext, volumePath:\\.\C: <Upstream> 20080627 11:53:14.698 324 FREP 450 FrsReplicator::UpdateVolume Update Volume:6A7E9F21-4169-11DD-AF51- 806E6F6E6963 <Upstream> 20080627 11:53:14.708 324 VLMG 2327 VolumeManager::AddContentSet Initializing contentSet. csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 <Upstream> 20080627 11:53:14.708 324 CSMG 546 ContentSetManager::ContentSetManager csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ptr:00B766B0 <Upstream> 20080627 11:53:14.708 324 CPAR <Upstream> 20080627 11:53:14.708 324 CPAR <Upstream> 20080627 11:53:14.708 324 CPAR 2476 Config::ParamBlock::Print [[ DfsrReplicationGroup ]] 204 Config::DWordParam::Print LastChangeNumber: 1 [Flags:0x0] 1244 Config::DateTimeParam::Print LastChangeTime: 6/27/2008 15:53:14 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print LastChangeSource: 2008dc01.fabrikam.com [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print Description: <null> [Flags:0x0] 1050 Config::GuidParam::Print ReplicationGroupGuid: 33DACEEE-D60C-4BF1-911C- EA5C487A78CB [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR <Upstream> 20080627 11:53:14.708 324 CPAR 2476 Config::ParamBlock::Print 556 Config::StringParam::Print ReplicationGroupName: NewRG1 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 1050 Config::GuidParam::Print ConnectionGuid: AF7B6836-D323-4A01-9448- [[ DfsrConnection ]] 09680B9ACAF5 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print ConnectionDn: CN=45c15215-2233-4e88-aa87- 48b75867d7e6,CN=7ee30623-f21f-489d-aa4b-6bdc73dbccc9,CN=Topology,CN=NewRG1,CN=DFSRGlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 1050 Config::GuidParam::Print PartnerGuid: 0C33B8DA-F55A-4F85-BA95- <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print PartnerName: 2008MEM02 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print PartnerDn: CN=264ffb2a-ac64-4f0b-9701- CCD84C4E7F59 [Flags:0x1] c9d9c85cb27f,CN=Topology,CN=NewRG1,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print PartnerDns: 2008mem02.fabrikam.com [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print PartnerPrincName: FABRIKAM\2008MEM02$ [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 2476 Config::ParamBlock::Print [[ DfsrReplicatedFolder ]] <Upstream> 20080627 11:53:14.708 324 CPAR 1050 Config::GuidParam::Print ReplicatedFolderGuid: 05631532-B65C-45AF-BB49- F237ACB6CF7C [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print ReplicatedFolderDn: CN=NewRF1,CN=Content,CN=NewRG1,CN=DFSR-GlobalSettings,CN=System,DC=fabrikam,DC=com [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print ReplicatedFolderName: NewRF1 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 1050 Config::GuidParam::Print ReplicationGroupGuid: 33DACEEE-D60C-4BF1-911C- 324 CPAR 1050 Config::GuidParam::Print MemberGuid: 5EF77FE2-B1BF-41B4-9DA6-51F6549F523E EA5C487A78CB [Flags:0x1] <Upstream> 20080627 11:53:14.708 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 911 Config::PathParam::Print RootPath: C:\NewRF1 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 204 Config::DWordParam::Print RootSizeInMb: 10240 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 911 Config::PathParam::Print StagingPath: C:\NewRF1\DfsrPrivate\Staging <Upstream> 20080627 11:53:14.708 324 CPAR 204 Config::DWordParam::Print StagingSizeInMb: 4096 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 911 Config::PathParam::Print ConflictPath: [Flags:0x1] C:\NewRF1\DfsrPrivate\ConflictAndDeleted [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 204 Config::DWordParam::Print ConflictSizeInMb: 660 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print FileFilter: ~*, *.bak, *.tmp [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 556 Config::StringParam::Print DirectoryFilter: <Upstream> 20080627 11:53:14.708 324 CPAR 390 Config::BoolParam::Print Ghosted: FALSE [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 390 Config::BoolParam::Print CacheObeyConnectionSchedule: FALSE [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 204 Config::DWordParam::Print MinAgeInCacheInMin: 0 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 204 Config::DWordParam::Print MaxAgeInCacheInMin: 0 [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 390 Config::BoolParam::Print Enabled: TRUE [Flags:0x1] <Upstream> 20080627 11:53:14.708 324 CPAR 390 Config::BoolParam::Print IsPrimary: TRUE [Flags:0x1] This server is [Flags:0x0] the upstream and is marked as Primary. It will authoritative for all data. <Upstream> 20080627 11:53:14.708 3836 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:Normal <Upstream> 20080627 11:53:14.708 3836 CSMG 837 ContentSetManager::Initialize csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ptr:00B766B0 <Upstream> 20080627 11:53:14.708 3836 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{05631532-B65C- 45AF-BB49-F237ACB6CF7C} state:InitialBuilding <Upstream> 20080627 11:53:14.708 3836 CSMG 3182 ContentSetManager::CreateRootRecord Adding root record csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ghosted:0 <Upstream> 20080627 11:53:14.718 3820 CFAD 7697 Config::AdConfig::CheckSchemaVersion DMD object:CN=Schema,CN=Configuration,DC=fabrikam,DC=com, objectVersion:44 <Upstream> 20080627 11:53:14.738 3836 CSMG 3298 ContentSetManager::CreateRootRecord LDB Inserting ID Record: root replicated folder record created in the database. + fid 0x700000000AC58 + usn 0xa73000 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v82 GVSN now set to match server GUID. The version is high because there has been other files replicated on this server in a different RG previously. + uid {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 UID is set to v1 to mark the first folder created on server. + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080627 15:46:41.522 GMT (0x1c8d86cfe56c4bc) + createTime 20080627 15:45:37.768 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name NewRF1 + <Upstream> 20080627 11:53:14.818 3836 LDBX 4028 Ldb::Insert Inserting contentSetRecord: the database is updated to mark initial building on the Primary server + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {5EF77FE2-B1BF-41B4-9DA6-51F6549F523E} + state: InitialBuilding + startVersion: v81 + authRebuilding: 0 + stageVolumeSerialNumber: 0 + stageFid: 0x0 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080627 11:53:14.988 3836 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 0 <Upstream> 20080627 11:53:14.988 3836 STAG 6158 StagingManager::RegisterContentSetsOnPath {05631532-B65C-45AF-BB49- F237ACB6CF7C} added to the replicated folder list. <Upstream> 20080627 11:53:14.998 3836 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {5EF77FE2-B1BF-41B4-9DA6-51F6549F523E} + state: InitialBuilding + startVersion: v81 + authRebuilding: 0 + stageVolumeSerialNumber: 48ac1944ac192e46 + stageFid: 0x100000000AC80 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080627 11:53:14.998 3836 CSMG 1274 ContentSetManager::Initialize Walk replica set to initialize or fix up database. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 <Upstream> 20080627 11:53:14.998 3836 DIRW 515 DirWalkerTask::QueueMoveinJob Queuing move-in. uid:{05631532-B65C-45AF- BB49-F237ACB6CF7C}-v1 fid:0x700000000AC58 name:NewRF1 <Upstream> 20080627 11:53:14.998 676 DIRW 256 DirWalkerTask::Run Start walking directory. all files on the Primary 676 DIRW 945 DirWalkerTask::MoveinStep Starting to process move-in job. uid:{05631532- 676 DIRW 2428 DirWalkerTask::CreateOneRecord LDB Inserting ID Record: the first file server are now walked <Upstream> 20080627 11:53:14.998 B65C-45AF-BB49-F237ACB6CF7C}-v1 <Upstream> 20080627 11:53:14.998 is found by the dirwalker job. In this case it is a copy of ‘explorer.exe’ + fid 0x100000000AC7C + usn 0xa71e60 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 it’s a file, not a folder + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v83 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v83 the file UID and GVSN must match at this point + parent {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 We can tell by the parent that the file is directly in the root of the replicated folder + fence + clockDecrementedInDirtyShutdown 0 16010101 00:00:00.000 P + clock 20080627 15:46:41.600 GMT (0x1c8d86cfe62a5f4) + createTime 20080627 15:46:41.522 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name explorer.exe file name + <snipped out several other files that are in original log, for simpler reading> <Upstream> 20080627 11:53:14.998 676 DIRW 101 DirWalkerTask::Job::Finish MoveIn csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} uid:{05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 dir walking is done <Upstream> 20080627 11:53:14.998 676 DIRW 793 DirWalkerTask::RemoveJob Removing job type:1 uid:{05631532-B65C-45AF- BB49-F237ACB6CF7C}-v1 <Upstream> 20080627 11:53:14.998 676 LDBX 4386 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{05631532-B65C-45AF-BB49- 676 EVNT 725 EventLog::Report Logging eventId:4112 parameterCount:6 a 4112 event is F237ACB6CF7C}-v1 <Upstream> 20080627 11:53:14.998 written the event logs in order to mark that the upstream Primary member is now done with its initial sync processing and ready to serve files. <Upstream> 20080627 11:53:14.998 676 EVNT 745 EventLog::Report eventId:4112 parameter1:05631532-B65C-45AF-BB49- <Upstream> 20080627 11:53:14.998 676 EVNT 745 EventLog::Report eventId:4112 parameter2:C:\NewRF1 <Upstream> 20080627 11:53:14.998 676 EVNT 745 EventLog::Report eventId:4112 parameter3:NewRF1 <Upstream> 20080627 11:53:14.998 676 EVNT 745 EventLog::Report eventId:4112 parameter4:NewRG1 <Upstream> 20080627 11:53:14.998 676 EVNT 745 EventLog::Report eventId:4112 parameter5:33DACEEE-D60C-4BF1-911C- 676 EVNT 745 EventLog::Report eventId:4112 parameter6:5EF77FE2-B1BF-41B4-9DA6- F237ACB6CF7C EA5C487A78CB <Upstream> 20080627 11:53:14.998 51F6549F523E <Upstream> 20080627 11:53:15.008 676 CSMG 4599 ContentSetManager::UpdateRootFence LDB Updating ID Record: a root fence marks data in the content set as authoritative for any conflicts + fid 0x700000000AC58 + usn 0xa73000 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080627 15:53:14.748 GMT + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v82 + uid {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080627 15:46:41.522 GMT (0x1c8d86cfe56c4bc) + createTime 20080627 15:45:37.768 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name NewRF1 + <Upstream> 20080627 11:53:15.008 676 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} newState:Normal (auth:0) Initial sync is now done as far as the authoritative server is concerned. Its state for the replicated folder is set to Normal. <Upstream> 20080627 11:53:15.008 676 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {5EF77FE2-B1BF-41B4-9DA6-51F6549F523E} + state: Normal + startVersion: v81 + authRebuilding: 0 + stageVolumeSerialNumber: 48ac1944ac192e46 + stageFid: 0x100000000AC80 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080627 11:53:15.008 676 CSMG 2697 ContentSetManager::DbBuildComplete Finished scanning content set and building database info: {05631532-B65C-45AF-BB49-F237ACB6CF7C} Transition from InitialBuilding to Normal replica set is in Normal mode now <Upstream> 20080627 11:53:15.008 676 DIRW <Upstream> 20080627 11:53:15.008 3836 CSMG 303 DirWalkerTask::Run Exit. 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:InitialBuilding <Upstream> 20080627 11:53:15.008 3836 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{05631532-B65C-45AF- BB49-F237ACB6CF7C} csName:NewRF1 ptr:00B766B0 <Upstream> 20080627 11:53:15.008 3836 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:InitialBuilding <Upstream> 20080627 11:53:15.008 3836 CSMG 837 ContentSetManager::Initialize csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ptr:00B766B0 <Upstream> 20080627 11:53:15.008 3836 CSMG 2262 ContentSetManager::CheckContentSetState Updating content set record csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000 <Upstream> 20080627 11:53:15.008 3836 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{05631532-B65C- 45AF-BB49-F237ACB6CF7C} state:Normal <Upstream> 20080627 11:53:15.008 3836 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 0 <Upstream> 20080627 11:53:15.018 676 DOWN 3181 DownstreamTransport::SetupBinding Setting authentication information for 676 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{AF7B6836-D323-4A01-9448- partner: FABRIKAM\2008MEM02$ <Upstream> 20080627 11:53:15.018 09680B9ACAF5} remoteAddress:2008mem02.fabrikam.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008mem02.fabrikam.com] <Upstream> 20080627 11:53:15.028 676 DOWN 3900 DownstreamTransport::EstablishConnection Established connId:{AF7B6836- D323-4A01-9448-09680B9ACAF5} rgName:NewRG1 transport:12012224 <Upstream> 20080627 11:53:15.028 676 INCO 2942 InConnection::ConnectNetwork New connection connId:{AF7B6836-D323-4A01- 9448-09680B9ACAF5} transport:00B74AC0 unghostTransport:00000000 <Upstream> 20080627 11:53:15.028 676 INCO 2945 InConnection::ConnectNetwork connId:{AF7B6836-D323-4A01-9448- <Upstream> 20080627 11:53:15.028 676 INCO 3040 InConnection::ReConnectAsync transport:00B74AC0 unghostTransport:00000000 <Upstream> 20080627 11:53:15.028 676 INCO 3101 InConnection::ReConnectAsync Connection established with partner 09680B9ACAF5} fatalRemoteError:0 2008mem02.fabrikam.com. connId:{AF7B6836-D323-4A01-9448-09680B9ACAF5} rgName:NewRG1 <Upstream> 20080627 11:53:15.028 676 DOWN <Upstream> 20080627 11:53:15.028 3856 DOWN 3431 DownstreamTransport::AttachIn ptr:00B74AC0 3991 [ERROR] DownstreamTransport::EstablishSession Failed on connId:{AF7B6836- D323-4A01-9448-09680B9ACAF5} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} rgName:NewRG1 Error: + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3984 3856 C A failure was reported by the remote partner] + [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3984 3856 C The content set is not ready] 20080627 11:53:15.028 3856 INCO 3566 InConnection::RestartSession Retrying establish contentset session. connId:{AF7B6836-D323-4A01-9448-09680B9ACAF5} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 <Upstream> 20080627 11:53:15.028 3856 INCO 774 [WARN] SessionTask::Step (Ignored) Failed, should have already been processed. Error: + [Error:9027(0x2343) InConnection::EstablishSession inconnection.cpp:3657 3856 C A failure was reported by the remote partner] + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:4005 3856 C A failure was reported by the remote partner] + [Error:9027(0x2343) DownstreamTransport::EstablishSession downstreamtransport.cpp:3984 3856 C A failure was reported by the remote partner] + [Error:9051(0x235b) DownstreamTransport::EstablishSession downstreamtransport.cpp:3984 3856 C The content set is not ready] <snipped out repeated retries because partner server is still running through initial sync phase> <Downstream> 20080627 11:53:16.081 292 SRTR 712 SERVER_EstablishConnection Succeeded on connId:{AF7B6836-D323-4A01- 9448-09680B9ACAF5} replicaSetId:{33DACEEE-D60C-4BF1-911C-EA5C487A78CB} rgName:NewRG1 partnerAddress:2008mem01.fabrikam.com <Downstream> 20080627 11:53:16.081 292 SRTR 784 [WARN] SERVER_EstablishSession Failed on connId:{AF7B6836-D323-4A01- 9448-09680B9ACAF5} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} Error: + [Error:9051(0x235b) UpstreamTransport::EstablishSession upstreamtransport.cpp:707 292 C The content set is not ready] + [Error:9051(0x235b) OutConnection::EstablishSession outconnection.cpp:2623 292 C The content set is not ready] <snipped out repeated retries because partner server is still running through initial sync phase on iself> <Upstream> 20080627 11:57:25.809 3832 SRTR 712 SERVER_EstablishConnection Succeeded on connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} replicaSetId:{33DACEEE-D60C-4BF1-911C-EA5C487A78CB} rgName:NewRG1 partnerAddress:2008mem02.fabrikam.com <Upstream> 20080627 11:57:25.819 3832 OUTC 2610 OutConnection::EstablishSession Replacing content set. csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rgName:NewRG1 <Upstream> 20080627 11:57:25.819 3836 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {5EF77FE2-B1BF-41B4-9DA6-51F6549F523E} + state: Normal + startVersion: v81 + authRebuilding: 0 + stageVolumeSerialNumber: 48ac1944ac192e46 + stageFid: 0x100000000AC80 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080627 11:57:25.819 3836 CSMG 2340 ContentSetManager::UpdateLastOnlineTime Last online time updated: <Upstream> 20080627 15:57:25.819 csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} <Upstream> 20080627 11:57:25.829 2172 SRTR 1927 SERVER_AsyncPoll Received from connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} upstream server receives polling request from downstream <Upstream> 20080627 11:57:25.829 3832 SRTR 794 SERVER_EstablishSession Established connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} an RPC connection is established between both servers. <Upstream> 20080627 11:57:25.839 1128 SRTR 1880 SERVER_RequestVersionVector Received from connId:{FFC8C463-846D-4C16- 8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} seqNumber:1 changeType:notify upstream receives request for his version vector information <Upstream> 20080627 11:57:25.839 1128 SRTR 1880 SERVER_RequestVersionVector Received from connId:{FFC8C463-846D-4C16- 8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} seqNumber:2 changeType:all <Upstream> 20080627 11:57:25.839 1128 SRTR 1927 SERVER_AsyncPoll Received from connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} <Upstream> 20080627 11:57:25.849 1128 SRTR 882 SERVER_RequestUpdates Received from connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} credits:32 requestType:all <Upstream> 20080627 11:57:25.849 1128 SRTR 1927 SERVER_AsyncPoll Received from connId:{FFC8C463-846D-4C16-8B37- 19978C20FF8B} <Upstream> 20080627 11:57:25.849 676 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x10 <snipped out file replication operations that are better documented in previous scenarios> <Downstream> 20080627 11:57:29.025 480 ISYN 65 InitialSyncManager::ReturnToken InitialSync sync step finished. Delete all session tasks. downstream the initial sync task is being removed. <Downstream> 20080627 11:57:29.025 480 CSMG 2746 ContentSetManager::InitialSyncStepSyncComplete InitialSync sync step completed. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} transition from InitialSync(Sync) to InitialSync(Cleanup). The initial sync cleanup removes references to the sync. <Downstream> 20080627 11:57:29.025 480 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} newState:InitialSync(Cleanup) (auth:0) <Downstream> 20080627 11:57:29.025 480 LDBX 4062 Ldb::Update Updating contentSetRecord: Database set to cleanup mode for this replica set + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {0C33B8DA-F55A-4F85-BA95-CCD84C4E7F59} + state: InitialSync(Cleanup) + startVersion: v24 + authRebuilding: 0 + stageVolumeSerialNumber: 3a34b62834b5e753 + stageFid: 0x100000000A77F + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080627 11:57:29.035 480 INCO 6194 InConnection::CommitSession Connection in sync connId:{FFC8C463-846D- 4C16-8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 commitedSessionsWithUpdateFailures:0 downstream server believes it is successfully in sync without any remaining files. <Downstream> 20080627 11:57:29.035 480 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{FFC8C463-846D- 4C16-8B37-19978C20FF8B} csName:NewRF1 csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} <Downstream> 20080627 11:57:29.035 3628 CSMG csName:NewRF1 state:InitialSync(Sync) 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} <Downstream> 20080627 11:57:29.035 3628 UPMG 535 UpdateManager::Finalize Finalizing UpdateManager connId:{FFC8C463-846D- 4C16-8B37-19978C20FF8B} csName:NewRF1 csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} <Downstream> 20080627 11:57:29.035 3628 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{05631532-B65C-45AF- BB49-F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:57:29.035 3628 CSMG 1757 ContentSetManager::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 state:InitialSync(Sync) <Downstream> 20080627 11:57:29.035 3628 CSMG 837 ContentSetManager::Initialize csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} csName:NewRF1 ptr:00CC3AA0 <Downstream> 20080627 11:57:29.035 3628 CSMG 2262 ContentSetManager::CheckContentSetState Updating content set record csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000 <Downstream> 20080627 11:57:29.035 3628 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{05631532- B65C-45AF-BB49-F237ACB6CF7C} state:InitialSync(Cleanup) <Downstream> 20080627 11:57:29.035 3628 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 1695744 staging area is checked for usage and now contains ~1.5MB of data <Downstream> 20080627 11:57:29.045 3628 CSMG 2769 ContentSetManager::StartInitialSyncCleanup csId:{05631532-B65C-45AF- BB49-F237ACB6CF7C} <Downstream> 20080627 11:57:29.045 3748 ISYN <Downstream> 20080627 11:57:29.045 3748 CSMG 97 InitialSyncCleanupTask::Run csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} 2785 ContentSetManager::InitialSyncStepCleanupComplete InitialSync cleanup step completed. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} transition from InitialSync(Cleanup) to Normal cleanup tasks are done and the downstream server is ready to leave initial sync <Downstream> 20080627 11:57:29.045 3748 EVNT 725 EventLog::Report Logging eventId:4104 parameterCount:6 a 4104 event is logged to event viewer which states initial sync done. <Downstream> 20080627 11:57:29.045 3748 EVNT 745 EventLog::Report eventId:4104 parameter1:05631532-B65C-45AF- 745 EventLog::Report eventId:4104 parameter2:c:\newrf1 BB49-F237ACB6CF7C <Downstream> 20080627 11:57:29.045 3748 EVNT <Downstream> 20080627 11:57:29.045 3748 EVNT 745 EventLog::Report eventId:4104 parameter3:NewRF1 <Downstream> 20080627 11:57:29.045 3748 EVNT 745 EventLog::Report eventId:4104 parameter4:NewRG1 <Downstream> 20080627 11:57:29.045 3748 EVNT 745 EventLog::Report eventId:4104 parameter5:33DACEEE-D60C-4BF1- 745 EventLog::Report eventId:4104 parameter6:0C33B8DA-F55A-4F85- 911C-EA5C487A78CB <Downstream> 20080627 11:57:29.045 3748 EVNT BA95-CCD84C4E7F59 <Downstream> 20080627 11:57:29.045 3748 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} newState:Normal (auth:0) <Downstream> 20080627 11:57:29.045 3748 LDBX 4062 Ldb::Update Updating contentSetRecord: the database is updated to mark RF in normal mode. + contentSetId: {05631532-B65C-45AF-BB49-F237ACB6CF7C} + memberId: {0C33B8DA-F55A-4F85-BA95-CCD84C4E7F59} + state: Normal + startVersion: v24 + authRebuilding: 0 + stageVolumeSerialNumber: 3a34b62834b5e753 + stageFid: 0x100000000A77F + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080627 11:57:29.045 3748 CSMG 2829 ContentSetManager::InitialSyncComplete Finished initial sync. csId: {05631532-B65C-45AF-BB49-F237ACB6CF7C}. transition from InitialSync(Cleanup) to Normal <Downstream> 20080627 11:57:29.045 3748 ISYN 115 InitialSyncCleanupTask::Run Exit. csId:{05631532-B65C-45AF-BB49- F237ACB6CF7C} remoteAddress:2008mem01.fabrikam.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008mem01.fabrikam.com] Understanding DFSR debug logging (Part 14: A sharing violation due to a file locked upstream between two Windows Server 2008) In this scenario we will see file that is locked by an application, preventing replication from occurring. The upstream replicated folder will contain a file that does not yet exist on the downstream member. This is useful to understand as one of the most common troubleshooting areas in DFSR is in the area of sharing violation events. (lockedfileupstream - Dfsr00026 - 2008.log and lockedfiledownstream - Dfsr00023 - 2008.log) These are two Windows Server 2008 servers called 2008MEM01 and 2008MEM02 in the fabrikam.com domain. The logs are from 2008MEM01 (upstream) and from 2008MEM02 (downstream). Both servers are participating in the NEWRG1 replication group for the NEWRF1 replicated folder. The locked file is called “setup.exe” and the file has been exclusively write-locked with a file utility to simulate the scenario. These two debug logs have been significantly trimmed to remove extraneous entries caused by the repro requirements. <Upstream> 20080627 15:50:40.249 3616 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: A file needs to be replicated out + fid 0x500000000AC91 + usn 0xa9fe38 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080627 19:50:35.032 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 UID/GVSN match so this is an original file creation (in DFSR terms – if a file is copied into a replicated folder it is ‘created’ in DFSR terms). + parent {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080627 19:50:03.186 GMT (0x1c8d88efd9bd3de) + createTime 20080627 19:50:02.815 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name setup.exe the file is named setup.exe + <Upstream> 20080627 15:50:40.249 3616 JOIN 1167 Join::SubmitUpdate Sent: uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 name:setup.exe connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} csName:NewRF1 the upstream server submits update to its downstream partner <Downstream> 20080627 15:50:40.262 2424 DOWN 5186 [ERROR] DownstreamTransport::RdcGet Failed on connId:{FFC8C463-846D- 4C16-8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} rgName:NewRG1 update: the downstream server attempts to initiate replication of the file through RDC but receives an error + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + parent {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080627 19:50:03.186 GMT (0x1c8d88efd9bd3de) + createTime 20080627 19:50:02.815 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name setup.exe + Error: + [Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1096 2424 C A failure was reported by the remote partner] + [Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5124 2424 C A failure was reported by the remote partner] + [Error:32(0x20) DownstreamTransport::RdcGet downstreamtransport.cpp:5124 2424 W The process cannot access the file because it is being used by another process.] the specific error is that the file is exclusively locked upstream <Downstream> 20080627 15:50:40.262 2424 INCO 5599 InConnection::LogTransferActivity Failed to receive RAWGET uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 fileName:setup.exe connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} stagedSize:0 Error: another error is logged for an attempted RAWGET of the same file + [Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5201 2424 C A failure was reported by the remote partner] + [Error:9027(0x2343) RpcFinalizeContext downstreamtransport.cpp:1096 2424 C A failure was reported by the remote partner] + [Error:9027(0x2343) DownstreamTransport::RdcGet downstreamtransport.cpp:5124 2424 C A failure was reported by the remote partner] + [Error:32(0x20) DownstreamTransport::RdcGet downstreamtransport.cpp:5124 2424 W The process cannot access the file because it is being used by another process.] the file lock error is logged again <snipped out repeated attempts to replicate with same in use errors, for readability> <Upstream> 20080627 15:50:40.269 3132 SRTR 1880 SERVER_RequestVersionVector Received from connId:{FFC8C463-846D-4C16- 8B37-19978C20FF8B} csId:{05631532-B65C-45AF-BB49-F237ACB6CF7C} seqNumber:3 changeType:notify <Upstream> 20080627 15:50:40.269 1248 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080627 15:50:40.279 3476 SRTR 1927 SERVER_AsyncPoll Received from connId:{D7E7B14C-8DE9-4198-BA51- B8D13867171D} <Upstream> 20080627 15:50:40.279 2932 OUTC 784 OutConnection::OpenFile Received request for update: there are repeated requests from the downstream to the upstream server to replicate the file + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + parent {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080627 19:50:03.186 GMT (0x1c8d88efd9bd3de) + createTime 20080627 19:50:02.815 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name setup.exe + rdcDesired:1 connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rgName:NewRG1 <Upstream> 20080627 15:50:40.279 2932 STAG 987 StageWriter::AbortDownloadStage Successfully aborted staging file 95- {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95-{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95-Downloading.frx. Deleted. after a number of attempts upstream to stage the file, the attempt is finally aborted. This is not a permanent condition, the DFSR service will try again later after waiting in the hopes that the file will unlock. <Upstream> 20080627 15:50:40.279 2932 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Upstream> 20080627 15:50:40.279 2932 EVNT 725 EventLog::Report Logging eventId:4304 parameterCount:8 a 4304 sharing violation (exclusive file lock) warning is logged in the event log. <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter1:05631532-B65C-45AF-BB49- <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter2:C:\NewRF1\setup.exe <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter3:C:\NewRF1 <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter4:{EDE2D64E-1306-4C7C- <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter5:NewRF1 <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter6:NewRG1 <Upstream> 20080627 15:50:40.279 2932 EVNT 745 EventLog::Report eventId:4304 parameter7:33DACEEE-D60C-4BF1-911C- 745 EventLog::Report eventId:4304 parameter8:5EF77FE2-B1BF-41B4-9DA6- F237ACB6CF7C B568-449A98371AA2}-v95 EA5C487A78CB <Upstream> 20080627 15:50:40.279 2932 EVNT 51F6549F523E <Upstream> 20080627 15:50:40.300 2932 SRTR 2344 [WARN] InitializeFileTransferAsyncState::ProcessIoCompletion Failed connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} rdc:1 uid:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 gsvn:{EDE2D64E-13064C7C-B568-449A98371AA2}-v95 Error: + [Error:32(0x20) UpstreamTransport::OpenFile upstreamtransport.cpp:1117 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) OutConnection::OpenFile outconnection.cpp:1618 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) OutConnection::GetReplicaReader outconnection.cpp:2289 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) NtfsFileSystem::MakeBackupReader ntfsfilesystem.cpp:526 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) MarshalFileReader::OpenFileId marshaller.cpp:4991 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) Marshaller::OpenSourceFile marshaller.cpp:4334 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) Marshaller::InitSourceFile marshaller.cpp:4205 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) MarshalContext::OpenFileForInfo marshaller.cpp:3320 2932 W The process cannot access the file because it is being used by another process.] + [Error:32(0x20) MarshalContext::OpenFileForInfo marshaller.cpp:3237 2932 W The process cannot access the file because it is being used by another process.] completion:0 ptr:00E77D48 <snipped out repeated attempts to replicate with same in use errors, for readability> <Downstream> 20080627 15:50:55.300 2424 MEET 1207 Meet::Install Retries:4 updateName:setup.exe uid:{EDE2D64E-1306-4C7C- B568-449A98371AA2}-v95 gvsn:{EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 connId:{FFC8C463-846D-4C16-8B37-19978C20FF8B} csName:NewRF1 updateType:remote the downstream server has tried to replicate the file four times by now. <Upstream> 20080627 15:51:06.357 2932 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: the file hash can finally be added to the DFSR database upstream as the file has been unlocked. + fid 0x500000000AC91 + usn 0xa9fe38 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080627 19:50:35.032 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + uid {EDE2D64E-1306-4C7C-B568-449A98371AA2}-v95 + parent {05631532-B65C-45AF-BB49-F237ACB6CF7C}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080627 19:50:02.815 GMT + csId {05631532-B65C-45AF-BB49-F237ACB6CF7C} + hash 324AE6CC-5F635DEF-31E86733-00737CAA + similarity 1511151F-0C323F1B-0216212C-09171E20 + name setup.exe 20080627 19:50:03.186 GMT (0x1c8d88efd9bd3de) + replication will proceed normally from this point. Understanding DFSR debug logging (Part 15: Pre-Seeded Data Usage during Initial Sync) In this scenario we will see a new replication group and replicated folder created, where data has been preseeded (i.e. pre-staged) on both servers. This is a common scenario, where data has existed on a few servers and been kept in sync through other mechanisms than DFSR (such as robocopy). It’s also often used when building new DFSR servers in a depot to save initial sync time before deploying the server to the field. (preseedupstream - Dfsr00012 - 2008.log and preseeddownstream - Dfsr00014 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The logs are from 2008x86SRV10 where the file is created (upstream) and from 2008x86SRV11 where it is replicated (downstream). Both servers are participating in the SeededRG replication group for the PreseededRF replicated folder. The upstream server contains files ‘matched.dll’ (which has an identical file pre-seeded on the downstream) and ‘samenameonly.dll’ (which has the same name and path on the downstream but differs in its contents slightly). The downstream server also contains file ‘onlydownstream.dll’ which does not exist on the upstream and will be covered by pre-existing logic. <Upstream> 20080910 16:22:24.423 2928 VLMG 1158 VolumeManager::Initialize Volume initialized. volId:\\.\C: <Upstream> 20080910 16:22:24.423 3392 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{7F8CFBB0-4973- 4B53-AAD5-3328870036FB} state:InitialBuilding New replica set is being built <Upstream> 20080910 16:22:24.501 3392 CSMG 3182 ContentSetManager::CreateRootRecord Adding root record csId:{7F8CFBB0- 4973-4B53-AAD5-3328870036FB} csName:preseededrf ghosted:0 <Upstream> 20080910 16:22:24.517 3392 CSMG 3298 ContentSetManager::CreateRootRecord LDB Inserting ID Record: The DFSR database has a base record added for the new replica set. + fid 0x80000000000B3 + usn 0x27f3650 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 + uid {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080910 17:14:04.242 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name preseededrf name of the replicated folder 20080910 19:14:41.883 GMT (0x1c913797a31f6a8) + <Upstream> 20080910 16:22:24.657 3392 LDBX 4028 Ldb::Insert Inserting contentSetRecord: The replicated folder record is add into the database + contentSetId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + memberId: {D964421D-59F0-434C-8826-ED91D268B143} + state: InitialBuilding The RG is in an initial building state + startVersion: v9 + authRebuilding: 0 + stageVolumeSerialNumber: 0 + stageFid: 0x0 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080910 16:22:24.970 3392 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 0 <Upstream> 20080910 16:22:24.970 3392 STAG 6158 StagingManager::RegisterContentSetsOnPath {7F8CFBB0-4973-4B53-AAD5- 3328870036FB} added to the replicated folder list. <Upstream> 20080910 16:22:24.970 3392 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + memberId: {D964421D-59F0-434C-8826-ED91D268B143} + state: InitialBuilding + startVersion: v9 + authRebuilding: 0 + stageVolumeSerialNumber: 48e8de48e8de33c2 + stageFid: 0x500000000BA72 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080910 16:22:25.017 2444 VLMG 1391 VolumeManager::ScanForSimilarity Begin scanning DB for similarity data. volId:\\.\C: <Upstream> 20080910 16:22:25.017 2444 VLMG 1474 VolumeManager::ScanForSimilarity End scanning DB for similarity data. volId:\\.\C: <Upstream> 20080910 16:22:25.079 3392 CSMG 1274 ContentSetManager::Initialize Walk replica set to initialize or fix up database. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf Now the DFSR service must walk all the folders and files in the replicated folder and add them to the database and USN journal. <Upstream> 20080910 16:22:25.079 3392 DIRW 515 DirWalkerTask::QueueMoveinJob Queuing move-in. uid:{7F8CFBB0-4973-4B53- AAD5-3328870036FB}-v1 fid:0x80000000000B3 name:preseededrf <Upstream> 20080910 16:22:25.079 3392 DIRW 256 DirWalkerTask::Run Start walking directory. <Upstream> 20080910 16:22:25.079 3392 DIRW 945 DirWalkerTask::MoveinStep Starting to process move-in job. uid:{7F8CFBB0- 4973-4B53-AAD5-3328870036FB}-v1 the Dir Walker (which finds all files and folders) is now executing. <Upstream> 20080910 16:22:25.079 3392 DIRW 2428 DirWalkerTask::CreateOneRecord LDB Inserting ID Record: our first file is added into the DFSR database. + fid 0x90000000000B6 + usn 0x27f2eb8 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 UID and GVSN will match because the file has never been modified in the lifetime of this content set on this server. + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:15:13.698 GMT (0x1c91368c99fb791) + createTime 20080910 17:15:05.932 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name matched.dll this is the file which will be identical on the downstream server + <Upstream> 20080910 16:22:25.079 3392 DIRW 2428 DirWalkerTask::CreateOneRecord LDB Inserting ID Record: The next file on the upstream server is added to the DFSR database + fid 0x60000000000B4 + usn 0x27fe1c8 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 UID and GVSN will match because the file has never been modified in the lifetime of this content set on this server. + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:57:01.398 GMT (0x1c9137f63dd4325) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name samenameonly.dll this is the file which will be binarily slightly different on the downstream server (but same name, path, security, attributes) + <Upstream> 20080910 16:22:25.079 3392 DIRW 101 DirWalkerTask::Job::Finish MoveIn csId:{7F8CFBB0-4973-4B53-AAD5- 3328870036FB} uid:{7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 both of the files on the upstream server have been found by the dirwalker. <Upstream> 20080910 16:22:25.079 3392 DIRW AAD5-3328870036FB}-v1 793 DirWalkerTask::RemoveJob Removing job type:1 uid:{7F8CFBB0-4973-4B53- <Upstream> 20080910 16:22:25.079 3392 LDBX 4386 Ldb::DeleteWalkerJob Deleting dirWalkerJob. uid:{7F8CFBB0-4973-4B53-AAD5- 3328870036FB}-v1 725 EventLog::Report Logging eventId:4112 parameterCount:6 The upstream <Upstream> 20080910 16:22:25.095 3392 EVNT DFSR server must now log 4412 event (in the DFSR event log) so that it is done with initial building tasks and is ready to serve files to downstream partners. The replicated folder is initialized. <Upstream> 20080910 16:22:25.095 3392 EVNT 745 EventLog::Report eventId:4112 parameter1:7F8CFBB0-4973-4B53-AAD5- <Upstream> 20080910 16:22:25.095 3392 EVNT 745 EventLog::Report eventId:4112 parameter2:C:\preseededrf <Upstream> 20080910 16:22:25.095 3392 EVNT 745 EventLog::Report eventId:4112 parameter3:preseededrf <Upstream> 20080910 16:22:25.095 3392 EVNT 745 EventLog::Report eventId:4112 parameter4:SeededRG <Upstream> 20080910 16:22:25.095 3392 EVNT 745 EventLog::Report eventId:4112 parameter5:19AFE009-299A-417C-A0AA- 745 EventLog::Report eventId:4112 parameter6:D964421D-59F0-434C-8826- 3328870036FB E43178ECC158 <Upstream> 20080910 16:22:25.095 3392 EVNT ED91D268B143 <Upstream> 20080910 16:22:25.095 3392 CSMG 4599 ContentSetManager::UpdateRootFence LDB Updating ID Record: A ‘fence’ is set which marks a content set as authoritative for all conflicts + fid 0x80000000000B3 + usn 0x27f3650 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:24.517 GMT + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 + uid {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080910 17:14:04.242 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name preseededrf 20080910 19:14:41.883 GMT (0x1c913797a31f6a8) + <Upstream> 20080910 16:22:25.095 3392 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} newState:Normal (auth:0) the content set state is now set to Normal on the upstream server, meaning that it is done with initial sync/initial building operations locally and is ready to serve files to all partners. <Upstream> 20080910 16:22:25.095 3392 LDBX 4062 Ldb::Update Updating contentSetRecord: Normal state is set + contentSetId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + memberId: {D964421D-59F0-434C-8826-ED91D268B143} + state: Normal + startVersion: v9 + authRebuilding: 0 + stageVolumeSerialNumber: 48e8de48e8de33c2 + stageFid: 0x500000000BA72 + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Upstream> 20080910 16:22:25.173 3392 CSMG 2697 ContentSetManager::DbBuildComplete Finished scanning content set and building database info: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} Transition from InitialBuilding to Normal <Upstream> 20080910 16:22:25.173 3392 DIRW 303 DirWalkerTask::Run Exit. <snipped out long step of contacting other server successfully, getting ready to work – this is documented in previous scenarios> <Upstream> 20080910 16:22:32.142 3392 EVNT 1126 EventLog::AuditInstall Audit source was found <Upstream> 20080910 16:22:32.142 3392 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080910 16:22:32.142 3392 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: database is updated to include similarity and hash information + fid 0x90000000000B6 + usn 0x27f2eb8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:25.079 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:15:13.698 GMT (0x1c91368c99fb791) + createTime 20080910 17:15:05.932 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 12DEDDE4-FEE039FA-807CA87E-6A3BD51A hash is set and can be used for comparison purposes with any downstream copies of the file to avoid/require replication. + similarity 331B142E-143C3835-0A240739-230C1618 + name matched.dll + <Upstream> 20080910 16:22:32.158 3392 JOIN 1167 Join::SubmitUpdate Sent: uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 name:matched.dll connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf the update information for matched.dll is sent to the downstream partner. <Upstream> 20080910 16:22:32.158 3392 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Upstream> 20080910 16:22:32.158 3392 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: Hash/similarity information is added to the DFSR database for the other file, samenameonly.dll. This file is similar to the downstream partner (as we will see) in that it has same name, path, and most of its data is identical. + fid 0x60000000000B4 + usn 0x27fe1c8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:25.079 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:57:01.398 GMT (0x1c9137f63dd4325) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 72D6A531-D011696C-D6D0983A-D953F419 + similarity 06190414-382A030F-142D3A1A-10243A3F + name samenameonly.dll + <Upstream> 20080910 16:22:32.158 3392 JOIN 1167 Join::SubmitUpdate Sent: uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 name:samenameonly.dll connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf As above, update information sent to downstream partner regarding the samenameonly.dll. <Upstream> 20080910 16:22:32.158 1724 OUTC 784 OutConnection::OpenFile Received request for update: + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 + uid {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:14:41.883 GMT (0x1c913797a31f6a8) + createTime 20080910 17:14:04.242 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 138816B1-4218E5A2-D9B2A1F3-8A52E6A4 + similarity 00000000-00000000-00000000-00000000 + name preseededrf + rdcDesired:1 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} rgName:SeededRG 20080910 16:22:32.158 1724 OUTC 1534 OutConnection::OpenFile Sent file uid:{7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 name:preseededrf fileSize:312 connId:{EB1242D3-E048-4212-AECF3C703EE2CC92} rgName:SeededRG <Upstream> 20080910 16:22:32.158 1724 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x10 <Upstream> 20080910 16:22:32.158 1724 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} rdc:1 context:00000000,00000000,00000000 uid:{7F8CFBB0-4973-4B53-AAD53328870036FB}-v1 gvsn{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 ptr:008F2B28 <Upstream> 20080910 16:22:32.158 3680 SRTR 1880 SERVER_RequestVersionVector Received from connId:{EB1242D3-E048-4212- AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} seqNumber:3 changeType:notify <Downstream> 20080910 16:22:32.244 1708 MEET 3358 Meet::InstallOverwrite Moving away content that is in the way updateName:preseededrf uid:{7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf <Downstream> 20080910 16:22:32.244 1708 NTFS 1257 NtfsFileSystem::SetAttributes oldFileAttributes:0x10 newFileAttributes:0x10 <Downstream> 20080910 16:22:32.244 1708 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: + fid 0x100000000000B3 + usn 0x2a60648 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 + uid {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:14:41.883 GMT (0x1c913797a31f6a8) + createTime 20080910 17:14:04.242 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 138816B1-4218E5A2-D9B2A1F3-8A52E6A4 + similarity 00000000-00000000-00000000-00000000 + name preseededrf + <Downstream> 20080910 16:22:32.244 1708 MEET 3431 Meet::InstallOverwrite -> DONE Install-overwrite completed updateName:preseededrf uid:{7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.244 1708 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080910 16:22:32.244 1708 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:2 processed:1 failures:0 sessionId:1 open:0 updateType:0 processStatus:0 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf update: + present 1 + nameConflict 0 + attributes 0x10 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v10 + uid {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + parent {00000000-0000-0000-0000-000000000000}-v0 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:14:41.883 GMT (0x1c913797a31f6a8) + createTime 20080910 17:14:04.242 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 138816B1-4218E5A2-D9B2A1F3-8A52E6A4 + similarity 00000000-00000000-00000000-00000000 + name preseededrf + <Downstream> 20080910 16:22:32.244 1708 MEET 1207 Meet::Install Retries:0 updateName:matched.dll uid:{F96F1AF0-1F39-4EDB- 8493-590B7A9E44EC}-v11 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf updateType:remote this is misleading – the file is not actually replicated at this point, but the log entry will occur even if the file is a perfect match. You will note as you read further down that there is no “MoveOut Moving contents and children out of replica” or “Download Succeeded” referencing the ‘matched.dll’ file, because no bits went on the wire other than metadata. <Downstream> 20080910 16:22:32.244 1708 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Downstream> 20080910 16:22:32.244 1708 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: downstream server now must insert the hash information into its DFSR database regarding the matched.dll file. If these matched, there is no reason to replicate the file. + fid 0x120000000000B7 + usn 0x2a4cc38 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:22.071 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v10 + uid {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v10 the downstream server is now using the UID and GVSN information from the upstream server. Whatever was there locally before is discarded. + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:16:00.023 GMT (0x1c91368e53c4ffb) + createTime 20080910 17:16:00.023 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 12DEDDE4-FEE039FA-807CA87E-6A3BD51A note the match from the hash on the upstream server in previous log entries. + similarity 331B142E-053C3835-0A240739-230C1618 + name matched.dll + <Downstream> 20080910 16:22:32.244 3924 MEET 1207 Meet::Install Retries:0 updateName:samenameonly.dll uid:{F96F1AF0-1F39- 4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf updateType:remote metadata about the samenameonly.dll file is being sent. <Downstream> 20080910 16:22:32.244 3924 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Downstream> 20080910 16:22:32.244 3924 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: Hash must be recorded in DB for the files in order to compare with an upstream copy + fid 0x400000000BBDD + usn 0x2a4f650 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:22.071 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12 + uid {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:45:57.275 GMT (0x1c9136d147b4a51) + createTime 20080910 17:16:00.023 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash D2FCA79F-B5F5B8D1-1DA18CD4-2BFE9249 note that the hash does not match what was on the upstream server version of the file. + similarity 06190401-382A030F-142D3A1A-10243A3F + name samenameonly.dll + <Downstream> 20080910 16:22:32.244 2600 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{EB1242D3-E048- 4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.259 1708 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: the ‘matched.dll’ database entry must now be updated to include the new GVSN/UID from the upstream + fid 0x120000000000B7 + usn 0x2a4cc38 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:22.071 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v10 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:16:00.023 GMT (0x1c91368e53c4ffb) + createTime 20080910 17:15:05.932 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 12DEDDE4-FEE039FA-807CA87E-6A3BD51A + similarity 331B142E-053C3835-0A240739-230C1618 + name matched.dll + <Downstream> 20080910 16:22:32.259 1708 NTFS 1257 NtfsFileSystem::SetAttributes oldFileAttributes:0x20 newFileAttributes:0x20 <Downstream> 20080910 16:22:32.259 1708 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: UID/GVSN synced in database on downstream + fid 0x120000000000B7 + usn 0x2a60908 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 GVSN/UID match now on the downstream partner for the ‘matched.dll’ file + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:15:13.698 GMT (0x1c91368c99fb791) + createTime 20080910 17:15:05.932 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 12DEDDE4-FEE039FA-807CA87E-6A3BD51A + similarity 331B142E-143C3835-0A240739-230C1618 + name matched.dll + <Downstream> 20080910 16:22:32.259 1708 MEET 3589 Meet::InstallMove -> DONE Install-move completed updateName:matched.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 connId:{EB1242D3-E048-4212AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} the ‘replication’ of the matched.dll file is now completed. This means that all the metadata about this file is now in sync between the upstream and downstream servers. <Downstream> 20080910 16:22:32.259 1708 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:1 processed:2 failures:0 sessionId:1 open:0 updateType:0 processStatus:0 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf update: All work for the ‘matched.dll’ is now done. + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v11 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:15:13.698 GMT (0x1c91368c99fb791) + createTime 20080910 17:15:05.932 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 12DEDDE4-FEE039FA-807CA87E-6A3BD51A + similarity 331B142E-143C3835-0A240739-230C1618 + name matched.dll + <Downstream> 20080910 16:22:32.259 1708 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{EB1242D3-E048- 4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.259 3924 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: Now the DFSR database record must be updated for the ‘samenameonly.dll’ + fid 0x400000000BBDD + usn 0x2a4f650 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:22.071 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12 GVSN does not yet match + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 UID now set to match via some replication of the metadata + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:45:57.275 GMT (0x1c9136d147b4a51) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash D2FCA79F-B5F5B8D1-1DA18CD4-2BFE9249 Hash does not match + similarity 06190401-382A030F-142D3A1A-10243A3F + name samenameonly.dll + <Downstream> 20080910 16:22:32.259 3924 MEET 5674 Meet::LocalDominates Conflicting gvsn:{F2A45CDC-59A7-472A-AECC- FD10628F046B}-v12 updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf Conflict resolution must occur as the downstream server will lose all conflicts in an initial sync scenario. Review the ‘Conflicted file’ scenario above for more details. Remember that this event can be misleading as it implies the local copy of the file is going to win – this is just the function name, not the actual action. 784 OutConnection::OpenFile Received request for update: Upstream server <Upstream> 20080910 16:22:32.267 2304 OUTC receives a request from downstream to replicate the samenameonly.dll because they do not match + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 72D6A531-D011696C-D6D0983A-D953F419 + similarity 06190414-382A030F-142D3A1A-10243A3F + name samenameonly.dll + rdcDesired:1 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} rgName:SeededRG 20080910 19:57:01.398 GMT (0x1c9137f63dd4325) <Downstream> 20080910 16:22:32.337 3924 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Downstream> 20080910 16:22:32.431 3924 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080910 16:22:32.431 3924 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 12- {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12-{F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12-Downloaded.frx <Downstream> 20080910 16:22:32.540 3924 ASYN 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: <Downstream> 20080910 16:22:32.540 3924 RDCX 1811 Rdc::SyncClientState::Flush Rdc Need Assembler Statistics: uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 fileName:samenameonly.dll connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} Because the file was preseeded, we have the option to use RDC in this scenario (unlike a raw initial sync with no data on the downstream partner). Upstream requests RDC bits based on signatures exchanged previously. + TOTAL + Compression Ratio + Target Uncompress Size 69847 + Target Compress Size 34383 + Bytes Received + Signature Bytes Received + Number of remote calls + SEED + Rdc Need Size 0 0 + Xpress Blocks 9 9 51 3444 Signatures: 528 528 Data: 2916 528 4 Signatures: 1 Needs: 1 Data: 2 + Uncompressed Xpress Blocks 2 2 + Blocks copied to target 7 7 + SOURCE + Rdc Need Size 4106 0 + Xpress Blocks 2 0 + Uncompressed Xpress Blocks 1 0 + Blocks copied to target 0 0 <Downstream> 20080910 16:22:32.540 3924 INCO 5610 InConnection::LogTransferActivity Received RDCGET uid:{F96F1AF0-1F39- 4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 fileName:samenameonly.dll connId:{EB1242D3E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} stagedSize:34495 RDC information logged for performance monitoring purposes <Downstream> 20080910 16:22:32.540 3924 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080910 16:22:32.540 3924 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 12- {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12-{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12-Downloaded.frx the updated file is reassembled in the downstream staging folder. Only the different bits were sent over the wire <Downstream> 20080910 16:22:32.540 3924 MRSH 3959 MarshalContext::Initialize Create file:[samenameonly-{F96F1AF0-1F39- 4EDB-8493-590B7A9E44EC}-v12.dll] with attributes:0x20 <Downstream> 20080910 16:22:32.540 3924 MEET 2585 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf the file is copied to the Installing directory <Downstream> 20080910 16:22:32.540 1708 STAG 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.540 3924 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080910 16:22:32.540 3924 MEET 2032 Meet::Download Download Succeeded : true updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} replication of the file is complete as far as the upstream is concerned <Downstream> 20080910 16:22:32.540 3924 MEET 5674 Meet::LocalDominates Conflicting gvsn:{F2A45CDC-59A7-472A-AECC- FD10628F046B}-v12 updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf the file is going to be conflicted and the original downstream version moved into the ConflictAndDeleted folder. <Downstream> 20080910 16:22:32.540 3924 MEET 2772 Meet::InstallRename Move out previous version of same file updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf older file to be supplanted <Downstream> 20080910 16:22:32.540 3924 MEET 4867 Meet::MoveOut Moving contents and children out of replica. newName:samenameonly-{F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12.dll updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf record: older version of the file is now being moved to the ConflictAndDeleted folder. The ConflictAndDeletedManifest.xml will be updated. + fid 0x400000000BBDD + usn 0x2a4f650 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 20:22:22.071 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 (I) + clockDecrementedInDirtyShutdown 0 + clock 20080910 17:45:57.275 GMT (0x1c9136d147b4a51) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash D2FCA79F-B5F5B8D1-1DA18CD4-2BFE9249 + similarity 06190401-382A030F-142D3A1A-10243A3F + name samenameonly.dll + 725 EventLog::Report Logging eventId:4412 parameterCount:9 event logged <Downstream> 20080910 16:22:32.540 3924 EVNT in the DFSR event log marking the conflict operation having occurred and this downstream server as having lost. <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter1:7F8CFBB0-4973-4B53- 745 EventLog::Report eventId:4412 AAD5-3328870036FB <Downstream> 20080910 16:22:32.540 3924 EVNT parameter2:C:\preseededrf\samenameonly.dll <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter3:C:\preseededrf <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter4:{F96F1AF0-1F39-4EDB- 8493-590B7A9E44EC}-v12 <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter5:preseededrf <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter6:SeededRG <Downstream> 20080910 16:22:32.540 3924 EVNT 745 EventLog::Report eventId:4412 parameter7:19AFE009-299A-417C- 745 EventLog::Report eventId:4412 parameter8:FFB459B6-EB2D-4DEB- 745 EventLog::Report eventId:4412 parameter9:samenameonly- A0AA-E43178ECC158 <Downstream> 20080910 16:22:32.540 3924 EVNT 911F-D948C4FDEF6E <Downstream> 20080910 16:22:32.540 3924 EVNT {F2A45CDC-59A7-472A-AECC-FD10628F046B}-v12.dll <Downstream> 20080910 16:22:32.540 3924 MEET 2837 Meet::InstallRename File moved. rootVolume:{3C84BB07-22D1-11DD-862B- 806E6F6E6963} parentFid:0x100000000000B3 fidInInstalling:0x400000000B9F3 usn:0x2a631d0 updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212AECF-3C703EE2CC92} csName:preseededrf The new version of the file is moved into the replicated folder. <Downstream> 20080910 16:22:32.540 3924 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: DFSR database updated to reflect all current information about the file now that it is fully replicated and available to end users. + fid 0x400000000B9F3 + usn 0x2a631d0 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 Note GVSN and UID now match and are identical to what was on the upstream server + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:57:01.398 GMT (0x1c9137f63dd4325) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 72D6A531-D011696C-D6D0983A-D953F419 Hash now matches upstream + similarity 06190414-382A030F-142D3A1A-10243A3F + name samenameonly.dll + <Downstream> 20080910 16:22:32.540 3924 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:samenameonly.dll uid:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 gvsn:{F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.540 3924 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:3 failures:0 sessionId:1 open:0 updateType:0 processStatus:0 connId:{EB1242D3-E048-4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf update: + present + nameConflict 1 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + uid {F96F1AF0-1F39-4EDB-8493-590B7A9E44EC}-v12 + parent {7F8CFBB0-4973-4B53-AAD5-3328870036FB}-v1 + fence 16010101 00:00:00.000 P + clockDecrementedInDirtyShutdown 0 + clock 20080910 19:57:01.398 GMT (0x1c9137f63dd4325) + createTime 20080910 17:15:05.916 GMT + csId {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + hash 72D6A531-D011696C-D6D0983A-D953F419 + similarity 06190414-382A030F-142D3A1A-10243A3F + name samenameonly.dll + <Downstream> 20080910 16:22:32.540 3924 ISYN 65 InitialSyncManager::ReturnToken InitialSync sync step finished. Delete all session tasks. <Downstream> 20080910 16:22:32.540 3924 CSMG 2746 ContentSetManager::InitialSyncStepSyncComplete InitialSync sync step completed. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} transition from InitialSync(Sync) to InitialSync(Cleanup). <Downstream> 20080910 16:22:32.540 3924 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} newState:InitialSync(Cleanup) (auth:0) <Downstream> 20080910 16:22:32.540 3924 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + memberId: {FFB459B6-EB2D-4DEB-911F-D948C4FDEF6E} + state: InitialSync(Cleanup) + startVersion: v9 + authRebuilding: 0 + stageVolumeSerialNumber: 48e8de48e8de33c2 + stageFid: 0x400000000B9EE + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080910 16:22:32.540 3924 INCO 6194 InConnection::CommitSession Connection in sync connId:{EB1242D3-E048- 4212-AECF-3C703EE2CC92} csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf commitedSessionsWithUpdateFailures:0 <Downstream> 20080910 16:22:32.540 3924 UPMG 418 UpdateWorker::ConsumeUpdates No pending updates. connId:{EB1242D3-E048- 4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.540 1708 CSMG 1757 ContentSetManager::Run csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf state:InitialSync(Sync) <Downstream> 20080910 16:22:32.540 1708 UPMG 535 UpdateManager::Finalize Finalizing UpdateManager connId:{EB1242D3-E048- 4212-AECF-3C703EE2CC92} csName:preseededrf csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} <Downstream> 20080910 16:22:32.540 1708 CSMG 1779 ContentSetManager::Run Scheduling restart now csId:{7F8CFBB0-4973-4B53- AAD5-3328870036FB} csName:preseededrf ptr:00ED9340 <Downstream> 20080910 16:22:32.540 1708 CSMG 1757 ContentSetManager::Run csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf state:InitialSync(Sync) <Downstream> 20080910 16:22:32.540 1708 CSMG 837 ContentSetManager::Initialize csId:{7F8CFBB0-4973-4B53-AAD5- 3328870036FB} csName:preseededrf ptr:00ED9340 <Downstream> 20080910 16:22:32.540 1708 CSMG 2262 ContentSetManager::CheckContentSetState Updating content set record csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} csName:preseededrf ghosted:0 readOnly:0 readOnlySince:16010101 00:00:00.000 <Downstream> 20080910 16:22:32.540 1708 CSMG 2298 ContentSetManager::CheckContentSetState Content set csId:{7F8CFBB0- 4973-4B53-AAD5-3328870036FB} state:InitialSync(Cleanup) <Downstream> 20080910 16:22:32.556 1708 STAG 2600 Staging::ScanStagingDirectory Staging space usage is: 40960 <Downstream> 20080910 16:22:32.556 1708 CSMG 2769 ContentSetManager::StartInitialSyncCleanup csId:{7F8CFBB0-4973-4B53- AAD5-3328870036FB} now any pre-existing files must be removed. <Downstream> 20080910 16:22:32.556 3924 ISYN <Downstream> 20080910 16:22:32.556 3924 ISYN 97 InitialSyncCleanupTask::Run csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} 364 InitialSyncCleanupTask::MoveOut Moving \\.\C:\preseededrf\onlydownstream.dll to pre-existing:0x400000000B9F4 csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} the ‘onlydownstream.dll’ file (which did not exist on the downstream) is now moved into PreExisting folder and the PreExistingManifest.XML is updated. <Downstream> 20080910 16:22:32.556 3924 CSMG 5884 ContentSetManager::DeleteChildren LDB Deleting ID Record. uid:{F2A45CDC-59A7-472A-AECC-FD10628F046B}-v11 Any references to the preexisting file are removed from the DFSR database. <Downstream> 20080910 16:22:32.556 3924 CSMG 2785 ContentSetManager::InitialSyncStepCleanupComplete InitialSync cleanup step completed. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} transition from InitialSync(Cleanup) to Normal no further preexisting files found. <Downstream> 20080910 16:22:32.556 3924 EVNT 725 EventLog::Report Logging eventId:4104 parameterCount:6 A 4104 event is logged in the DFSR event log to show that the initial sync is done downstream and the server is entering normal replication mode for this content set. <Downstream> 20080910 16:22:32.556 3924 EVNT 745 EventLog::Report eventId:4104 parameter1:7F8CFBB0-4973-4B53- <Downstream> 20080910 16:22:32.556 3924 EVNT 745 EventLog::Report eventId:4104 parameter2:C:\preseededrf <Downstream> 20080910 16:22:32.556 3924 EVNT 745 EventLog::Report eventId:4104 parameter3:preseededrf <Downstream> 20080910 16:22:32.556 3924 EVNT 745 EventLog::Report eventId:4104 parameter4:SeededRG <Downstream> 20080910 16:22:32.556 3924 EVNT 745 EventLog::Report eventId:4104 parameter5:19AFE009-299A-417C- 745 EventLog::Report eventId:4104 parameter6:FFB459B6-EB2D-4DEB- AAD5-3328870036FB A0AA-E43178ECC158 <Downstream> 20080910 16:22:32.556 3924 EVNT 911F-D948C4FDEF6E <Downstream> 20080910 16:22:32.556 3924 CSMG 2897 ContentSetManager::SetContentSetState Set content set state. csId:{7F8CFBB0-4973-4B53-AAD5-3328870036FB} newState:Normal (auth:0) state now normal, no more fencing or initial sync. <Downstream> 20080910 16:22:32.556 3924 LDBX 4062 Ldb::Update Updating contentSetRecord: + contentSetId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB} + memberId: {FFB459B6-EB2D-4DEB-911F-D948C4FDEF6E} + state: Normal + startVersion: v9 + authRebuilding: 0 + stageVolumeSerialNumber: 48e8de48e8de33c2 + stageFid: 0x400000000B9EE + isTombstone: 0 + readOnlySince: 16010101 00:00:00.000 + beingDeleted: 0 + dbLossRecover: 0 + <Downstream> 20080910 16:22:32.556 3924 CSMG 2829 ContentSetManager::InitialSyncComplete Finished initial sync. csId: {7F8CFBB0-4973-4B53-AAD5-3328870036FB}. transition from InitialSync(Cleanup) to Normal initial sync is done. Understanding DFSR debug logging (Part 16: File modification with RDC in very granular detail (uses debug severity 5)) In this scenario we will see a file modified and how that change is replicated between servers, specifically in regards to RDC similarity usage. The debug log has been set to severity 5 for deeper details than usual. This is useful to understand how efficient RDC is with a given type of file during a controlled modification. It is also more useful to set this level of debug severity for specific troubleshooting so this example will show considerable detail (and chaff) compared to previous entries. (rdcupstream - Dfsr00003 - 2008.log and rdcdownstream - Dfsr00003 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The logs are from 2008x86SRV10 where the file is created (upstream) and from 2008x86SRV11 where it is replicated (downstream). Both servers are participating in the RDCRG replication group for the RDCRF replicated folder. The file is called “pooltag.txt”. The file was already replicated previously and has now been modified slightly. Before reading this scenario, please review scenario ‘File Modified on Windows Server 2003 R2’. <Downstream> 20080908 09:40:55.332 808 DOWN 1732 AsyncRpcHandler::RequestVvUp Sent on connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} reqType:VvUpRequest reqState:Pending seqNumber:10 status:0 ptr:00D832E8 <Downstream> 20080908 09:40:55.332 808 DOWN 4095 DownstreamTransport::RequestVvUp Sent on connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} rgName:RDCRG <Downstream> 20080908 09:40:55.332 808 INCO 3750 InConnection::RequestVvUp Requested upstream version vector. requestState:00D832E8 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} csName:rdcrf changeType:notify important note – these three downstream entries being written are actually happening *after* the upstream entries below. The timing is off due to the repro environment (i.e. there is no way to have a change notification occur before a file was changed naturally) <Upstream> 20080908 09:40:55.341 2880 USNC is updated to reflect a file being changed 2361 UsnConsumer::UpdateIdRecord LDB Updating ID Record: The DFSR database fid 0x300000000BA79 note the file ID for cross-reference with the USN journal + usn 0x2618a08 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 16:39:09.319 GMT + present 1 + nameConflict 0 + attributes 0x20 File, not a folder + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 The GVSN has been increased and is + entries higher than the UID. Since this is the only change that has happened since the file was created, it is incremented by one. + {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 The UID reflects that the file was uid originally created on this server (same GUID) + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} The content set ID is for the RDCRF replicated folder + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name pooltag.txt the file in question + <Upstream> 20080908 09:40:55.341 2880 RDCS 807 FrsSimilarityManager::Delete Deleteing similarity data. Vol:{3C84BB07- 22D1-11DD-862B-806E6F6E6963} FileId:0x300000000BA79 existing RDC similarity signature information deleted for the upstream copy fo the file, as it will need to be recalculated during staging. This is part of cross-file similarity only. <Upstream> 20080908 09:40:55.341 2880 USNC 2364 UsnConsumer::UpdateIdRecord ID record updated from USN_RECORD: USN update occurs on upstream partner. Technically the USN update itself occurs before, but this operation also reflects updating the DFSR database with USN information. + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000BA79 same File ID as above, it’s the same file + ParentFileRefNumber: 0x1000000000A77E + USN: 0x2618a08 + TimeStamp: 20080908 09:40:55.341 Pacific Standard Time + Reason: Close Data Extend Data Overwrite the file has been modified + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 file, not a folder + FileNameLength: 22 + FileNameOffset: 60 + FileName: pooltag.txt file is the ‘pooltag.txt’ covered by this scenario + <Upstream> 20080908 09:40:55.341 2880 LDBX 4300 Ldb::UpdateLastVersion Updating lastVersion:18 <Upstream> 20080908 09:40:55.341 2880 LDBX 3340 LdbManager::WakeUpSleepers Wake up callback 00887470 <Upstream> 20080908 09:40:55.341 2708 UPST 1399 UpstreamTransport::FlushVvUp 001A17F0 <Upstream> 20080908 09:40:55.341 2708 UPST 1417 UpstreamTransport::FlushVvUp send connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} seqNumber:8 status:0 vvGeneration:4 vvUp: <Upstream> 20080908 09:40:55.341 2632 SRTR 1880 SERVER_RequestVersionVector Received from connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} seqNumber:9 changeType:all <Upstream> 20080908 09:40:55.341 2632 SRTR 1927 SERVER_AsyncPoll Received from connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} <Upstream> 20080908 09:40:55.341 2632 UPST 1297 UpstreamTransport::AddAsyncPoll Inserted new async request rpcStatePtr:001A17F0 <Upstream> 20080908 09:40:55.341 2708 UPST 1399 UpstreamTransport::FlushVvUp 001A17F0 <Upstream> 20080908 09:40:55.341 2708 UPST 1417 UpstreamTransport::FlushVvUp send connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} seqNumber:9 status:0 vvGeneration:4 vvUp:{5CB120DE-D2C2-452A8280-B45FC155224F} |-> { 16..18} + <Upstream> 20080908 09:40:55.341 2632 SRTR 882 SERVER_RequestUpdates Received from connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} credits:32 requestType:all Upstream server receives a request from downstream to send update information <Upstream> 20080908 09:40:55.341 2632 UPST 88 UpdateBuffer::UpdateBuffer UpdateBuffer created. connId:{68E26C24-5C97- 47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Upstream> 20080908 09:40:55.341 2632 SRTR 1927 SERVER_AsyncPoll Received from connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} <Upstream> 20080908 09:40:55.341 2632 UPST 1297 UpstreamTransport::AddAsyncPoll Inserted new async request rpcStatePtr:001A11B0 <Upstream> 20080908 09:40:55.341 2708 JOIN 1167 Join::SubmitUpdate Sent: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 name:pooltag.txt connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} csName:rdcrf Upstream sends update information to the downstream server through RPC. <Upstream> 20080908 09:40:55.341 2708 UPST 145 UpdateBuffer::SubmitUpdate Update buffered. connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} updateCount:0 totalCredits:32 updateUid:{5CB120DE-D2C2452A-8280-B45FC155224F}-v17 updateGvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 <Upstream> 20080908 09:40:55.341 2708 UPST 221 UpdateBuffer::FlushUpdates Completing async updates call. connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} updateCount:1 totalCredits:32 status:0 completionStatus:0 <Upstream> 20080908 09:40:55.341 2708 UPST 98 UpdateBuffer::~UpdateBuffer UpdateBuffer deleted. connId:{68E26C24-5C97- 47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Upstream> 20080908 09:40:55.341 2632 SRTR 2136 InitializeFileTransferAsyncState::Start 00844750 <Upstream> 20080908 09:40:55.341 2036 SRTR 2177 InitializeFileTransferAsyncState::ProcessIoCompletion 00844750 <Upstream> 20080908 09:40:55.341 2036 OUTC 784 OutConnection::OpenFile Received request for update: Upstream server now prepared to serve the modified file + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name pooltag.txt + rdcDesired:1 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} rgName:RDCRG <Upstream> 20080908 09:40:55.341 2036 RDCX 639 Rdc::MyFRS_RDC_FILEINFO::ComputeRecursionDepth RecursionDepth = 1, filesize=123431 Upstream server prepares to calculate RDC data for a file <Upstream> 20080908 09:40:55.341 2036 OUTC 875 OutConnection::OpenFile rdcDesired=1, filesize=123431, rdcMinFileSizeInKb=64, rdcSignatureLevels=1 RDC configuration data (RDC should be used, file size, minimum size that RDC can be used with, how many signature levels can be used (i.e. signatures of signatures – depends on file size)) <Upstream> 20080908 09:40:55.341 2036 OUTC 2188 OutConnection::GetStageReaderOrWriter Check if the file is already staged correctly with up to date hash and signatures. In this case it’s not. + fid 0x300000000BA79 + usn 0x2618a08 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 16:40:55.341 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name pooltag.txt + Failed to get stage reader as the file is not staged notes that staging will now need to occur as the file did not already exist with the same info <Upstream> 20080908 09:40:55.341 2036 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloading (refCount==1) the file is locked in the replicated folder temporarily so that it cannot be modified while being copied into staging. <Upstream> 20080908 09:40:55.341 2036 STAG 4305 Staging::FindAllFiles Older version found:17-{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-Downloaded.frx find any older staged versions of the file so that they can be deleted prior to superseding <Upstream> 20080908 09:40:55.341 2952 SRTR 1880 SERVER_RequestVersionVector Received from connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} seqNumber:10 changeType:notify <Downstream> 20080908 09:40:55.348 2152 DOWN 2723 AsyncRpcHandler::ProcessReceive Completion. connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} reqType:VvUpRequest reqState:Completed status:0 ptr:00D832E8 <Upstream> 20080908 09:40:55.373 2036 STAG 4113 Staging::OpenForWrite name:pooltag.txt uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 file now copied into staging and compressed with XPRESS <Upstream> 20080908 09:40:55.373 2036 OUTC 2225 OutConnection::GetStageReaderOrWriter the file has been staged and is ready to be acted upon by RDC + fid 0x300000000BA79 + usn 0x2618a08 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 16:40:55.341 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name pooltag.txt + StageReader:00000000 StageWriter:0083F750 Policy:0 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) <Upstream> 20080908 09:40:55.373 2036 RDCX 639 Rdc::MyFRS_RDC_FILEINFO::ComputeRecursionDepth RecursionDepth = 1, filesize=123699 information about the file that will be used by RDC processing (size here is uncompressed) <Upstream> 20080908 09:40:55.373 2036 RDCX 3622 Rdc::FrsSignatureIndexFile::Open Opening FrsSignatureIndexFile OK for write Levels=1..1 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 Alternate datastream of RDC opened <Upstream> 20080908 09:40:55.373 2036 RDCX 462 StreamToIndex RDC generate begin: (0..1), uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A4DF9A4F93C52} RDC signature generation begins <Upstream> 20080908 09:40:55.373 2036 RDCX 176 SignatureGenerator Level=0, Depth = 1 depth refers to ‘signatures of signatures’. A larger file can have signatures created based on other signatures. <Upstream> 20080908 09:40:55.373 2036 RDCX <Upstream> 20080908 09:40:55.373 2036 MRSH <Upstream> 20080908 09:40:55.373 2036 RDCX 208 SignatureGenerator Similarity enabled 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 504 StreamToIndex RDC generate end: (0..1), uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A4DF9A4F93C52} RDC signature generation is complete <Upstream> 20080908 09:40:55.373 2036 CSMG 4844 ContentSetManager::UpdateHash LDB Updating ID Record: Hash and RDC similarity data now added to the DFSR database + fid 0x300000000BA79 + usn 0x2618a08 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080908 16:40:55.341 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 4EE34B30-5AE41344-E837A741-2F45F5D9 file hash checksum now set + similarity 2F003931-38353202-2221050D-34192B12 similarity ‘master’ checksum now set + name pooltag.txt + <Upstream> 20080908 09:40:55.482 2036 ASYN <Upstream> 20080908 09:40:55.482 2036 STAG 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloaded (refCount==1) <Upstream> 20080908 09:40:55.482 2036 STAG 3012 Staging::UpdateContentSetInfo Update contentInfoHistory <Upstream> 20080908 09:40:55.482 2036 STAG 2739 Staging::AddCommitFile File added: 49152 access time: 20080908 16:40:55.341 reserved: 0 new usage: 98304 <Upstream> 20080908 09:40:55.482 2036 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloading (refCount==0) <Upstream> 20080908 09:40:55.482 2036 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 18- {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18-Downloaded.frx file now fully staged and ready to serve <Upstream> 20080908 09:40:55.482 2036 OUTC 1313 OutConnection::OpenFile WRITE_FILE_TO_STAGE record.simData=(2F003931- 38353202-2221050D-34192B12,4EE34B30-5AE41344-E837A741-2F45F5D9) <Upstream> 20080908 09:40:55.482 2036 OUTC 1476 OutConnection::OpenFile Prepare to serve over RDC uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt fileSize:123699 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} rgName:RDCRG RDC signature information can be sent to the downstream partner through RPC so that the downstream can request the blocks for any missing signatures on the downstream copy <Upstream> 20080908 09:40:55.482 2036 RDCX 3067 Rdc::SyncServerState::CreateReaders RDC Creating readers: uid:{5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F540309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} read signature info from the staged file in order to send to downstream <Upstream> 20080908 09:40:55.482 2036 RDCX 3622 Rdc::FrsSignatureIndexFile::Open Opening FrsSignatureIndexFile OK for read Levels=1..1 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 <Upstream> 20080908 09:40:55.482 2036 RDCX <Upstream> 20080908 09:40:55.482 2708 STAG 3093 Rdc::SyncServerState::CreateReaders Opening level:1 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Upstream> 20080908 09:40:55.482 2708 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Partial (refCount==1) <Upstream> 20080908 09:40:55.482 2708 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Partial (refCount==0) <Upstream> 20080908 09:40:55.482 2708 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==1) <Upstream> 20080908 09:40:55.482 2708 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==0) <Upstream> 20080908 09:40:55.482 2708 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==1) previously staged version of the file locked for deletion <Upstream> 20080908 09:40:55.482 2708 STAG 2840 Staging::FileDeleted File deleted: 49152 access time: 20080908 16:39:09.648 new usage: 49152 <Upstream> 20080908 09:40:55.482 2708 STAG 3012 Staging::UpdateContentSetInfo Update contentInfoHistory <Upstream> 20080908 09:40:55.482 2708 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==0) <Upstream> 20080908 09:40:55.482 2708 STAG 223 StagingCleanupTask::DeleteQueuedFiles Deleted uid:{5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 older version of the staged file deleted <Downstream> 20080908 09:40:55.488 1044 DOWN <Downstream> 20080908 09:40:55.488 1044 RDCX 1272 WrapRpcInitializeFileTransferAsync 0 764 Rdc::SeedFile::Initialize RDC signatureLevels:1, uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt fileSize(approx):131072 csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} enableSim=1 downstream server must read signature information from its own copy of the file now in order to compare with upstream <Downstream> 20080908 09:40:55.488 1044 RDCX 833 Rdc::SeedFile::Initialize Level is 1 <Downstream> 20080908 09:40:55.488 1044 RDCX 902 Rdc::SeedFile::Initialize enableSimilarity=1, simData=2F003931- 38353202-2221050D-34192B12,4EE34B30-5AE41344-E837A741-2F45F5D9 <Upstream> 20080908 09:40:55.498 2036 OUTC 1534 OutConnection::OpenFile Sent file uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 name:pooltag.txt fileSize:45314 connId:{68E26C24-5C9747A2-9F54-0309E426B2C5} rgName:RDCRG file is not truly being sent yet, this is a misleading log entry. Downstream is still deciding what it needs, the upstream is ready to send. <Upstream> 20080908 09:40:55.498 2036 OUTC 1542 OutConnection::OpenFile Update syncInfoHistory <Upstream> 20080908 09:40:55.498 2036 SRTR 2357 InitializeFileTransferAsyncState::ProcessIoCompletion Initialized connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} rdc:1 context:0084BC10,008B4C28,00000000 uid:{5CB120DE-D2C2-452A-8280B45FC155224F}-v17 gvsn{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 ptr:00844750 <Downstream> 20080908 09:40:55.504 1044 RDCX 1262 Rdc::SeedFile::UseSimilar similarrelated (SimMatches=14) uid:{5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt csId:{21A87CB1-5E1D47A0-A47A-4DF9A4F93C52} (related: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v17 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}) downstream has decided to use RDC between these two GVSN versions of the file (which has matching UID) <Downstream> 20080908 09:40:55.504 1044 OUTC 2188 OutConnection::GetStageReaderOrWriter check to see if the file is already staged on downstream so that signatures can be compared. + fid 0x300000000BA2C + usn 0x26331a8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 20080908 16:39:09.656 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 this is the previous version. + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:39:09.319 GMT (0x1c911d16aba44f8) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 038209BA-4AAA2DF7-FAAF1C1D-7A61284A + similarity 3B003931-38353202-2221050D-34193912 + name pooltag.txt + Failed to get stage reader as the file is not staged not yet staged downstream <Downstream> 20080908 09:40:55.504 1044 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==1) file locked in order to be staged downstream <Downstream> 20080908 09:40:55.504 1044 STAG 4113 Staging::OpenForWrite name:pooltag.txt uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 file written into staging <Downstream> 20080908 09:40:55.504 1044 OUTC 2225 OutConnection::GetStageReaderOrWriter + fid 0x300000000BA2C + usn 0x26331a8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 20080908 16:39:09.656 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:39:09.319 GMT (0x1c911d16aba44f8) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 038209BA-4AAA2DF7-FAAF1C1D-7A61284A + similarity 3B003931-38353202-2221050D-34193912 + name pooltag.txt + StageReader:00000000 StageWriter:00D7F750 Policy:0 <Downstream> 20080908 09:40:55.504 1044 SETT 153 Settings::GenericDwordSetting::operator () Assigned default value. valueName:AsyncReadThresholdBytes value:262144 <Downstream> 20080908 09:40:55.504 1044 RDCX 1510 Rdc::SeedFile::UseRelated Staging "UIDRelated" file uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0A47A-4DF9A4F93C52} (related: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}v17 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}) <Downstream> 20080908 09:40:55.504 1044 RDCX 3622 Rdc::FrsSignatureIndexFile::Open Opening FrsSignatureIndexFile OK for write Levels=1..1 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 <Downstream> 20080908 09:40:55.504 1044 RDCX 462 StreamToIndex RDC generate begin: (0..1), uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A4DF9A4F93C52} <Downstream> 20080908 09:40:55.504 1044 RDCX 176 SignatureGenerator Level=0, Depth = 1 <Downstream> 20080908 09:40:55.504 1044 RDCX 208 SignatureGenerator Similarity enabled <Downstream> 20080908 09:40:55.504 1044 MRSH 4615 Marshaller::Marshal FileAttrs in metadata : 0x20 <Downstream> 20080908 09:40:55.520 1044 RDCX 504 StreamToIndex RDC generate end: (0..1), uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0-A47A4DF9A4F93C52} <Downstream> 20080908 09:40:55.598 1044 ASYN <Downstream> 20080908 09:40:55.598 1044 STAG 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==1) <Downstream> 20080908 09:40:55.598 1044 STAG 3012 Staging::UpdateContentSetInfo Update contentInfoHistory <Downstream> 20080908 09:40:55.598 1044 STAG 2739 Staging::AddCommitFile File added: 49152 access time: 20080908 16:40:55.504 reserved: 0 new usage: 53248 <Downstream> 20080908 09:40:55.598 1044 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==0) <Downstream> 20080908 09:40:55.598 1044 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 17- {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-Downloaded.frx 91 RdcCache::Find 0xF00000000A77E pooltag.txt similarity_table being <Downstream> 20080908 09:40:55.598 1044 RDCC used to find a similar file reference <Downstream> 20080908 09:40:55.598 1044 RDCC 232 RdcCache::MatchSuffix Nothing found for \\.\c:\rdcrf\DfsrPrivate\ConflictAndDeleted\pooltag.txt* <Downstream> 20080908 09:40:55.598 1044 RDCC 284 RdcCache::MatchPaths 0xF00000000A77E pooltag.txt (root: 0xF00000000A77E) <Downstream> 20080908 09:40:55.598 1044 RDCX 3622 Rdc::FrsSignatureIndexFile::Open Opening FrsSignatureIndexFile OK for read Levels=1..1 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 <Downstream> 20080908 09:40:55.598 1044 RDCX 2265 Rdc::SeedFile::OpenSeedSigDB Using seed file for uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt csId:{21A87CB1-5E1D-47A0A47A-4DF9A4F93C52} seed(type:UIDRelated uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v17 fileName:pooltag.txt depth=1) <Downstream> 20080908 09:40:55.598 1044 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloading (refCount==1) <Downstream> 20080908 09:40:55.598 1044 STAG 4305 Staging::FindAllFiles Older version found:17-{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-Downloaded.frx <Downstream> 20080908 09:40:55.613 1044 STAG 4113 Staging::OpenForWrite name:pooltag.txt uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 <Downstream> 20080908 09:40:55.613 1044 RDCX 3622 Rdc::FrsSignatureIndexFile::Open Opening FrsSignatureIndexFile OK for write Levels=1..1 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 <Downstream> 20080908 09:40:55.613 1044 XRNA 55 XpressRdcNeedAssembler::XpressRdcNeedAssembler this:00E19D18 <Downstream> 20080908 09:40:55.613 1044 XRNA 967 XpressRdcNeedAssembler::GetSourceRdcNeedDataAsync Starting RDC source thread. this:00E19D18 <Downstream> 20080908 09:40:55.613 2564 SETT 153 Settings::GenericDwordSetting::operator () Assigned default value. valueName:AsyncRpcDownloadMinSizeInBytes value:65536 <Downstream> 20080908 09:40:55.613 2564 XRNA 833 XpressRdcNeedAssembler::GetSourceRdcNeedDataThread Entering RDC source need download thread. this:00E19D18 (use RPC async pipe:0) <Downstream> 20080908 09:40:55.613 2564 XRNA 919 XpressRdcNeedAssembler::GetSourceRdcNeedDataThread Exiting RDC source need download thread. this:00E19D18 <Downstream> 20080908 09:40:55.613 1044 XRNA 276 XpressRdcNeedAssembler::ProcessRdcNeeds All needs processed. this:00E19D18 <Downstream> 20080908 09:40:55.613 1044 XRNA 291 XpressRdcNeedAssembler::FinalizeRpcDownload Shutting down RPC pipe thread this:00E19D18 <Upstream> 20080908 09:40:55.623 2952 SRTR 1513 SERVER_RdcGetSignatures Sent context:0084BC10,008B4C28,00000000 level:1 offset:0 length:65536, sizeRead:1050 uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v18 csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Upstream> 20080908 09:40:55.623 2952 SRTR 1604 SERVER_RdcPushSourceNeeds offset:0, length: 2020 <Upstream> 20080908 09:40:55.623 2952 SRTR 1604 SERVER_RdcPushSourceNeeds offset:121665, length: 2034 <Upstream> 20080908 09:40:55.623 2952 SRTR 1623 SERVER_RdcPushSourceNeeds Received context:0084BC10,008B4C28,00000000, needCount:2 RDC signature ‘needs’ sent through RPC to downstream <Upstream> 20080908 09:40:55.623 2952 SRTR 1727 SERVER_RdcGetFileData Sent context:0084BC10,008B4C28,00000000 2013 <Upstream> 20080908 09:40:55.623 2952 SRTR 1727 SERVER_RdcGetFileData Sent context:0084BC10,008B4C28,00000000 0 RDC blocks arrive through RPC to the downstream server <Downstream> 20080908 09:40:55.692 1044 ASYN <Downstream> 20080908 09:40:55.692 1044 RDCX 510 AsyncUnbufferedFileWriter::Close Async WRITE Statistics: 1811 Rdc::SyncClientState::Flush Rdc Need Assembler Statistics: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} RDC statistics written to log about what was sent over wire (could be seen in Performance monitor as well, to some extent) + TOTAL + Compression Ratio + Target Uncompress Size + Target Compress Size + Bytes Received 64 123699 raw size of the file 45118 XPRESS compressed size of the file 3063 Signatures: 1050 Data: 2013 data sent over the wire (bytes of signatures, bytes of file blocks) + Signature Bytes Received + Number of remote calls + SEED + Rdc Need Size 0 0 + Xpress Blocks 15 15 + Uncompressed Xpress Blocks + Blocks copied to target + SOURCE + Rdc Need Size 4054 0 + Xpress Blocks 3 0 + Uncompressed Xpress Blocks 1 0 + Blocks copied to target 0 0 <Downstream> 20080908 09:40:55.692 1044 XRNA 1050 1050 4 Signatures: 1 Needs: 2 2 13 13 1 Data: 2 89 XpressRdcNeedAssembler::~XpressRdcNeedAssembler this:00E19D18 <Downstream> 20080908 09:40:55.692 1044 INCO 5735 InConnection::RdcGet Update syncInfoHistory <Downstream> 20080908 09:40:55.692 1044 INCO 5610 InConnection::LogTransferActivity Received RDCGET uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 fileName:pooltag.txt connId:{68E26C24-5C9747A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} stagedSize:45314 <Downstream> 20080908 09:40:55.692 1044 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080908 09:40:55.692 1044 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==0) <Downstream> 20080908 09:40:55.692 1044 MEET 1970 Meet::Download Done downloading content updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf data done being replicated to downstream <Downstream> 20080908 09:40:55.692 1044 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloaded (refCount==1) downstream copy of the file locked for adding RDC data <Downstream> 20080908 09:40:55.692 1044 STAG 3012 Staging::UpdateContentSetInfo Update contentInfoHistory <Downstream> 20080908 09:40:55.692 1044 STAG 2739 Staging::AddCommitFile File added: 49152 access time: 20080908 16:40:55.598 reserved: 0 new usage: 102400 file blocks added to the downstream staged file <Downstream> 20080908 09:40:55.692 1044 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloading (refCount==0) <Downstream> 20080908 09:40:55.692 1044 STAG 799 StageWriter::CompleteDownloadStage Completed download or stage file 18- {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18-Downloaded.frx staging and replicating done for the file downstream 2570 Meet::TransferToInstalling file now needs to be decompressed into <Downstream> 20080908 09:40:55.692 1044 MEET the Installing folder. <Downstream> 20080908 09:40:55.692 1044 MRSH 3959 MarshalContext::Initialize Create file:[pooltag-{5CB120DE-D2C2-452A- 8280-B45FC155224F}-v18.txt] with attributes:0x20 <Downstream> 20080908 09:40:55.692 1044 MEET 2585 Meet::TransferToInstalling Transferring content from staging area into Installing updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf ready to process file copy into the Installing directory (now decompressed) <Downstream> 20080908 09:40:55.692 808 STAG 108 StagingCleanupTask::Run Start to cleanup private staging directory. csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Downstream> 20080908 09:40:55.692 808 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Partial (refCount==1) <Downstream> 20080908 09:40:55.692 808 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Partial (refCount==0) <Downstream> 20080908 09:40:55.692 808 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==1) <Downstream> 20080908 09:40:55.692 808 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloading (refCount==0) <Downstream> 20080908 09:40:55.692 808 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==1) <Upstream> 20080908 09:40:55.701 2952 SRTR 1772 SERVER_RdcClose uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} connId:{68E26C24-5C97-47A29F54-0309E426B2C5} <Upstream> 20080908 09:40:55.701 2952 RDCX 2833 Rdc::SyncServerState::~SyncServerState RDC Need Reader Statistics: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} upstream server logs RDC statistics for Performance counter historical information + TOTAL + Compression Ratio 25 + RDC Need Size 4054 + Bytes sent to downstream 3063 + Uncompressed XPRESS blocks 0 + Compressed XPRESS blocks 1 + Copied XPRESS Blocks 0 + Bytes read using async I/Os 0 <Upstream> 20080908 09:40:55.701 2952 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Upstream> 20080908 09:40:55.701 2952 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloaded (refCount==0) <Downstream> 20080908 09:40:55.707 1044 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: <Downstream> 20080908 09:40:55.707 1044 MEET 2618 Meet::TransferToInstalling Obtaining fid of the newly installed file updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf <Downstream> 20080908 09:40:55.707 1044 MEET 2631 Meet::TransferToInstalling Read 123699 bytes, wrote 123699 bytes updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf file decompressed from Staging into Installing with real name <Downstream> 20080908 09:40:55.707 1044 MEET 2032 Meet::Download Download Succeeded : true updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} The staging and Installing folder processing is done on the downstream <Downstream> 20080908 09:40:55.707 1044 FIDL 110 FidLockMan::Lock Read: 0xF00000000A77E <Downstream> 20080908 09:40:55.707 1044 FIDL 115 FidLockMan::Lock Write: 0x300000000BA2C <Downstream> 20080908 09:40:55.707 1044 FIDL 115 FidLockMan::Lock Write: 0x300000000BA2F <Downstream> 20080908 09:40:55.707 1044 FIDL 135 FidLockMan::Lock read: 1 write: 2 0 <Downstream> 20080908 09:40:55.707 1044 MEET 1434 Meet::InstallStep Start transaction <Downstream> 20080908 09:40:55.707 1044 MEET 5486 Meet::FindUidRelated Obtain USN information for file on disk <Downstream> 20080908 09:40:55.707 1044 MEET 3840 Meet::ProcessUid Uid related found uidRelated:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v17 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf <Downstream> 20080908 09:40:55.707 1044 MEET 5694 Meet::LocalDominates Remote version dominates localgvsn:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v17 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf this is not a true conflict occurring, this is a side effect of the level 5 debug verbosity. It is simply a conflict check. <Downstream> 20080908 09:40:55.707 1044 MEET 5274 Meet::FindNameRelated Access name conflicting file. updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf <Downstream> 20080908 09:40:55.707 1044 MEET 4256 Meet::GetNameRelated Name related not found. updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf Not a conflict <Downstream> 20080908 09:40:55.707 1044 MEET 3034 Meet::UidInheritEnabled UidInheritEnabled:0 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf <Downstream> 20080908 09:40:55.707 1044 MEET 2772 Meet::InstallRename Move out previous version of same file updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf previous version of the file must now be overwritten. <Downstream> 20080908 09:40:55.707 1044 MEET 4867 Meet::MoveOut Moving contents and children out of replica. newName:pooltag-{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17.txt updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf record: previous version is overwritten. This actually causes a deletion to occur as we will see below. + fid 0x300000000BA2C + usn 0x26331a8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 20080908 16:39:09.656 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:39:09.319 GMT (0x1c911d16aba44f8) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 038209BA-4AAA2DF7-FAAF1C1D-7A61284A + similarity 3B003931-38353202-2221050D-34193912 + name pooltag.txt + <Downstream> 20080908 09:40:55.707 1044 MEET 4989 Meet::MoveOut Purge existing file in Deleted updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf the older version of the file had been moved to the Deleted folder. It is then purged and is gone from the file system. <Downstream> 20080908 09:40:55.707 1044 MEET 4995 Meet::MoveOut RenameDelete file fid:0x300000000BA2C updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf old version of the file is gone. <Downstream> 20080908 09:40:55.707 1044 MEET 2796 Meet::InstallRename Tunneling last access time in Installing. lastAccessTime: 20080908 16:39:09.288 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf the last accessed time of the previous file is ‘tunnelled’ (i.e. written to) the new copy of the file in the Installing directory before the file is written to the replicated folder. <Downstream> 20080908 09:40:55.707 1044 MEET 2822 Meet::InstallRename Moving contents from Installing to final destination. Attributes:0x20 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf file moved from Installing to the real replicated folder downstream. <Downstream> 20080908 09:40:55.707 1044 MEET 2837 Meet::InstallRename File moved. rootVolume:{3C84BB07-22D1-11DD-862B- 806E6F6E6963} parentFid:0xF00000000A77E fidInInstalling:0x300000000BA2F usn:0x26359b8 updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf the move from Installing to the RF is complete <Downstream> 20080908 09:40:55.707 1044 MEET 2866 Meet::InstallRename Update database with new contents updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf the DFSR database must now be updated to reflect the new file information now that the file is replicated and ready for end user access. <Downstream> 20080908 09:40:55.707 1044 MEET 2940 Meet::InstallRename Updating database. updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf <Downstream> 20080908 09:40:55.707 1044 MEET 6746 Meet::UpdateIdRecord LDB Updating ID Record: DFSR database updated with the new GVSN, hash, and similarity information + fid 0x300000000BA2F + usn 0x26359b8 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 1 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 Now matches upstream GVSN + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 4EE34B30-5AE41344-E837A741-2F45F5D9 + similarity 2F003931-38353202-2221050D-34192B12 + name pooltag.txt + <Downstream> 20080908 09:40:55.707 1044 RDCS 807 FrsSimilarityManager::Delete Deleteing similarity data. Vol:{3C84BB07- 22D1-11DD-862B-806E6F6E6963} FileId:0x300000000BA2C <Downstream> 20080908 09:40:55.707 1044 MEET 2949 Meet::InstallRename -> DONE Install-rename completed updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csName:rdcrf csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} <Downstream> 20080908 09:40:55.707 1044 MEET 1638 Meet::InstallStep Done installing file updateName:pooltag.txt uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 connId:{68E26C24-5C97-47A29F54-0309E426B2C5} csName:rdcrf file replication done for this updated version of the file <Downstream> 20080908 09:40:55.707 1044 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 state: Downloaded (refCount==0) <Downstream> 20080908 09:40:55.707 1044 INCO 5897 InConnection::UpdateProcessed Received Update. updatesLeft:0 processed:1 failures:0 sessionId:3 open:0 updateType:0 processStatus:0 connId:{68E26C24-5C97-47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} csName:rdcrf update: + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v18 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 + parent {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 16:40:55.341 GMT (0x1c911d1a9ebf1e5) + createTime 20080908 16:39:09.288 GMT + csId {21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} + hash 4EE34B30-5AE41344-E837A741-2F45F5D9 + similarity 2F003931-38353202-2221050D-34192B12 + name pooltag.txt + <Downstream> 20080908 09:40:55.707 16:40:55.692 new usage: 53248 808 STAG 2840 Staging::FileDeleted File deleted: 49152 access time: 20080908 <Downstream> 20080908 09:40:55.707 808 STAG 3012 Staging::UpdateContentSetInfo Update contentInfoHistory <Downstream> 20080908 09:40:55.707 808 STAG 1266 Staging::LockedFiles::Unlock Unlocked file UID: {5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 state: Downloaded (refCount==0) <Downstream> 20080908 09:40:55.707 808 STAG 223 StagingCleanupTask::DeleteQueuedFiles Deleted uid:{5CB120DE-D2C2-452A- 8280-B45FC155224F}-v17 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v17 previous version of staged file is deleted <Downstream> 20080908 09:40:55.707 1044 LDBX 3340 LdbManager::WakeUpSleepers Wake up callback 00DC73C0 <Downstream> 20080908 09:40:55.707 1044 INCO 6169 InConnection::CommitSession Committing connId:{68E26C24-5C97-47A2-9F54- 0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} csName:rdcrf session:3 delta:1 newVersionVector intervals:1 vector:{5CB120DE-D2C2-452A-8280-B45FC155224F} |-> { 16..18} + <Downstream> 20080908 09:40:55.707 1044 INCO 1909 InConnection::InSync Checking for in sync. connId:{68E26C24-5C97-47A2- 9F54-0309E426B2C5} <Downstream> 20080908 09:40:55.707 1044 INCO 6194 InConnection::CommitSession Connection in sync connId:{68E26C24-5C97- 47A2-9F54-0309E426B2C5} csId:{21A87CB1-5E1D-47A0-A47A-4DF9A4F93C52} csName:rdcrf commitedSessionsWithUpdateFailures:0 <Downstream> 20080908 09:40:55.707 1044 INCO 6200 InConnection::CommitSession Update syncInfoHistory <Downstream> 20080908 09:40:55.707 1044 HIST 1177 StateHistory::Update Fire sync info record state update downstream server is now completely in sync with upstream and has no receieving backlog + syncGuid {403E4E1A-2E57-4DEA-AD75-808855B6EE9F} + state In Sync + initReason Schedule + connectionGuid {68E26C24-5C97-47A2-9F54-0309E426B2C5} + replicationGroupGuid {5CB973F5-6B04-40D6-AAD9-85F2855F6AC5} + replicationGroupName RDCRG + memberGuid {3D0C9825-BC62-4D16-94F8-BC73BC3438D4} + memberName 2008X86FSRV11 + updatedNotTransferred 0 + updatedTransferred 1 + updatedToBeTransferred 1 + byteTransferred 45314 + tombstonesGenerated 0 + conflictsGenerated 0 + currentForceReplicationEndTime 16010101 00:00:00.000 + currentForceReplicationBandwidthlevel * + Understanding DFSR debug logging (Part 17: Replication failing because of blocked RPC ports (uses debug severity 5)) In this scenario we will see a file created on the upstream server and attempted replication with its downstream partner. RPC traffic is being blocked between the machines by an incorrectly configured firewall. This is a common scenario and basic understanding of firewalls, TCP/IP, ports, and RPC is assumed. Debug logging severity is set to 5 in order to see more details about the problem state. (rpcportsblocked - Dfsr00008 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The log is from 2008x86SRV10 where the file is created (upstream). Both servers are participating in the RpcPortRG replication group for the RpcportRf replicated folder. The file is called “fveupdate.exe”. <Upstream> 20080908 10:12:45.417 3372 USNC 2612 UsnConsumer::CreateNewRecord LDB Inserting ID Record: File added to the replicated folder on the upstream server + fid 0x300000000BAAC + usn 0x2633c60 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v28 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v28 + parent {3C47E305-FDE9-43F6-A550-791D9568C1D3}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080908 17:12:43.261 GMT (0x1c911d61b214f69) + createTime 20080908 17:12:43.261 GMT + csId {3C47E305-FDE9-43F6-A550-791D9568C1D3} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name fveupdate.exe file is name ‘fveupdate.exe’ + <Upstream> 20080908 10:12:45.417 1632 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{108028D9-F00E-4F1E-A8EF- BF60DB623231} remoteAddress:2008x86FSRV11.contoso.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008x86FSRV11.contoso.com] An RPC connection setup attempt occurs over TCP (using the UUID of DFSR, which is the GUID 5bc1ed07-f5f5-485f-9dfd-6fd0acf9a23c) between upstream and downstream server <Upstream> 20080908 10:12:45.433 3372 USNC 2615 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000BAAC + ParentFileRefNumber: 0xD00000000BA35 + USN: 0x2633c60 + TimeStamp: 20080908 10:12:43.261 Pacific Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite File Create + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 26 + FileNameOffset: 60 + FileName: fveupdate.exe + <Upstream> 20080908 10:12:45.433 3372 LDBX 4300 Ldb::UpdateLastVersion Updating lastVersion:28 <Upstream> 20080908 10:12:45.433 3372 USNC 3459 UsnConsumer::CheckPoint Updating journalRecord: updateFlags=0 + usnId: 0x1c8b6df35167c8c + nextUsn: 0x26360f8 + checkpointUsn: 0x2633c60 + checkpointTimestamp: 20080908 17:12:43.261 + journalWrapped: 0 + journalIdChanged: 0 + slowRecoverNotFinished: 0 + dirtyRecoveryMode: 0 + dirtyShutdownRecoveryTimestamp: 16010101 00:00:00.000 + dirtyRecoveryRecordsMarkedFinished: 0 + <Upstream> 20080908 10:13:04.246 2508 SETT 153 Settings::GenericDwordSetting::operator () Assigned default value. valueName:RpcContextHandleTimeoutMs value:1800000 <Upstream> 20080908 10:13:04.246 2508 SETT 153 Settings::GenericDwordSetting::operator () Assigned default value. valueName:MinRateCounterUpdateIntervalSec value:29 <Upstream> 20080908 10:13:06.433 1632 DOWN 3868 [WARN] DownstreamTransport::EstablishConnection Failed. Try flat name. RPC connection has failed + [Error:9027(0x2343) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 1632 C A failure was reported by the remote partner] returns error 9027 + [Error:1722(0x6ba) DownstreamTransport::EstablishConnection downstreamtransport.cpp:3853 1632 W The RPC server is unavailable.] returns extended error 1722 (“The RPC server is unavailable”) <Upstream> 20080908 10:13:06.433 1632 DOWN 3099 DownstreamTransport::SetupBinding Entering SetupBinding <Upstream> 20080908 10:13:06.433 1632 DOWN 3181 DownstreamTransport::SetupBinding Setting authentication information for partner: CONTOSO\2008X86FSRV11$ the partner that was being connected to <Upstream> 20080908 10:13:06.433 1632 DOWN 3363 DownstreamTransport::SetupBinding Setup connId:{108028D9-F00E-4F1E-A8EF- BF60DB623231} remoteAddress:2008x86FSRV11.contoso.com stringBinding:[5bc1ed07-f5f5-485f-9dfd- 6fd0acf9a23c@ncacn_ip_tcp:2008x86FSRV11] <Upstream> 20080908 10:13:27.434 1632 DOWN 383 LogExtendedErrorInformation Extended error information: various extended error information is logged for troubleshooting purposes. All are from WINERROR.H and can be translated with err.exe + Process ID : 3148 process ID of DFSR.EXE + System Time : 20080908 17:13:27.434 + Generating component : 2 + Status : 1722 + Detection location : 501 + Flags : 0 + NumberOfParameters : 4 + 0 Unicode string: [ncacn_ip_tcp] + 1 Unicode string: [2008x86FSRV11] + 2 Long : -1988219297 + 3 Long : 1722 <Upstream> 20080908 10:13:27.434 1632 DOWN 383 LogExtendedErrorInformation Extended error information: + Process ID : 3148 + System Time : 20080908 17:13:27.434 + Generating component : 8 + Status : 1722 Error “The RPC server is unavailable” + Detection location : 1442 + Flags : 0 + NumberOfParameters + : 1 0 Unicode string: [2008x86FSRV11] <Upstream> 20080908 10:13:27.434 1632 DOWN 383 LogExtendedErrorInformation Extended error information: + Process ID : 3148 + System Time : 20080908 17:13:27.434 + Generating component : 8 + Status : 1237 error “The operation could not be completed. A retry should be performed.” + Detection location : 313 + Flags : 0 + NumberOfParameters : 0 <Upstream> 20080908 10:13:27.434 1632 DOWN 383 LogExtendedErrorInformation Extended error information: + Process ID : 3148 + System Time : 20080908 17:13:27.434 + Generating component : 8 + Status : 10060 error “A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.” + Detection location : 311 + Flags : 0 + NumberOfParameters : 3 + 0 Long : 135 + 1 Pointer : 00000000 + 2 Pointer : 6F000A0A00000000 <Upstream> 20080908 10:13:27.434 1632 DOWN 383 LogExtendedErrorInformation Extended error information: + Process ID : 3148 + System Time : 20080908 17:13:27.434 + Generating component : 8 + Status : 10060 + Detection location : 318 + Flags : 0 + NumberOfParameters : 0 <Upstream> 20080908 10:13:27.434 1632 DOWN 373 LogExtendedErrorInformation Done enumerating extended error information Understanding DFSR debug logging (Part 18: LDAP queries failing due to network (uses debug severity 5)) In this scenario we will see a DFSR server attempt to contact its DC through LDAP to read the current replication topology. LDAP lookups are being blocked by ‘firewall/network/DC down’ so there are no responses. (ldapblocked - Dfsr00008 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x64FSDC01 in the contoso.com domain. The log is from 2008x86SRV10 where the file is created. The other server is a domain controller. Review scenario “Domain Controller Bind and Configuration Polling on Windows Server 2008”. <Upstream> 20080908 11:19:23.236 3940 CFAD 2159 [ERROR] Config::AdQuery::Search Failed to ldap_search_ext_s(). Error:Server Down base:CN=2008X86FSRV10,CN=Computers,DC=contoso,DC=com domain controller is not responding to an LDAP search request for the sending computer’s own DN <Upstream> 20080908 11:19:23.236 3940 CFAD + 8456 Config::AdConfig::IsConnected Lost connection to AD. Error: [Error:58(0x3a) Config::AdQuery::StartSearch ad.cpp:2261 3940 W The specified server cannot perform the requested operation.] it’s important to note that DC connectivity errors will not all be LDAP-only. This error 58 is a WINERROR.H translated to “The specified server cannot perform the requested operation” with err.exe + [Error:58(0x3a) Config::AdQuery::StartSearch ad.cpp:2204 3940 W The specified server cannot perform the requested operation.] + [Error:58(0x3a) Config::AdQuery::Search ad.cpp:2169 3940 W The specified server cannot perform the requested operation.] + [Error:81(0x51) Config::AdQuery::Search ad.cpp:2169 3940 U Server Down] the other extended error is actually an LDAP error that will translate with err.exe to LDAP_SERVER_DOWN in WINLDAP.H <Upstream> 20080908 11:19:42.174 3940 CFAD 317 Config::AdConnection::Connect Binding to dcAddr:\\10.10.0.101 dcDnsName:\\2008x64FDC01.contoso.com this is the DC where the LDAP bind is being attempted against. It returns both IP and DNS name. <Upstream> 20080908 11:19:42.174 3940 CFAD 149 Config::AdConnection::BindToAd Trying to connect. hostName:2008x64FDC01.contoso.com <Upstream> 20080908 11:20:03.175 3940 CFAD 3021 [ERROR] Config::AdSession::Connect Failed to ldap_connect(). timeout:30 Error:Server Down <Upstream> 20080908 11:20:03.175 3940 CFAD 179 [ERROR] Config::AdConnection::BindToAd Failed to bind to AD. Error:[Error:58(0x3a) Config::AdSession::Connect ad.cpp:3027 3940 W The specified server cannot perform the requested operation.] <Upstream> 20080908 11:20:03.175 3940 CFAD 149 Config::AdConnection::BindToAd Trying to connect. hostName:10.10.0.101 <Upstream> 20080908 11:20:24.192 3940 CFAD 3021 [ERROR] Config::AdSession::Connect Failed to ldap_connect(). timeout:30 Error:Server Down <Upstream> 20080908 11:20:24.192 3940 CFAD 179 [ERROR] Config::AdConnection::BindToAd Failed to bind to AD. Error:[Error:58(0x3a) Config::AdSession::Connect ad.cpp:3027 3940 W The specified server cannot perform the requested operation.] <Upstream> 20080908 11:20:24.192 3940 SCFG 1888 [WARN] ServiceConfig::DsPollIsDue Failed to enable lightweight polling. Error: + [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:8326 3940 W One or more arguments are not correct.] misleading error, the previous LDAP failure caused another operation to return this error + [Error:160(0xa0) Config::AdConfig::Connect ad.cpp:8077 3940 W One or more arguments are not correct.] + [Error:160(0xa0) Config::AdConnection::Connect adconnection.cpp:365 3940 W One or more arguments are not correct.] + [Error:160(0xa0) Config::AdConnection::BindToAd adconnection.cpp:184 3940 W One or more arguments are not correct.] Understanding DFSR debug logging (Part 19: File Blocked Inbound by a File Screen Filter Driver (uses debug severity 5)) In this scenario we will see an attempted file replication. The downstream partner is running the File Server Resource Manager role with file screens configured and these screens are not matched to the DFSR file filters. The debug log has been set to severity 5 for deeper details than usual. (filescreenupstream - Dfsr00008 - 2008.log and filescreendownstream - Dfsr00009 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The logs are from 2008x86SRV10 where the file is created (upstream) and from 2008x86SRV11 where it is replicated (downstream). Both servers are participating in the FsrmRg replication group for the FsrmRf replicated folder. The file is called “spoolsv.exe”. FSRM is configured with the default “block executable files” file screen. <Upstream> 20080908 13:21:16.113 3264 USNC 2612 UsnConsumer::CreateNewRecord LDB Inserting ID Record: File created upstream + fid 0x300000000BACF + usn 0x2685058 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 + parent {9D619939-CA99-497B-90F1-D667B4D76F05}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock + createTime 20080908 20:21:16.113 GMT + csId {9D619939-CA99-497B-90F1-D667B4D76F05} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name spoolsv.exe file named ‘spoolsv.exe’ 20080908 20:21:16.113 GMT (0x1c911f0721d8af3) + <Upstream> 20080908 13:21:16.113 3264 USNC 2615 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x300000000BACF + ParentFileRefNumber: 0x60000000000B3 + USN: 0x2685058 + TimeStamp: 20080908 13:21:16.113 Pacific Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite File Create + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 22 + FileNameOffset: 60 + FileName: spoolsv.exe + <Upstream> 20080908 13:21:16.113 3264 LDBX 4300 Ldb::UpdateLastVersion Updating lastVersion:39 <Upstream> 20080908 13:21:16.113 3264 LDBX 3340 LdbManager::WakeUpSleepers Wake up callback 008753C0 <Upstream> 20080908 13:21:16.113 3460 UPST 1399 UpstreamTransport::FlushVvUp 00201800 <Upstream> 20080908 13:21:16.113 3460 UPST 1417 UpstreamTransport::FlushVvUp send connId:{4373FD61-670B-4687-846B- C8D8A71E0044} csId:{9D619939-CA99-497B-90F1-D667B4D76F05} seqNumber:10 status:0 vvGeneration:5 vvUp: <Upstream> 20080908 13:21:16.128 2748 SRTR 1880 SERVER_RequestVersionVector Received from connId:{4373FD61-670B-4687- 846B-C8D8A71E0044} csId:{9D619939-CA99-497B-90F1-D667B4D76F05} seqNumber:11 changeType:all <Upstream> 20080908 13:21:16.128 2748 SRTR 1927 SERVER_AsyncPoll Received from connId:{4373FD61-670B-4687-846B- C8D8A71E0044} <Upstream> 20080908 13:21:16.128 2748 UPST 1297 UpstreamTransport::AddAsyncPoll Inserted new async request rpcStatePtr:00201800 <snipped out operations covered in detail in earlier sections> <Downstream> 20080908 13:21:16.525 2036 MEET 2822 Meet::InstallRename Moving contents from Installing to final destination. Attributes:0x20 updateName:spoolsv.exe uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 gvsn:{5CB120DE-D2C2452A-8280-B45FC155224F}-v39 connId:{4373FD61-670B-4687-846B-C8D8A71E0044} csName:fsrmrf file has been RDC-reconstructed on the downstream partner <Downstream> 20080908 13:21:16.525 2036 MEET 1638 Meet::InstallStep Done installing file updateName:spoolsv.exe uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 connId:{4373FD61-670B-4687846B-C8D8A71E0044} csName:fsrmrf downstream server will now copy the file into replicated folder. <Downstream> 20080908 13:21:16.525 2036 MEET 1641 Meet::InstallStep Deleting fid in installing updateName:spoolsv.exe uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 connId:{4373FD61-670B-4687846B-C8D8A71E0044} csName:fsrmrf <Downstream> 20080908 13:21:16.525 2036 MEET 1263 Meet::Install -> WAIT Error processing update. updateName:spoolsv.exe uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 connId:{4373FD61-670B-4687846B-C8D8A71E0044} csName:fsrmrf csId:{9D619939-CA99-497B-90F1-D667B4D76F05} code:5 Error: the FSRM datascrn filter driver now blocks the write operation from occurring on the downstream server, as remotely added EXE files are not allowed. The error is unfortunately bubbled as ‘access denied’, but security is not related here at all, it’s just the error returned by the filter driver. + [Error:5(0x5) Meet::InstallStep meet.cpp:1657 2036 W Access is denied.] + [Error:5(0x5) Meet::InstallRename meet.cpp:2960 2036 W Access is denied.] + [Error:5(0x5) NtfsFileSystem::Move ntfsfilesystem.cpp:1188 2036 W Access is denied.] + [Error:5(0x5) NtfsFileSystem::Move ntfsfilesystem.cpp:999 2036 W Access is denied.] + [Error:5(0x5) FileUtil::RenameByHandle fileutil.cpp:386 2036 W Access is denied.] + [Error:5(0x5) FileUtil::RenameByHandle fileutil.cpp:383 2036 W Access is denied.] <Upstream> 20080908 13:21:16.535 2748 SRTR 1772 SERVER_RdcClose uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v39 csId:{9D619939-CA99-497B-90F1-D667B4D76F05} connId:{4373FD61-670B-4687846B-C8D8A71E0044} <Upstream> 20080908 13:21:16.535 2748 ASYN 1291 AsyncUnbufferedFileReader::Close Async READ Statistics: Understanding DFSR debug logging (Part 20: Skipped temporary and filtered files (uses debug severity 5)) In this scenario we will see a pair of files being created on an upstream server. One of the files is marked with the TEMPORARY attribute and one has an extension of TMP which is being filtered by DFSR. This will show the common scenarios of files which do not appear to ever replicate for unknown reasons. (tempfilesupstream - Dfsr00008 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The log is from 2008x86SRV10 where the file is created. The files are realtemp.doc (which has temp attribute set) and pseudotemp.tmp (which is filtered by DFSR). <Upstream> 20080908 13:43:09.067 3856 USNC 1244 UsnConsumer::ProcessUsnRecord Skipping USN_RECORD with FILE_ATTRIBUTE_TEMPORARY flag: the USN journal update process will mark when files are filtered for any reason. In this case the file is structurally temporary due to an attribute. + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x80000000000B6 + ParentFileRefNumber: 0x70000000000B3 + USN: 0x268e058 + TimeStamp: 20080908 13:43:09.052 Pacific Standard Time + Reason: Close Security Change + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x120 0x20 (file) & 0x100 (temporary) + FileNameLength: 24 + FileNameOffset: 60 + FileName: realtemp.doc the file called ‘realtemp.doc’ + <Upstream> 20080908 13:43:09.083 3856 USNC 1294 UsnConsumer::ProcessUsnRecord Filtered USN_RECORD: In this case the USN update is filtered because the file has a name matching the DFSR file filters (by default, ~*, *tmp, *.bak) + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x50000000000B4 + ParentFileRefNumber: 0x70000000000B3 + USN: 0x268e160 + TimeStamp: 20080908 13:43:09.083 Pacific Standard Time + Reason: Close Rename New Name + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 file, not a folder + FileNameLength: 28 + FileNameOffset: 60 + FileName: pseudotemp.tmp file ends with extension of TMP and is filtered Understanding DFSR debug logging (Part 21: File replication performance from throttling (uses debug severity 5)) In this final scenario we will see a file being replicated successfully, but where the replication appears to be very slow. A bandwidth throttle has been configured within the DFSR replication group schedule to restrict traffic to 128Kbps. This is useful in understanding how throttling works as well as determining that slow replication has been configured intentionally. (throttleupstream - Dfsr00010 - 2008.log and throttledownstream - Dfsr00012 - 2008.log) These are two Windows Server 2008 servers called 2008x86SRV10 and 2008x86SRV11 in the contoso.com domain. The logs are from 2008x86SRV10 (the upstream) and 2008x86SRV11 (the downstream). The replication schedule is at 128 Kilobits per second and the file being replicated is named “imageres.dll”. Debug logging severity is set to 5 to see additional details. <Upstream> 20080909 17:01:15.186 2880 USNC 2612 UsnConsumer::CreateNewRecord LDB Inserting ID Record: file is created on the upstream server. + fid 0x500000000BB0A + usn 0x27d2a30 + uidVisible 0 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 16010101 00:00:00.000 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 + parent {43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 00:01:15.186 GMT (0x1c912d857ca1d84) + createTime 20080910 00:01:15.186 GMT + csId {43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name imageres.dll file named ‘imageres.dll’ + <Upstream> 20080909 17:01:15.186 2880 USNC 2615 UsnConsumer::CreateNewRecord ID record created from USN_RECORD: + USN_RECORD: + RecordLength: 88 + MajorVersion: 2 + MinorVersion: 0 + FileRefNumber: 0x500000000BB0A + ParentFileRefNumber: 0xC00000000BA6B + USN: 0x27d2a30 + TimeStamp: 20080909 17:01:15.186 Pacific Standard Time + Reason: Basic Info Change Close Data Extend Data Overwrite File Create + SourceInfo: 0x0 + SecurityId: 0x0 + FileAttributes: 0x20 + FileNameLength: 24 + FileNameOffset: 60 + FileName: imageres.dll + <Upstream> 20080909 17:01:15.186 2880 LDBX 4300 Ldb::UpdateLastVersion Updating lastVersion:90 <Upstream> 20080909 17:01:15.186 2880 LDBX 3340 LdbManager::WakeUpSleepers Wake up callback 009786F8 <Upstream> 20080909 17:01:15.186 2956 UPST 1399 UpstreamTransport::FlushVvUp 002F58A8 <Upstream> 20080909 17:01:15.186 2956 UPST 1417 UpstreamTransport::FlushVvUp send connId:{9569E157-9E0A-4AE0-B62C- 90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} seqNumber:12 status:0 vvGeneration:8 vvUp: <Upstream> 20080909 17:01:15.186 3980 SRTR 1880 SERVER_RequestVersionVector Received from connId:{9569E157-9E0A-4AE0- B62C-90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} seqNumber:13 changeType:all <Upstream> 20080909 17:01:15.186 3980 SRTR 1927 SERVER_AsyncPoll Received from connId:{9569E157-9E0A-4AE0-B62C- 90D23303DE85} <Upstream> 20080909 17:01:15.186 3980 UPST 1297 UpstreamTransport::AddAsyncPoll Inserted new async request rpcStatePtr:002F58A8 <Upstream> 20080909 17:01:15.186 2956 UPST 1399 UpstreamTransport::FlushVvUp 002F58A8 <Upstream> 20080909 17:01:15.186 2956 UPST 1417 UpstreamTransport::FlushVvUp send connId:{9569E157-9E0A-4AE0-B62C- 90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} seqNumber:13 status:0 vvGeneration:8 vvUp:{0E1F0993-5130-4BB2B409-FD13366B9A0C} |-> { 32, 33} + {5CB120DE-D2C2-452A-8280-B45FC155224F} |-> { 84..90} + <Upstream> 20080909 17:01:15.186 3980 SRTR 882 SERVER_RequestUpdates Received from connId:{9569E157-9E0A-4AE0-B62C- 90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} credits:32 requestType:all <Upstream> 20080909 17:01:15.186 3980 UPST 88 UpdateBuffer::UpdateBuffer UpdateBuffer created. connId:{9569E157-9E0A- 4AE0-B62C-90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} <Upstream> 20080909 17:01:15.202 2956 JOIN 1122 Join::SubmitUpdate LDB Updating ID Record: + fid 0x500000000BB0A + usn 0x27d2a30 + uidVisible 1 + filtered 0 + journalWrapped 0 + slowRecoverCheck 0 + pendingTombstone 0 + internalUpdate 0 + dirtyShutdownMismatch 0 + meetInstallUpdate 0 + meetReanimated 0 + recUpdateTime 20080910 00:01:15.186 GMT + present 1 + nameConflict 0 + attributes 0x20 + ghostedHeader 0 + data 0 + gvsn {5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 + uid {5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 + parent {43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D}-v1 + fence 16010101 00:00:00.000 + clockDecrementedInDirtyShutdown 0 + clock 20080910 00:01:15.186 GMT (0x1c912d857ca1d84) + createTime 20080910 00:01:14.874 GMT + csId {43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} + hash 00000000-00000000-00000000-00000000 + similarity 00000000-00000000-00000000-00000000 + name imageres.dll + <Upstream> 20080909 17:01:15.202 3980 SRTR 1927 SERVER_AsyncPoll Received from connId:{9569E157-9E0A-4AE0-B62C- 90D23303DE85} <Upstream> 20080909 17:01:15.202 3980 UPST 1297 UpstreamTransport::AddAsyncPoll Inserted new async request rpcStatePtr:002F5308 <Upstream> 20080909 17:01:15.202 2956 JOIN 1167 Join::SubmitUpdate Sent: uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 name:imageres.dll connId:{9569E157-9E0A-4AE0-B62C-90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} csName:throttlerf <snipped out information documented in other scenarios> <Downstream> 20080909 17:01:18.905 3188 STAG 1218 Staging::LockedFiles::Lock Successfully locked file UID: {5CB120DE- D2C2-452A-8280-B45FC155224F}-v90 GVSN: {5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 state: Downloading (refCount==1) <Downstream> 20080909 17:01:18.905 3188 STAG 4113 Staging::OpenForWrite name:imageres.dll uid:{5CB120DE-D2C2-452A-8280- B45FC155224F}-v90 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 upstream server ready to replicate file <Downstream> 20080909 17:01:18.905 3188 DOWN 6256 DownstreamTransport::DownloadFileAsync rpcAsyncState:045AE088 <Downstream> 20080909 17:01:18.905 3188 DOWN 5970 DownstreamTransport::RpcAsyncPipeDownload rpcAsyncState:045AE088 <Upstream> 20080909 17:01:18.921 696 SRTR 2529 RpcAsyncPipeState::RpcAsyncPipeState this:009210A0 rpcAsyncState:002F58A8 context:00933280 bytePipe:002E8590 <Upstream> 20080909 17:01:18.921 696 SRTR 3051 RawGetFileDataAsyncState::RawGetFileDataAsyncState 009210A0 <Upstream> 20080909 17:01:18.921 696 SRTR 2596 RpcAsyncPipeState::Start this:009210A0 <Upstream> 20080909 17:01:18.921 696 SRTR 2710 RpcAsyncPipeState::InitializeDataReader Starting pipe thread. this:009210A0 <Upstream> 20080909 17:01:18.921 3784 SRTR 3079 RawGetFileDataAsyncState::DataPipeThread Entering data pipe thread. this:009210A0 <Upstream> 20080909 17:04:31.134 928 CFAD 10450 Config::AdReader::Peek Subscriptions Checksum, old = 20953, new = 20953 <Upstream> 20080909 17:09:07.506 3784 SRTR 3132 RawGetFileDataAsyncState::DataPipeThread Exiting data pipe thread. this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2940 RpcAsyncPipeState::Process Push eof this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2969 RpcAsyncPipeState::Process Completing this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2648 RpcAsyncPipeState::ProcessIoCompletion Release this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 3056 RawGetFileDataAsyncState::~RawGetFileDataAsyncState 009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2553 RpcAsyncPipeState::CloseDataPipe this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2556 RpcAsyncPipeState::CloseDataPipe Shutting down pipe. this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2543 RpcAsyncPipeState::~RpcAsyncPipeState this:009210A0 <Upstream> 20080909 17:09:07.506 3832 SRTR 2553 RpcAsyncPipeState::CloseDataPipe this:009210A0 <Upstream> 20080909 17:09:41.148 928 CFAD 10450 Config::AdReader::Peek Subscriptions Checksum, old = 20953, new = 20953 <Downstream> 20080909 17:01:23.327 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 4100 ms (waitResult 258) downstream DFSR service replicates a percentage of the file at full bandwidth, then artificially stops replicating. <Downstream> 20080909 17:01:25.030 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 1700 ms (waitResult 258) <Downstream> 20080909 17:01:28.436 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 3400 ms (waitResult 258) <Downstream> 20080909 17:01:38.437 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 10000 ms (waitResult 258) <Downstream> 20080909 17:01:50.344 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 11900 ms (waitResult 258) <Downstream> 20080909 17:02:02.751 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 12400 ms (waitResult 258) <snipped out many repeats of this> <Downstream> 20080909 17:14:55.987 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 5600 ms (waitResult 258) <Downstream> 20080909 17:14:58.299 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 2300 ms (waitResult 258) <Downstream> 20080909 17:15:01.909 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 3600 ms (waitResult 258) <Downstream> 20080909 17:15:09.018 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 7100 ms (waitResult 258) <Downstream> 20080909 17:15:18.518 3188 DOWN 6631 BandwidthThrottler::WaitOneInterval Throttling: Waited for 9500 ms (waitResult 258) After roughly 14 minutes the file has been replicated <Downstream> 20080909 17:15:18.518 3188 DOWN 6093 DownstreamTransport::RpcAsyncPipeDownload Wait completion rpcAsyncState:045AE088 RPC file download session pipe can be closed. <Downstream> 20080909 17:15:18.550 3188 INCO 5735 InConnection::RdcGet Update syncInfoHistory <Downstream> 20080909 17:15:18.550 3188 INCO 5610 InConnection::LogTransferActivity Received RAWGET uid:{5CB120DE-D2C2- 452A-8280-B45FC155224F}-v90 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 fileName:imageres.dll connId:{9569E157-9E0A4AE0-B62C-90D23303DE85} csId:{43F13D7D-F9B1-42C6-B90C-7BC8DC2EB16D} stagedSize:12597886 <Downstream> 20080909 17:15:18.550 3188 MEET 1970 Meet::Download Done downloading content updateName:imageres.dll uid:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 gvsn:{5CB120DE-D2C2-452A-8280-B45FC155224F}-v90 file has been copied to the staging directory on the downstream server. This wraps up the 21 part blog series on reading the DFSR debug logs. I hope you found this interesting and helpful. - Ned Pyle