Two File Servers and a whole lot of duplication and corrupt files

[jsejas]

FS A= File server A
FS B= File server B

FS A was using DFS to replicate its data contents to FS B and was working until about this time last year.

FS A received one of the first cryptolock viruses in the USA. Completely locking up the server for an extended amount of time. In the time of crisis the previous MSP added a login script to add a second mapped drive to FS B which had all the contents of FS A because of DFS and instructed the users to use that drive for their work as it was "current" and not infected. This was supposed to be a temporary solution until the FS A was unlocked and cleaned up.

DFS was disabled the moment the virus hit FS A.

FS A was eventually cleaned, however there are now MANY corrupted files on FS A so the mapped drive to FS B remained in place because there were no corrupted files on FS A.

The previous MSP was fired and we were hired. This is part of the clean-up project we were left with after they had gone.

Users at the organization have been saving to both FS A and FS B with no real direction on which one they are supposed to use internally. We sat down with the users and explained that a clean up of both directories had to be done and handled internally. We are not going to help clean-up their file structure. Too much liability. However, we want to provide them with tools that can help them. Here are some scenarios that we WILL run across:

Same file names
Corrupted files
Duplicate folders
Duplicate file names in different folders
Duplicate folders in different root folders

I'm sure there will be many more fun scenarios but, I just can't think of any at the moment.


Is Beyond Compare the best tool for helping the users? I know the risks on letting multiple users use this tool so I am still apprehensive.


Any similar scenarios or solutions are welcome.


Thank you for your time,

Jim

[Aaron]

Hello,

BC3 can load both locations (two directories) side by side, and then compare them based on file structure and file name. In 3 of the 4 view modes, this means that the folder's location (subdirectory structure) is important for the alignment of the items. If the folders have different names, or have been moved, they would not align and be detected as a difference.

In the 4th view mode, you can Ignore Folder Structure and align all files names in any subfolder based on name. This requires that all files in all subfolders have unique names, as the name alignment is first before any comparison is run.

If the files can be aligned, then we can run a variety of comparisons (including a full Binary, or configurable Rules-based) to determine if the files are different, and can easily bring one file or the other over to another side.

Since File System B is so important (the only clean copy?), you can customize a shortcut to BC3 with a /lro or /rro to disable editing on one side or the other. If possible, it might be best to create a full back up of either or both locations before letting users modify them, just in case users accidentally delete or edit something they shouldn't.