Retrospect Blog

Maximizing Backblaze B2 performance with Retrospect

Retrospect and b2 778

In last week’s post, we covered setting Retrospect to work with Backblaze’s B2 service. For network speeds up to about 100 Mbps, Retrospect can saturate your network with a single backup. If you are fortunate enough to have a super-fast connection, here are some steps you can take to maximize Retrospect’s performance with Backblaze.


Retrospect can perform up to sixteen backups (or any combination of script types) at a single time. If you have a Gigabit internet connection, chances are you are backing up many computers and so can take advantage of this Retrospect feature. The other upside to this is that you maximize your other network and CPU resources this way as well.


Many scripts can read from a backup set at the same time, but only one can write to it at the same time. So, you will need to create a set for each script. This can be one set per source, or you can use a set per department or area. This also gives you more granularity over your policies, allowing you to set different grooming and retention policies per set. You do not need to have different Backblaze accounts or even buckets to do this. Retrospect can create and use many different sets in a single bucket.

Setting up the scripts

After that, setting up the scripts is straightforward. If you already have a script with all the options you want, you can duplicate it and change out the sources and schedules.

Tip: we recommend leaving the Activity Thread option as the default (to use any thread). If you set all the scripts to use the same thread, they will queue up in line, defeating your intention.

More praise for Proactive

These scripts can be proactive ones. As I covered in my In praise of proactive post, proactive scripts can simplify a lot of the scheduling issues and ensure your policy stays in effect. You can create different proactive scripts and they will all play nicely together.

On the other hand

It is possible of course that you do not want to saturate your network every time you do a backup. Retrospect already has that covered. If even one backup at a time is too much for your users, you can limit Retrospect’s bandwidth in our global Cloud preferences. Set the upload or the download bandwidth limit to what works for you. (You may want to leave the download bandwidth unlimited as most folk want the restore to happen as soon as possible!). These limits apply to all our other supported cloud storage providers, not just Backblaze.

In conclusion

Whether you are looking to maximize your network connection or keep it in check, Retrospect has the tools to make it happen. Try us out today!


Bio jg

JG Heithcock

JG Heithcock is CEO of Retrospect, Inc. and has eighteen years experience in the storage and backup industry.