Open topic with navigation

Verification log

In the log file, each verification process is delineated by beginning and end markers. A list of files that are different on the source and target is provided as well cumulative totals for the verification process. The information provided for each file is the state of its synchronization between the source and the target at the time the file is verified. If the remirror option is selected so that files that are different are remirrored, the data in the verify log reflects the state of the file before it is remirrored, and does not report the state of the file after it is remirrored. If a file is reported as different, review the output for the file to determine what is different.

Sample verification log

• Timestamp—The last modified date and time of the file
• Size—The size, in bytes, of the file
• Mask—The attributes associated with the file. See further details below.
• Security descriptors—The NTFS file permissions of the file. If the file permissions are different, the message "Security descriptors are different" will be logged. If the file permissions are the same, nothing will be logged.
• Bytes out of sync—The number of bytes that are not synchronized between the file on the source and the file on the target. If the data in the file is identical, the message "0 BYTES OUT OF SYNC" will be logged. If the file is different, the message will indicate how many bytes were different. This message does not indicate that the file was remirrored during the verify.

The mask must be converted in order to determine what attributes are assigned to a file. The mask is a hexadecimal number corresponding to a binary number that indicates what the attributes are. Using the following steps, you can determine how the mask corresponds to the attributes of a file.

1. Each mask begins with 0x. Identify the hexadecimal number after the constant 0x. For example, if the mask is 0x23, then the hexadecimal number you are interested in is 23. The hexadecimal number may be up to four digits.
2. Convert the hexadecimal number to its 16-digit binary equivalent. You can use the Windows calculator for this conversion.
1. Select Calculator from your Accessories program or apps group.
2. Switch to scientific view, if it is not already in that view, by selecting View, Scientific.
3. Select Hex.
4. Enter the hexadecimal number, for example 23, as specified in your verification log.
5. Select Bin and the hexadecimal number will change to the binary equivalent.
6. Pad the beginning of the binary equivalent with zeroes (0) so that the number is 16 digits long. For example, hexadecimal number 23 converts to 100011, so the 16-digit binary equivalent would be 0000000000100011.
3. Determine what number (0 or 1) appears in each position of the binary number. Because binary numbers count from right to left, start with position 1 on the right.
• 1—Read only
• 2—Hidden
• 3—None
• 4—System
• 5—Directory
• 6—Archive
• 7—Encrypted
• 8—Normal
• 9—Temporary
• 10—Sparse file
• 11—Reparse point
• 12—Compressed
• 13—Offline
• 14—Not content indexed
• 15—None
• 16—None

4. Using the list above, identify those attributes that are enabled by those positions equal to one (1). The positions equal to zero (0) are disabled and that attribute does not apply. So hexadecimal number 23, which converted to 0000000000100011, indicates read only, hidden, and archive. Another example might be mask 0x827 which converted to binary is 0000100000100111. Positions 1-3, 6, and 12 are all enabled which indicates the file is read only, hidden, archive, and compressed.

   Files that were replicated with the Replicate NTFS security attributes by name feature enabled, will be identified as different in the log file because of the local name attribute. The files will be the same.