This is the second in a multi-part series. Follow the series here.
Migration might seem to be a strange term when it comes to leveraging the public cloud, but most companies already have applications running either on-premises or in hosted data centers. There are a number of immediate benefits if those apps are migrated to a public cloud:
• There’s little to no re-coding involved
• User access to those applications or workloads will remain similar or the same
• The cloud is more flexible, resilient, and less expensive to use than hosted or on-premises servers
Because of this, the migration of existing workloads is how most companies begin their cloud journey.
So how do you prepare to migrate workloads? The first step is obviously to identify any and all workloads that are candidates for migration. If this sounds like a daunting task, it isn’t. First of all, existing virtualized applications are likely candidates, as are any hosted web-facing applications, including internal resources like SharePoint.
We have seen a variety of tools from partners and third parties to automate a lot of this preparation process. For example, one of our partners, Airnet Group, has a tool that will automatically interrogate a network and actually prepare a cost estimate of what a customer can save by migrating various workloads. There are network evaluation tools from third parties that will collect usage data and help determine how easy or difficult it will be to migrate a workload. And finally there are partners with deep expertise in the area of cloud engagements who can help identify what, how, and when workloads can be effectively migrated to the cloud.
This first step isn’t as much strategy as it is inventory: what have you got running, what are the best first candidates for migration, and what are the requirements.
With larger companies, we’ve often found that cloud deployments occur as part of a new effort: a data center consolidation at a financial services provider, a new patient-facing application for a healthcare provider, or an acquisition at a multi-national manufacturer – all are examples of projects where public cloud became a key element. In this case, preparation is less company-inclusive but more project exclusive; and the steps still remain relatively the same.
In our next blog, we’ll look at strategy, which is the next step in a successful cloud transition.
If you would like more information on how Barracuda can help you migrate to the public cloud, visit us on the web here:
Rich est directeur marketing pour les produits de cloud public chez Barracuda. Il a rejoint l'équipe dans le cadre de l'acquisition de C2C Systems en 2014. Rich est l'un des experts du cloud public de Barracuda. Il travaille directement sur les écosystèmes cloud et est cité dans des ebooks de Microsoft sur la sécurisation du cloud public. Il est également contributeur régulier des blogs thématiques sur le cloud de Barracuda. Dans le cadre de notre travail sur le cloud, il aide au développement de stratégies et à leur exécution avec nos partenaires et nos équipes commerciales.
Vous pouvez contacter Rich par e-mail à l'adresse firstname.lastname@example.org.