A data center migration into the cloud is commonly a frightening enterprise initiative that may take years as you transition your present {hardware}, software program, networking, and operations right into a model new surroundings. In our roles with Google Cloud’s Skilled Providers group, we work facet by facet with prospects to collaboratively architect and allow information heart migrations into Google Cloud. Through the years, we’ve participated in a number of migration journeys, and devised a common strategy. Alongside the way in which, we’ve stumbled throughout numerous complexities and realized numerous classes. On this weblog submit, we offer a excessive stage overview of our beneficial information heart migration course of. Then, in future weblog posts, we’ll present a extra detailed view into the engineering and program administration migration elements of a migration. 

The migration journey

Each information heart migration has a purpose behind it—one thing like the will for price financial savings or to develop into extra cloud native. This leads to a enterprise goal resembling “migrate n information facilities to Google Cloud by this date.” No matter your motivation, the frequent problem is allow a profitable information heart migration whereas successfully managing danger. 

To assist, we’ve developed a repeatable migration strategy that consists of 4 phases: Discovery, Planning, Execution and Optimization. For many information heart migrations, leveraging this repeatable framework might help establish property, reduce danger utilizing a multi-phased migration strategy, allow deployment and configuration, and at last, optimize the top state. 

Part 1: Discovery

Step one of our migration strategy is the Discovery part. Right here we accomplice with a corporation’s information heart group to know and doc your entire information heart footprint. This contains understanding the prevailing {hardware} mapping, software program functions, storage layers (databases, file shares), working methods, networking configurations, safety necessities, fashions of operation (launch cadence, deploy, escalation administration, system upkeep, patching, virtualization, and so forth.), licensing and compliance necessities, in addition to different related property. 

On this part, our goal is to acquire an in depth view of all related property and assets of the present information heart footprint. These assets must also embrace a useful resource grouping classification, which might be leveraged within the following phases for dependency mapping and migration wave planning. For instance, whereas inventorying an information heart, it is best to establish the assorted working environments (non-production vs. manufacturing), dependencies (third-party software program, area controllers, and so forth.) and the enterprise influence of all functions, together with third-party methods which might be within the migration scope. 

The important thing milestones within the Discovery part are:

  • Making a “shared” information heart stock footprint – All groups which might be a part of the cloud migration ought to concentrate on the property and assets that may go reside.

  • Finishing an preliminary GCP foundations design – This includes figuring out centralized ideas of the GCP group resembling folder construction, Identification and Entry Administration mannequin, community administration mannequin, and extra.



Leave a Reply

Your email address will not be published. Required fields are marked *