After looking at the Log files, Windows File Explorer, Reflector’s History screen, and the log files all match. Differential files are always deleted when the Log file says they should have been deleted, and likewise are not deleted when there is no mention in the log file. That leads me to believe there is a bug in the software/logic.
Ver 2.3.6 has two file output structures.
A.If ‘Differential copies to make before Full’ is larger than ‘Differential Copies to keep’, only the last ‘Differential copies to keep’ Differential copies are kept. No Full copies are ever made.
B.If ‘Differential copies to make before Full’ is equal or smaller than ‘Differential copies to keep’, ‘Differential copies to keep’ number of Differential copies alternate with Full copies. No copies are ever deleted. An initial Full copy is made.
I don’t think this is the intended output structure.
I’m a hardware electrical engineer, so I’m not in a good position to make specific software suggestions. To collect my thoughts and hopefully better communicate the problem, I put together a partial flow chart and some tables.
My suggested changes are:
1.Set up an internal counter of the number of Differential copies created since the last Full copy. As Differential copies are deleted, this counter does not change. This counter is used to calculate when to make the next Full copy, which also resets the counter.
2.In the logic to calculate when to delete Differential copies, don’t stop counting Differential copies at the last Full copy. Count all Differential copies. This will allow the ‘Differential Copies to keep’ equal or greater than ‘Differential copies to make before Full’ cases to delete properly.
Probably my flow chart is not exactly how the software is implemented, but I hope it helps with two presently interrelated variables.
Thanks
bwhit
Ver 2.3.6 has two file output structures.
A.If ‘Differential copies to make before Full’ is larger than ‘Differential Copies to keep’, only the last ‘Differential copies to keep’ Differential copies are kept. No Full copies are ever made.
B.If ‘Differential copies to make before Full’ is equal or smaller than ‘Differential copies to keep’, ‘Differential copies to keep’ number of Differential copies alternate with Full copies. No copies are ever deleted. An initial Full copy is made.
I don’t think this is the intended output structure.
I’m a hardware electrical engineer, so I’m not in a good position to make specific software suggestions. To collect my thoughts and hopefully better communicate the problem, I put together a partial flow chart and some tables.
My suggested changes are:
1.Set up an internal counter of the number of Differential copies created since the last Full copy. As Differential copies are deleted, this counter does not change. This counter is used to calculate when to make the next Full copy, which also resets the counter.
2.In the logic to calculate when to delete Differential copies, don’t stop counting Differential copies at the last Full copy. Count all Differential copies. This will allow the ‘Differential Copies to keep’ equal or greater than ‘Differential copies to make before Full’ cases to delete properly.
Probably my flow chart is not exactly how the software is implemented, but I hope it helps with two presently interrelated variables.
Thanks
bwhit
Statistics: Posted by bwhit — 15 Feb 2023, 07:17