Skip to main content

Veeam v12, does Wasabi support SOSAPI as I’m trying to create an archive tier. It looks like SOSAPI has to be used with archive. Is this correct?

Wasabi does not support SOSAPI from what I have seen and tested with.  I do a lot of testing with it too.

Maybe ​@drews can shed some light for you or someone from Wasabi lurking here on the community.


thanks.

Its interesting that the Veeam documentation says this….

clearly doesnt work.

Also need to an archive tier for Artesca so hopefully it works with that.

Can we switch off SOSAPI ?


thanks.

Its interesting that the Veeam documentation says this….

clearly doesnt work.

Also need to an archive tier for Artesca so hopefully it works with that.

Can we switch off SOSAPI ?

Yeah not sure why the document says that and SOSAPI is not integrated to be honest. Better to let the experts answer that one.

SOSAPI is integrated so you cannot switch it off once you add storage that supports it unfortunately.


There aren’t a ton on services that use the SOSAPI yet.  Some of the services listed as Veeam Ready for SOSAPI are local appliances or Software Defined such as Object First, Cloudian, Scality, and the like.  I’m actually not sure if any of these are cloud-based services.

https://www.veeam.com/partners/alliance-partner-technical-programs.html?type%5B%5D=sosapi

 

As for archive tier, I believe that Wasabi’s take is that it is unnecessary considering the low cost of their storage when used as a capacity tier. 

https://wasabi.com/solutions/active-archiving

https://wasabi.com/glossary/tiered-storage-system

 

I know that for Archive tiers, S3 Glacier and Azure Archive storage are compatible, but Veeam also lists “S3 Compatible” archive storage.  There’s a couple other providers, but that list is very short.

https://www.veeam.com/partners/alliance-partner-technical-programs.html?type%5B%5D=archive-tier

 

 

So that all leads to, why do you think you need an archive tier?  I ran the numbers once and Glacier was slightly cheaper as an archive tier than just keeping it in Wasabi as a capacity tier, but it was an inconsequential number unless you’re talking about massive amounts of data and didn’t seem to be worth the hassle.


Also need to an archive tier for Artesca so hopefully it works with that.

I had to google Artesca, and it looks like this is part of Scality.  Scality is listed as archive tier compatible so I’d give that a solid maybe.  For sure it’ll be archive-compatible before Wasabi is.


Also need to an archive tier for Artesca so hopefully it works with that.

I had to google Artesca, and it looks like this is part of Scality.  Scality is listed as archive tier compatible so I’d give that a solid maybe.  For sure it’ll be archive-compatible before Wasabi is.

yes Artesca is the baby scality as the RING is the multiple site setup. As its all Scality then I’d expect that to be supported but I’ll check…. Scality has a very close relationship with Veeam.


There aren’t a ton on services that use the SOSAPI yet.  Some of the services listed as Veeam Ready for SOSAPI are local appliances or Software Defined such as Object First, Cloudian, Scality, and the like.  I’m actually not sure if any of these are cloud-based services.

https://www.veeam.com/partners/alliance-partner-technical-programs.html?type%5B%5D=sosapi

 

As for archive tier, I believe that Wasabi’s take is that it is unnecessary considering the low cost of their storage when used as a capacity tier. 

https://wasabi.com/solutions/active-archiving

https://wasabi.com/glossary/tiered-storage-system

 

I know that for Archive tiers, S3 Glacier and Azure Archive storage are compatible, but Veeam also lists “S3 Compatible” archive storage.  There’s a couple other providers, but that list is very short.

https://www.veeam.com/partners/alliance-partner-technical-programs.html?type%5B%5D=archive-tier

 

 

So that all leads to, why do you think you need an archive tier?  I ran the numbers once and Glacier was slightly cheaper as an archive tier than just keeping it in Wasabi as a capacity tier, but it was an inconsequential number unless you’re talking about massive amounts of data and didn’t seem to be worth the hassle.

 

thanks very much, yes I did speak to Wasabi and they explained the same reasoning. 


Comment