When all 19 other servers accept their part of the file and commit it to disk safely they signal the original server "we're good, this file is safe", and ONLY AT THAT POINT does that server respond to your computer with "Ok, the file is safely stored at Backblaze".
So we need to get through it, and only then can you know your upload performance for real.ĭisclaimer: I work at Backblaze and wrote a lot of the client running on your computer pushing files at Backblaze's datacenter.Ī note about threads and performance: Any one Backblaze thread can only reach about 10 - 15 Mbits/sec in performance for a reason totally unrelated to your network speed, or Backblaze's network speed - Backblaze's servers accept the file your computer sends, split it into 17 equal parts called "shards", calculates 3 additional parity shards using a math formula called Reed-Solomon, and the server you uploaded it to writes 1 of those parts to it's local disk, and transmits the remaining 19 parts to other servers in other locations in the Backblaze datacenter. So getting through the 50,000 small files at the start of a backup is really important. And as soon as Backblaze finally gets through a small file AND has an hour or two after that (very important) then you are finally “free” and won’t ever have to face that file blocking your progress again. Backblaze NEEDS to power through the small files, it needs to get through the ALL of the small files, and clicking pause loses AT LEAST 10 minutes of progress every time it is clicked. Why 8 hour backup sessions? Because customers “play” with things too much, Backblaze cannot be improved by clicking “Pause” all the time. But 3 or 4 days after you start those small files will all be transmitted, and then you can see the true performance. And the overhead of opening an HTTPS connection for 1 and 2 byte files SLAUGHTERS performance. Why do you always need to wait 3 or 4 days to worry about upload speeds? Because Backblaze backs up in small file size order, small files first. The difference will tell you the progress. Now you are finally able to click the “How Long Will My Backup Take?” link! Alternatively, look at the control panel for “Files Remaing” and write down the numbers 1 hour into an 8 hour backup session, and write down the numbers 7 hours into a backup session. Any estimate before 2 - 3 days has passed will be wrong (see below for explanation). Notice this is probably at least 3 days after you installed. NOTE: it is fine to pause Backblaze anytime you like, but this is different, you are trying to figure out how long your initial backup will take.ĥ) After Backblaze has had at least 3 of these 8+ hour sessions, you are ready to estimate how long the backup will take. The reason you turned off your screen saver in step #2 is so WITHOUT touching the mouse or keyboard you can read the numbers off the Backblaze Control Panel. If you touch the mouse or keyboard during this time you have to start over.
BACKBLAZE BACKUP WILL TAKE 912 DAYS HOW TO
Ok, so the web page is just a brainless calculator, if you change the URL argument of “mb” then the web calculator will change like this:ĭoes all that make sense? Ok, so in the end, it sounds like you are wondering how long your backup will take? If that is the case, here is how to figure that out:ġ) Pause your backup by clicking once, and waiting at least 10 seconds for everything to “settle” and stop.Ģ) Turn off all power savings modes on your computer so the computer does not go to sleep, the monitor and screen saver should not even trigger.Ĥ) Let it run this way for at least spans of 8 hours without touching the mouse or keyboard. The URL for you is not included in your screenshot. You can see those things (and change them) in the URL. The second link/screenshot is not really just the speed of your hard drive though - it is closer to a “real” calculation that takes several things into account. They aren’t even remotely related to each other. Put differently, one of the screenshots/links measures the speed of your network card in your computer, the OTHER measures the speed of your hard drive - you should NOT assume they are the same number. For example, if the files on your hard drive can only be read off the hard drive at 10 Mbits/sec, then a network of 50 Mbits/sec won’t magically allow your hard drive to read files at 50 Mbits/sec, correct? That is NOT how fast the backup will go because bandwidth is not the slowest link in your situation. One of those two links measures the bandwidth between your computer and the Backblaze datacenter.
0 kommentar(er)
