Cloud migrations have cratered seemingly well-planned projects. The issue is universal; visibility and understanding of the holistic environment, dependencies and the quantification of risk. Setting expectations for migrating services and applications today, without proper and comprehensive visibility, is a gamble at best. The result is a failed Cloud migration journey that has ramifications past just the time spent and cost.
Cloud Migration comes with tremendous reward, and risk. The probability is high that there will be critical business service interruption, data loss, financial loss and reputational loss. The reward is the potential for dramatic costs savings, but a lack of dependency and configuration knowledge causes most organizations to end up spending more and more until cloud costs eclipse budgets. AWS, Azure and most Cloud providers have done a great job on provisioning…once you get there. The key question every business leader asks is…” how do I successfully migrate more and more complex enterprise applications quicker so I can take advantage of all the benefits sooner?”
At FireScope, we understand the challenges and our view is different on how an enterprise should build a cloud migration protocol. Technology and process are key. On the technology front, strong tools are needed to discover ‘all” application and ‘all’ configuration items – and, they must transverse “all” the virtual, physical and cloud environments simultaneously. Gaining visibility into “all” the dependencies between these items is key; including the complexities behind load balancers, databases, storage, etc., and not just the servers. Otherwise, what type of visibility do you really have? Once your dependencies are understood, you most likely will need to adjust, segment and update the service components (i.e. decommission underserved servers, reclaim VMs, etc.) to gain the cost savings as well as improve your risk level. Your chosen migration tool should also analyze and rank the migration risk by service, so you can have the confidence to execute your game plan; and be easy to install and use.
Bottom line…a FireScope Cloud Migration protocol in just 10 steps:
1. Get immediate and comprehensive visibility into complex environments (advanced discovery);
2. Understand the relationships (dependency);
3. Visually map and understand those dependencies and the environment (mapping);
4. Rank the present risk of migrating that service and migrate low risk services for a quick win (analysis engine)
5. Adjust dependencies and eliminate unused/unneeded resources (mapping);
6. Rank the risk again and approve migration based on acceptable risk level (analysis engine);
7. Output the approved service migration source data (reports/data files/outputs);
8. Migrate the app/service;
9. Map the service and all its dependencies again at its new location, validate and operate; and
10. “Rinse and Repeat” until your migrations are complete.
Rule #11. Keep the tool and all the data maps and dependencies for easy, future adjustments and business continuity/disaster recovery requirements; and, make sure the tool alerts you to any changes or adjustments to any of the services on a real-time, ongoing basis.
FireScope has thought this through and worked with clients on cloud migration. FireScope Cloud Advisor provides immediate visibility into complex virtual, physical and cloud infrastructure to automatically discover and map how your IT assets work together and ranks the risk for each business service for cloud and datacenter migrations. We are launching a ‘sneak-peak’ of our new product offering for a few VIPs with a short and informative webinar/demonstration on August 24, 2017 at 1pm CST. Look forward to seeing you or your associates there!
Please Register Here