B2 vs s34/26/2023 I have also tried without compression without any variation in outcome.Įrror occurs immediately after snapshot (about 5 mins later, but its the next line in the debug log), but we don't fail out for another 18 minutes we get the bad allocation error every second until we finally die with a terminal 'bad allocation' error and completely fall over with an auto-restart of the script: T22:20:00. Perhaps most importantly, it enables us to sustainably offer cloud storage at a of the price of S3, which you will really appreciate as your application or service grows. But they have two data centers which can be an issue for some structures, where you need to be overly compliant. The short answer is that our architecture enables some useful differentiators for B2. Not saying that what they are doing is insecure or that there API is inferior in any way, just mentioning that there are improvement areas. Normal backup to B2, concurrency set to 1, compression set to zsd - no other settings (ie no 'delete before' or 'with memory' - just a standard backup with zstd compression). BackBlaze B2 is cheap, is fast and overall cool. Currently the S3 API is limited to sending and retrieving data, but they could possibly add IAM APIs that would allow you to create policies to be more secure with bucket access.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |