How cloud migration helps control cloud spend

These best practices are designed to help you avoid issues that can drive up cloud costs. They are focused on the kinds of missteps I see most often in cloud migration projects. 

1. Identify infrastructure issues early

My most memorable example of an infrastructure issue was with a customer in Europe that wanted to migrate workloads to our data center in New York. They had planned out exactly how they wanted to get it done and by when. Unfortunately, they hadn’t considered the lack of connectivity and the slow internet speeds in their geography. They would have been transmitting data for months (well past their target go-live date) had we not intervened to suggest a better way.

2. Assess your skillset honestly

Since migrating workloads to the cloud has become easier, many business leaders just assume their in-house staff can manage the project. Maybe they can, but if they’re new to a platform or don’t have the bandwidth, augmenting internal resources with external expertise saves everyone from a lot of headaches.

Also read: How to Assemble Your Cloud Strategy Team 

3. Look at applications realistically

Is your ERP system really ready for a private cloud or public cloud services? Or does it need to be refactored or replaced to ensure data security, performance, and compatibility with platforms? Are you able to move to an Infrastructure as a Service (IaaS) or Software as a Service (SaaS) model? 

Migrating a monolithic, data-intensive, and mission-critical application like ERP is challenging enough. The last thing you need is to decide mid-migration that the application will create more problems in the cloud than it’s worth. This is especially a big concern for businesses using ERP for supply chain management. 

Also read: 5 Decisions to Make Before Moving to the Cloud 

4. Plan for the migration holistically

So, you’ve decided to leave one of your legacy applications on-premises while you migrate more cloud-ready applications. Make sure you understand the interdependencies between applications, so you don’t break any essential connections during the move. When we work with migration customers, we use a special tool to assess interdependencies and then group the migration project into phases to ensure nothing gets broken in the process.

5. Factor in the human element

One of the costs that I see underestimated time and time again is the human cost. Generally speaking, planning a cloud migration strategy is a big job that can last for months. Depending on their role, staff can find it challenging to do their “day job” while also working on the migration project. And, because the actual migration work is often done on nights and weekends, it may not be feasible for some to work the extra hours. 

6. Create a cloud governance framework

Ignoring your cloud resources can create all kinds of headaches – cost, performance, security, compliance, unplanned downtime, cloud sprawl, etc. A cloud governance framework covers the policies and practices you will use to ensure your cloud continues to meet your objectives.

Cloud Readiness Assessments augment cloud migration best practices

A well-planned migration project can help you control migration costs, as well as ongoing monthly costs. A Cloud Readiness Assessment is the first step. 

The readiness assessment can help you control costs in many ways. Here are just five: 

Uncover unforeseen obstacles

Easily the most dangerous obstacles in any migration project are the ones you don’t see ahead of time, and therefore, can’t plan for. These obstacles often require you to backtrack the migration, redo work already completed, and sometimes even start from scratch. The Cloud Readiness Assessment looks at people, business processes, and infrastructure to ensure that everything is in alignment. 

Align IT to the business

What are your cloud migration objectives? When we ask this question of IT and business leadership, we often get very different responses. This can lead to poor decision-making, not because those involved didn’t know what they were doing, but because they had different end goals in mind. Gaining alignment is a core goal of the Cloud Readiness Assessment.

Build a better business case

Our Cloud Readiness Assessments typically include a cost/benefit analysis to help you build the business case for your cloud strategy. A natural benefit of this data-driven analysis is an estimate of migration costs as well as monthly costs. 

Identify cost savings opportunities

During the Cloud Readiness Assessment, we’ll work with you to evaluate your cloud usage and validate your choice of cloud platforms. As part of the assessment, we’ll also help you identify specific cloud features, like edge computing, that can help with cost optimization.

Create cloud visibility

Visibility isn’t a cost savings benefit, but it can help you budget appropriately for each phase of the migration. Laying out the roadmap during the Cloud Readiness Assessment helps ensure everyone knows what to expect and when. 

We can help you with your cloud migration

Even if you plan to handle every aspect of your migration project in-house, it helps to work with managed services provider, like TierPoint. Because we’ve managed hundreds of migration projects, chances are good we will spot pitfalls your internal team can’t see. Learn more about Cloud Migration services. Not ready for a cloud assessment? If you’re looking for insight to help fine-tune or validate your cloud strategy, consider a complimentary cloud workshop. 

When is this happening? The end of Extended Support for Windows Server 2008 and R2 stops on January 14, 2020 and on July 19, 2019 for the 2008 versions of SQL Server. Without Extended Support, IT departments will no longer receive bug fixes, security updates or critical patches.

Fortunately, both Microsoft and TierPoint are offering help for IT departments that need to upgrade. Microsoft has information about migration options on its website, noted Dave McKenney, director of product management for TierPoint. In addition, TierPoint can help with consulting, migration support and managed Azure services.

McKenney–along with Allen Rogerson, Windows engineer for TierPoint, and Jacob Wilkins, database administrator—hosted an informational webinar, The End is Near! Preparing for SQL Server 2008 and Windows Server 2008 End of Life to help IT administrators understand their options. Following is some of the highlights from that session.

Windows Server New Features and Migration Options

There are many good reasons for migrating up to Windows Server 2016, including several useful and innovative new features. Three important ones are:

• Containers. Windows containers provide operating system level virtualization to enable Windows and Linux applications to be packaged with their libraries and dependencies, and then run on a single (Windows or Linux) without needing individual servers for each application. Developers use the open source Docker tools to create Windows containers.
• Host Guardian Service (HGS) and shielded VMS. The HGS provides confirmation and key protection to “shield” the Hyper-V VMs from tampering or unauthorized access.
• Windows Defender Credential protects login credentials against theft or malware by storing them in protected containers.

IT departments have three options for migrating off Windows Server 2008. Those are:

• Upgrade to an on-premises version of Windows Server 2016 or 2019. This is a straightforward option but is likely to require downtime to accomplish.
• Rehost workloads in Azure. Customers can begin migrating their 2008 workloads to Azure VMs and receive free Extended Security Updates for an additional three years.
• Upgrade first to 2012. Organizations that can’t afford any downtime to migrate to the on-premises 2016 can, instead, upgrade 2008 to 2012, then to 2016. There is no way to upgrade directly to 2016. Those on or migrating to 2012 are encouraged to continue the upgrade planning process as mainstream support for 2012 has ended and extended support will end in 2023.

Waiting to migrate and buy Extended Security Updates is another non-migration related option. The Extended Security Updates, available for three years, doesn’t provide bug fixes, compliance updates or any other new features or fixes – just basic security patches.

New Features and Migration Options for SQL Server/SQL Database

SQL Server 2017 and Azure SQL Database have several useful and innovative new features–including better diagnostics and administration, faster performance, advanced analytics and business intelligence, hybrid cloud features, data warehousing and OLTP performance improvements.

Five particularly important features target improved disaster recovery and security:

Always-on Availability Groups, introduced in 2012, is perhaps the most popular reason for migrating. Availability groups are a set of databases designed to fail over together. The feature offers database-level protection and high availability and disaster recovery, as well as offloading of read-only workloads from your primary replica to a secondary, conserving resources for mission critical workloads.

Always-on Failover Clustering, enabled by Windows Server Failover Clustering, is a SQL Server instance installed across nodes in a cluster with shared disk storage.

Always-on encryption keeps data safe as it moves to and from the Database Engine. Even the DBAs working with the data can’t see it if they’re not authorized to.

Row-level security provides greater granularity by allowing data owners to restrict visibility of entire rows based on the user and query. For example, an unauthorized user in marketing querying an employee database for possible charity volunteers won’t be shown a row of employee social security numbers.

Data masking obfuscates data by replacing it with equivalent but fake data for non-authorized users. Data masking allows developers, application testers and others to use the data without seeing the actual information.

SQL Server migration options

IT departments have three options for moving up from SQL Server 2008 and R2:

• In-place upgrade. You can choose to move up to SQL Server 2012, 2014, 2016 or 2017. However, SQL Server 2012 is already off mainstream support and 2014 goes off it this coming July. Because upgrading is a time-consuming project, it’s best to move to the latest version available to increase the time before the next upgrade. The downsides are downtime and a more complicated rollback should that be necessary.
• Side-by-side migration. This option helps minimize downtime and allows for testing in the new environment pre-migration. Rollbacks are easier too. However, it does require additional hardware.
• Move to Azure. As with Windows Server, you can migrate to Azure SQL Database Managed Instance. Managed Instance is a new version of the original Azure SQL Database that is nearly equivalent to on-premises SQL Server. Hence, if you need instance-level features in SQL, this is the better version.

Regardless of which path you choose; expert assistance can make the move go more smoothly. As a managed Azure services and colocation provider,  TierPoint has the infrastructure and expertise to help you plan and execute a migration or upgrade quickly and with minimal downtime.