1. Home
  2. Training Library
  3. Cloud Migration
  4. Courses
  5. Cloud Migration Strategy Considerations

Business Continuity in Cloud Environment

play-arrow
Start course
Overview
DifficultyBeginner
Duration1h
Students2859
Ratings
4.7/5
star star star star star-half

Description

Cloud Migration services from your on-premise environment can sometimes be very simple and other times an extremely complicated project to implement. For either scenario there are always considerations to bear in mind when doing so. This course has been designed to highlight these topics to help you ask the right questions to aid in a successful Cloud migration.

Within this course we look at how timing plays an important part of your projects success and why phased deployments are important.

Security is also examined where we focus on a number of key questions that you should have answers to from a business perspective before your Cloud migration.

One of the biggest decisions is your chosen public cloud vendor, how do you make the decision between the available vendors, what should you look for when selecting you will host your architecture, this course dives into this question to help you finalize your choice.

Understanding the correct deployment model is essential, it affects how you architect your environment and each provides different benefits, so gaining the knowledge. I look at how you can break this question down to help you with your design considerations.

We also cover service readiness from your on-premise environment and how to align these to the relevant Cloud services.

Your design will certainly be different from your on-premise solution, I discuss the best approach when you start to think about your solution design, some of the do’s and some of the don’ts.

Once you have your design, it’s important to understand how you are actually going to migrate your services ensuring optimum availability and minimal interruption to your customer base, for example looking at Blue/Green and Canary deployments.

Cloud migration allows for some great advantages within your business continuity plans, as a result, I have included a lecture to discuss various models that work great within the Cloud.

Course Objectives

By completing this course you will:

Have a greater visibility of some of the key points of a Cloud Migration
Be able to confidently assess the requirements for your migration

This course has been designed for the following audience

Business Management
Business Strategy
Technical Management
Technical Operations

Pre-requisites

For this course it's assumed that you have a working knowledge of Cloud Computing and Cloud principles

This course includes

• Over 59 minutes of high-definition video

• 13 lectures

 

What You Will Learn about Cloud Migration

Introduction - This provides an introduction to the trainer and covers the intended audience. We will also look at what lectures are included in the course, and what you will gain as a student from attending the course.

Time Management – How time plays an important part of a successful cloud migration. We discuss the key points to allow time for and how to use it to plan a phased migration

Security – This lecture will give you the ability to ask the key security questions to the business before performing a migration to the Cloud.

Selecting a Vendor – Here you will learn how to define the best way to assess which vendor would be a good fit for your migration based on a number of considerations

Selecting a Cloud Deployment Model – This discusses different Cloud deployment models where you will understand the differences between them before gaining insight to the questions you should be asking before making a decision as to which to select

Are your services ready to move to the Cloud? – This lecture will help provide you with the ability to identify if your on-premise applications and services are ready to migrate to the Cloud. There are a number of issues that could arise which we dive into

Alignment of Services – Here we learn how to categorize your current services and how to map them across to the Cloud service

New Design – This lecture discusses the importance of not performing a ‘lift and shift’ from on-premise into the Cloud. We look at how this design should be addressed using high availability and other Cloud characteristics

Migration and Deployment options – Here you will learn the differences between the different deployment methods that could be used and how to tackle the questions around migrating your data into the Cloud to start with

Optimization and Cost Management – Here we look at some of the considerations around optimization of your costs and how you can achieve greater efficiency

Business Continuity – The Cloud offers a number of different DR methods which are discussed here and you will be able to define the differences between these and when to you one method over the other

Proof of Concept – In this lecture you will learn the importance of implementing a proof of concept design before your production migration

Summary - Lastly, we will take note of some of the important factors learnt from the previous lectures.

If you have thoughts or suggestions for this course, please contact Cloud Academy at support@cloudacademy.com.

Transcript

Hello, and welcome to this lecture covering your business continuity in the cloud.

One aspect of your migration strategy should include the changes this makes to any business continuity or disaster recovery plans your organization has. The cloud provides a great platform of building resiliency into your business, which can greatly enhance your recovery plans when it comes to a disaster striking in whatever form that may be. This could be anything from a severe earthquake, potentially taking out entire data centers within a geographic region, to a subset of critical systems becoming unavailable due to a configuration change by human error. Whatever the reason and how you cast a service interruption as a disaster is down to you. However, what is essential is that you have a set of policies and procedures that dictate how to recover from such instances.

Prior to cloud adoption, you would likely have this set of procedures defined, utilizing off-site premises with capacity to implement and run your key production systems, utilizing back-ups to bring your services and business back to an operational state as soon as possible, with as little data loss as feasibly possible. Now with the adoption of the cloud, should a natural disaster occur and your premises become unusable, you will obviously still need new premises for your employees. However the services hosted within the cloud will be unaffected. Should the disaster occur in the cloud vendor's data center, then you'll experience problems unless you have configured high availability within your environment to handle such an event.

The cloud allows you to deploy applications and services in a highly available and resilient way. Any critical system should be architected with failure in mind, allowing it to continue to function should a major outage occur. One of the best ways to do this is by utilizing multiple geographic locations to run the systems. You're trying to ensure it continues to run even if a complete data center within the vendor is made unavailable.

Some of the vendors offer whitepapers on the best way to achieve DR within their cloud, and the following points and methods are detailed in the AWS DR whitepaper, which can be found here. The models and best practices discussed to help with business continuity, are backup and restore, pilot light, warm standby, and multi-site. Each of these models offer a different RTO, recovery time objective, and RPO, recovery point objective.

Before we go on, I just want to explain what each of these are for those unaware.

RTO is defined as the maximum amount of time in which a service can remain unavailable for before it's classed as damaging to the business. For example, if your RTO for a service was two hours, and your outage occurred at 2:00 in the afternoon, then your service must be back up and running by 4:00 in the afternoon, before unacceptable damage to the business was experienced.

RPO is defined as the maximum amount of time for which data could be lost for a service. For example, if you had an RPO of eight hours, and you had an outage at 9:00 p.m., and then resumed your service at 10:00 p.m., you would have to ensure your restore of data was from a backup from 1:00 p.m. or later that day.

OK, so now I want to give you a high-level overview of the different continuity models, starting with backup and restore.

If you're using the cloud to store backups of your on-premise architecture to a highly durable and cost-effective storage solution, then this allows for a rapid access to your backups should a disaster occur. As long as you have an Internet connection, you have the means and ability to perform and restore to any location. However, this is only dependent on the speed of your Internet connection, or any other direct connection that you may have, so bear this in mind. Some providers offer solutions to transport huge datasets physically from the cloud to your data center's door. For example, AWS Import/Export Snowball service. You could also simply restore your backups to some provisioned instances that you may wish to spin up in the cloud to help speed up the recovery process.

OK, the next model is the pilot light method. This essentially requires you to have the minimum number of computing database instances required to operate your core services running separately to your production environment. This core set of services would then be replicating data from your production environment, ensuring that the core data is up to date should it ever be required. If a disaster did occur, then this core would then quickly be able to resume the core services whilst you spent time scaling out to support the demands of the rest of your environment, without taking a huge amount of time to restore data.

The warm standby is an extension of the pilot light method. But it's a fully functional system with an increased fleet size compared to that of the pilot light, therefore reducing your RTO. You could even use this warm standby as a testing environment if need be. Again, should a failure occur, this smaller version of your production environment could take the load in services, and then scale up to the full demand of your production environment very quickly.

Lastly, multi-site. Multi-site is exactly that, whereby you use the cloud to re-create either your on-premise services within the cloud, replicating data between on-premise and the cloud, or replicating your existing cloud architecture to another region within the cloud. All elements of your infrastructure should be completely replicated to allow a disaster to happen to your on-site infrastructure, but then taken over by those within the cloud. This offers the quickest RTO and RPO from the four methods discussed.

This takes us to the end of this lecture. Coming up next we take a look at why a proof of concept should be considered.

About the Author

Students56270
Labs1
Courses55
Learning paths38

Stuart has been working within the IT industry for two decades covering a huge range of topic areas and technologies, from data centre and network infrastructure design, to cloud architecture and implementation.

To date, Stuart has created 50+ courses relating to Cloud, most within the AWS category with a heavy focus on security and compliance

He is AWS certified and accredited in addition to being a published author covering topics across the AWS landscape.

In January 2016 Stuart was awarded ‘Expert of the Year Award 2015’ from Experts Exchange for his knowledge share within cloud services to the community.

Stuart enjoys writing about cloud technologies and you will find many of his articles within our blog pages.