Previously, it was removing this account only if it was still used by the bvckup2 service. ⦁ Switching back to desktop mode now unconditionally removes "Bvckup 2 Service" user account if it exists. Now it uses Get/SetSecurityInfo from Win32 API and it queries and sets all required bits in one go. Previously this was done with NtQuery/SetSecurityObject from Native API and it was setting each piece separately. ⦁ Reworked how security attributes (owner, group, DACL, SACL) are cloned. ⦁ Reworked the > section of backup settings. This is by design, but it's subject to change in later releases. NOTE that streams on *folders* are NOT replicated or processed in any way.
⦁ Added support for copying NTFS alternate data streams on files. Thanks for the compliments and the licenses, gentlemen. though the R75+ releases should show better resistance to this sort of thing.Īs of 76.1 it's possible to suppress at-startup messages about missed backup runs - (second item on the list). But if it was a blue screen or a power cycle, then it could be the reason. If it were a clean reboot after an orderly shutdown, this should not be happening. If you are on R75 or newer, the symptoms mean that the UI configuration file got either wiped or corrupted. This was over a year ago though, but just in case please check you are running a reasonably fresh version. There was a change in Release 75 to how configuration files are saved, making the whole thing a bit more robust. > After getting the settings to stick for quite a while, they come unstuck again after a reboot backups that should only run at night + network connectivity issues that got resolved during the day), it will cause a stampede if more than one backup uses a removable drive that gets plugged in, etc. Making it a default is not the best option. Somehow I stopped getting notifications for new posts in this thread.
0 kommentar(er)
