Cloud Migration

Cloud migration is the process of moving workloads, data and related services to a cloud platform, either from on-premises hardware or from another cloud. Common strategies range from moving a server unchanged to rebuilding an application to use cloud-native services.

Why it matters

Migration projects often cause outages because of overlooked dependencies, DNS timing, data synchronization or hidden hardcoded addresses. Planning typically includes an inventory of systems and dependencies, a choice of strategy per workload, a test migration, a cutover plan and a rollback path. Costs and performance should be measured before and after, since a migrated application may behave differently when its database or services end up in a different network.

Example

1. Inventory servers, databases, DNS names, certificates
2. Lower DNS TTL a few days ahead
3. Replicate data to the new environment
4. Test using a hosts-file entry or staging URL
5. Cut over, monitor, keep old environment for rollback

Common mistakes

• Cutting over without a rehearsed rollback.
• Forgetting email, cron jobs, certificates or IP allowlists tied to the old server.
• Moving a database away from its application and creating high latency.
• Skipping monitoring during the changeover.

Related

• Lift and shift
• TTL
• Database migration
• गाइड: Migrate a website without downtime

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.