3 Types of Archives: What's Right For You?

December 03, 2015 Geoff Bourgeois Cloud, Archiving, Cloud Archiving, Cold Storage, Gartner, Industry Analysis, Storage Strategies 0 Comments

There are generally 3 types of archives in enterprise IT:

  • Governance archives (aka. legal hold or compliance archive).
  • Cold storage archives.
  • Active archives.

Here's a breakdown of the three types of archives.

Governance archives (aka. Enterprise Information Archiving)

Rigid. Costly. Cumbersome.  That's a harsh but accurate way to sum up this category.

Governance archiving is usually driven by regulatory compliance and/or a desire to be prepared for eDiscovery, with stringent requirements and SLAs.  As a result, pricing is at a premium, and vendor contracts tend to be complex.  Often times pricing/licensing models are quite complex.  And the user experience is often an afterthought.

The primary content targeted with governance archives is messaging (email and instant messaging), although vendors do claim support for various content types ranging from websites to social media to files.

Gartner started to track this market in 2002 / 2003, and in their 2015 EIA Magic Quadrant claim the market size was $1.92 billion in 2014.  With a 9.1% CAGR through 2019 - and a long history of vendor acquisitions - it can be said this market has already seen it's glory day in the hot sun.  Today, migrations are commonplace and the big trend - like anything else - is to go SaaS.

Cold storage archives (aka. nearline storage)

In a previous post I opined about 'cold storage' being used synonymously with 'archiving'.  Cold storage offerings like Amazon Glacier and Google Nearline are the epitome of this category.

Cold storage archives' main focus is on parking low-to-no-touch data as cheaply as possible.  That's really it, that's all.  But watch out for retrieval times.  As you can see here and here, fetching your data from cold storage archives can literally take days.

While low cost is enticing it can be hard for an enterprise to identify suitable data for this kind of archiving.  So obvious candidates like backups and data from retired apps tend to be what is parked here.  Because there isn't any integrated user access, data management, or features that would help you in the event of eDiscovery or an audit cold archives are often viewed as dangerous by experienced IT leaders, requiring investment in development or 3rd-party software.

Active archives (aka. we need storage tiering without disrupting users)

Emerging in recent years is the concept of 'active archiving'.  To be quite honest, I don't like the name, but that's what many are calling it.  These solutions are more user centric and - because they aim to help manage data growth and reduce storage costs - they are much more affordable than governance archives.

The active archiving concept is great and there's room for innovation, which I like.  However, it isn't immune to things like compliance and litigation, so it will be interesting to see to what extent active archives address feature needs in these areas.  If active archives do bleed into the governance arena it'll be interesting to see how vendors handle this and what kind of disruption it causes.

I tend to view active archiving as having the potential to be the best of both worlds.  By the way, this is the category of archiving I see HubStor providing.

What's right for you?

Governance, cold, or active?  Or somewhere in between?  You might argue these categories are not mutually exclusive.  A vendor's solution may span categories.  But usually an archive solution is really just suited for a particular category.

I think in each category we're seeing SaaS as a major theme.

Some might say backup is another category of archiving.  Despite being sponsored content, I like what the folks at Storage Switzerland say about backup vs archive.

Interested to hear your thoughts and opinions.

 

About the Author

Get Notified

Recent Posts

RSS

Add to your favorite RSS reader using: blog.hubstor.net/rss.xml or http://blog.hubstor.net/rss.xml