Jun 17, 2019
This release implements a licensing model change. In a gist, we are switching from the use-based licensing to the feature-based model.
* This change has been in works for a very long time, being first
announced almost 3 years ago in August 2016. I genuinely hope
it doesn't come as a surprise to anyone's who's been following
bvckup2 development and updates.
New license types
Previously, the type of required license was determined by whether the software was to be used on one's home computer for processing personal data or in any other setup.
With this release, the license determines the feature set the program:
⦁ Pro licenses are all inclusive and cover all features, both present
⦁ Basic licenses are meant for a simpler use and include a subset
of Pro features. It is now considered complete and it will not be
Additionally, the Server edition of a Pro license is now be required for Windows Server installations.
For complete details see this page - https://bvckup2.com/features
Support and upgrade access
Another change is with the tech support and software upgrades.
Basic licenses will be limited to forum-based support and minor updates (patch releases) only. Pro licenses will come with a year of Pro support that includes email-based support and access to major updates (upgrades).
After a year, it'll be possible to extend Pro support for another year for a fee of 20% of the original license cost. This is optional. Should it be not extended, the installation will no longer be eligible for _upgrading_ and its tech support will downgrade to the public forum option.
This is essentially a "rolling" form of a conventional upgrade model when a new major version is released every year and existing users have a choice of either staying with the last year release or upgrading at a substantial discount.
This post has a bit more details - https://bvckup2.com/wip/07062018
Status of existing licensess
All existing licenses and activation codes remain valid and they will continue to function exactly as they did before.
Personal and Professional licenses will be treated by new program versions as if they were Pro licenses, of Workstation and Server kinds respectively.
They will also have non-expiring Pro support coverage, meaning that they will receive all patches and upgrades on us, forever.
In other words, the program now supports 4 licenses types - Personal, Professional, Basic and Pro - but only the new ones are available for purchase.
For any questions please get in touch via email@example.com
or post them here - https://bvckup2.com/support/forum/topic/1076
Jun 17, 2019
Additional changes in this release
⦁ Reworked how verbose file and folder exclusions work
Starting with R80 explicitly excluding a folder in Backup What window
of backup settings now unconditionally takes all folder contents out of
backup, with no other "include" rules being applied to it.
See this post for details - https://bvckup2.com/wip/11062019
⦁ Updated the logo
See this post for details - https://bvckup2.com/wip/06062019
⦁ Reworked check-for-updates mechanism for better clarity
See this post for details - https://bvckup2.com/wip/13062019
Jun 24, 2019
⦁ Resolved an issue with expanding More Option section
⦁ Resolved an issue with showing bogus "missed a run" warning when
upgrading from pre-80 releases. See this post for details -
Aug 08, 2019
⦁ Run-on-device-arrival scheduling now applies to local devices only -
as opposed to being also triggered by a network share becoming
⦁ Exporting configuration now also picks up email alert templates.
⦁ Configuration self-backup now covers additional config files.
⦁ Resolved an issue with reporting reparse points that are folders -
that is, when running into a reparse paint _of an unknown type_
the program will now correctly report the event both if it is a file
reparse point and if it's of a directory kind.
⦁ Resolved a cosmetic issue with the Welcome window - some text was
clipped, and now it's not.
⦁ Resolved an issue with logging email alerting failures - an exotic issue
triggered when the dispatch of a "missed a backup run" alert ends
_precisely_ when the job is being launched. This literally required a
microsecond precision in timing, but apparently some installation
managed to achieve that.
⦁ Reworked email alerts module to double-check message formatting -
this has to do with a report of qmail refusing an email alert because it
(allegedly) contained a lone LF character as a line terminator  instead
of CRLF. Looking at the code on our side there's no way this could've
had happened, it always sends CRLF. But just in case the alerting
module now explicitly re-checks that all lines are CRLF terminated
immediately before sending them to the remote end.
Aug 21, 2019
⦁ Switched to using new code signing certificate - due to changing the
name of the company from Pipemetrics to IO Bureau.
Do note that because of this change all existing installations except
for 80.2 will receive an update packaged in a special way. This is
because versions 80.1 and older expect the update package to carry
a signature of "Pipemetrics SA", so we use some acrobatics to ensure
that's the case (even though we no longer can sign new releases with
that certificate). I'll post more details in the blog shortly as it's an
interesting topic if a bit technical.
⦁ Resolved an issue with auto-launching the UI in service mode - with
older installations that were switched to the service mode a while ago
(as in "several years"), R80.2 will erroneously assume that it needs to
run in a desktop mode IF it is set to auto-start on Windows logon.
The backup service would still run and execute all the backups, but
the UI wouldn't want to connect to it, insisting on running as a full
app => it will show up unlicensed and with an empty list of jobs.
The problem is benign and restarting the UI would re-attached it to
the service, but the symptoms were scary.
⦁ Resolved a logging issue with trial expiring at the exact same moment
one of the jobs starts a scheduled run.
Aug 23, 2019
⦁ Resolved an issue with scheduled backup jobs getting stuck in the
"Will run in a moment..." state. This is specific to 80.3 changes, so
if you are running 80.3, the update is required.
⦁ Updated the EULA to refer to the company under its new name.
Sep 24, 2019
⦁ Added support for opportunistic backup of offline files - this is related to the OneDrive folder backups. It is now possible to temporarily suppress processing of files that are offline (i.e. not cached locally).
for the background and
for the HowTo.
⦁ Added support for cloud-specific attributes to the file filters - it is now possible to exclude/include items based on their Pinned, Unpinned and Recall-On-Xxx attributes.
for the explainer.
⦁ Added ReFS to the list of recognized file systems - this basically means that bvckup2 now knows the timestamp resolution and the maximum file size of ReFS, which is used in cases when it cannot determine these through active testing.
⦁ Enabled support for TLS 1.1 and 1.2 in the email module - this should resolve issues with email alerts mysteriously failing with "failed to secure the connection" errors, when they were sent to mail servers refusing older protocol revisions AND just flat out dropping connections instead of reporting their issues with the protocol revision.
⦁ Humanized error reporting for offline cloud-stored files - a handful of errors relating to trying to read offline file is now also explained in plain English.
⦁ Fixed a quirk with scheduling of periodic jobs - this is a good one. Just like the Oracle from The Matrix, it's been with us from the very beginning.
Basically, if a job was set to run at 12:00, being run manually at 11:59 and then cancelled at 12:01, then it will be re-run immediately after that. This was because the time of the next run was computed relative to the _start_ of the previous attempt... whereby it should've been the latest of the last-attempt start and the last-good-run finish.
⦁ Resolved an issue with the SSD detection logic - we can all thank HTS541010B7E610 for this, because for whatever reason this HDD reports that it supports TRIM, which it clearly shouldn't since is an SSD-specific operation. Well done, WD.
⦁ Resolved an issue with reporting NTFS stream copying errors - destination-side errors were erroneously reporting as being source-side.
Oct 30, 2019
⦁ Added UI support for configuring program's update channel. See this blog post for details (and don't forget to hold Ctrl down when opening the Help menu) -
If all goes as planned, the "preview" channel will go live early next week.
⦁ Reworked the crash handling code - simplified it, removed some dependencies, etc. Not that it gets used a lot, but still it's better to have it and not need it than to need it and not have it.
⦁ Reworked engine-to-UI communication bootstrap - in service mode, the engine can now open log files on behalf of UI's process even if it runs under a non-admin user.
As per https://bvckup2.com/support/forum/topic/1042/6798
⦁ Fixed a scanner issue when running into a duplicate file/folder. More specifically, it would prematurely stop the scan of a folder if it managed to run into an item with a duplicate name, e.g. "aBc.txt" after already seeing "abc.txt".
This was the bug in the scanning logic. It is fixed now by, obviously, *not* stopping the scan and reporting the dupe as an error.
The context here is that Windows native NTFS is case-insensitive. It's preserves the case, but won't allow creating two files with names that differ only in their case.
However Linux re-implementation of NTFS is case-Sensitive, which is the norm in the Unix world. It is perfectly possible to create files that differ only in case... not that it actually gets used much, except by an accident.
So using an NTFS volume both in Windows and Linux may result in files that break Windows' case-insensitivity restriction.
⦁ Fixed a scheduling loop when a certain override is in place. As per this exchange - https://bvckup2.com/support/forum/topic/1251/6781
⦁ Fixed an issue introduced in 80.6 whereby the meaning of "set valid file data" option in ultra copier's configuration was reversed, so 80.6 ended up always trying to set the data. The issue was mostly cosmetic as this operation is optional, but it still counted as a backup error if it failed.
If you are seeing errors like the one in  and you are on 80.6, then do a manual update to 80.6.1 using https://bvckup2.com/update
. Otherwise updating is entirely optional.
Nov 20, 2019
⦁ 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. a folder that should be empty is not empty, a file that shouldn't exist is already there, etc. When this happens, the backup is cancelled and immediately re-run, but with destination re-scanned afresh. This release merely tightens up the list of exact errors and conditions that are used to detect these cases.
⦁ 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. 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. At this point it used to start in the desktop mode instead of connecting to the service. No more of that now.
⦁ Fixed a smaller issue with the 2-stage file copier. Two-stage copying is used when _updating_ files and the delta copying is off. The file will first be copied into a temp file, which will then renamed into its properly name backup copy. The issue was with detecting if the source file was actively changing during the copy and issuing a warning to that effect. More specifically, this warning was never issued and now it is.
Dec 16, 2019
⦁ Revised file attribute handling logic a bit - starting with this release, if the program sees a file system volume that supports the Archive attribute ONLY, then it will act as if this attribute is NOT supported either. This is a workaround for QNAP devices that will report Archive attributes set on files, but refuse to clear them.
⦁ Fixed an issue with destination snapshot management. It has to do with handling of files that get renamed _and_ updated between the backup runs when the backup is aborted between these two actions.
The problem was file's current timestamp was recorded in the snapshot after the rename and then again after the update. So the rename went through, but the update didn't, the file ended up looking like is was still in sync with the original.
Kudos to Aram for not only managing to trigger this issue, but also for noticing and reporting it.
Topic is locked.