mostbad.blogg.se

B2 backblaze
B2 backblaze













b2 backblaze

It is a trial and error process to find the right number of threads for your use case. If you aren't, try to keep increasing the number of threads until you see performance dip. If you are maxing out your CPU, RAM, disk or network usage, decrease the number of threads. We recommend that you start with the default 10 threads and watch you system activity. There is not a set amount of threads that will work best in every scenario or for every user. A list of actions taken is always printed. Progress is displayed on the console unless '-noProgress' is specified. "b2://my-bucket-name/a/path/prefix/".įile uploads are done in parallel in multiple threads The source file location must be a local file path, and the B2 bucket destination must be a B2 bucket path. To initially upload a source directory to a B2 bucket destination: The basic parameter structure for the b2 sync call is as follows:ī2 sync \ If you haven't installed the B2 Command Line tool, you can do so here. The B2 sync command is used within the B2 Command Line tool. You can upload files from this directory and then either sync changes only, add new files, create file versions, or even hold onto versions for a specified number of days. The B2 sync command is meant to be used to keep a local directory synced with a B2 destination.















B2 backblaze