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. In order to enable this behavior exit Bvckup, add the following line to %LocalAppData%\Bvckup2\ui\bvckup2-ui.ini, save it and then start Bvckup again.⦁ Fixed an issue with program mode switching via command line. However, with this change it is now possible to have file-level errors to be treated as critical so that they too would trigger a systray blink and notification. those that either prevent backup from starting or those that abort it. By default, only backup-level errors are considered critical - i.e. ini only option and it has to do with what kinds of errors are treated by Bvckup as "critical". Backups with non-critical errors can now too be flagged Missed backups are now again flagged on launchĥ. Systray "minimize" now always minimizes to systrayĤ. If you don't know what this is, you probably don't need it :)ģ. ServiceConfigPath registry tweak is again supported If an app doesn't indicate that it is aware of this awesomeness, W8.1 will blur the hell out of it on a High DPI monitor.Ģ. Added support for Window 8.1 per-monitor DPI modeĪpparently Windows 8.1 implemented something called per-monitor DPI, meaning that if you have an average monitor and a High DPI one, then W8.1 will run them at different DPI. So the workaround is that Bvckup will now re-query device fingerprint in 5 seconds after a new device is indicated by Windows.ġ. This likely means that there's a delay after device is reported as available by Windows and it is being accessible in way needed for computing the fingerprint. I cannot reproduce this issue locally, but based on "field" reports the issue can typically be solved by restarting Bvckup. Added provisional workaround for device fingerprints not being always available. Fixed an issue with shadow copying "as needed" optionħ. Fixed timestamp issue with Synology DiskStationĦ. Fixed "remind to check for updates" option All sorts of interesting events followed, including a crash (fixed separately).Ĥ. When Bvckup was switched back from service to the app mode, it would under certain circumstances re-copy its /engine subfolder and that would place all its contents under the ownership of Administrator account and make it inaccessible to the app *if* it wasn't running with full admin rights. Fixed file ownership issues when switching app's mode Fixed support for NTFS de-duplication reparse pointsģ. Fixed support for case-sensitive file systemsĢ. * Third, there are changes to better handle disappearing/disconnecting network locations when they are used as a source for real-time backups.ġ. It makes no sense, but it works and Bvckup now does this for you, behind the scenes. Grab just a username under which the share is accessible under regular user account and then issue "net use \\server\share /user:" from Bvckup running as full admin. Next, restart Bvckup with full admin rights. Then, say, you have accessed the share, entered the password and it is now available in Windows Explorer. Say, you set backup to use \\server\share\foo and this share requires username/password on the first access. * Second is a fix for the following scenario. * First is that network paths behind mapped network drives are now monitored if/when the drive becomes unavailable. Improved support for network drives and locations
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |