So when the setup gets to extracting program files, it disables this redirection. This has several side-effects including the setup having some of its file system requests redirected to pseudo folders. When used on 64-bit machines, Windows runs it under WoW64 emulation. Unlike the app itself that comes in both 32- and 64-bit versions, the setup is a 32-bit executable. ⦁ Resolved an exotic issue with the setup being run under Wow64 These are basically "are you alive?" pings and they do nothing more but pollute the logs. ⦁ Decreased log verbosity in service mode - the Interrogate commands sent by Windows to the service are no longer logged. So this copy-to-temp-restart-from-there piece of code has been in the installer from the very beginning, but the latest version (76.x) has effectively disabled it when we added support for scripted installation. This is done, because network shares accessible in a non-privileged Admin session may not necessarily accessible from an elevated version of the same (these are two different sessions and Windows doesn’t sync their share lists, at least not by default). In this case, when the setup needed to elevate (UAC), it would copy itself to a local temporary directory and restart using this copy instead. The issue was with running the setup off a network location. ![]() ⦁ Resolved an issue when the setup is run off a remote location ⦁ Resolved an issue when de-elevation of the UI process fails - that's for an exotic case when "Run as Admin" is disabled in Preferences while bvckup2.ini is inaccessible for writing. Will effectively force the app to behave exactly as it did prior to 75.9. The following line in backup job's settings.ini. Now, starting with 76.1 suppressing attribute comparison now also eliminates their querying during the scan phase. This resulted in needlessly slower scanning, especially for over-the-network locations. However, this did NOT suppress querying these attributes during the scan phase. With release 75.10 we added an option to suppress *comparison* of security attributes, forcing the app to do the original "lazy" attribute copying. This is a fairly expensive operation, especially when it's done at scale. With release 75.9 the app started also query and compare these attributes if a backup was set to copy them. It never monitored these attributes for changes. Prior to release 75.9 the app would copy these attributes if the option was enabled, but only if a file needed updating for some other reason. ![]() Querying this information during the scan phase - this has to do with how a backup is processed it is set to copy DACL/Owner/Group attributes. ⦁ Disabling security information monitoring now also disables See for details on INI file format and editing. These alerts can be suppressed by setting respective entry in engine/bvckup2-engine.ini file to 0: Former is due to a check for missed backups that is run when the app is started and latter is when it is running and detects computer waking up from a sleep. ⦁ New log message for backup runs that are missed due to theĬomputer being asleep or hibernating - the app now differentiates between missing a backup because it was not running and because the computer was asleep. ⦁ Hidden files matching found.? are now excluded by default - these are "lost" disk clusters recovered by chkdsk. This is a bit messy, but it will be reworked shortly. This will leave the delivery config behind so that the unlicensed alert could be sent. This obviously requires the alert delivery to be configured, so if you'd like to enable just this "unlicensed" alert, you will need to fully configure an alert for any backup job, OK the changes and then switch that job alert off. In similar vein the app will now dispatch an email alert when it detects entering an unlicensed state. New email alert for when the app becomes unlicensed ![]() If you are on the Insider Preview program, you will still need to reactivate once more after the next Windows update, but that's it. So as of this release the Install Date is excluded for the installation fingerprint. In practice however Windows updates that are pushed through the Microsoft's Insider Preview Program change Windows Install Date, thus invalidating Bvckup 2's license and requiring the reactivation. Revised version of system IDs as used for license bindingīvckup 2 installation license is bound to a dozen of system parameters, including things like Computer SID and Windows Install Date, all of which are supposed to remain static on any given computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |