Blog categories

My blog posts and tweets are my own, and do not necessarily represent the views of my current employer, my previous employers or any other party.

Many of these blogs were originally posted elsewhere on public sites, but have been re-posted here with attributions to the original location -- strictly as a means of a centralized archive of my perspectives.

I do not do paid endorsements, so if I am appear to be a fan of something, it is based on my personal experience with it. If I am not talking about your stuff, it is either because I haven't worked with it enough or because my mom taught me "if you can't say something nice ... "

New ESG Research on BaaS, DRaaS and Tertiary

These days, you can’t have a discussion on modernizing your IT infrastructure without talking about “cloud” … but when it comes to Data Protection, there isn’t just one kind of Data Protection as a Service (DPaaS).

In fact, most folks are considering up to three different DPaaS capability sets, including:

  -  BaaS – Backup as a Service, where files are backed up to the cloud (with/without an intermediary on-premise caching solution)

  -  DRaaS – Disaster Recovery as a Service, where whole machines (typically VMs) are replicated and restart-able from the cloud.  Some DRaaS include rudimentary BaaS as a side-benefit

  -  ‘Tertiary STaaS’ – Adding cloud-storage to one’s existing on-premise backup solution. These implementations can vary greatly from a third-usable copy via the cloud service to simply ‘block-storage’ that has to be remounted by the original backup application.

BaaS, DRaaS, Tertiary

Should a cloud-capability be part of your data protection strategy?  Probably (but not certainly)

Which solution do you need?  That depends on your recovery goals.

So, what kinds of folks are buying which DPaaS capabilities (and why)? 

That is what ESG’s latest research report covers – CLICK HERE to check it out.

Thanks for reading – and Happy Monday, y’all.

[Originally posted on ESG’s Technical Optimist.com]

Leave a Reply

@JBuff on Twitter