Veeam and Backblaze Backups

[aicrd]

I'm currently testing out Veeam with Backblaze Immutable backups as currently our offsite backup only consists of mailing an tape to someone.

 

I keep getting this error when Veeam starts to offload the backups to backblaze "Content-Length header not found in response headers" as well as "S3 returned empty versionId for newly uploaded object"

 

Some googling reveals nothing that could help me out here. The errors also arent very specific.

[aicrd]

Oh. I've apparently hit my daily Class B transaction caps. Forgot to add a CC to my account.

[aicrd]

Even with those limits removed I'm still getting the same errors when Veeam is attempting to upload the backups to Backblaze. Does anyone have any ideas?

[kmount]

Hi,

 

I think this may be part of what is referred to in the latest Veeam forum digest as a change Backblaze has put in to support immutable backups.

 

May be worth checking the setup by support.

 

Big object storage news today! Backblaze changed the game last week by introducing S3 Object Lock support, becoming the first major public cloud vendor other than Amazon itself to provide support for immutable Veeam backups! Like many, I was expecting Wasabi to be the first and only major cloud vendor to deliver S3 Object Lock support this year – so to say that I am pleasantly surprised is an understatement... wow, these guys are really taking the market by the storm! The functionality is available immediately and has already been verified through Veeam Ready program, as Backblaze provided us an account with early access to this functionality.

 

The timing for this feature could not be any better too, because we started getting support cases from customers having issues registering Backblaze with Veeam recently. Upon closer investigation, the issue appeared to be specific to v10: it did not exist in previous versions, which allowed to register Backblaze buckets normally (and keep using them after upgrading to v10 too). The root cause is that v10 blocks the registration of S3 buckets with object versioning enabled and object lock disabled, as this is an unsupported configuration which can result in significant extra storage costs for customer. Luckily, now that Backblaze added support for object lock, you can create buckets with supported configuration (both object versioning and object lock enabled), which can be registered with v10 normally. So, as it stands right now, enabling object lock on Backblaze S3 buckets is actually mandatory to be able to register them with Veeam. We plan to address this in the next cumulative patch by replacing the blocking logic with a big warning explaining users they must enable object lifecycle management rules to clean up deleted objects automatically (or face extra costs of storing objects that have been removed by the retention policy