![]() ![]() It creates a mirror from one location to another, it doesn’t do anything clever like a two-way sync or a system backup and it doesn’t encrypt or compress data along the way. One of the other reasons it’s so fast is its single-minded approach. This means you can leave it running in the background while still using your PC for other tasks. It uses multiple read/write requests in parallel to speed up the transfer process and is able to run intensive tasks on multiple CPU cores, but scale back its activity when the PC is under load. After the initial backup of course it’s quicker still as it will only save changes. It’s designed to be fast and starting from scratch in our tests it saved 1.3GB of files to an external USB 2.0 drive in just two minutes. If you want to you can stop there and simply run the backup job - it’s as easy as that - but there are other options if you need them. Click this and you can choose a source and destination for your save. The ease of use continues on the first run when the only option you get is Add new backup. On installation it automatically detects whether you have a 32 or 64-bit system and proceeds accordingly. Produced by Swiss company Pipemetrics, Bvckup 2 is small - the installer is less than 2MB in size - but packs in a surprising amount of sophistication. I am planning to make this change within the next two major releases, so hopefully this will help improving usability around "archive_modified" option.Bvckup 2 aims to change all of this with a backup solution that’s clean, simple to use, elegant and fast. Restoring from this becomes as trivial as copying stuff back, just like it is for the primary backup copies. So what I think needs to be done is to just create date/time tagged top-level folder in $Archive for every run that archives something and then store the files/folders there, as is. That's what the archiving was originally for, and this is why it uses this funky scheme of appending timestamps to the names. ![]() In particular, the main scenario was simpler users directing their backups at already populated folder, clicking through all the warnings and then wondering where the heck all their stuff went. It was originally done this way because archiving was meant to be a pure safety net feature to help people recovering from accidental deletes at source. That, I think, has a simpler solution, which is to change the $Archive to NOT add timestamps to the archived file names. The only case where restoring support is justified is when restoring from the _archive_. I still think that restore functionality doesn't belong to the program, because it will still front rather trivial functionality and I am against adding features of this kind, especially if they will have a prominent UI presence, which will imply that they *are* more complicated that they actually are. Jul 22, - I merged all your posts into one and moved it here from "Feature requests" thread. What's a good backup tool without a convenient way to restore the backups it produces? :) but then again, maybe a separate backup restore tool, like in the screenshots above, would prove very useful, otherwise, and that's even more true when using file versioning) restoring a previous state is a total pain. ![]() I've read your position about Bvckup being a backup-only tool and not wanting to make it too complex by adding other features. Sry, if the above image link is not working, try In the future, could a similar version be implemented? Thanks! When I browse a back-upped dir, I can see the files, the several version of the files available, and I can restore a dir at a specified point in time. Bvckup2 works wonders, but I feel there's no convienent way of restoring from Bvckup2 backups. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |