![]() It basically didn't know AD streams existed so it panicked when it started to get progress updates on them. ⦁ Fixed an issue with copying AD (alternate data) streams - this was introduced in 80.9 with addition of the new time/speed estimator. Just to make things a bit more organized compared to how it was before. It groups together VSS snapshot disposal, device/media ejection, email alert dispatch and post-backup command details. ⦁ Added "Finishing up" section to the log of a backup run. It is however possible to switch this off if needed. It's a fix transparent to normal use, so this is what the program will do from now on. The person who reported this didn't manage to find the exact cause, but they reported a workaround - adding a space at the end of each line. First line will have only one symbol clipped, second - two, etc. This has to do with a bizarre case when a text in email alerts had every line split into two parts with a split point steadily crawling from the back of the line to its beginning. ⦁ Added an option for ending all lines in email alerts with a space. ![]() ⦁ Added display of the name of an AD stream being copied. Make the animation look a bit nicer and smoother. ⦁ Increased refresh rate of the progress reporting to 20 Hz - a smaller change that bumps up the number of progress bar updates from 4 to 20 times a second. The goal is to ensure that we _always_ show progress regardless of how slow it goes, but without it spinning _too_ fast. ⦁ Added new adaptive %-age display for longer file copies - the UI will now automatically increase the number of decimals in the completed %-age value if the copying is going slow. Second, the program would panic (due to a wrong self-consistency ⦁ Fixed an issue with retrying the backup of new files - that is, if theīackup of a brand new file failed on the first try, but succeeded on Too heavy and "2" was off its proper pixel boundary. ⦁ Cleaned up and re-balanced the logo a bit. The program to dispose of the updates once they are installed byīy adding the following override to the engine settings: With this release it is now possible to tell When the program is updated using built-in Check For Updatesįunction, all downloaded update packages are retained in itsĬonfiguration directory. ⦁ Added an option for not retaining downloaded updates. This is the exact same information that is already logged for filesīeing updated with regular (non-archiving) backups. It'd be possible to understand why the file was deemed modified. Now log timestamps and sizes of source and backup copies so that When the archiving of _modified_ files is enabled, the program will ⦁ Added detailed logging around modified file archiving. ⦁ Added new time/speed estimator for longer file copies. More specifically, this warning was never issued and now it is. The issue was with detecting if the source file was actively changing during the copy and issuing a warning to that effect. The file will first be copied into a temp file, which will then renamed into its properly name backup copy. Two-stage copying is used when _updating_ files and the delta copying is off. ⦁ Fixed a smaller issue with the 2-stage file copier. At this point it used to start in the desktop mode instead of connecting to the service. More specifically - install the program, switch to the service mode, login under a different desktop user (or alternatively nuke the UI-side config folder), start the UI, exit it, start it again. ⦁ Fixed an issue with the UI startup in service mode - this has to do with starting the UI under a _different_ user account for the _second_ time. This release merely tightens up the list of exact errors and conditions that are used to detect these cases. When this happens, the backup is cancelled and immediately re-run, but with destination re-scanned afresh. a folder that should be empty is not empty, a file that shouldn't exist is already there, etc. ⦁ Revised the logic used to detect out-of-sync snapshots - that is, when the program runs into an error that can only mean that its cached file index of destination is invalid, e.g.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |