This had to do with 78.6 and 78.7 trying to reduce the number of kernel requests it makes when copying file/folder meta info (timestamps, attributes, etc.) They would first try to use certain API that is usually available except for some cases (such as Samba based shares). ⦁ Resolved an issue with recording file timestamps in snapshot. ⦁ Fixed an exclusion rule for OneDrive internal file to actually _exclude_ the file rather than _include_ it, as per ⦁ Fixed an issue with reading plaintext passwords from the INI files, as per ⦁ Added support for 0xA000001D reparse point type, it is now ignored by default, as per At this point trying to switch the app back to the service mode would fail (as a precaution) as the "Bvckup 2 Service" account would already be there. This led to an issue when the service was switched to run under another account and the app was switched to the desktop mode. 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. ⦁ Fixed a small issue with error handling in the delta copier - one of the internal self-consistency checks was too strict and erroneously fired when a file needed updating at an offset of 0 and the write request failed immediately. Note that passwords are always stored obfuscated, so the plaintext will be replaced with an obfuscated version the next time bvckup2 saves the INI file. This is done by starting the right-hand part with ! sign, e.g. For a password settings (such as the one for a share or an SMTP server login) it's now possible to specify the password in the INI file in plaintext. ini support for specifying share passwords in plaintext - this is as per. 849C9593-D756-4E56-8D6E-42412F2A707B with System and Hidden attributes is now excluded from the backups by default. ⦁ Added new default exclusion for a file internal to OneDrive - a zero-sized file called. This change tells Bvckup 2 to process this folder as a regular directory. ⦁ Added support for OneDrive reparse points - recent updates to W10 rolled out a newer version of OneDrive that now uses reparse points to inject its principle folder into the file system. ⦁ Support for grouping jobs into scheduling queues ⦁ Periodic scheduling fallback for faulty real-time jobs ⦁ New mode for email alerts - "on changes and errors" ⦁ Speeded up the scanning of remote shares Important changes from later 77.xx releases ini files now start with an UTF-8 byte-order-mark ⦁ Auto-updates will now wait until the backup engine is idle ⦁ Periodic backups can now be scheduled for Feb 29th ⦁ Fixed an issue with preserving delta state when copying errors out ⦁ Fixed an issue with the "scroll to last error" UI feature ⦁ Fixed an issue with handling out-of-space condition ⦁ Added support for verbose reporting of configuration issues ⦁ Added support for "quiet times" in the scheduler It will only send over the changes from the destination to the sources snapshot.⦁ Completely reworked file/folder exclusion/inclusion module This tool stores the destination cache on the source as a snapshot, so it doesn’t have to scan the entire destination over and over again. No file is copied at all, unless you have changed it and then it performs a sync afterwards on block-level.Īnd there is so much more to write about, but these are the things that popped as the most import ones for me. When you move a file between folders at the source, bvckup 2 recognizes it and simply performs a move on the destination. Well, after checking it……it really is beyond robocopy.īvckup 2 addresses delta copying for larger files, that means only the modified blocks are synced and not the entire file. This week i noticed a product “ bvckup 2” which is introduced as “ Data mirroring & replication, Beyond robocopy“. But if you know ROBOCOPY, it cannot sync open files and it copies the entire file over and over again when it has changed. It’s an old one, but still working (almost) perfectly. In Windows we normally use ROBOCOPY in order to copy data between locations. By angioni Janu#bvckup, #copying, #robocopy, #sync, #toolĪs a Linux specialist, rsync is a tool we use a lot during migrations or in application clusters like Pacemaker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |