Might it be worth adding this option to the settings for each backup job (with the default set to single-copy mode)? Oct 10, 2016Interesting numbers, thanks, Mark.
#IS BVCKUP 2 WORTH IT PRO#
You said “This feature is going to be available under a Pro license only. It is obviously hardware sensitive, as well as fundamentally dependent on the particular backup one is considering (my daily work folders are quite different to my photo & video folders). I can check v76.7.3 on my network at work, on Monday, for interest. I have a NAS here, but it’s not in daily use yet and won’t add any value, I think to what you already know about network performance. However, I am aware that network backups of large data sets is a different matter entirely. What’s more, my backups are generally incremental anyway, ie daily updating a small number of changes, and Bvckup 2 is blindingly fast as it is! My conclusion is that for my system and my type of backups, parallel copying is not good :( OK, so moved on to a different scenario, and just used hard drives:īackup size: 2.83 GB / 2551 files / 500 folders
Source on a local SATA hard drive, destination (empty) on a flash memory stick Source on a local SATA hard drive, destination (empty) on a local IDE hard drive. Continuing with the large data set mentioned above:īackup size: 15.00 GB / 29706 files / 3628 folders Thanks!Īt home, running on an older system, I’ve run some tests. I'm very curious to see other people's numbers. If you give it a try, please share the results below. That is, don't expect any miracles with external USB 2.0 drives or SD cards. 1 Gbps wire link.įor local copies it should also have noticeable effect, but again, the faster the drives the more pronounced the effect should be. The effects of parallel copying are most pronounced when copying to or from a network shared, and especially when going over a fast connection, e.g.
! Make sure to exit the app before making any INI changes or your changes will be ignored and overwritten by the app. The default is 0, which is the 16-4-1 auto behavior described above. It is possible to override the thread count by changing the following option in job's settings.ini: It will log the exact thread count in Processing section of the log:Ģ016.10.07 15:09:54.872 (UTC+1) 2 0 Running the backup. * 1 copy at a time if backing up in confines of one drive * 4 copies if copying between two local drives and * 16 file copies in parallel if copying to or from a network share We now have a reasonably stable build that supports parallel copying and you are welcome to play with if you'd like: * This is similar to the robocopy /mt option if you are familiar with the tool. For larger files the opening/closing time is dwarfed by the copying time, but for smaller files they are comparable, so if we can task the OS with opening/closing several files in parallel, then we speed things up. When a file is copied, there's a fixed time cost of opening and closing it and then there's a cost of actual copying that is proportional to the file size. As you might've heard Bvckup 2 is getting support for copying several files in parallel during a backup.
0 kommentar(er)
