![]() 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. You are discouraged from using UI-side overrides, because it's cleaner to let the engine manage new job defaults.⦁ 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. The difference here is that the former will clear the default exclusions list and the latter will preserve it. The engine looks for and loads \engine\backup-override.iniĭO NOTE that #2 and #3 require release 78.19 or newer.Īdditionally, the UI will also do legacy processing of new backup settings by loading overrides either from \ui\backup-template.ini or The engine looks for and loads \engine\backup-template.iniģ. The engine first sets a new job to hard-coded defaults.Ģ. Similar mechanism can be used to override values in a template used to initialize new backup jobs.ġ. #2 provides a way to apply an override to all jobs at once and #3 is a way to patch a specific job.ĭO NOTE that #2 requires release 78.19 or newer. The engine looks for and loads \engine\backup-00xx\override.ini The engine looks for and loads \engine\backup-override.iniģ. The engine reads \engine\backup-00xx\settings.iniĢ. When a job is loaded, its settings are read and then patched as follows:ġ. Similar mechanism is used for overriding backup job settings. Overriding settings - Existing backup jobs These files are never modified by the program. Override files are loaded immediately after primary ini files. ![]() In addition to directly editing bvckup2-engine.ini and bvckup2-ui.ini, you can also modify settings in these files by creating a so-called "override" ini file and placing your changes there. Whenever you tell the app to download and install the update (in response to the "New version available" prompt), the update is downloaded and stored in this directory. This folder host the UI configuration (window state, position, update check status, etc.) in a file called. \engine\bvckup2-engine.ini - the engine configuration \engine\bvckup2-email.txt - a text file with the email alert template \engine\bvckup2.lic - a text file with your license Now, climbing back up to \engine level, there are several files of note. This folder can be deleted if needed, just keep in mind that doing so will cause the app to re-copy files in full once they are modified at source. This will be the largest part of each backup's configuration, potentially with a lot of files, taking up non-trivial amount of disk space. The "delta" sub-folder contains binary files with per-block checksums for all files in the backup that were copied with the delta copier. Snapshot.dat - binary file with the snapshot of the destination Settings.ini - the backup configuration, all of it The engine folder contains settings and the state data of all configured backups, each in its own sub-folder, starting with backup-0001:ĭelta\ - sub-folder with checksum files from delta copierīackup.log - plain text file with the log of the backup jobīackup.tdb - binary index file of the above, used internally These capture the context of certain operations in the app and they are primarily needed for troubleshooting issues with tech support. There will likely be an assortment of other log files, e.g. \bvckup2.ini - settings shared between the engine and the UI \updates - a folder with all previously downloaded app's updates \engine - a folder with the engine data (see below)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |