When to Think About Cloud

Posted on

Is cloud still thought of as “separate” from your other operations and projects?  Allwyn Sequeira  of The Data Center Journal advises that we must break free from that mind-set and instead think of public cloud as a system that works with your data center and supplements what you are running on-premise today. Essentially, cloud is a key piece of a hybrid operation that can help improve performance, agility and scalability. Mr. Sequeira provides several scenarios where cloud adoption should be considered.

Equipment upgrades and refreshes.  Do you have local equipment close to reaching capacity or a new project that requires your system to scale?  It may seem automatic to request a price for new hardware to meet the new demand, but actually, this is a great time to explore what cloud options are available and how they would work with your data center. Cloud can be provisioned faster than new physical hardware, and long term cloud will allow you to scale and adapt to future needs quicker.

Mergers and acquisitions.  When a company merges with another or acquires new businesses, this is a great time to think through cloud adoption. The cloud can be a cost-effective solution for integrating new systems and it can reduce transition time versus building or installing new hardware.

Pilot projects and testing.  Many companies adopt cloud solutions for development and testing of new projects.  The cloud removes the need to provision specific hardware to the project reducing time and cost.

Look at cloud as another tool in your IT toolbox.  It should be considered like any other tool when you are creating solutions to meet business and market needs.

The Road to Using Hybrid Cloud

Posted on

Integrating cloud into your organization is more of a journey than a one-time project. As your business needs evolve so can your cloud needs.  Is hybrid cloud adoption your next stop?   By adopting hybrid cloud companies can tap into the flexibility of public cloud services while also utilizing private cloud for more sensitive data and applications. Today let’s look at seven steps your organization can take to integrate hybrid cloud from John Meegan of IBM’s Thoughts on Cloud.

How to get started:

  • Determine the cloud deployment model
  • Integrate with existing enterprise systems
  • Address connectivity requirements
  • Develop governance policies and service agreements
  • Assess and resolve security and privacy challenges
  • Manage the cloud environment
  • Consider a backup, archive and data recovery plan

Mr. Meegan explains more on how to choose the right cloud deployment model, “The right deployment model aligns IT and business needs, and makes it easier to achieve those objectives.” He lists out the following decision criteria to guide your hybrid cloud adoption (or any cloud model):

  • flexibility
  • security
  • speed
  • automation
  • cost
  • locality
  • service levels
  • system interdependencies.

Your company’s unique operation and needs should drive what cloud model to choose.

On connectivity, he points out that IT should remember that aside from connecting components, you must also consider does the connection meet service levels, security and does it empower your overall IT management strategy.  Mr. Meegan also mentions your organization should consider using network virtualization if available and make sure connectivity also supports resilience and disaster recovery requirements.

Finally, think through how you will manage your hybrid cloud environment. What tools do you have in place? What tools does your cloud provider have? How can these be utilized in your operations? Working in multiple environments creates additional challenges but the right management strategies and tools can help your team manage your IT operations in and out of the cloud.

Hybrid Cloud
Source: thoughtsoncloud.com

Understand Your IT Before Moving to the Cloud

Posted on

Today let’s take a look at recommendations on how to ensure successful cloud adoption.

Reynaldo Mincov Jr. in a recent Thoughts on Cloud post tees up a cloud definition: “Cloud is about efficiency, economy, scalability, elasticity and doing things faster and better.”

The cloud allows companies to scale without the added capital expense of purchasing new hardware.  The cloud can bring efficiency by taking on routine admin processes, freeing up more time for innovation. The cloud can open up new opportunities by allowing any-sized organizations access to enterprise-class technology. But, before you can reap the benefits of cloud you must first know your own IT systems. Mr. Mincov adds, “for successful cloud adoption, you first need to deeply understand your IT environment by identifying those workloads that will best fit your target cloud environment while also giving you a consistent return on your investment.”

Mr. Mincov shares these pointers for gaining a deeper understanding of your IT systems and environment:

  • Business impact. Which systems are mission critical and which are less critical? Classify and rank. For cloud first try moving a small, back-end system to gain experience
  • Production versus development and test.  How are these environments the same, how are they different? Mr. Mincov recommends that your test environment should be configured to match production
  • Performance. Again examine your applications and determine what the impacts are to each if the app is slow or offline. Determine which are “performance-sensitive”
  • Complexity. Rank your IT for complexity. Something with several integration points should not be your first choice for cloud
  • Security. What compliance and regulations are important to your industry and must also be followed in the cloud
  • Preparation.  Measure how “cloud ready” you are. Be honest, what other tasks or transformations must take place in order to be ready to bring cloud into your organization. And, don’t forget to think about how to prepare your staff

Knowing your current IT systems in and out will help you make the right choices to better ensure successful cloud adoption.

The Reality of Cloud Adoption in 2016

Posted on

by James Keating III, Business Technology Architect, Evolving Solutions

Since I have been working with, in or around the cloud for a good portion of my career, first as a Data Center manager in placement decisions be it into the cloud or purposefully in colo sites, or in data centers I managed, to my work as a cloud architect, the one thing I am always asked about is use cases.  The question is usually either asked as a way to defend keeping all things in an owned data center, or by folks who have only heard of cloud in passing and can’t quite grasp what it really is.  My answer is usually around what the business goals are and what current problem areas exist.  This is because I don’t think cloud, just like all of the rest of IT, is a one size fits all.  Basically, it is a tool in the tool belt of IT, just like various SAN, NAS, Server and Software options are.  Not everyone fits running SAP, just like not everyone needs a Tier 1 storage array.  The goals of the company and skill sets are what make the use cases for or against cloud or anything in IT.

With all of that said/typed in the above paragraph, I would like to take some time to define the most common cloud use cases that I see being adopted by the various customers I am working with.  Most people I have asked seem to think development or “bursting” type use cases are what cloud is for, however I rarely see these as the use cases that really lead people into taking advantage of the cloud and saving money doing so.  The use case/s I usually see the most that benefit in terms of flexibility, definable scope and return on investment are Backup, Archive, Disaster Recovery and to a lesser but growing extent Data Analytics.   These may not seem like the ones that many people hear about when they see cloud marketing, or attend a cloud seminar, but they are indeed some of the most cost effective use cases for the power of the cloud.

I will use some costing numbers in the following examples, these are real numbers rounded up to show a high water mark so to speak.  I have also purposely chosen a smaller customer example rather than a large enterprise to start with to illustrate in smaller more understandable numbers why these use cases can be good financial decisions.  I am going to outline Disaster Recovery using cloud solutions for a small corporation that has the following items:

  • Total number of systems = 5
  • Data size = 2.5 TB
  • Backup software utilized = Veeam
  • RTO target = 48 hours
  • RPO target = 12 hours
  • MOL target = 100%
  • Replication manner = AWS storage Gateway

Just a quick level set on definitions:

  • RTO = Total outage window
  • RPO = Total data loss potential
  • MOL = Acceptable performance level of the DR location compared to production.

I know this example is very small when compared to large environments, but I have chosen it specifically because many small companies don’t have real disaster recovery abilities or real backups because they are deemed too expensive based upon the size of the overall IT budget.  In this example, the customer was able to utilize an AWS storage gateway and Veeam backup software to create a workable disaster recovery and backup plan using Amazon Web Services S3 storage and during a disaster EC2 compute.  This example does take human work to get the system up and running in a disaster but is much better than the original solution of backups written onsite to the same storage array as production with no ability to recover if the storage or facility was lost.

Actual cost figures for a disaster recovery test:

  • Actual RPO achieved = 8 hours
  • Actual RTO achieved = 36 hours
  • Actual MOL achieved = 100%
  • Monthly Spend for DR/backup data =  $200 to $300
  • Cost of DR test = $50
  • Cost of running 30 days at DR = $1500

So as you can see, for minimal investment, this customer was able to have a workable disaster recovery plan, because of the cloud and the ability to not have a full time disaster recovery site.

For those who are saying yes, but that is such a small environment, I will provide another cost example for a larger customer.  This one is more involved so I will not go into all the details, but just list out what was used and the real costs.

  • Total number of systems = 100
  • Data size = 96 TB
  • Backup software utilized = Veeam
  • RTO target = 4 hours
  • RPO target = 30 Minutes
  • MOL target = 100%
  • Replication manner = Zerto and Altavault

Results of DR test

  • Actual RPO Achieved = 12 Minutes
  • Actual RTO Achieved = 6 hours
  • Actual MOL Achieved = 100%
  • Monthly Spend for DR/backup data =  $2800
  • Cost of DR test = $1900
  • Cost of running 30 days at DR = $5500

In summary, it has been my experience that a good place to look at cloud in terms of financial benefit and increased resilience using the ability of the cloud is often DR, backup and archive.  If you would like to know more specifics, as with everything in IT, mileage will vary depending on the specifics of the actual data and software involved, feel free to  Evolving Solutions to discuss any of these use cases in greater detail.

______________________________

James Keating III is a Business Technology Architect for Evolving Solutions. James is a technology leader in the IT community and brings a combination of excellent technical skills and business acumen which allows him to guide customers in developing IT solutions to meet business requirements.

Update on Cloud Adoption

Posted on

Industry analyst and author Joe McKendrick breaks down a recent survey of 1,000 plus technology managers on their company’s cloud adoption and use.

First on Forbes, Mr. McKendrick reports that enterprises surveyed used on average six cloud services. Survey respondents were using or piloting at least six different clouds, mostly a combination of public and private projects. The survey also found a cloud workload split based on number of employees:

  • Businesses with more than 1,000 employees were more heavy on private workloads
  • Businesses with less than 1,000 employees were typically more heavy on public workloads

Mr. McKendrick comments on ZDNet, “Not too long ago, cloud computing lurked in the shadows, seen as a workaround to bottlenecky IT departments. Lately, however, that perception seems to have turned around almost entirely. Organizations are almost pleading with IT managers to help them navigate the new cloud world.”  With cloud adoption hitting a high the survey found that more businesses are moving to central IT management to plan for cloud use across the organization and  44% of the respondents up from 31% in 2015 acknowledge the role of central IT to set cloud policies.

As far as challenges, the survey found that one major concern of enterprise leaders (it even topped security in this year’s study) is having enough resources and knowledge on-hand to manage or carry out their cloud strategies. Leaders are also worried about budget but the article points to new tools and methodologies, such as DevOps, as possible answers to help them meet demand.

Overall the survey found that it is a hybrid cloud world out there, where organizations are looking for the “right” cloud to meet their needs.