villamaya.blogg.se

1. Bvckup error details are currently unavailable verification#
2. Bvckup error details are currently unavailable windows#

The problem was that the program was looking at source and backup copies to decide which meta data (attributes, timestamps, etc.) should be cloned after the contents are updated. This is referred to as "staged" copying and it helps preserving an older backup copy in case of abortive mid-backup failures. When a file are copied in full, the program first copies it into a temporary file on the backup side and then renames this temp file to match the source file. ⦁ Fixed an issue with "staged" file copying - this has to do with copying files _without_ the use of the delta copier, in full. More specifically, it will fail when backing up from a remote share and the symlink points at a location that is local to the remote machine. Now, as you can probably guess, in some cases this check misfired. In later 79 releases the scanning module got a new check, whereby it would query the attributes of a location that a symlink is pointing at and would complain and ignore the symlink if the query fails.

Bvckup error details are currently unavailable verification#

⦁ Revised symlink verification logic in the scanning module. Beware of the temptation to use WM_SETREDRAW, use with utmost care and only after due testing.Īlso added an explicit indicator of whether the background scan is still in progress or not. ⦁ Improved file tree browser rendering performance - tangentially related to the previous item, basically improved the rendering speed of the widget by at least a factor of 2. The issue was that if the window is OK-closed while the tree wasn't fully populated, any existing excl/incl rules that applied to not-yet-discovered items were discarded. It's a process that may take a while and it runs in the background. When the Backup Settings > Backup What window is opened, the file/folder selection widget starts populating the tree. ⦁ Fixed an issue with the file tree browser. ⦁ Fixed handling of certain exclude/include rule combos - this has to do with Copying module didn't handle it terribly well because of an overly strict internal check. Basically, we would append, say, 1 MB to such file and then ask it to be trimmed to exactly that new size - and the latter request will fail. This covers a particularly exotic case when a backup copy gets corrupted (at rest!) in a way that still allows extending it, but prevents it to be trimmed to the exact size. ⦁ Fixed handling of corrupted files in the copying module.

Bvckup error details are currently unavailable windows#

This had to do with certain Windows function being not available on XP and re-implemented using another, XP-specific API, which in turn appears to have been documented incorrectly, so things weren't working as designed.Īnd, yes, someone did actually run into this issue, so they ARE still on XP. ⦁ Fixed an issue on Windows XP with handling backup cancellation. For the life of me I can't recall why it was done this way, but regardless of that this restriction is now removed. Previously, when the program is set to auto-update itself, it wouldn't do that if there was no valid license. ⦁ Reworked auto-update option to not require a production license. The fix was to sequence these operations, so that one is executed after the other. "the file in use" reported for the folder rename). More specifically, if both file's and its parent folder's names need a case change (on the backup side), then in some cases these two changes will be made _exactly_ in parallel, resulting in some rather obscure errors (e.g. ⦁ Reworked name case changing logic to handle certain case better. Now the ID is preserved, so it's easier to find all retries of the same operation.

Previously, when a backup step was retried, it would appear in the log under a new step ID. ⦁ Reworked logging to preserve original IDs of steps when they are retried. ⦁ Reworked backup summary wording to be more precise in presence of errors and retries. ⦁ Reworked retrying logic to accommodate steps failing with 2+ errors. That is, the program will now retry folder creation, file/folder move and file copying steps if they fail with a transient error when cloning item's meta data (attributes, timestamps, security info, etc.) ⦁ Reworked retrying logic to act on errors that occur when processing item attributes.