This might not seem like too much of a risk at home on your PC, but if you are handling sensitive files at the workplace, you are probably not that eager to venture too far without some form of backup for your documents.
Simple and efficient backup creation
• 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.
• As for the actual available features, once you go deeper into the settings panel, you can find options like shadow copying, device tracking and concurrent backups, which allow you to fully customize the way your files and documents are being kept safe.
Scheduled backups and realtime actualization
• A good rule of thumb for creating backups is to make them as often as possible. Of course, that is not always possible. Bvckup includes a backup scheduler that automatically generates backups for your documents at user-defined time intervals and allows you to focus on other tasks.
• Realtime backup protection comes into play when you want the backup files to be updated at the same rate with the original ones. Bvckup can monitor the initial documents and apply the changes to the backup versions as soon as they happen.
• File corruption, viruses and accidental deletion happen all the time, regardless of the experience the person handling the computer has. Backups are vital for any machine that holds sensitive information and has to deal with many updates and operations that could damage it.
• Bvckup provides a good solution for such purposes and is extremely easy to use for anyone. The multi-core processing capabilities allow it to run smoothly on a wide variety of computers and perform well even on weaker systems.
• Continuously monitor for changes and back them up as soon as they happen.
• Scheduled and manual
• Run backups at fixed time intervals or only when started manually.
• Asynchronous I/O
• Eliminate idling during data transfers by having multiple read and write requests running in parallel.
• Reduce the amount of data being moved around by copying modified parts of files only. This speeds things up, in many cases dramatically.
• Speed things up by running computationally intensive tasks such as data hashing on all CPU cores, but scale back when computer is under load.
Run-time memory use is now capped:
* The amount of memory the app now uses to run a backup does NOT depend on the size of said backup. Needless to say that this is extremely important change that means that Bvckup 2 is now formally capable of handling backups of arbitrary size – anything from a handful of files to millions of files. Behind the scenes the app uses a form of a swap file to keep things off RAM when it’s not actively using them.
The Fine Print:
* This change is linked to a major rework of several parts of the app that spanned nearly 3 months. In practical terms this means that there’s an increased risk of edge cases, bugs and wrinkles slipping through the testing and ending up in the release. The risk is low, but still please keep an eye on anything odd and report to the support if spotted
Delta copying improvements:
* Previously, delta copying was used for files of 2MB and larger.
* With this release the threshold is raised to 32MB, but the delta copying is also used for files between 2 and 32MB that were modified less than 30 days ago. The idea, basically, is that delta copying now used for files that are either large or that change frequently.
* The net effect of this change that the backups complete faster *and* that there’s less state date stored in the backup configuration.
“Export configuration” option:
* Just what it says on the label – an option to save app’s entire configuration in a single .zip file, accessible from Menu / Help.
* Restoring the configuration is a simple matter of extracting the contents of the zip file into %LocalAppData%Bvckup2 folder, but just in case the exact instructions are included in the .zip file itself.
* Source or destination location disappearing during the scan now correctly aborts the backup
* It’s now possible to suppress “Backup run was missed because the app wasn’t running” notifications. This is done by setting “conf.report_missed_runs” to 0 in the backup’s settings.ini. See FAQ for how to make this change properly.
* Tentative workaround for log index files getting locked by the antivirus when the log is rotated.
* It’s now possible to force the app ignore specific drive letters (just as if they have no devices behind them). This is controlled by “drives_to_ignore” variable in bvckup2-engine.ini file, which is a bit mask of drives (bit 0 – drive A, bit 1 – drive B, etc.).
* WindowsSystem32MicrosoftProtectRecovery is now excluded by default
* UI-to-service connection timeout is now configurable and the default was raised from 5 to 7 seconds. Because reasons.
OS: Windows XP / XP 64 bit / Vista / 7 / 7 64 bit / 8 / 8 64 bit / 2003 / 2008