When the company's business migration between cloud platforms, and planning processes are more important than products and technologies, at least in the short term.
Most enterprise cloud computing strategy has gone beyond the simple choice between on-premise and public cloud deployments. Instead, companies are increasingly seeking cloudy method, in which an application can move between cloud platform, or even as a combination of systems and services reside on different cloud platforms. This is an ambitious goal, many organizations have not yet been fully realized. In contrast, so far, many companies main concern is to simplify migration between cloud platform, processes and technology.
Before the service migration from one platform to another cloud cloud platform program, some common understanding of project management and planning considerations are very important, these considerations apply to any situation. The following strategies can help you build and implement seven key steps to migrate:
1. Determine your goals
Cloud platform motivation varies across organizations. Some companies seeking to create a more powerful distributed disaster recovery (DR) and business continuity environment, while other companies are looking for software development and test infrastructure. Specific program objectives and cloud computing will affect the migration of content, manner, time.
2. Assess your environment
Assess applications and data assets is essential. Assessment typically involves the use of automated software to discover and inventory applications and data, and associated system configuration and license. It also needs to find connections and dependencies between applications and data sources. As a result of the migration to cloud platform tactical plans.
3. The identification and preparation of data and applications
Data and metadata capture and preparation will be an important part of the pre-migration process. Its tasks include capturing infrastructure configuration details, such as the network addressing, CPU Specifications, memory, storage. Data preparation requires the user to create a snapshot of a virtual machine or container volumes and images, and is ready to replicate the work of any database.
4. Perform the migration
Enterprises can copy the data in various ways to the cloud computing environment, for example through a direct connection or network transmission VPN, and bulk transfer by a removable hard disk. Other options include packaged software and services designed to automatically create a disaster recovery environment for a particular infrastructure (such as VMware).
5. Configure the target cloud infrastructure
This is a heavy task of initiatives. Cloud computing infrastructure and services to host the migration of enterprise applications and data needed to create. This may include setting a virtual machine, storage volumes, networks, databases, load balancers, access management.
6. test and we optimize new environment
Before organizing the work load in production must be carried out under various load and stress conditions on the new cloud computing environment to fully test and optimize it to provide acceptable performance. Testing should also include a variety of fault conditions, to determine the efficacy and redundant system resources (if any).
7. The workload switching to the new environment
The final step is the company's work load switching and migration to the new platform. And any migration events, this migration is best in non-working hours and low demand time to complete, because there may be some downtime. Usually you need to re-adjust the data to the database since the capture self-replication process to add.
Migration Scenarios
Today, cloud migration and cloud computing users scenes as much. However, these are among the most common method to migrate cloud platform:
Re-hosting / re-replacement: This method is also known to enhance and transfer typically involves the application to migrate from on-premise cloud platform. Re-replace mode cloud platform, cloud-based computing services to replace the services, such as database or container cluster management system, which requires some slight modifications compared with the re-hosting.
Repurchase: when to migrate to another cloud service platform, the company can repurchase of goods, or direct shopping. They provide goods and services with a self-management system (such as e-mail and ERP systems) to replace an equivalent SaaS product.
Reconstruct and rebuild: This may be the same as before moving to a managed container services to package the application into the container, it may cloud the surrounding native service, containers and redesign the application server functions as comprehensive.
Retention or exit: goal setting and evaluation stage led to the recognition of certain obsolete IT systems in function, underutilized or not to migrate.
Agnostic and hybrid cloud infrastructure stack
Sometimes, re-construction method will lead a strategic review of its business infrastructure. Often, companies need a little need to modify the software stack, and can be deployed across multiple cloud platforms. Several major IT vendors for this increasingly common goal of providing basic products and services for mixed enterprise environments or cloudy. Some of the most important include: Microsoft Azure Stack, Google Cloud Anthos, AWS Outposts and container-based cloudy PaaS, such as Cloud Foundry or Red Hat OpenShift.
Cloudy challenges and constraints
The migration of applications from on-premise cloud computing providers into a single cloud platform can unlock a world of high-value services, migration (whether due to fear or locking desire for high availability) between cloud platforms need to be more cautious. Migration between cloud platforms need to address the most basic infrastructure services, and the expense of cloud-specific features, or it means a different form of locking - that is, such as VMware Cloud Foundry or cloudy stack.
Dalian Which gynecological hospital good mobile.0411fk.com