To get this working for you, we want to use the content scan you expect (probably Rules-based) and have the comparison be configured to return the status you want. If you double click to view any files, that runs a Rules-based scan, which replaces any previous scan and updates the center column for that pair of files. My hunch would be that either the Override setting was disabled, or that the content scan is returning that the files are 'different' when you expect them to be the same. Once one of these scans is run, the timestamp does not matter directly, since it is overridden by the Override Quick Test results option (enabled by default). To compare all data, you use a Binary scan, but to compare only the visible text you would use a Rules-based scan. However, once viewed in the Text Compare, the files might then appear as the same, since viewable data might be equal (while invisible Binary data might be different). With default settings (Timestamp/Size/Override enabled) with the addition of a Binary scan, if files show as different, it would mean they are Binary different. Initially, I did not think that the timestamp was the cause, but it is hard to say without a screenshot showing the center column I mentioned. Please let us know if you have any questions. This column does not populate between folders, only files, so you need to expand subfolders to verify. ![]() You can determine what results a content scan returned by looking at the center column between two files, which populates with the specific content scan's results. You would then also enable Binary or Rules-based. This is controlled in the Session Settings, Comparison tab, where Timestamp, Size, and Override Quick Test Results should all be enabled. This could be directly to the destination, or to a 3rd temporary location before you copy over to the server.Ī Binary compare would compare the contents, and by default would override the timestamp/size comparison. Use the Edit menu -> Expand All, Edit menu -> Select All Files, then Copy To Folder (removing the folder structure). Instead of using Syncovery to flatten the structure, you could use BC3's Copy To Folder command. ![]() Viewing the files is similar to running a Rules-based comparison scan, which could be used instead of a Binary scan if these results are acceptable. If the timestamp is different, then the files would be marked as different. This difference may not be visible: it could be a end of line character difference or other binary metadata.īy default, BC3 only performs a timestamp/size comparison. If a binary content scan is returning that the files are different, then there is a binary difference between them. But I was under the impression that binary comparison COMPARED THE CONTENTS of the files, and ignored the dates? I have been told that it might be the case that the subfolder-stripped files are not correctly updated by date. But all the files INSIDE a sub-folder, which the sync software then strips out to 'flatten it' are NOT reported as identical by the binary comparison.Ĥ. The files in the root directory of the folder being sync-ed report being identical on both sides. ***Clearly, something about the process of "flattening" the files changes them. I created another to test this, and it ALSO identified it in both places as THE SAME.ģ. ![]() It was a test document I created but saved in the parent folder root, OUTSIDE THE FOLDER TREE. *** The software DID mark one file as identical on both the WebDav Flat-folder and the Local Tree-Folder. But I don't think the dates should matter if its doing a binary content comparison?Ģ. The dates modified are different (since the WebDav files have the date of transfer, and the originals have date of creation of last modified).ġ. I've tested it several times - opening different random files, and have found them to be exactly the same (Windows reported size for instance). But it reports that ALL the files in both folders are different (no matches, even though these are the same files) I have tried Beyond Compare to investigate out of the 3000 or so files which ones are different (not being sync-ed). ![]() However, checking both the local Tree folder and the Flat file WebDav folder, I found different numbers of files (even though the sync software only reported a few naming conflicts, there is a 100+ file discrepancy). (This is accomplished with sync software called Syncovery.) I use sync software to 1-way sync my document folder to a WebDav folder.īut I have a weird usage case which requires a FLAT FILE STRUCTURE on the WebdDav side, so the software strips out the directory structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |