![]() ![]() If the run was cancelled in a very specific moment when it was just entering the planning phase, the program would panic because not all of planner's temporary data was disposed of properly. ⦁ Patched an issue with cancelling a run while in planning phase. This was caused by the fact that their firmware is stuck in the last century and doesn't support more efficient file enumeration methods. When backing up to- or from- certain WD Passport models and "network drives" of some other vendors, the backup would fail with 0xC00000BB error. ⦁ Patched an issue with scanning certain "network drives". Completely eliminated the underlying bottleneck and also reduced run-time memory usage while at it. ![]() This is a proper fix for the issue of move detection very slow when the number of created and deleted files for a specific run is in hundreds of thousands. ⦁ Revised file move detection for speed and lower memory usage. ⦁ Added (a bit of) fast keyboard navigation to the log viewer.Ĭlicking on a log entry and then pressing Left Arrow key will climb up the log to the first sibling entry that is expanded OR to the parent entry otherwise.Ĭlicking on a log entry and then pressing Right Arrow key will scan down for the nearest sibling entry that is open OR to the end of the sibling list. ⦁ Added keyboard shortcuts for the main window:Ĭtrl-X dismisses a message at the bottom of the window ⦁ "Pause for a bit" option is now available in the system tray menu ⦁ Release notes for found updates are presented in a new way: ⦁ When in planning phase, the UI will now show a progress bar. This change streamlines recovering files from the archive and it paved the way for promoting "archive modified" feature to full UI presence. For example, previously archiving abc.txt would result inĪnd under the new archive structure it will be This release introduces new $Archive structure which does away file name mangling and instead distributes files into a set of time-stamped folders. This made a task of recovering files from the archive tedious, because every recovered file had to have the timestamps trimmed from its name. In particular, archiving a file involved moving it to the $Archive folder and then appending a timestamp of the archival *to its name*. This option was introduced 8 (eight) years ago, but it remained on the outskirts of the feature set because of how file archiving worked in general. This release finally adds UI support for an option of archiving backup copies of modified files - the analog of "file history" or "file versioning": Storage device queries to after the startup is completed. ⦁ The program starts up a bit faster now. ![]() ⦁ Delta copying now uses Blake3 as its principal block hash algorithmīy default, allowing for gigabyte speeds on most modern machines. "post" phase (folder timestamp sync) as well as the archive trimming. Only the copying (main) phase was executed this way, but this releaseĮxtends it to the "prep" phase (folder operations, file moves, etc.), the Program is capable of executing several actions at once. ⦁ All parts of backup run are now fully parallelized, meaning that the New scanner also implements several other notable enhancements,ĭescribed in "Assorted improvements" below. Storage, replacing original "snapshots" and eliminating the use ofĮphemeral swap files that had to be converted to the permanent Time-consuming "File ID retrieval" phase. Of retrieving more in one go, eliminating the need for a separate and New version switches to using highly efficient Native API. Retrieving directory listings and various file and folder details, andīuilding the list of files and folders the be backed up. ⦁ Brand new scanning module - a part of the program responsible for Using our example above, this will be at /home/jetbackup/backups/.jetbackup.Assorted changes aimed at further increasing the speed of backups: jetbackup file that exists in the backup directory. If you wish to use the original backup directory set on server 1 as a regular destination on server 2 then you must remove the. The Read-Only option will allow you to add the destination on server 2 with the same backup directory set in server 1, however, you will only be able to Restore and Download the existing backups from a read-only destination. Then in order to create an SSH Destination with the same credentials on Server 2, you must configure a unique path like /home/jetbackup/backups2. For Example: If you have an SSH Destination on Server 1 with backup directory set as /home/jetbackup/backups. (Destination: "NAME" #) In order to increase the security of your backups, JetBackup has allowed only one Destination per Backup Directory. On JetBackup 5, you may notice the following error when creating a destination that uses the same Backup Directory as another JetBackup Destination: Error: This destination path is already owned by other destination in this server. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |