What we are seeing is log files that are almost exactly 2GB, and where the file list building detail is missing, the file action begins in the middle of a file name (so we can't see what came before), and the log ends in the middle of an action entry with no summary data. The only additional Log setting we enable is File List Building Detail, so I wouldn't expect that to create "excessive" logging. However, with 400000+ files with actions, I guess it could be.
Here are a couple of examples of what we see:
-a---- 5/27/2022 3:40 PM 2147540449 3_CTE - 2022-05-27 13.21.30 - 435384 copied (621.5GB), 3477 renamed.log
-a---- 5/26/2022 7:00 PM 2149779767 3_CTE_Debug - 2022-05-26 16.24.39 - INCOMPLETE. 529135 copied (707.7GB) of 529136, 9974 renamed, Err.log
This is not an editor issue, this is a file size issue. And we don't intend to use an editor at all with these, but rather to parse out and re-format the data in the logs with Powershell.
I will give the Exact Mirror with the safety options a try, but I have a couple of questions:
- If this doesn't work, we'll need to keep doing what we are doing. Please provide the INI setting that will allow us to keep the Log settings permanent.
- Since I don't have an easy way to test with the production data, how can I run a "what if" that generates the list of actions that would be taken, but without taking them?
Thanks for the help!