Bvckup is an application that handles many complicated processes behind the scenes, yet keeps its main user interface extremely sleek and lightweight, allowing you to make full use of its extended functions without them overwhelming you.Additionally, this validation can be switched off if needed. These errors are non-critical, they don't cause the backup to be aborted. The overly pedantic code was relaxed to allow for malformed files names and the scanning module now reports all invalid names as errors. Except for one place where the code _expected_ the name to be valid and would fail a self-consistency test if the name was malformed. This case is notable because it's a quick and dirty way of concealing files from the common software and it's also a flag of malware presence.Īll other naming violations were checked, but weren't reported or acted on. Prior to this release the program checked for one specific violation of the naming rules - when the name started with NUL character and would effectively appear zero-length. This requires using the so-called native (NT) API, but it's not terribly difficult. In practice - you guessed it - it may, because it's still possible to create file/folders named like that. In theory, there should be no case when a program would see any of these forbidden names when it, say, lists directory contents. : and ?, and they also may not ASCII symbols with codes between 0 and 31 decimal. ⦁ Reworked handling of malformed file and folder names.īrought to you by, kudos to sjcnyc for reporting it.Īccording to the Microsoft spec file and folder names may not contain certain reserved symbols, e.g. ⦁ Resolved an issue with newly added backu The program would report the event, but won't actually stop waiting for the completion. ⦁ Resolved an issue with not acting on timeout while waiting for the post-backup command completion. Holding Ctrl down does the same thing as above - it forces an one-time rescan of the destination. When updating from 81.18 and earlier releases, all backup jobs that are set to use destination snapshots and perform file move detection will be forced to do an one-time destination re-scan.Īlternatively, any accumulated discrepancies may be flushed out by running backup jobs manually with Ctrl-Go. This issue was introduced in the original release 81 and it was due to a bug in a move detection logic in the planning module. In these cases, files _will_ be moved and/or renamed, but they will _not_ updated until the next job run that re-scans destination. and with the job set to use destination snapshots. they are moved from a folder that gets deleted. ⦁ Resolved an issue with modified files not getting updated when. This is now fixed.Īlso, while at it, there's now a new shortcut command for this sort of emergency mode rollback -īvckup2.exe -force -console %LocalAppData%\Bvckup2 The issue was that the handler of this command would sometimes cancel the switch mid-run because it thought the UI was requesting it. So the only way to undo the mode switch is through the command line using "bvckup2 -switch-to-app. In this case the program ends up in a state where it has a service configured and all backup jobs stored in %ProgramData%\Bvckup2 folder, but it can't be switched back to the desktop mode, because the UI cannot start, because the service cannot start. This has to do with the case when the program is switched to run as a system service, but the service cannot start due to an organization-wide security restriction that the local admin has no control over. ⦁ Fixed an issue with program mode switching via command line.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |