In this presentation we present EAGLE's ideas on designing a modern tiered storage infrastructure. We will cover the basic strategies and requirements of tiers 1/2/3, object-based, cloud, and edge storage, along with the importance of categorizing data sets so that you can ultimately build a solid blueprint and business case. Other topics include transitioning to an effective tiered storage model, controlling storage growth, and emerging ideas and technologies for data storage.
Even if organizations don’t know how to analyze the data yet, they are collecting it because stored data is like money in the bank.
Tell your story about growth issues; ask if other folks are having this issue.
“Buckets of Storage” is a common analogy that EAGLE uses to describe storage and backup needs. The takeaway is that growing storage and complexity requires the use of multiple storage tiers which meet the business needs of the enterprise (in terms of data availability, cost, connectivity, etc).
Applications live here; high performance and reliability/availability is a requirement. This stuff is expensive!
In relation to the storage pyramid, most data (that is immediately accessible) lives here.
Disk is still king in this space (due to availability and capacity needs).
Maintenance windows are “allowed” (typically).
5 years ago, we all thought tape has died, but it has really just transferred to tier 3 spaces (where we see the most growth)
Historically fulfilled by tape; cloud and archive-grade disk is increasingly considered a good fit in this space.
Concerns about cloud storage include privacy, security, encryption, authentication, and availability. What good is a backup if it takes a week to restore (“resume generating event”).
If you take advantage of SaaS in the cloud, cloud storage may work very well for you. You can even replicate to another zone and bring up your application in that zone if necessary.
“You already have a cloud.” – Mention your story about “private cloud”.
Recap: “cloud may be a good fit and should be examined on a case by case basis”
As opposed to fixed block sizes, object-based storage works at a higher level. The data is categorized into objects that are stored efficiently and contain metadata. This metadata makes object-based storage an excellent fit for policy-based storage.
It's important to keep in mind that each vendor’s technology is proprietary. These shortcomings make object-based storage less useful for primary storage.
Five years ago many large organizations thought they had a handle on desktops and laptops (through the use of policies that kept files on centralized file servers), but the increased use of BYOD has brought this issue back into the forefront.
Edge data is often not viewed properly in the mobile workforce era (legal and security risks abound).
Ask about any questions concerning the tiers we have discussed.
Administrators and decision-makers need to consider multiple factors in order to understand where data should live. The goal is to make intelligent decisions about where your data should live. You are on the path to building a roadmap to a tiered storage model.
You are trying to analyze your data and figure out how many “buckets” or tiers make sense for your organization.
You must have your business continuity metrics laid out. If not, they stand to muck up your storage tiers.
Setting the objectives should come from looking at the business impact of applications being unavailable, and the business impact of loss of data.
Example: data with high low RTO and low performance characteristics may still need to be on high-end storage.
Typically folks size for tier 1 apps (in terms of performance) and the overall capacity of your storage. This was an easy decision 5 years ago because you could fit everything on one tier (datasets were so small).
While you are building your blueprint you need to consider that availability and performance requirements cost money.
Many folks don’t see archive data in the proper light. Archive data may lose the requirements for performance and version & change tracking, but it still has value.
Oil industry analogy.
Now that you have an understanding of what storage options are on the table, and what your own data looks like, you can start to layout a blueprint of where you want to be.
This process will create a blueprint that is different for everyone.
Ask for questions.
Non-IT folks need to be taught about responsibility concerning storage use. Not part of their daily responsibilities to be conscious of IT factors. Use this reality to sell quotas to management.
Example: “running water at the hotel”.
Ask if other folks have struggled with slowing storage growth.
Active Archive – cheapest place possible while maintaining business SLA’s
Let me know if you want a copy of the presentation!
Reiterate: The way we see it, our job is to take the complex and make it simple… that means adding real value by leveraging our expertise and integration capabilities to help you find a solution that makes sense for your business. And now, with our new solutions, if that means customer-managed \ on-prem, Eagle-managed \ Eagle-prem, or somewhere between, we have you covered.