For many organizations, global expansion necessitates the reach that only the cloud can provide. And if your business is heavily invested in Microsoft applications, you’re likely to closely evaluate Microsoft Azure as a cloud option. Our new white paper, “Effective Azure Migration, Moving Applications to the Cloud” shows how one large property and casualty insurance provider moved from an on-premises data center to the Azure cloud.
There’s a debate raging in IT about what steps established organizations should take to move their older traditional applications to the cloud. On one side of the argument you have a contingent of IT professionals already reaping the benefits of cloud computing. They assert that the future of IT is in the cloud—that companies need to get on board by moving their apps to the cloud now. On the other side you have old-school IT folks with an “if it ain’t broke, don’t fix it” mentality. They rightly point out that these traditional apps are often the backbone of a company’s business and argue that running them on dedicated infrastructure seems to be working just fine. So why tinker with a good thing?
I spend a considerable amount of time in front of customers and prospects. Over the last few months, I’ve gotten a lot of questions about hybrid cloud. What’s the right approach? How long does migration take? What needs to be done in preparation? What benefits can our organization expect to receive? After fielding these questions across the country for lots of different size companies in a variety of industries, I thought it might be valuable to share some answers.
Are you still clinging to your trusty old server that’s gracefully aging towards obsolescence? Perhaps you are still running important applications on older servers with old operating systems because they’re “good enough” and still “work fine.” In many respects, your old server is like a trusty old car. You know where the kinks are and it gets you where you need to go. But lurking below the surface of that trusty old car, and your old server, can be hidden risks that can result in very big problems, even dangers, usually when least expected.
So you’ve made up your mind that you’re going to move workloads onto a service provider’s infrastructure. Now you’re faced with a big question: should I rebuild my environment while migrating to avoid more disruption later? Here are eight pros and a few cons to consider when making your decision.
Most system administrators are not only concerned with improving IT capabilities, but also how to best transition to a new environment. “How do I get my app, website, database or development environment onto a new infrastructure, with the least amount of hassle?”
In my position as a Launch Manager on our Cloud Launch Team, I speak everyday with customers who are bringing an application over to Rackspace from another hosting provider. Whether it’s a WordPress blog, a Magento eCommerce site, or a custom-built mobile app, my fellow Launch Managers and I work with our customers to provide a smooth transition from one provider to another. Today, I’ll outline five questions you should ask before starting a migration to Rackspace (or any other hosting provider). I will also be hanging out at 1 p.m. CDT Thursday, April 24 with other Rackers to discuss these questions in more detail. Join us on Google+ to Hangout, or watch the embedded video below.